Move through states

Guides you through advancing your automation request from creation to publication, including options to defer or reject requests that no longer meet your criteria.

The automation request lifecycle consists of:

• Draft — Initial creation
• Planned — Ready for development work
• In progress — Active development underway
• Published — Ready for execution
• Deferred — Paused temporarily
• Rejected — No longer being pursued

In this section, you will:

• Move an automation request to the planned state
• Move an automation request to the In progress state
• Defer an automation request
• Reject an automation request
• Publish an automation request

• Move an automation request to the planned state
  After creating an automation request, move it to the Planned state before you work on it or create associated automation tasks or resources.
• Move an automation request to the In progress state
  As you begin the development for the automation request, move it to the In progress state. This state notifies anyone using Automation Center that the work for the automation is in progress.
• Defer an automation request
  Defer an automation request from Automation Center if the priority of the request has changed and it is not urgent anymore.
• Reject an automation request
  Reject an automation request from Automation Center if it's a duplicate of an existing automation or if it doesn’t meet the required criteria.
• Publish an automation request
  Publish an automation request from Automation Center to make the request ready for execution.