Step 1: Go to the Advanced Configuration tab of the store Action in Flow F1.
public object ExecuteAction(string param, dynamic obj)
var value = obj.YourObject;
System.IO.File.WriteAllText(@"C:\tmp\Replace This.txt", value);
Step 4: Replace the “<Replaces This>” text, with the name of the file, where the value will be stored. We will name it SalesOrder in this example.
The custom code above was used to store a value from SAP GUI, that’s why the obj.MessageParameter, a flow on the web for example, this could be obj.innerText.For other object types and/or technologies, properties may vary. For instance, the default property from an SAPGuiTextEdit is "text". These default value properties are automatically assigned when the Store action is executed during recording. Thus, when the user goes to the Advanced configuration, the line '3' will be already pre-populated with the default value property from the object in question. For more information about the Store action advanced configuration, go to Lesson 5.
Step 6: In F2, create a custom action.
Step 7: The extra step will now need to be updated to fetch the stored value. Go to the User tab for the step and change the values as in the following example:
Step 8: Click Save.
Go to Advanced Configuration Tab of the custom action and and enter the following code::
public object ExecuteAction(string param, dynamic obj)Step 9: Replace the “<Replaces This>” text from the name in Step 4. In our case, it will be SalesOrder again.
return System.IO.File.ReadAllText(@"C:\tmp\Replace This.txt");
Step 10: Click Save.
Step 11. At this point you will have the value from F1 passed to the custom action parameter of F2. So you can use it as a reference in any other action from F2, including a verification step.
The value will now be fetched and stored in parameter SalesOrder in step 1.2. We now need to link the step 1.3 to pick up the value from parameter SalesOrder.
Go to the DataSet from the flow.
Step 12: Click on the Parameter Options for the Step 1.3