You are here: Reference > Rule types > Service MQs > Service MQ rules - Completing the New or Save As form

Service MQ rules
Completing the Create, Save As or Specialization form
  1. About 
  2. New 
  3. Service 
  4. Request 
  5. Response 
  6. History 
  7. More... 

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 may copy data instances but they do not support specialization as they are not versioned.

Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:

This help topic identifies the key parts and options that are applicable to the record type 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 7 Platform class and methods, for flexibility.

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

Key parts:

A Service MQ rule has three key parts:

Field

Description
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 7 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 7 Platform activity being called. See How to enter a Java identifier.

Rule resolution

When searching for a Service MQ rule, the system filters candidate rules based on a requestor's RuleSet list of RuleSets and versions.

Circumstance-qualified and time-qualified resolution features are not available for Service MQ rules. The class hierarchy is not relevant to Service MQ rule resolution.

Up About Service MQ rules

Open topic with navigation