You can prioritize the execution of Transactions, Templates, or Process Flows, based on what they're associated with, the Company or its Partners. For this, you need to create a dedicated queue that in turn creates a corresponding runtime service. To achieve this, follow the instructions given below.

On the Account menu, click Maintenance.
In the left panel, select Queue Management.
On the Queue Management screen, click Create Queue.
In the Add Queue window, enter the details in the following fields.
In the Queue Information section,
1. In the Name and Description fields, enter the name and description respectively for the queue.
2. In the Category field, select Partner or Company.
  
  Select Partner if you want the transactions associated with this Partner to be executed on a dedicated Runtime instance. Select Company if you want a specific set of Transactions, Templates, or Process Flows to be executed on a dedicated Runtime instance.
  If you select Partner as a category, do the followings.
  1. In Partner field, select one or more partners.
    You also have the option to select the resource intensive Transactions to be processed through a separate queue on a dedicated Runtime instance. To do this,
  2. Select the Resource Intensive checkbox.
    
    Select Resource Intensive checkbox if you have transactions in which a large amount of data is going to be processed. You can skip this step if you don't have any resource intensive Transaction.
  3. Select the Transaction that you know is resource intensive.
  If you select Company as a category, you need to enter the following details.
  1. In the Transactions field, select the Transactions.
  2. In the Template field, select the Templates.
  3. In the Process Flow field, select the Process Flows.
In the Autoscaler Settings section,
1. Leave the field Deployment Name as it is.
  
  The Deployment Name field is non-editable. It contains the name of the service created based on the name you have given to the Queue. The format of the Service name will be as follows: Runtime-<QueueName>. For example, Runtime-QueueA, wherein QueueA is the name of the Queue.
2. In the Minimum Pod field, enter the minimum number of Runtime instances to start with when there is a request for Autoscaling.
3. In the Maximum Pod field, enter the maximum number of Runtime instances to have in the service.
4. In the Autoscaler Threshold field, enter the threshold value for the messages in the queue.
  
  The system checks for the number of messages in the queue at an interval of every 30 seconds. At that moment, if the system finds that the number of messages in the queue is equal to or greater than the value defined in this field, it creates a new Runtime instance.
Click Save.

Viewing a queue

You can view an existing queue by following the steps given below.

Select the queue that you want to view.
Click the icon under Actions column.
Click View.

You'll be able to view all the details of the queue. Refer to screenshot below.

Editing a queue

You can edit an existing queue by following the steps given below.

Select the queue that you want to edit.
Click the icon under Actions column.
Click Edit.

You can't edit the name of a queue.
Edit the required fields.
Click Save.

You may be interested in...

What is new
Application architecture
Key terms
Install
Usage scenarios

Browser not supported