Skip to main content

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

Service SAP form - Completing the Create, Save As, or Specialization form

Updated on April 6, 2022

Important: Service SAP rules are no longer being actively developed, and are being considered for deprecation in upcoming releases. Using Service SAP rules does not follow Pega development best practices. Use Service SOAP rules instead. For more information, see Service SOAP 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.

Create a Service SAP rule by selecting Service SAP from the Integration-Services category.

Note: Create a Service Package data instance before creating a Service SAP rule; the name of the Service Package data instance is the first key part of a collection of Service SAP rules.

A Service SAP rule has three key parts. The class and method name key parts are considered "external" and are unrelated to Pega Platform classes and methods, for flexibility. For example, a service that is already exported and deployed on a client computer may be changed to call a different Pega Platform activity. Because the external representation and the WSDL file hasn't changed, you do not need to redeploy and modify the application code on the client computer.

Customer Package NameSelect the name of the service package (instance of the Data-Admin-ServicePackage class); this package groups related Service SAP rules. Choose a name already defined through a Service Package data instance. See About Service Package data instances.
Customer Class NameEnter a class name to logically group related methods. This name need not match the Pega Platform class that the activity belongs to, but must be a valid Java identifier. See How to enter a Java identifier.
IdentifierEnter an identifier that describes the function of the Pega Platform activity that the service calls. See How to enter a Java identifier.

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

Close Deprecation Notice
Contact us