Ruleset form
Complete the Category tab
  1. About 
  2. New 
  3. Versions 
  4. Security 
  5. Category 
  6. History 
  7. More... 

Complete this tab to control the category of this rulesetand to provide additional information for Component rulesets.

In most cases, accept the default category Standard.

TipDon't confuse rulesetof type Standard, which you can create on this form, with standard ruleset, the Pega-zzzz ruleset that define PRPC itself.

Field

Description

RuleSet Type

Select to indicate which category this ruleset belongs to. Your selection affects where this ruleset can appear 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. (All rulesets created in V5.3 and earlier belong to this category.)
  • Component — A restricted ruleset designed to encapsulate functional or capabilities that operate on embedded pages only. Rules in a component ruleset are designed and intended for reuse in multiple systems and applications. See component ruleset for the restrictions.
  • Shared — A restricted ruleset designed for reuse that operates on top-level pages only. See shared ruleset for the restrictions.
  • Branch — Appears only in branch rulesets, which are designed for use with development branches. You cannot change this setting. You create branch rulesets in the Branch area on the Application rule form's General tab. See Application form - Completing the General tab. Also see branches and branch RuleSets.

The category determines where versions of this ruleset can appear on the General tab of the Application form, and so affects requestor ruleset lists and rule resolution. See How the system assembles and uses your ruleset list.

NoteChoose this value carefully. Although you can change ruleset of Types other than Override later, Pega 7does not then check whether existing rules in the ruleset meet the restrictions of the Shared or Component categories.

Note In release before V6.3, an Override ruleset was available. It contains rules that by design override rules in other, non-override rulesets. As of V6.3, this type is no longer supported. It cannot be included in an Application rule's ruleset list. If your application depends on Override Ruleset, you must eliminate this dependency to make the application work in V6.3+.

TipDon't confuse ruleset with a Type of Standard — which you can create using this form and tab — with the standard ruleset, the Pegasystems-supplied rulesets named Pega-ZZZZZ which define Pega 7.

Property to Embed in Application

These optional fields appear only when the Ruleset Type field is Component.

Use the Versions tab to identify version-specific information about a component RuleSet.

Recommended Name

Optional. Identify a Page-mode property that is to be available to both the primary (calling) application and the component ruleset. This provides communication between the primary application and the component application.

Component Clipboard Pages

add row

Page Name

Optional. Identify a clipboard page name that is accessed (read, updated, or both) by the component, to pass values to and from the calling application.

Page Class

Optional. Identify the class of the page.
Test Automation Settings Optional. Select this check box when you plan to add test case rules to the ruleset. If this box is not checked, no automated unit test rules can be added to the ruleset.

 

Related Topics IconRelated Topics

Open topic with navigation