Skip to main content

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

Suggest edit
Updated on March 16, 2022

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

Important: Service MQ rules are no longer being actively developed. To avoid upgrade issues when these rules are deprecated, use Service JMS rules instead. For more information about Service JMS rules, see Service JMS 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 topics:

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

Note: Create a Service Package data instance before creating a Service MQ rule; the name of the service package becomes the first key part of a group of related Service MQ 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 MQ rule by selecting Service MQ from the Integration-Services category.

A Service MQ rule has three key parts:

FieldDescription
Customer Package Name Select the name of a service package (instance of the Data-Admin-ServicePackage class); this package groups related Service MQ rules. Choose a name already defined through a Service Package data instance. 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 a class name to logically group related methods. This name may or may not refer to 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 a Java identifier that describes the Pega Platform activity being called. See How to enter a Java identifier.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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