Skip to main content


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

Service JSR94 rules - Completing the Create, Save As, or Specialization form

Updated on August 10, 2022

Note: Service JSR94 rules are no longer being actively developed, and are being considered for deprecation in upcoming releases. Using Service JSR94 rules does not follow Pega development best practices. Consider other implementation options instead.
Note: Create a Service Package data instance before creating a Service JSR94 rule; the name of the service package becomes the first key part of a group of related Service JSR94 rules. The class and method name key parts are considered "external" and unrelated to the Pega Platform class and methods, for flexibility.

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

A Service JSR94 rule has three key parts:

FieldDescription
Customer Package Name Select a service package name (instance of the Data-Admin-ServicePackage class); this service package groups related Service JSR94 rules. Choose a name already defined by a Service Package data instance. See About Service Package data instances.
Customer Class Name Enter the name of the service class. This is an arbitrary text value that is a Java identifier, not an instance of Rule-Obj-Class class. See How to enter a Java identifier.

The service package name and service class name group service rules.

Identifier Enter an identifier for the service method. See How to enter a Java identifier.

This name is an arbitrary text value; it is not an instance of Rule-Method. The service method named describes what the service rule does.

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