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

Service SOAP rules
Completing the Create, Save As, or Specialization form
  1. About 
  2. New 
  3. Service 
  4. Request 
  5. Response 
  6. Faults 
  7. XML Page 
  1. Advanced 
  2. Test Cases 
  3. History 
  4. 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 using the following Developer Help topics:

This help topic help topic identifies the key parts and options that are applicable to the record type you are creating.

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

NOTE: Create a Service Package data instance before creating a Service SOAP rule; the name of the Service Package data instance is the first key part of a collection of Service SOAP rules.

Key parts:

A Service SOAP rule has three key parts:

The class and method name key parts are considered "external" and are unrelated to Pega 7 Platform classes and methods, for flexibility. For example, a service that is already exported and deployed on a client computer may be changed to call a different Pega 7 Platform activity. Because the external representation and the WSDL file hasn't changed, you do not need to redeploy and modify the application code on the client computer.

Field

Description
Customer Package Name

Select the name of the service package (instance of the Data-Admin-ServicePackage class); this package groups related Service SOAP rules. Choose a name already defined through a Service Package data instance. See About Service Package data instances.
Customer Class Name

Enter a class name to logically group related methods. This name need not match 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 function of the Pega 7 Platform activity that the service calls. See How to enter a Java identifier.

Rule resolution

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

Related Topics Link IconRelated information

Open topic with navigation