Use Case - Validating the application
2 Tasks
30 mins
Scenario
The U+ Comms project team is now ready to initiate work on the project. As the system architect, validate the operators, access groups, and application rules. And as the decisioning architect, validate the Next-best-action designer artifacts.
The U+ team has confirmed that decisions will be made for individual subscriptions, and the application should also support making decisions at the account level. However, because there won't be any decisions made at the household level, this entity can be removed from the application. Remove the Household entity and save the updated context dictionary to regenerate all the artifacts.
Detailed Tasks
1 Other details
- Use the System Architect operator to access Dev Studio and App Studio.
- In App Studio, remove the top-level Household entity from the context dictionary.
- Save the updated context dictionary and re-generate all artifacts.
- In Dev Studio, review the newly created applications.
- In Dev Studio, review the imported operators and access groups.
- Use the Decisioning Architect operator to access Pega Customer Decision Hub™.
- In Customer Decision Hub, review the Next-Best-Action Designer tabs.
- In Customer Decision Hub, review the Profile Designer.
- In Customer Decision Hub, review the available Profile Data Sources.
2 Acceptance criteria
- Application records and rulesets are reviewed.
- Operators and Access Groups are reviewed.
- Household context is removed from the context dictionary.
- Next-Best-Action Designer tabs are reviewed.
- Profile Designer and Profile Data Sources are reviewed.
Available in the following mission:
Want to help us improve this content?