Skip to documentation content
Common workflows

Ongoing integration support

What firms can expect after an approved connection is tested and placed into use.

On this page

Before you start

  • A tested and approved connection.

Typical workflow

  1. 1

    Name operational and technical owners.

  2. 2

    Monitor successful and failed handoffs.

  3. 3

    Replace access and update mappings through the agreed process.

  4. 4

    Test material changes before rollout.

Named ownership

The firm and implementation team identify who owns access, workflow review, source-system changes, exception handling, and support escalation.

Monitored handoffs

Important connected workflows can be monitored for missing submissions, rejected actions, mapping changes, expired access, or unusual duplicate activity.

Managed change

When an enabled capability or private contract changes, responsible developers should obtain the applicable updated reference and confirm testing expectations before rollout.

Keep in mind

  • When an enabled capability materially changes, integration owners should confirm whether updated private guidance and testing expectations are available.
Still need help with this guide?Contact PlaintiffDesk