To store modified information, you can use a top-level data page that you need to provide in the flow action. You can also use an embedded data page. However, in this scenario the new information persists only in the context of a current case and your application does not save the new data to any external system.

1. In the navigation pane of Dev Studio, click Records.
2. Expand the Process category, and then click Flow Action.
3. If you use the Robotic Desktop Automation (RDA), specify the post-processing automation to run on the user's desktop when you want to send data that users enter in a case form to all the applications that run on the user's desktop:
   1. In the Run robotic automation field, enter an automation name.
   2. In the Description field, enter text that describes the purpose of the automation.
   Note: Automations always run synchronously and flow processing pauses while the automation is in progress. After the automation stops processing, the system updates the clipboard, and then the data transform runs.
4. Optional: To save a data page after the flow action completes, in the Savable data pages subsection, list the data pages that you want to save:

   Choices	Actions
   Use a data page	Click Add data page. Optional: To save the data page only under certain circumstances, in the When field, enter a When condition rule. At run time, if the When rule evaluates to true, the application saves the data page. If you leave this field blank, the application always saves the data page. In the Data page field, specify a data page to save.
   Use a data relationship by providing an autopopulated property	Click Add data page. Optional: To save the data page only under certain circumstances, in the When field, enter a When condition rule. At run time, if the When rule evaluates to true, the application saves the data page. If you leave this field empty, the application always saves the data page. Select the Use associated property check box. In the Autopopulate property name field, specify an autopopulated property.

5. Optional: To add more data pages, click Add data page, and then repeat step 4.
6. Optional: To monetize efforts connected with performing the flow action, in the Apply cost field, specify the flow action cost:
   • To specify the cost manually, enter an expression or a number in units of any type, such as currency.
   • To calculate the value automatically, enter a property reference that identifies a numeric property that is used in your computation.
   In a single application, use only numbers or property references.
7. In the Apply data transform field, specify a data transform that the system applies to the current primary page at run time.
8. In the Run activity field, enter the activity that the system runs after processing the flow action is complete.

   Consider the following factors when you use an activity for post-processing:

   • Do not include a Commit method in the activity.
   • If you use an activity that depends on parameter values that a user enters after selecting this flow action, enter the activity in the post-processing configuration rather than placing the activity in the flow.
   • You can use the activity to perform validation processing and add messages to the clipboard if validation fails. Validation by applying an activity is more suitable for complex validation scenarios. The activity can also perform additional processing that occurs after the user successfully submits the flow action.
9. If the activity includes parameters, in the Parameters section, enter values for the parameters.
10. Click Save.