Data and Integration
What the exam tests
Data and Integration questions check that you can separate case data from reusable reference data, choose a data source, and map external responses into case properties without creating brittle integrations.
Core rules
- Data types model reusable business objects (Customer, Address); properties hold values on cases or data pages.
- A data page is a named, cacheable data source with a scope: thread, requestor, node, or application. Scope controls reuse and freshness.
- Refresh strategy options include reload if older than, reload once per interaction, and do not reload.
- A data transform maps source values to target properties; it is not a data source.
- Integration uses REST or SOAP connectors to a system of record; error handling and timeouts belong in the design.
- Use a keyed data page for parameterized lookups; avoid caching case-specific values on a shared page.
Worked example
A claims app needs customer addresses from a CRM REST service. Create data type Address, data page D_CustomerAddress scoped to requestor, with a one-hour reload-if-older strategy and a data transform mapping the JSON response to Address properties. The reasoning: requestor scope shares the cache across that user's cases without leaking between users; the one-hour rule balances freshness and service load. Case-specific address edits stay on the case, not the shared page.
Traps
Using a data page for a single case value; choosing node scope for user-specific data; confusing a data transform with a connector; ignoring connector error handling; assuming a data type is a database table.