Mobility
What the exam tests
Mobility questions test whether you can deliver a usable field or customer experience on a device, including responsive design, offline behavior, synchronization, and app distribution.
Core rules
- A mobile app in Pega is configured as an application channel with branding, navigation, and device capabilities; it is not just a small browser window.
- Responsive case types adapt to screen size; test the actual views, not only the desktop preview.
- Offline-enabled case types cache work so field users can continue without connectivity; changes sync on reconnect.
- Conflict resolution must be chosen deliberately when the same case changes on device and server.
- Push notifications require user permission and an event design that avoids noise.
- Distribution can be public store or enterprise; branding, signing, and versioning are part of the release.
Worked example
A field technician repairs equipment in basements with no signal. Enable offline for the Work Order case type, cache the technician's assigned cases, allow photo capture and status updates offline, and set a server-wins conflict policy for schedule changes. The reasoning: the technician's core task must complete offline, but dispatch scheduling is centrally controlled, so server-wins protects the schedule while local notes merge.
Traps
Assuming a web application is automatically mobile-ready; enabling offline without a conflict policy; testing only on a desktop emulator; forgetting notification permissions; publishing an app version without a rollback plan.