Service HTTP 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 topicsusing the following Developer Help topics:
- Creating a rule
- Creating a rule specialized by circumstance
- Creating a rule or data instance
- Creating a specialized or circumstance rule
This information identifies the key parts and options that apply to the record type that you are creating.
Create a Service HTTP rule by selecting
A Service HTTP rule has three key parts:
|Customer Package Name||Select the name of the Service Package data instance for this 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 a name that logically groups related service methods (service rules). This name is unrelated to Rule-Obj-Class instances; it must be a valid Java identifier. See How to enter a Java identifier.|
|Identifier||Enter an arbitrary identifier that describes the function of the Pega Platform activity called by this service. See How to enter a Java identifier.|
ArticleService HTTP rules