Create a Service SAP rule by selecting
Service SAP from the
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 Name||Select 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 Name||Enter 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.|
|Identifier||Enter an identifier that describes the function of the Pega Platform activity that the service calls. See How to enter a Java identifier.|