WEBVTT

00:00:01.000 --> 00:00:04.490
This accompanies our article on connecting software.

00:00:04.920 --> 00:00:09.690
When CRM, scheduling and accounting exchange information, define which

00:00:10.000 --> 00:00:12.375
application may change each field.

00:00:12.400 --> 00:00:16.650
In a fictional organisation, a customer order moves from CRM to

00:00:16.680 --> 00:00:18.810
scheduling and then accounting.

00:00:18.840 --> 00:00:21.530
Meanwhile, someone changes an address.

00:00:21.600 --> 00:00:25.210
Which application should distribute that particular change?

00:00:25.240 --> 00:00:30.410
The CRM owns customer details, scheduling owns execution status, and

00:00:30.600 --> 00:00:32.970
accounting owns invoice numbers.

00:00:33.080 --> 00:00:37.050
These fields travel in agreed directions without casually overwriting

00:00:37.080 --> 00:00:39.450
fields owned by other systems.

00:00:39.480 --> 00:00:44.090
Specify source, destination, stable reference and transfer trigger for

00:00:44.120 --> 00:00:45.370
each field.

00:00:45.520 --> 00:00:48.890
Define clearing, archiving and deletion too.

00:00:48.920 --> 00:00:54.050
Two-way synchronisation is not blanket permission to update every available field.

00:00:54.280 --> 00:00:57.610
An address change from CRM may reach scheduling.

00:00:57.800 --> 00:01:02.170
An execution status changed there can return as status information,

00:01:02.280 --> 00:01:06.250
without automatically changing the customer details held in the CRM.

00:01:06.840 --> 00:01:10.250
A change arriving from the wrong source, or without a customer

00:01:10.280 --> 00:01:12.690
mapping, needs explicit handling.

00:01:12.920 --> 00:01:16.570
An apparently successful connection must not hide a failed or

00:01:16.600 --> 00:01:18.490
incorrect data transfer.

00:01:18.760 --> 00:01:21.250
Compare records over the same period.

00:01:21.480 --> 00:01:25.450
Which changes arrived, which are missing and which await recovery?

00:01:26.040 --> 00:01:31.450
Show administrators the last successful processing time and the required freshness.

00:01:31.720 --> 00:01:36.490
Choose one operational problem and test creation, changes, deletion

00:01:36.600 --> 00:01:38.330
and recovery after failure.

00:01:38.840 --> 00:01:42.410
Check whether an existing connector supports these agreements before

00:01:42.440 --> 00:01:44.570
developing a custom integration.

00:01:44.840 --> 00:01:48.970
Good integrations preserve meaning and responsibility as they transfer

00:01:49.000 --> 00:01:49.770
information.

00:01:50.280 --> 00:01:54.570
Our source article on software integrations helps define sources,

00:01:54.800 --> 00:01:58.730
directions, exceptions and maintenance in practical terms.