Planning integrations · ASRR Tech
What should you check before changing an integrated field?
Map systems reading or writing the field. Test the new meaning against existing data and align user instructions.
A practical example
A status gains a new value unknown to another system.
This is an illustrative situation for assessing your own process.
Checklist for your team
- List dependencies.
- Test existing records.
- Update agreements.
What does success look like?
The change causes no unexplained handover failure.
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.