Skip to main content


Upgrading REST connectors with URLs that only contain parameters

Suggest edit Updated on January 29, 2021

Because the URL configuration is not compatible with the new configuration, update URLs that contain only parameters, for example, {host}/{path}/{type}/{name}/{version}, before upgrading REST connectors.

Replace the {host} parameter with a valid base URL, for example,, so that the application extracts the correct base URL, resource path, and query string. Then save the REST connector before upgrading.

  1. In Dev Studio, click RecordsSysAdminIntegration-ConnectorsConnect REST.

  2. Click on the REST connector that you want to upgrade.

  3. On the Service tab, in the Resource path field, replace the{host} parameter with a valid base URL.

  4. Click Save.

  5. Click Upgrade to new endpoint configuration.

    By default, the Provide URL option is selected, and the Base URL and Resource path fields are populated with the base URL that you specified and the resource path parameters, respectively.
  6. Optional:

    Create a new application setting.

    1. Click Use application setting.

    2. In the Base URL field, press the Down arrow key and select Create New Setting.

    3. In the Create Setting For URL window, in the Owning ruleset field, enter the domain for the application setting. This value does not have to equal a ruleset name; it functions as a namespace.

    4. In the Name field, enter a name for the application setting.

    5. In the Short description field, enter text that describes the purpose of the application setting.

    6. Optional:

      Specify a category in the Category field.

    7. In the Value per production level section, in the Value fields, enter the setting value for the specified production level.

    8. Click Submit.

  7. Click Save.

Related Content


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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us