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

Service JMS 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 JMS rule; the name of the service package becomes the first key part of a group of related Service JMS 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 JMS rule by selecting Service JMS from the Integration-Services category.

Key parts:

A Service JMS rule has three key parts:

Field

Description
Customer Package Name

Select the name of the service package (instance of the Data-Admin-ServicePackage class); this service package is used to group related Service JMS rules. 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 is an arbitrary identifier to logically group related methods. This name need 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 an identifier that describes the Pega 7 Platform activity being called. See How to enter a Java identifier.

Rule resolution

When searching for a Service JMS 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 JMS rules. The class hierarchy is not relevant to Service JMS rule resolution.

Up About Service JMS rules

Open topic with navigation