In most cases, accept the default Standard ruleset type.

1. In the Records explorer of Dev Studio, click SysAdminRuleSet, and click a rule to open it.
2. Click the Category tab.
3. 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.
     Note: All rulesets created in Pega Platform 5.3 and earlier belong to this category.
   • 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.
   Caution: Choose this value carefully. Although you can change ruleset types other than Override later, Pega Platform does not then check whether existing rules in the ruleset meet the restrictions of the Shared or Component categories.
4. 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:
   1. 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.
   2. In the Page Name field, enter a clipboard page name that the component can access to pass values to and from the calling application.
   3. In the Page Description field, enter a description for the clipboard page.
   4. Click Add a row to add additional properties.
5. 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.
6. Click Save.