Queue-Based Scheduler for Robility Flow
The Queue-Based Scheduler enables scheduling of published Robility Flows for execution using queue-based triggers. Workflows are automatically initiated when items are available in the selected queue from Interact, supporting continuous and event-driven processing. The scheduler checks the configured Interact queue for new transactions every one minute and initiates the workflow accordingly.
Pre-requisites
1. A queue must be configured in Interact before you can set up a Queue-Based Scheduler.
2. Publish the queue to the manager from Robility Flow. Ensure the “Enable External Flow” option is enabled while publishing, if not enabled, the published flow will not appear in the Workflow Name dropdown when configuring the Queue-Based Scheduler.
Configuration Fields
1. Queue*: Select the Interact queue to associate with this scheduler trigger. The scheduler monitors this queue and initiates workflow execution based on incoming items.
2. Flow Type*: Defines the type of workflow to be executed. This must be set to Robility Flow for queue-based scheduling.
3. Workflow Name*: Displays a list of published queue workflows. Select the workflow that should be executed.
4. Timezone: Specifies the timezone for the scheduler to ensure trigger execution aligns with the selected regional time settings.
5. Non-Working Days: Upload an .xlsx or .xls file containing dates on which the trigger should not execute. A predefined template is available under the Non-Working Days Template option, and the uploaded file must follow the required format.
6. Save: After configuring all required fields, save the scheduler configuration to activate the queue-based trigger and enable automated workflow execution based on queue activity.
Scheduler Trigger Behavior
When Does the Scheduler Trigger?
The scheduler triggers each time a new item is detected in the monitored Interact queue and is available for processing.
Business Rules and Queue Transitions
When a business rule is configured in the scheduled queue, the business rule is evaluated first. If the rule moves the transaction to another queue, the Queue-Based Scheduler on the source queue will not be triggered.
For example, if Sample 1 has a business rule that moves any incoming transaction to Sample 2, and a Queue-Based Scheduler is configured on Sample 1, the scheduler will not be triggered. The business rule is completed first, moving the transaction out of Sample 1.
