Skip to main content


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

Updating the integration layer for REST integration

Updated on November 23, 2022

On the Review page of the Create REST Integration wizard, you can review and optionally update the information for the integration layer of your REST integration in the Integration layer section.

  1. In the Integration layer section, in the Integration class field, update the name for the base class of your REST integration.
  2. In the Parent class field, use the autocomplete control to update the parent class for the base class.
  3. To update the base class identifier, click Edit next to the ID field for the base class.
  4. In the Connector Name field, update the name of the REST connector.
    The default name is the name that you entered on the Resource methods page of the wizard.
  5. To update the identifier for the connector, click Edit next to the ID field for the REST connector.
  6. In the Context section, click Edit.
  7. In the Development branch field, select a development branch in which you want to create your REST integration, or select No Branch.
  8. In the Choose application layer field, select the application in which you want to create your REST integration.
  9. To add your REST integration to a new ruleset or an existing ruleset, in the Add to ruleset field, perform one of the following actions:
    • To create a ruleset, select New and enter the name of the ruleset in the text field.
    • To use an existing ruleset, select Existing and select a value in the Ruleset and Version fields.
  10. Click Submit.
  • Previous topic Updating and generating records for REST integration
  • Next topic Updating the data layer for REST integration

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