ClearLine Technology Methods
SENAITE / Bika Recovery Risk Checklist
Use this when an inherited SENAITE or Bika environment still matters to production, but support, backups, reports, hosting, or upgrade paths are unclear.
Safety rule: do not make blind production changes. Review access, backups, customizations, reports, and rollback options before touching production.
Access and ownership
- Who has administrative access?
- Are accounts named, current, and owned by the lab?
- Is there an emergency access path?
- Are credentials stored safely outside one person’s memory?
Backups and restore
- Where are backups stored?
- How often are they created?
- Has restore been tested?
- Is there a rollback point before report/workflow changes?
Custom reports, labels, and exports
- Which COAs, labels, COCs, worksheets, and exports are custom?
- Where does each template live?
- What client or method logic affects output?
- Which changes would break client deliverables?
Hosting and runtime
- What server/container runs the system?
- What versions of Python, Plone, SENAITE/Bika, and add-ons are involved?
- Who can restart safely?
- Where are logs and runbooks?
Recovery decision
- Stabilize current system if production risk is high.
- Repair reports/documents if client deliverables are the pain.
- Plan upgrade/migration only after current state is documented.
- Move to managed support only after CTM accepts operational responsibility.