Skip to main content


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

Connect SAPJCo rules - Completing the Create, Save As, or Specialization form

Updated on April 6, 2022

Before you begin: To generate Connect SAPJCo rules, the Connector and Metadata wizard requires prerequisite software provided by SAP, as well as JAR files you create based on the SAP Business API. For information on prerequisites and working with Connect SAPJCo connectors, see "Before You Begin" in the Connect SAPJCo Connectors section of the Pega Community article Pega Process Extender for SAP Business Suite.
Important: Connect SAPJCo rules are no longer being actively developed and will be deprecated in Pega Platform 8.7. To avoid upgrade issues when these rules are deprecated, use Connect Java rules. For more information, see About Connect Java rules.

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Based on your use case, you use the Create, Save As, or Specialization form to create the record. The number of fields and available options varies by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields using the following Developer Help topicsusing the following Developer Help topics:

This information identifies the key parts and options that apply to the record type that you are creating.

To create a Connect SAPJCo instance:

  1. In the header of Dev Studio, click CreateIntegration-ConnectorsConnect SAPJCo.
  2. On the Create form, enter values in the fields to define the context of the flow.
    1. In the Label field, enter text that describes the purpose of the circumstance definition.
    2. Optional: To change the default identifier for the circumstance definition, click Edit, and then provide a unique value in the Identifier field.
    3. Select the Context.
    4. In the Apply to field, press the Down Arrow key and select the class that defines the scope of the circumstance definition.
    5. In the Add to ruleset field, select the name and version of a ruleset that stores the circumstance definition.
  3. Click Create and open.

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