How to use Worksoft Certify’s Execution Flow Rule feature
In Certify, we usually apply logics for any process step in the “On True/On False” tab to change the execution flow.
You can find the below list of available actions for both On True and On False sections in this tab
2) Exit Process
3) Start at first step with next record
4) Exit All
6) Execute Process
7) Change Execution Flow
Consider a process with 2 or more rows of data in its Recordset
In case the first row of data fails at a verification step, in the ‘On False’ section of the step we may use Skipped → Start at first step with next record to skip the rest of the steps without exiting the process. Also, this action will select the next row of the Recordset and begin the execution from first for that current process.
Consider a parent process with 2 or more rows in its Recordset and containing a child process,
Let’s consider a requirement to use the next record of the parent process during a verification failure in the child process,
This cannot be achieved using the “Start at first step with next record” because this will only select the next record from the current process. So, we must exit the child process and use this logic in the parent process steps.
But, applying this logic will yield more steps even though it satisfies the requirement.
This is the time when Execution Flow Rule comes for rescue.
Execution Flow Rule
The action “Change Execution Flow” is used to change the execution flow from within your child process to your parent process(E2E) either to choose the next data from the parent process Recordset or to exit the process.
In short, Execution flow Rule provides a way to navigate and exit within parent process.
Execution Flow rule has 2 options:
1.Exit Process: Exits the current process and returns to the parent process.
2.Skip record and Start at first step: Stops the execution at the current step and returns the execution to the first step of the process where the execution flow rule is defined. If the process has Recordset attached, then the next row or record in the Recordset is used. If the process does not have a Recordset, the process exits.
We must define the execution flow rule at the parent level of a process
Execution Flow Rule Creation
1.Open Process Details tab → Right click in execution flow rule space.
2.Select Add and you should see a window titled ‘Execution Flow Rule Manager’.
3.Right click in this window and select New Execution Flow Rule.
4.Enter the Name of the rule, select the Action to be performed from the drop down and press OK.
5.New execution rule will be added in the Execution Flow Rule window.
6.This Execution Flow Rule can be added to a parent process at the integration level.
Now, we can use this execution flow rule in the above scenario to skip the execution of rest of the steps of the child process and move to its parent step to select the next record.
Depending on the above scenario we may choose Skipped → Change Execution Flow in the On False section and then choose the execution flow rule that we created earlier.
Here, when the first record fails, this step will skip rest of the steps of the child process and changes the execution flow by using the second record of the parent Recordset right away. It starts executing from the beginning of the parent process with the second record of its Recordset.
This helps us save some time and steps by not executing rest of the steps unnecessarily and directing the flow to its parent process to use the next record in the Recordset.