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 File rule by selecting
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 Platform class and methods, for flexibility.
|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 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 Platform activity being called by the service.|