Manage multiple data entry points with entity keys

This is for experienced users of Axway Decision Insight who are data integration specialists.

Use case

You might often track a single transaction through multiple application systems which do not share the same identification logic. As a result, you might need to rely on multiple ID values for consolidating a single transaction lifecycle end-to-end. 

The following diagram describes an example of a transaction lifecycle.

Multiple keys enable the consolidation of a transaction lifecyle by chaining its keys (usually two by two). This implies that when received, a key - except the very first key - should be linkable with a previous one. 

As for any flow monitoring context, ensure that:
  • The final events that allow marking a transaction as completed are clearly identified.
  • All transaction-related events carry a timestamp with the corresponding time zone and all timestamps must be aligned on the same clock.

Keep in mind that multiple keys work under certain specific conditions:

  • Events must be received in a chronological order, otherwise, this could lead to receiving key usurpation error messages or creating separate transaction instances that will not be consolidated into a single one afterward.
  • Every "binding" event should carry a timestamp that allows linking the keys in a timely manner.

Set up a multiple-key management system

1 - Define the entity keys in the observation model

Instances can be resolved using one or more keys. Setting up a multiple-key management system consists in adding as many keys as required to track a transaction from end to end.

2 - Use multiple keys to update transaction life cycle in data integration mappings

Bind the keys together at transaction update

When integrating an event containing both keys (the key that has already been retrieved and the one you want to store next), you will then need to:

  • Resolve the transaction instance using the key in use at resolution time.
  • Use the Bind key operation to use the new key. This key will then be used by the next instance resolution.

Unbind all keys at transaction closing

When integrating an event that closes transaction instances. Keep in mind that the Unbind key operation must be performed on every key.

Use case example

Here is an example application that corresponds to the use case of this page:


Related Links