Reusability - Configuration keys

(Demo in webinar Link for Developers chapter 4 - Configuration Keys)

Configuration keys are used to add data that is not available in the data received from the source system (your ERP, WMS, CRM etc.) to a document for a partner. Examples: EDI Contract Number mandatory by the receiver + addresses handled differently at the two parties (receiver/sender) - with different locations as delivery, buyer and invoice, you might need a rule to handle differences.

When the configuration key is available and included in the mapping of a certain document format, the value for it can vary from partner to partner and from distribution to distribution.

If the developer needs to see how to handle the configuration key in the mapping, this is discribed in Webinar “Link for Developers” part 12 “Link REST API”: Link for Developers

Variants and versions

Existing formats can be used to build new ones.

If a format for a customer is close to an existing format and differences can’t be handled with conversions or configuration keys, the developer can use variants and versions to create new formats based on existing ones. To understand what we mean by these different expressions see:Link Basic Building Blocks