Skip to main content

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

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

Updated on August 10, 2022
Note: Service Java rules are no longer being actively developed, and are being considered for deprecation in upcoming releases. Using Service Java rules does not follow Pega development best practices. Consider other implementation options instead.
Note: Create a Service Package data instance before creating a Service Java rule; the name of the service package is the first key part of a collection of Service Java rules.

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

A Service Java rule has three key parts:

Customer Package Name Select the name of the service package (instance of the Data-Admin-ServicePackage class). The service package must exist before you can create the service rule. See About Service Package data instances. If your application is to process requests from this service asynchronously through a background agent, define a Service Request Processor data instance ( Data-Admin-RequestProcessor-Service class) with this Customer Package Name value as key.
Customer Class Name Enter the name of the service class. This name is an arbitrary identifier; it is not an instance of Rule-Obj-Class but must be a valid Java identifier. 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. This name is a string; it is not an instance of the Rule-Method class. The service method named describes what the service rule does. 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