You are here: Reference > Rule types > Service Files > Service File rules Completing the Create, Save As, or Specialization form

Service File rules
Completing the Create, Save As or Specialization form

  1. About 
  2. New 
  3. Service 
  4. Method 
  5. Request 
  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.

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

Note: Create a Service Package data instance before creating a Service File rule.

Key parts:

A Service File rule has three key parts. The class and method name key parts of the Service File rule are considered "external" and unrelated to Pega 7 Platform class and methods, for flexibility.

Field

Description
Customer Package Name

Select the name of the service package; this package name groups related Service File 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 may or may 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 by the service.

Rule resolution

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

Note: Each File Listener instance references a single Service File rule, not a group of rules as in other services.

Related Topics Link IconRelated information

Open topic with navigation