Page Comparison

The Queue Management feature in Adeptia Connect allows you to manage and regulate the execution of Transactions, Templates, and Process Flows. You can create a dedicated queue for the execution of Transactions associated with a Partner on a dedicated runtime instance. You can also run a specific set of Transactions, Templates, or Process Flows that are not associated with a particular Partner, on a dedicated runtime instance by using Queue Management. A queue that you may have created can be edited or deleted at any point in time. 

When you create a queue, a new runtime service also gets up at the same time, and it starts accepting the transactions from that queue to process them. 

Write steps for creating/editing/deleting queues from Queue Management.

It regulates and expedites the execution by :

The Queue Processor executes process flows based on the priority information associated with each process flow. You have the following priority levels available to set for a process flow: 

Process flows with High, Medium, and Low priority are executed by the Queue Processor. The order of execution of process flows based on the priority is as follows:

1. High
2. Medium
3. Low
   

Process flows with same priority level are executed on first-in, first-out (FIFO) basis. 

Refer to the section Defining Priorities for Process Flows to know how to set the priority. Adeptia recommends you to set the priority for your process flows in such a way that none of them remains in the queue for a long time. This is also to mitigate any risk of low or medium priority process flows not being executed at all. 

See also

• Allowing you to line up the Process Flows based on where they're coming from - a specific partner, or the company itself.
• Producing a dedicated and a corresponding dedicated runtime service for the Process Flows.
• Managing the number of pods automatically based on the minimum, maximum, and the threshold values defined for them.