User Experience Design
Compose the user experience deliberately
Pega UX questions test how forms, sections, harnesses, flow actions, and views combine to present a case. A harness defines the overall case workspace; sections and views organize fields; flow actions present task-specific choices. Layouts, repeating grids, and dynamic layouts control presentation, while visibility, disable, and read-only conditions control behavior. Validation rules and field-level conditions should be used consistently so users see why a field is required or unavailable.
Client-side versus server-side behavior
Conditions that depend only on values already on the clipboard can often run client-side. If a condition depends on data that must be fetched or recalculated on the server, the section or view may need a refresh. A common mistake is hiding a field with a visibility condition and expecting it to be removed from the clipboard; hidden fields can still be submitted unless the design prevents it. Similarly, making a field read-only does not necessarily prevent a malicious client from submitting a value.
Traps candidates miss
Do not confuse a section with a harness or a flow action. A section is a reusable UI fragment; a harness frames the case; a flow action is a task-level action. Also distinguish cosmetic layout changes from behavioral changes that affect validation or data capture. Accessibility and localization requirements are design concerns, not afterthoughts.
Worked rule of thumb
If an approver field must appear only when Amount exceeds a threshold, use a visibility condition on the field or section. If Amount is changed by a server-side calculation, refresh the container so the condition is re-evaluated. If the field must never be edited after submission, use a read-only condition plus server-side validation.