To support Version Control System Integration (VCSI), a set of outbound integration endpoint options allow STEP to publish system configurations to a branch in Git, an external Version Control System (VCS) (refer to: https://git-scm.com). Using an inbound integration endpoint (IIEP), files from a Git branch can be combined, enriched with processing instructions, and imported on a target system as a STEPXML file.
This functionality allows for easy comparison of configurations across systems in a Development, Test, Acceptance, and Production (DTAP) environment and is meant to aid customers who need to transfer configuration changes between different systems and/or ensure systems are in sync configuration-wise. Users can choose to configure a collection to group changes or a change package.
Note: For on-premises systems, the 'configuration-management' add-on component must be activated to enable VCSI.
Configuration / Data
In STEP, the distinction between configuration and data is not always clear. While most of the objects and settings that can be found in the workbench System Setup tab are clearly configuration, the Tree tab holds both data and configuration. For example, objects like import, export, and bulk update configurations are configuration, but in addition, classification hierarchies, upper levels in the product and entity hierarchies, and entity structures used for modeling reference data, are widely regarded as configuration.
For the functionality presented in the related topics and in the topics of the Version Control System Integration (VCSI) documentation, there is no distinction between 'configuration' and 'data.' Instead, as described in the OIEP for VCS Integration with Git Delivery or the OIEP for VCS Integration with Change Packages topic, this can be configured. However, the functionality is not designed to handle vast amounts of data objects (e.g., SKUs).
Additional Information
Refer to the following topics for more information: