action-center
2020.10
false
- Release Notes
- Getting Started
- Installation and upgrade
- Activities
- Designing long-running workflows
- Start Job And Get Reference
- Wait for Job and Resume
- Add Queue Item And Get Reference
- Wait For Queue Item And Resume
- Create Form Task
- Wait for Form Task and Resume
- Resume After Delay
- Assign Tasks
- Create External Task
- Wait For External Task and Resume
- Complete Task
- Forward Task
- Get Form Tasks
- Get Task Data
- Add Task Comment
- Update Task Labels
- Actions
- Processes
OUT OF SUPPORT
Action Center
Last updated May 21, 2024
Single node Action Center connected to a single node Orchestrator instance.
- 3 hours of test time
- Form Data payload having a size of 5000 bytes.
- 28K Actions created.
- Executed 17 different API endpoints.
- Simulated concurrent users.
Action Center can scale to a high number of concurrent users if the connected Orchestrator can handle load w.r.t unattended Robots and Database as per the requirements documented here.
The following recommendations are based on an in-house load test with the above-mentioned sample data in a sandboxed environment.
Customers need to derive hardware size based on their business requirement (average payload size, load expected, concurrent users, etc).
- Up to 4K users [2 CPU @min 2.0 GHz, 4 GB RAM]
- Up to 12k users [4 CPU @ min 2.0 GHz, 4 GB RAM]