LinkedIn
Copied!

Table of Contents

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

Service dotNet rules are no longer being actively developed and will be deprecated in Pega Platform 8.7. Using Service dotNet rules does not follow Pega development best practices. Use Service SOAP rules instead. For more information, see Service SOAP 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.

Create a Service Package data instance before creating a Service dotNet rule; the name of the Service Package data instance becomes the first key part of a collection of Service dotNet rules.

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

A Service dotNet rule has three key parts. The class and method name key parts are considered "external" and unrelated to Pega Platform class 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 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 a package name that groups related Service dotNet 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 class to which the activity belongs, but must be a valid Java identifier. See How to enter a Java identifier.
Identifier Enter a method name that describes the function of the activity called by the service; this value must also be a Java identifier.

Related Content

Did you find this content helpful?

Have a question? Get answers now.

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