Use Case
Use Case
Let’s continue from the use case utilized in the “Field” and “Queue” configuration. Now, to move the transactions from one queue to another queue with required conditions, here we are going to create business rules.
Step1:
1. Login to the Manager and navigate to the project where the “Interact” has been configured.
2. Click on the “Business Rules” which is the third step on the project configuration setup.
3. Click on the “Create Rule” button to build the first rule.
4. The “Rule Configuration” window will pop-up on the screen.
Step 2:
In this step, we will create the first rule to move transactions loaded into the ‘Index’ queue to the ‘FetchData’ queue and copy all field values to the destination queue.
Note: In this scenario, we are adding transactions to the ‘Index’ queue for the project.
1. The “Rule Name” can be customized accordingly, here let’s set the rule name as “Indexing the transactions”.
a. Now, click on the “Source Queue” name and here I am choosing the “Index” queue from the drop-down. It will select the fields that are available in the “Index” queue.
b. Next, in this case, we are not adding any validations that needs to be actioned to any fields in this queue.
c. Hence move to the “Else” part and in the “Destination Queue” name and here choosing the value as “FetchData” queue from the drop-down.
i. Now, in the “Action” area, choose the value as “Copy”.
ii. Then, copy all the fields that are available in the “Source” queue to destination queue.
d. Click on “Save” to not lose the configuration and validations added to the project.
Step 3:
In this step, we will create a second rule to move transactions to another queue based on specific conditions. Specifically, from the ‘FetchData’ queue, we will validate the ‘REQUESTID’ field for the next action. Refer the below steps.
1. Click on the “Create Rule” button.
a. Here enter the rule name as “Request ID Validation”. Refer the sample excel sheet attached in the “Field configuration” step.
b. Choosing the Source queue name as “FetchData” queue as the bot will move the transactions automatically from Index to Fetchdata queue from the first rule.
2. In the “If” part, select the field value as “RequestID.”
a. Then choose the “Operator” as “Does Not Contains” and set up the condition value as “REQ”.
b. It will enable the bot to action when the field “REQUESTID” value does not contain “REQ” in it.
3. In the “Then” part, setting the destination queue as “Rejected.”
a. Here, set the action type as “Set” and choose the “field” as “Process Comments”.
b. Enter the value as “Not eligible to process the data”.
4. In the “Else” part, we are going to set the destination queue as “Processing” queue.
a. Now, click on “Add” button to save the configuration.
5. Click on “Save”.
Result: In this case, we will be resulted with two possible scenarios under one rule configuration.
1. If the “RequestID” field does not contains the “REQ” in it, the bot will move the transaction to “Rejected” queue with process comments as “Not eligible to process the data”.
2. If the “RequestID” field contains “REQ” in it, the bot will action to move the transactions to “Processing” queue.
