User Experience
What the exam tests
User Experience questions check whether you can design a case-working interface around a persona's task, using Pega's views and layouts, responsive behavior, and clear validation rather than exposing the data model.
Core rules
- Design from the persona and microjourney outward: what the user must decide, see, and do at each step.
- Views present case data; layouts arrange them. Reuse views across stages instead of duplicating forms.
- Progressive disclosure keeps primary fields visible and moves secondary detail into expandable or secondary views.
- Responsive design serves desktop, tablet, and mobile from one case type; test at realistic widths.
- Validation should appear next to the field with actionable text; instructions belong where the decision is made.
- Pulse and dashboards support collaboration and at-a-glance status, not data entry.
Worked example
A claims adjuster must review a claim, see photos, and approve or reject. Build a Summary view with read-only claim number, claimant, and amount; a Photos view with a gallery; and Approve/Reject actions with a required rejection reason. Hide medical notes unless the adjuster holds the Medical Reviewer role. The reasoning: the layout mirrors the decision sequence, and the conditional visibility enforces least privilege in the UI as well as in security rules.
Traps
Designing screens around tables rather than tasks; putting every field on one view; relying on color alone to signal state; using generic validation messages; forgetting that UI visibility is not a security control.