View on GitHub


« Back to Contents

Transactions | Fields

Due to each movement service requiring different information, each transaction model contains a set of soft fields. These fields are effectively a collection of key-value pairs of strings. These fields are then mapped to the appropriate part of the request sent to the movement service.

Generic vs Specific Fields

Originally, the key for each field in a service capability was unique to that service. This has the potential to cause mapping issues for applications, so we are currently in the process of producing a set of generic field keys which will be used across movement services making it easier for service providers to develop their integration. Backwards compatibility with the existing field keys will be maintained.

Generic Field Key List

Work in progress