Skip to main content

 –

Configuring a save plan for a data page in App Studio

Suggest edit Updated on August 16, 2021

Configure a save plan to update data in a savable data page. You can use the save plan to persist data updates from the case lifecycle to external systems. By keeping the persistence logic with the data page, the logic is reusable and consistent.

Before you begin: You must configure a data source for the data page before you configure a save plan. For more information, see Updating connections and field mappings for a data object.Note: The option to configure a save plan is available only for single object data pages.
  1. In the navigation pane of App Studio, click Data.
  2. On the Data objects and integrations landing page, click a data page.
  3. On the Data pages tab, in the data page for which you want to configure a save plan, click MoreConfigure 'Save' options.
  4. If you changed the data sources or data save options of the data page in Dev Studio, the system displays the Replace 'Save' option window. Click Replace to advance to the Connection details window.
  5. In the Connection details page, in the System field, select a system of record.
    • Create new - Create a new system to connect to an external database by using a REST connection. Then, enter a name and a description for the new system.
    • Use an existing system - Select the name of an existing system to connect to an external database by using a REST connection.
  6. In the Connection section, choose whether to connect to an endpoint URL or an OpenAPI specification.
    ChoicesAction
    Enter endpoint URL
    1. In the Method field, choose the connection method.
      Save plans support the POST, PUT, and PATCH methods.
    2. In the Endpoint URL field, enter the endpoint URL of the data.
    3. In the Parameters section, choose which parts of the URL are dynamic and need to be parameterized for future calls.
      1. Select the URL part that you want to parameterize.
      2. In the Parameter name field, enter the name.
    4. In the Headers section, click Add header to specify a request header and its value. Some services require extra information, for example, API version.
    5. In the Authentication section, select the type of authentication to use to connect to the system of record.
      For more information about basic and NTLM authentication, see Authenticating with basic or NTLM authentication.

      For more information about OAuth 2.0 authentication, see Authenticating with OAuth 2.0.

    6. Click Next to advance to the Data mapping page. For more information, see Mapping fields for data pages.
    Use openAPI
    1. For more information about connecting to an OpenAPI Specification, see Integrating with a REST API by using OpenAPI Specification.
    2. Click Next to advance to the Data mapping page. For more information, see Mapping fields for data pages.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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