This content has been archived and is no longer being maintained.

Table of Contents


Applications enabled for decision management

Through decision management-enabled applications, you and your business users can implement a management strategy that is personalized for each customer and that guides every customer interaction and decision. As a result, you can improve customer engagement by anticipating customer needs and optimizing work to provide a better, faster, and more effective customer experience. When creating a functional decision management application in the Pega 7 Platform, you must correctly configure application dependencies and establish a well-defined organizational structure with right access groups and operators.

Application dependencies

The core decision management rulesets (Pega-DecisionEngine and Pega-DecisionArchitect) are part of the PegaRULES application. PegaDM provides additional revision management functionality.


Enterprise applications that are built on PegaRULES have access to the core run-time and design-time functionality. This functionality includes decisioning rule types, landing pages, and operational configuration. PegaRULES also includes text analytics (Pega-NLP ruleset), predictive analytics (Pega-DecisionScience ruleset), and the implementation-supporting data that is sourced from big data stores (Pega-BigData ruleset).


Enterprise applications that are built on PegaDM can access the revision management functionality. For more information, see Revision management of decisioning rules in the Pega 7 Platform.

If PegaDM is unavailable, add the highest available 07-10 version of Pega-DecisionManager to your application's ruleset.


The organization record provides the default class that contains the proposition hierarchy for your application (unless specified differently in the pxDecisioningClass field value) and provides the application dimension information. It is important to make the transparent and fully defined organization hierarchy available to all operators who work with applications that have decision management enabled.

If you work with multiple applications that access the same set of propositions, ensure that the same top-level class is configured on the Proposition Management landing page and that applications have access to the same ruleset that contains the classes that support the proposition hierarchy.

For more information, see Organization landing page.

Work pool

A work pool is a set of allowed work items or cases that a user can work on within an application. In most cases, the work pool is required for work items. The parent Work- and Work-Cover- classes for these work items and cases are specified in the user's access group. From the Decision Management perspective, you need a work pool for simulation and data flow runs.

For more information, see Standard classes derived from the Work- base class.

Access group and operators

For applications that are created by using the default options, the <Application_Name>:Administrators access group does not require any changes. For all other access groups:

  • Verify that the minimum number of required roles in the access group are enabled (PegaRULES:SysAdm4 or :Administrator, PegaRULES:SysArch4, PegaRULES:ProArch4, PegaRULES:WorkMgr4 or PegaRULES:User4) and that the required portal layouts are also enabled.
    PegaRULES:SysAdm4 or :Administrator must be enabled for users who configure the proposition hierarchy top-level class.
  • Verify that the local customization points to the application's ruleset and ruleset version are configured.

For more information, see Access Group data instances and Operator ID data instances.


To import your application to another Pega 7 Platform node, you can manually create a Product rule. To successfully import your decisioning application by using a Product rule, you must include the following assets in that Product rule:

  • Application records
  • Application rulesets
  • Classes that support the proposition hierarchy (by default, <OrgClass>-<ApplicationName>-SR)
    Starting with Pega 7.1.8, propositions are no longer data instances of the group class. If you use unversioned propositions, ensure that you enable the Include Descendants option in your Product rule.
  • Individual instances of the following rules:
    • Access group (Data-Admin-Operator-AccessGroup)
    • Operator ID (Data-Admin-Operator-ID)
    • Work pool (Data-Admin-DB-ClassGroup)
    • Organization (Data-Admin-Organization)
    • Division (Data-Admin-OrgDivision)
    • Work group (Data-Admin-WorkGroup)
    • Workbasket (Data-Admin-WorkBasket)
  • If applicable, the application's key performance indicator (KPI) definitions as individual instances of the following rules:
    • Query instances of the Data-Decision-Outcome-KPIDefinition class
    • Other rule instances that correspond to the KPIs that are used in your application

For more information, see About Product rules.

Published January 20, 2017 — Updated August 31, 2018

100% found this useful

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.