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

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 Portlet rule; the name of the service package becomes the first key part of a group of related Service Portlet rules. The class and portlet name key parts do not refer to the Pega Platform class and method rules. They are strings used to identify the rule.

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

A Service Portlet 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 package groups related Service Portlet rules. Choose a name already defined through a Service Package data instance. See About Service Package data instances.
Customer Class Name

Enter a Java identifier value to logically group related portlets (if more than one exists). The service package and service class names group the portlets into one portlet application. See How to enter a Java identifier.

Identifier Enter an identifier as a descriptive name for the portlet. See How to enter a Java identifier.