Skip to main content


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

Preparing your data for production

Updated on April 6, 2022

To avoid corruption of production data during development, create different environments for your data.

You use the Data Object wizard to create a data object, update an existing data object, or replace a data source. You can configure connection details for different environments on the Environment settings page in the Data Object wizard when you define source data during data object creation or when modifying data pages. Configure connection details for your development, stage, and production environments to specify the external systems that the data pages use to get data. As a best practice, it is recommended that the production endpoint URL be different from the development and stage endpoint URL.

  1. If you are configuring connection details from the Data Object wizard, skip this step. Otherwise, in the navigation pane of App Studio, click Data.
    1. On the Data objects and integrations landing page, in the Data pages column, click the data page for which you want to configure connections details for specific environments.
    2. On the Data pages tab, on the data page for which you want to update the settings, click MoreEnvironment settings.
  2. Optional: In the Endpoint URL section, update the application setting by performing one of the following actions:
    • To create a new application setting, in the Setting field, press the Down arrow key and select Create New Setting. Then change the values in the Name field and Category field if necessary.
    • To use an existing application setting, in the Setting field, press the Down arrow key and select an existing application setting from the list.
  3. In the section for the environment that you are configuring, click Edit.
  4. In the Do you want to edit this setting? dialog box, click Edit.
  5. Update the value in the Base URL field.
  6. Optional: In the Authentication section, update the application setting by performing one of the following actions provided in step 2.
  7. Configure authentication for the endpoint, based on the type of authentication that you choose.
    • To not authenticate, in the Authentication mode field, select None.
    • To use the basic HTTP authentication credentials:
      1. In the Authentication mode field, select Basic.
      2. In the User name field, enter a valid user name.
      3. Click Set password.
      4. Enter a password for the user name that you entered.
      5. Click Submit.
      6. In the Realm field, enter the realm of the user account on the server to which you are connecting.
      7. In the Host name field, enter the host name of the server to which the request is being sent.
      8. Optional: To receive a basic authentication request before the server gives an unauthorized response, select Preemptive authentication. Selecting this check box reduces connection overhead.
    • To use the NT LAN Manager credentials:
      1. In the Authentication mode field, select NTLM.
      2. In the User name field, enter a valid user name.
      3. Click Set password.
      4. Enter a valid password for the user name that you entered.
      5. Click Submit.
      6. In the Domain field, enter the domain of the user account that you provide in the User name field.
      7. In the Host Name field, enter the host name of the server to which the request is being sent.
  8. Optional: If you are using OAuth 2.0 authentication, see Authenticating with OAuth 2.0.
  9. Configure additional environments as needed.
  10. Click Submit.
  • Previous topic Integrating with a REST API by using OpenAPI Specification
  • Next topic Updating connections and field mappings for a data object

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