Planning integrations · ASRR Tech
When should you choose a one-way integration?
Use one direction when the receiving system mainly consumes data. Two-way exchange requires additional rules for simultaneous changes and conflicts.
A practical example
A reporting environment receives customer attributes without updating them back.
This is an illustrative situation for assessing your own process.
Checklist for your team
- Describe usage.
- Choose update location.
- Assess conflicts.
What does success look like?
The chosen direction supports the process without unnecessary dual administration.
Test this with a recognisable record and have a colleague review the outcome. Note missing information or decisions. Use that finding to improve a working agreement before applying the process more broadly.
Planning integrations: the wider process
An integration needs agreement about data meaning and ownership. Decide the source system for each field, when information is exchanged and who resolves discrepancies. Availability of a product integration does not imply every data flow is supported. Verify the direction, fields and requirements using an example from your own process. Test missing data and a temporary failure. Ask an employee to check that synchronised information is usable for the next step.