A real-time integration needs an agreed operating boundary. Identify where the request begins, where the response is used, and who can investigate a problem.
Review the Unhappy Paths
Document behavior for a timeout, a service error, and an unexpected response. Ask the compliance owner to approve the behavior. Then exercise it with controlled data in the integration review.
- Keep requests traceable to their input records.
- Make unresolved states visible to operators.
- Retain the result and configuration needed for review.
- Provide an escalation route with a named owner.
Bring Your Workflow to the Documentation
Start with the public documentation and the DNCScrub overview. Confirm the exact behavior of the integration you intend to use.
