To support lifecycle management of configurations it is possible to group them in so called Application Configuration Packages. It is possible to export a configuration package from one environment and install it in another environment. An exported Application Configuration Package contains configuration items, and the package info, including information about when the package was exported. When exporting the package, also free-text information about the version can be provided.
A package is exported from the Application Configuration Package window using the option Export. In the export window that is opened you need to enter a path to where the files should be exported.
When exporting a package you will get one file in xml format with the package information, containing the name of the package, the author etc. This file also includes which items that are included in the package, but the actual details of each item are stored separately in one file for each item in a folder named "Items". An item file contains the item definition and all translations belonging to the item.
The export path is all that is required to export the package. Additionally there are some more options:
The package file and the "Items" folder are packaged into one zip file by selecting the option Export as a Zip file.
Version is a free-text information field that can be set when exporting a package. The version will be set on the package when imported. This way the Author of the package can tag the export to be able to keep track what version that is installed in a certain environment.
The Comment will be available as a text in the exported xml file and also visible in the Import Configuration window when installing a package. This can be used to provide the receiver of the package a short description of what has been done in this version.
Note:It is recommended to synchronize Custom Fields/Enumerations or LUs before a delivery and then include in the ACP.