Categorizing a ruleset
Complete this tab to control the category of this ruleset and to provide additional information for Component rulesets.
In most cases, accept the default Standard ruleset type.
- In the Records explorer of Dev Studio, click , and click a rule to open it.
- Click the Category tab.
- In the RuleSet Type field, select the category to which this
ruleset belongs.Your selection affects where this ruleset appears in a requestor's ruleset list, and how rule resolution finds the rules in the ruleset.
- Standard – A "normal" ruleset that can contain all types of rules.
- Component – A restricted ruleset designed to encapsulate functional or capabilities that operate only on embedded pages. Rules in a component ruleset are designed and intended for reuse in multiple systems and applications.
- Shared – A restricted ruleset designed for reuse that operates on top-level pages only. See shared ruleset for the restrictions.
- If you chose the Component rule type in step 3, the
Property to embed in application section displays. To establish
communication between Pega Platform and a component application, complete
the following fields:
- In the Recommended Name field, enter a
Page
-mode property that is made available to both the primary (calling) application and the component ruleset.This provides communication between the primary application and the component application. - In the Page Name field, enter a clipboard page name that the component can access to pass values to and from the calling application.
- In the Page Description field, enter a description for the clipboard page.
- Click Add a row to add additional properties.
- In the Recommended Name field, enter a
- Optional: To add test case rules to the ruleset, in the Test automation
settings section, select Use this ruleset to store test
cases. For more information, see Creating unit test cases for rules.
- Click Save.
Previous topic Defining the security of a ruleset Next topic Deleting a ruleset