Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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

Links may not function; however, this content may be relevant to outdated versions of the product.


Updated on March 11, 2021

Propositions are product offers that you present to your customers to achieve your business goals. Propositions can be tangible products like cars or mobile devices, or less tangible like downloadable music or mobile apps. You can view the existing propositions and create new ones on the Proposition management landing page.

Note: This article describes the decision management capability of Pega Platform. If you intend to use this feature specifically in Pega Customer Decision Hub, Pega’s solution for 1:1 Customer Engagement, see the Customer Decision Hub documentation.

Proposition hierarchy

All propositions are organized by business issue and group. In this hierarchy, a business issue can have one or more groups which contain a series of related propositions (for example, bundles, credit cards, loans, and mortgages grouped under the sales issue).

When you define a hierarchy of propositions you create new classes in your application. You start with creating classes that represent business issues. Next, you create classes representing groups that can store classes representing propositions.

The classes that support the propositions hierarchy are created accordingly in the <OrgClass>-<ApplicationName>-SR class, the <OrgClass>-<ApplicationName>-SR-<Issue> class, and the <OrgClass>-<ApplicationName>-SR-<Issue>-<Group> class.

Proposition types

You can create the following types of propositions:

Versioned propositions
These propositions are part of the decision data rule instance managing propositions for a given group. You can view versioned propositions in the Hierarchy tab. They are also referred to as decision data records.
These propositions are data instances of the group data class. You can view unversioned propositions in the Proposition data tab.

When you create a group in a particular business issue, you can save the group as a decision data rule or decision parameter. The option you select determines if the group can contain versioned or unversioned propositions.

Proposition management can operate exclusively in the versioned mode if you set the PropositionManagement/isOnlyVersionedProposition dynamic system setting to true. By default, it is false and allows you can perform proposition management in both modes, versioned, and unversioned.

Proposition validity

Each proposition that you create has a validity setting assigned to it. You can set a proposition as always active. You can also manually invalidate a proposition. In addition, you can set a validity period for a proposition, which is a time frame when that proposition is active. This time frame is defined by the pyStartDate and pyEndDate properties.

Proposition conversion

If you want to do proposition management only through decision data records, but the propositions hierarchy contains unversioned propositions, you need to convert them into decision data records. After the conversion, propositions are managed through the decision data record and the old proposition data instances are deleted.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us