The rule type rule-service-COM is deprecated. As appropriate, migrate to Service dotNET 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:
This information identifies the key parts and options that apply to the record type that you are creating.
Create a Service Package data instance before creating a Service COM rule; the name of this data instance becomes the first key part of a collection of Service COM rules. The class and method name parts of the key are considered "external" and are unrelated to the Pega Platform class and methods for flexibility.
Create a Service COM rule by selecting Service COM from the Integration-Services category.
A Service COM rule has three key parts:
Field |
Description |
| Customer Package Name |
Select a package name that groups related Service COM rules. Choose a name already defined through a Service Package data instance. See About Service Package data instances. |
| Customer Class Name |
Enter a name to logically group related methods. This name may or may not refer to the Pega Platform class that the activity belongs to. Make this a legal Visual Basic identifier: start the name with a letter and use only letters, digits, and underscore. |
|
Identifier |
Enter a name that describes the activity being called by the service. This is not a Pega Platform method or a Java method. Make this a valid Visual Basic identifier: start the name with a letter and use only letters, digits, and underscore. |
When searching for a Service COM 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 COM rules. The class hierarchy is not relevant to Service COM rule resolution.