Related information
Propositions are offers that you present to your customers. These can be tangible products like handsets or subscriptions, or less tangible like benefits, compensations, or services. You can view the existing propositions and create new ones on the Proposition Management landing page.
All the 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 groups under the sales issue). When you define a propositions hierarchy 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.
There are two types of propositions that you can create:
Versioned - these propositions are part of the decision data rule instance managing propositions for a given group. You can view them in the Hierarchy tab. They are also referred as decision data records.
Note: Propositions stored as decision data were introduced with Pega 7.1.8.
Unversioned - these propositions are data instances of the group data class. You can view them in the Proposition data tab.
When creating a group in a particular business issue, you can save it 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 by setting the PropositionManagement/isOnlyVersionedProposition dynamic system setting to true. By default, it is set to false and allows you to do proposition management in both modes, versioned, and unversioned.
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 will be managed through the decision data record and the old proposition data instances will be deleted.