Let's consider the following business scenario:
You want to run a set of unattended tests to create an item (e.g. an online order) and then display the contents of the order by selecting the automatically generated order ID from a list displaying all available orders.
Task1. Record the task for creating the order and store the order ID
Task2. Record the task for displaying the order contents by order ID
An important challenge arises: The ID is available only after the order is placed. The order ID is not available in the orders overview list so you are not able to record Task2 and start executing the test without interfering.
The Click user action provides the solution. You record a Click action on any item in the list and configure a parameter to provide the order ID captured in Task1. You import the parameter from Task1 to Task2. The parameter value is transmitted from one flow to the other during execution.
You have 3 orders available in your list:
You are currently creating ORDER538. The order ID is not available in the list now but it will be added automatically once you place the order.
Step1 Record Click action on any item in the list.
Step2 Configure parameter on the Click action and import value from previous task
1. Add parameter name (P_NewOrder)
2. Set parameter type (INPUT)
3. Save configuration
4. Go to dataset and import parameter value from previous task, the one where the order ID was generated. More about passing value between parameters in the same flow here.
Step4 Execute flow
During the execution of Task1 the new order with order ID ORDER538 will be created and added to the orders list so that it is available in the list for the next task execution.
The execution of Task2 containing a Click action with a parameter containing the value ORDER538 imported from Task1 can now be done unattended. All details are in place so that no intervention is needed.