Working with golive checklists
Create a golive checklist to automatically track items that must be reviewed before publishing the automation request. Every golive checklist is associated with an automation request.
This section has the following subsections:
A checklist template is provided with the product. Here are the details.
| Task name | Task description |
|---|---|
| Business/Validation Sign-off | Confirm that the automation meets all business requirements and acceptance criteria. This involves a formal sign-off from the business owner or process SME, ensuring that the automation behaves as expected in staging/sub-production environments. |
| Development Sign-off | The development team must confirm that all development tasks are complete, including code review, peer review \(if applicable\), and all technical requirements have been implemented. The developer also ensures that environment-specific variables and hard-coded test values have been removed or appropriately managed through config files. |
| Testing/QE Sign-off | QA must validate that functional, regression, and negative testing is complete in sub-production \(UAT or staging\). A formal sign-off document or ticket must be attached to indicate readiness. Include validation of edge cases and exception scenarios, especially for business-critical automations. |
| Production Configuration Pre-check | Ensure that all required configuration elements are in place in the production environment:- Application URLs, credentials, and API endpoints are updated - Schedules, triggers, or event rules are properly set - Environment variables, secrets, and certificates are configured correctly |
| Monitoring, Logging & Alerting Setup in Production | Validate that all operational monitoring hooks are active in production:- Logging destinations \(log servers, dashboards\) are correctly pointed - Alerts \(email/SMS/Slack/etc.\) are routed to the correct stakeholders - Health checks are enabled, and baseline performance is captured for comparison |
| Automation Enablement & Final Readiness Review | A final checklist is completed jointly by Dev, QA, CoE, and Business SMEs. This includes:- Setting the automation to “active/live” in production - Verifying all preconditions \(input data, triggers, service availability\) - Communicating go-live to impacted teams. This serves as the “green signal” to activate the automation in the production environment. |
- Create a checklist
Create a checklist to track the items for an automation request. A checklist is a list of tasks that you must track before publishing an automation request. - Edit a task
Edit a task if you want to update the checklist. - Clear a checklist
Clear a checklist if you no longer need the checklist for your automation request. - Create a template
Create a template when you think a golive checklist is useful for multiple automation requests. - Update a template
Update your template if you have changed the checklist and want those changes to reflect in your template. - Update task status
Update the status of a task so that it’s the latest and helps in the publishing of the automation request.
Parent Topic:Working with automations