Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

References to a rule by name

Updated on January 21, 2021

When referring to an instance of a rule or a rule category, it is not necessary to include the word rule or the fully qualified class name. Use the common name instead.

If you are unsure what the common name is, refer to the form header or inspect the tree structure in the Records Explorer. For example, refer to instances of Rule-Obj-Model as Data Transforms. The following screen shows how to find the common rule name:

The following table shows examples of referencing a rule by using its common name:
Rule typeExample
activityAdd a line to the activity to show the page.
control Pega Platform includes autogenerated controls to make it easy to build the user interactions that your application needs.
data transformAdd an action to the data transform to copy the page.
decision tableAdd a row to the decision table to return a result.
decision treeUse a decision tree to record if-then logic.
field valueA field value can define a localized variation of a text label.
flowA flow contains the processing instructions that define and drive a business process.
flow actionA flow action controls how users interact with user forms to complete assignments.
harnessUse harnesses to define the appearance and processing of your user forms.
libraryClick Compile to compile the functions in the library.
map valueUse a map value to create a table of number, text, or data ranges to convert one or two input values into a calculated result.
propertyUse a property to define a name and characteristics for data used in a work object.
report definitionUse a report definition to define a report.
requirementYou can associate requirements with a specification.
ruleset nameCreate a ruleset to identify, store, and manage a set of rules. In the Application rule, enter both the ruleset name and ruleset version.
ruleset versionYou can specify multiple ruleset versions for one ruleset.
sectionUse a section to define the appearance and contents of the user form for the flow action.
specificationYou can associate a specification with a shape in a process diagram.
ticketTickets support business exception processing in a process.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us