References to a rule by name
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:
Rule type | Example |
---|---|
activity | Add 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 transform | Add an action to the data transform to copy the page. |
decision table | Add a row to the decision table to return a result. |
decision tree | Use a decision tree to record if-then logic. |
field value | A field value can define a localized variation of a text label. |
flow | A flow contains the processing instructions that define and drive a business process. |
flow action | A flow action controls how users interact with user forms to complete assignments. |
harness | Use harnesses to define the appearance and processing of your user forms. |
library | Click Compile to compile the functions in the library. |
map value | Use a map value to create a table of number, text, or data ranges to convert one or two input values into a calculated result. |
property | Use a property to define a name and characteristics for data used in a work object. |
report definition | Use a report definition to define a report. |
requirement | You can associate requirements with a specification. |
ruleset name | Create a ruleset to identify, store, and manage a set of rules. In the Application rule, enter both the ruleset name and ruleset version. |
ruleset version | You can specify multiple ruleset versions for one ruleset. |
section | Use a section to define the appearance and contents of the user form for the flow action. |
specification | You can associate a specification with a shape in a process diagram. |
ticket | Tickets support business exception processing in a process. |
Previous topic Rule vs record Next topic Referring to Dev Studio menus