Definitions and ownership

The Automation Owner records the automation’s name and number, organization, owner, connector, trigger type and revision. These details identify the work that validation and later execution will use. A definition belongs to a specific organization, so the team can tell which operating context applies when the same kind of automation is used in different parts of a business.

A revision matters because a review decision and a run must refer to the version actually examined. Before asking for validation, the owner checks the input schema and retry policy alongside the connector. The definition’s status tells the team whether it is a draft, validated, approved, active or retired. Its latest execution result is a working summary; the run and step records carry the detailed trace.

• Ownership. Each definition has a named person responsible for preparing changes and following their results.
• Revision. Keep the version and revision visible when sending a definition for review or tracing an execution.
• Connector. Link the definition to the connection it uses, then review that connection’s organization and active period.

Agree who can create a draft, who reviews a validated revision and who starts a run. Decide how the team names source records and operation keys so a retry can be recognized. Confirm the organization boundary for each connector and the policy reference the Integration Steward will maintain. Choose which changes require a new revision instead of an edit to an existing one.

For a pilot, select one automation with a known source record and a result your team can check. Capture a draft revision and review it before running the process. If a connector or schema changes during the pilot, record the new version so later evidence still points to the earlier input.

Suppose an operations team processes a service request from an outside system. The Automation Owner selects the connector for the definition. The Reviewer looks at the exact revision and the validation trace before making a decision. The Operations Operator then starts a durable run for that reviewed version and records the source identifier with the execution. The resulting run points back to the definition, so the team can distinguish the approved instructions from the result of carrying them out.

If the owner changes the retry policy after review, treat the change as a new revision requiring its own validation and decision. The prior run remains tied to its original revision. This keeps a correction from rewriting the circumstances of an earlier result.

• Definitions by status — Find the current work by state, organization and owner.
• My definitions — Follow the revisions and results assigned to you.
• Definition status board — Compare drafts, reviewed work and retired definitions without mixing in run dates.

See validation and review and durable execution for the next decisions.