What is Ruleset in Pega?

A name RuleSet is an instance of the type of rule-Rule-RuleSet name. Each defines RuleSet an important subset of PegaRULES rules in the database because each instance of each type of reference rule or “belongs to” a RuleSet. A name RuleSet is an important aspect:

-Access control

-Grouping of interrelated rules

-Manage Rules

-Move applications – sets of rules – from a system process to another commander.

Understanding Rules in PRPC


As a container for components of your application, a RuleSet stores a related group of business rules. It’s what you deploy in your production environment or ship to a customer. RuleSets provide security, version control, and the ability to deploy your application in (or move it to) a different Process Commander environment. You must create a RuleSet before you can build an application.

Ruleset has 2 parts – Ruleset Name & Ruleset Version

-Rule-RuleSet-Name – Which defines the RuleSet name and other characteristics

It should contain Maximum 64 characters

Ex. PolicyAdmin

-Rule-RuleSet-Version – which defines the RuleSet Version.

It has 3 parts separated by a hyphen – Major, Minor & Patch

Ex. 01-05-07


When you create a new RuleSet, you can choose to specify an existing RuleSet as its parent or Prerequisite. This designation establishes a rule resolution relationship between it and your RuleSet, which can then inherit and extend existing features and characteristics.In most cases, you should specify Pega-ProCom as a prerequisite for new RuleSets. This Process Commander RuleSet contains the standard work management capabilities that you use as building blocks for your applications.

Create a new Rule Set Version

Steps to Create a new Rule Set Version:

-Go To Application

-Select New

-Select Rule

-Select SysAdmin

-Select Rule Set Version

On Selecting Rule Set Version, a new Pop-Up will be opened as follows.

How To Create RuleSet in Pega- Ruleset version

Select the Rule Set name created, in RuleSet Name field and provide a version number in the format xx-yy-zz and click on Create.

How To Create RuleSet in Pega- Creation of new instance in ruleset

In the above expression, xx-yy-zz represents

XX - a Major Version

YY - a Minor Version

ZZ - a Patch Version

A new Rule Set Version will be created like this,

How To Create RuleSet in Pega- New ruleset version in ruleset

Creating Rule set In PEGA 

Create a RuleSet to identify, store, and manage the set of rules that define an application or a major portion of an application. You may need five to eight RuleSets per application. Typically, these are created as you use the Application Accelerator; you do not need to create them with the RuleSet form.

How you use RuleSets in your application has important design and deployment consequences. For large and complex applications, several RuleSet may be appropriate. Before you create a RuleSet, think carefully about the purpose, use, and dependencies of current RuleSets and the new RuleSet.

Select -- > Application > Structure

To view a list of RuleSets in your application (including those your application is built on) and a list of prerequisites for each RuleSet.

In versions before V6.1, you used New RuleSet and New RuleSet Version forms to create RuleSet and version rules, respectively. Beginning with V6.1, you simultaneously create both rules in the New RuleSet Version form. You can create versions for a given RuleSet from the Versions tab.

Interested in mastering Pega Training? 

Enroll now for FREE demo on Pega Training Online.


Use the Rules Explorer to list all RuleSet rules in your system.


As a best practice, create the initial set of RuleSets you need using a wizard, such as the Application Accelerator.

When you create a new RuleSet, an initial RuleSet version 01-01-01 is also created.

After you create a RuleSet and version, enable developers to create and modify rules in the new RuleSet by referencing the new RuleSet version in an application rule and an access group that is available to yourself or other users.

Optional or special-purpose RuleSets



CheckInCandidatesInitially empty. Supports the Rule Check-in Approval process, and needed only by developers using that process. See How to use the Rule Check-in Approval process. Not locked.
PegaAESOptional RuleSet, part of the Autonomic Event Services product.
PegaAESRemoteOptional RuleSet, for client systems monitored by the Autonomic Event Services product.
PegaAppTestManagementOptional RuleSet, part of the Test Management Framework.
Pega-BIXOptional RuleSet, provides the Business Intelligence Exchange facility.
PegaCustFoundationOptional RuleSet, part of the Test Management Framework.
Pega-DecisionEngineOptional. Supports Decision Strategy Manager.

PegaE to PegaO

PegaForecasterNot used.
Pega-IACSupports the optional Internet Application Composer product.
Pega-MobileSupports the Pega Mobile product.

PegaP to PegaV

Pega-RepositoryReserved. Not used.
PegaRelationshipViewerOptional RuleSet, part of the Test Management Framework.  
PegaRuleStubsReserved. Do not reference this RuleSet in any configuration. Supports special processing for rule resolution performance.
Pega-SpecialControlsSupports access to third-party UI facilities in non-autogenerated sections. See Sections — Completing the HTML tab.

PegaW to PegaZ

PegaWAIOptional RuleSet that supports accessibility.


Reserved. Not used.


PmmlSupportPart of Decision Strategy Manager.

Foundation RuleSets In PEGA

These RuleSets provide facilities that are part of base PRPC and are typically available to all users. The correct order and versions of these RuleSets are defined by the application rule named PegaRULES:06-03. The descriptions below provide only a general indication of the scope of the features provided.



Pega-AppDefinitionSupports the Direct Capture of Objectives features.
Pega-AutoTestSupports Automated Unit Testing.
Pega-ContentSupports Content Management Interoperability Services.
Pega-DesktopSupports the Designer Studio.
Pega-EndUserUIHTML and JSP generation
Pega-EngineRule resolution, low-level foundation processing
Pega-EventProcessingSupports business events.
Pega-FeedbackSupports the Direct Feedback feature, which works with the Project Management Framework.
Pega-GadgetsDesigner Studio, landing pages
Pega-ImportExportZIP archive support
Pega-IntegrationArchitectRule forms
Pega-IntegrationEngineIntegration services and connectors runtime
Pega-IntSvcsIntegration, connectors and services
Pega-LocalizationToolsInternationalization and localization
Pega-LPLanding pages
Pega-LP-ApplicationApplication landing pages
Pega-LP-DataModelData model landing pages
Pega-LP-IntegrationIntegration landing pages
Pega-LP-OrgAndSecurityOrganization and security landing pages
Pega-LP-ProcessAndRulesProcess and rules landing pages
Pega-LP-ReportsLanding pages
Pega-LP-SystemSettingsSystems landing pages
Pega-LP-UserInterfaceUser interface landing pages
Pega-PortletSupports portlet services
Pega-ProcessArchitectRule forms
Pega-ProcessCommanderTopmost foundation RuleSet.
Pega-ProcessEngineFlows and other process rules, at runtime.
Pega-ProComWorkflow support and user portal facilities.
Pega-RULESActivities, Java generation, rule resolution, and basic engine operations.
Pega-RuleRefactoringRuleSet management
Pega-SearchEngineFull-text search. See Understanding the full-text search facility
Pega-SecurityVASupports the Rule Security Analyzer.
Pega-SystemArchitectDesigner Studio facilities
Pega-UIDesignUser interface facilities
Pega-UIEngineUser interface runtime facilities
Pega-UpdateManagerSupports the Update Manager for hotfixes and system scanning.

For in-depth understanding of Pega click on