orchestrator
2023.4
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Managing your host license
- Configuring system email notifications
- Audit logs for the host portal
- Maintenance Mode
- Organization administration
- Troubleshooting
Creating a Queue Trigger
Orchestrator User Guide
Last updated Oct 9, 2024
Creating a Queue Trigger
Note: Queue triggers and SLA predictions are interdependent in terms of queue-process association. So whenever configuring one,
the other is prefilled such as to have parity between the configurations. Say I define a queue trigger for queue Y to use
process X. SLA predictions for queue Y can only be made using process X, therefore X is prefilled and read-only when enabling
queue SLA for Y.
Important: For processes containing queue trigger activities, you need to create and edit the corresponding queue triggers only from
the Package requirements page, at process creation time. Manually created triggers (that is, from the Triggers page) won't be recognized by the queue trigger activity in the workflow.