Mapping Versioning
The mapping versioning is only available in the enterprise version of the module. The versioning allows you to have multiple versions of mappings and schedule the go-live of changes. Depending on the versioning mode the module will keep a copy of each mapping that was used in production. We do not have any automated change logs.
You can setup the versioning in the EDI Setup.
In the setup you have to select the Mapping Versioning Mode:
Mapping Versioning Mode
Anveo EDI Connect supports three versioning modes:
There can only be one version per mapping. This is the default option.
You can have multiple versions of mappings. Planning of go-lives, publishing etc. is supported. There is no protection of published mappings against modifications.
Each mapping has to be published, before it can be executed. A once published mapping cannot be modified and you have to create a new version.
Simple Versioning
This mode activates the versioning control actions on the mapping header. You can create new versions of the existing EDI mapping and schedule when a mapping should go live. There is no protection against modifying the current production version of an EDI mapping.
Please make sure that you only export one version of a mapping using the EDI Configuration Data Export at a time.
Auditible Versioning
This mode protects mappings from changes that are published to be used in production. As the EDI Processing Queue keeps track of the mapping version the module can track which mapping was used for which message.
Please make sure that you only export one version of a mapping using the EDI Configuration Data Export at a time.