Queue and organization setup

The Queue Administrator starts with the organization that owns the work. The organization name and code keep queues and bot definitions associated with the right operating unit. Its time zone matters when the team agrees what a scheduled date means. The administrator then creates an automation queue with its own name, code, effective dates and policy reference. A queue gives each bot definition an explicit place to run.

Source mappings describe how a source field relates to a target field in a queue. Record the types, transformation rule, version and effective date so that a mapping can be reviewed as the source system changes. These records support the setup decision; an Automation Operator should know which queue and mapping govern a definition before scheduling its revision.

• Organization. Keep the operating unit and its active state visible to the team responsible for the bots.
• Queue policy. Use a policy reference and effective dates to identify the queue terms in force for a planned run.
• Mapping. Document each field translation and its version beside the queue that uses it.

Choose who can maintain organizations, queues and mappings, and who checks a revised mapping before operators use it. Agree how the organization time zone is applied to scheduled dates and how effective dates are compared. Decide how to retire a queue while preserving definitions that already used it. The queue code should stay stable for external references; a change to policy should have an identifiable reference.

For example, a finance operations team may schedule a reconciliation bot against a queue for its organization. The administrator records the policy reference and the field mapping for the source transaction identifier. The Automation Operator selects that queue on the bot definition. When the source field changes, the administrator records a new mapping version and effective date, then asks the reviewer to examine the affected revision before it runs.

Open a definition planned for the next operating day. Confirm that its organization is active, its queue belongs to that organization and the policy is effective for the planned date. Read the mapping from the source field through the transform rule to the target field. The owner should be able to explain which revision will use that mapping. If the policy reference changes, keep the previous definition history readable rather than rewriting an earlier run.

• Queue policy register — Queue records with policy references, effective dates and operating organizations.
• Scheduled bot definitions — Definitions ready for scheduling or already placed on a queue.

See Define and schedule a bot for the first operating cycle and Review a revision for the independent decision.