Creating proposition hierarchy and properties
3 Tasks
25 mins
Beginner
Pega Platform '24.2
English
Scenario
Your task is to create a new structure for propositions in the Sample Application. The first step is to create a new proposition hierarchy. Next, create new BaseCost and LetterCount properties to make them available for the decision strategy. Finally, create new propositions.
Proposition hierarchy is crucial in decision strategies because it organizes all propositions by business issue and group. This structure allows for an efficient and targeted approach when defining and managing propositions. For instance, a business issue can have one or more groups that contain a series of related propositions.
Base cost and letter count are values defined for each proposition, and the strategy uses them to calculate the output. Creating new BaseCost and LetterCount properties defines the information you need to provide to reach your business goal:
BaseCost: The constant cost associated with printing a label.
LetterCount: The number of letters in the name of the printing label.
Use the following credentials to log in to the exercise system:
Role | User name | Password |
---|---|---|
Decisioning architect | DecisioningArchitect | rules |
Your assignment consists of the following tasks:
Task 1: Create a new business issue and group
In Dev Studio, create a new Enablement business issue and Labels group to accommodate new propositions.
Task 2: Create new SR properties and add them to the Decision Data Form.
Create new integer BaseCost and LetterCount properties in the Top Level Strategy Results class. Add both properties to the proposition form.
Task 3: Create new propositions
Manually create the Blue Label proposition in the Enablement issue and Labels group. Then, export the proposition as a CSV file to create a template. Edit the CSV file using the values shown in the following table, copy the start date from the Blue Label row, and then import the edited CSV file to create the remaining propositions:
Business Issue |
Group |
Proposition name |
Base cost |
Letter count |
Enablement |
Labels |
Blue Label |
40 |
9 |
Enablement |
Labels |
Red Label |
30 |
8 |
Enablement |
Labels |
Yellow Label |
20 |
10 |
Enablement |
Labels |
Black Label |
10 |
10 |
Challenge Walkthrough
Detailed Tasks
1 Create a new business issue and group
- On the exercise system landing page, click Launch Pega Infinity™ to log in to Dev Studio.
- Log in as a Decisioning Architect:
- In the User name field, enter DecisioningArchitect.
- In the Password field, enter rules.
- In the header of Dev Studio, cllick Configure > Decisioning > Decisions > Proposition Management > Hierarchy.
- On the Hierarchy tab, in the Business issues and groups section, click Add > New business issue, and then configure the details:
- In the Create new business issue window, in the Name field, enter Enablement.
- In the Ruleset field, ensure that ExerciseArtifacts is the default selection, and then click Create to create a new business issue.
- Confirm that the new Strategy Results class is displayed in the Application Explorer.
- In the Top Level section, click SR Class.
- In the To field, copy the Academy-Sample-SR class name.
- In the navigation pane of Dev Studio, click App.
- In the Application Explorer, in the search box, paste Academy-Sample-SR class name.
- Confirm that Enablement class is displayed in the Academy-Sample-SR class.
- In the Top Level section, click SR Class.
- Click Decisioning: Proposition Management tab.
- In the Business issues and groups section, click Add > New group, and then configure the details:
- In the Create new group window, in the Name field, enter Labels.
- In the Context section, select Enablement, and then click Create to create a new group.
- In the Business issues and groups section, expand the Enablement business issue, and then ensure that the new Labels group is nested.
- Refresh the Application Explorer to see the new group and the new decision data:
- In the upper-right corner of the Application Explorer, click the options button.
- Select Refresh App Explorer.
- Expand Enablement > Labels > Decision > Decision Data.
- Click Labels to open the new Labels decision Data Set.
2 Create new SR properties and add them to the Decision Data Form
- In the Decisioning: Proposition Management tab, in the Properties section, click Add property, and then configure the details:
- In the Create new property window, in the Name field, enter BaseCost.
- In the Property type field, select Integer, and then click Create to create a new SR property.
- Confirm that BaseCost is displayed in the properties list.
Note: Always create the SR properties in the Top Level SR Context as a best practice. This context enables the properties for use across all defined issues and groups. Create SR properties within a specific issue/group only if they are not to be used in other issues/groups.
- Repeat steps 1-2 to create the LetterCount property.
- In the Decision data records for versioned propositions section, in the Versioned proposition data column, click Labels to open Labels Decision Data.
- In the upper-right corner of the Decision Data: Labels, click Check out.
- Click the Form tab.
- In the Form fields section, click Add field.
- In the new row, in the Identifier column, enter or select .BaseCost.
- Repeat steps 7-8 for .LetterCount.
- In the upper-right corner, click Save.
3 Create new propositions
- Click the Data tab.
- Click New to add a new proposition.
- On the Create proposition tab, configure the details:
- In the Name field, enter Blue Label.
- In the ACTIVE section, select Within a defined time period.
- In the Description field, enter Blue Label.
- In the BaseCost field, enter 40.
Note: that the BaseCost and LetterCount properties from the previous task are now available in the form.
- In the LetterCount field, enter 9, and then click Create to create a new proposition.
- On the Labels tab, click Export, and then save the CSV file to your local machine.
- Open the CSV file.
- Add the remaining propositions according to this table:
Business Issue
Group
Proposition name
Base cost
Letter count
Enablement
Labels
Blue Label
40
9
Enablement
Labels
Red Label
30
8
Enablement
Labels
Yellow Label
20
10
Enablement
Labels
Black Label
10
10
- Use the StartDate value of the Blue Label proposition for the other propositions.
- Save the edited CSV file.
- In Dev Studio, on the Labels tab, click Import to import the edited propositions file:
- In the Import data window, click Choose File, and then select the edited CSV file.
- Click Load to review import details.
- Review the import details, and then click Import.
- In the upper-right corner, click Check in.
- In the Check In window, enter appropriate comments, and then click Check in.
Available in the following mission:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?