These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- RPA Task Manager
- Process
- Define and schedule a bot
Define and schedule a bot
A scheduled bot needs a known organization, queue, owner, date and revision. The Automation Operator prepares those details before invoking the scheduling workflow. The resulting operation trace and pending review decision make the scheduled revision visible to the next person.
Step by step
-
Establish the queue Queue Administrator
Queue Administrator checks the operating organization, queue policy reference and effective dates. Review the source mapping when the bot reads or writes external fields.
- Identifies the applicable operating policy and mapping
- Updates Organizations, Automation queues, Source mappings
-
Define the bot Automation Operator
Automation Operator records the definition number, name, owner, scheduled date and queue.
- Names the owner, queue and scheduled date
- Updates Bot definitions, People
-
Validate the revision Automation Operator
Automation Operator confirms the intended source record, runtime version and revision before changing the definition from Draft to Validated.
- Identifies the version ready for scheduling
- Updates Bot definitions
-
Schedule the bot Automation Operator
The scheduling workflow records the durable schedule run and step trace, marks the definition Scheduled, raises a pending review decision and appends state history.
- Persists the schedule trace and pending decision
- Updates Bot definitions, Operation runs, Operation steps, Review decisions, State history
Who does what
Roles and permissions- Queue Administrator
- Maintains queue context; Automation Operator owns the definition and schedule; Bot Reviewer receives the pending decision; Admin manages access.
Set up RPA Task Manager your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.