orchestrator
2022.4
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Classic Robots
- Troubleshooting
Test Data Queues
Orchestrator User Guide
Last updated Oct 17, 2024
Test Data Queues
Test data queues provide a way to store and manage your test data. The test data queue acts as a container that holds your queue items ready to be consumed through a set of activities. The queue items are uploaded or removed from the test data queue according to a first-in-first-out (FIFO) principle.
As an example of taking advantage of the test data queues, you can fill up your customer database with records or just prepare your test data by storing it in a queue, for consumption.