Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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

Updated on April 6, 2022

Important: Service HTTP rules are no longer being actively developed and will be deprecated in Pega Platform 8.7. To avoid upgrade issues when these rules are deprecated, use Service REST rules instead. For more information, see Service REST 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 topicsusing the following Developer Help topics:

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

Note: Before you begin creating a Service HTTP rule, create or identify a Service Package data instance; the name of the service package becomes the first key part of the Service HTTP rule.

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

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.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us