Ownership conflict policies

A record can be linked to several external systems, but only one of them is its owner: the system that linked to it first. Only the owner can change the record as a whole. The Ownership Conflict Policy of an external system decides what happens when that system sends a full update of a record that another system owns.

Strict (STRICT)

The update is not applied, and the system's code for the record is marked as a conflict. Until someone resolves it, the WMS does not accept data from this system under that code.

Relaxed (RELAXED)

The update is not applied either, but no conflict is recorded: the record keeps the owner's data, and the exchange with this system carries on without errors.

With either policy, a system that is not the owner can still change separate fields of the record under its main code, by naming them in _updateFields (see Building the payload).

For how a recorded conflict is resolved, see Conflicts.