Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adding a Save data page step

Updated on April 6, 2022

You can save data that is in a data page to a system of record by adding a Save data page step to a process in the case life cycle. This can improve performance and reduce memory requirements when multiple requestors in an application need to access the same information.

  1. In the navigation pane of Dev Studio, click Case types.
  2. In the process where you want to add the automation, click StepMore
  3. In the new window that appears, click Automations, and then click Save data page.
  4. On the right side of the new window, click Select.
    Result: The Save data page step is added to the process in the case life cycle.
  5. In the Step properties pane, in the Data Page Name field, select or enter the name of the savable data page that you configured.
    Select or enter a name that is an autopopulated property that references a savable data type.
  6. If the data page contains parameters, in the Parameters section, enter values for the parameters that are displayed.
  7. Optional: Autopopulated properties prevent the application from having to constantly monitor changes in key parameters, which are not always required and may slow performance. To specify an autopopulated property, complete the following steps:
    1. Select the Use associated property check box.
    2. In the Autopopulate Property Name field, select or enter the name of an autopopulated property.
  8. Click Save.
  • Previous topic Creating a save plan for a data page in Dev Studio
  • Next topic Saving data in a data page when running an activity

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us