The Version Control System Integration (VCSI) functionality is only limited per standard STEP functionality, meaning that not all configurations can be exported / expressed in STEPXML or can be added to change packages, and not all changes can be applied via the STEP Importer processing engine. The functionality works for settings stored in the STEP database rather than files in the application server file system.
Known configurations / settings that cannot be exported / expressed in STEPXML:
-
Web UI user configurable views
-
Web UI user defined searches
-
Web UI custom icons
-
Scheduled background processes (can be added to a change package, but not installed)
-
Workbench bookmarks
Known import limitations:
-
Deletions can only be performed for products, entities, classifications, and assets using the STEPXML Joiner. STEPXML for deleting such objects in a target system must be produced by a configured Jenkins job, or a job in a similar tool, upon identifying objects present in the target system and not present in the source system. The STEPXML Joiner for Change Packages does not support the Processing Instructions features, including replacement rules, deletions, missing object tags, or global settings.
-
A number of update operations for configuration objects cannot be carried out if there is data in the system conflicting with the change.
-
A number of updates require special handling. For Oracle databases, this action requires single-update mode (SUM), as defined in the Single-Update Mode topic.For Cassandra databases, this action uses Lock-free Schema Change (LFSC) functionality, as defined in the Lock-free Schema Change topic.
-
In some cases, workflow definitions cannot be updated if there are tasks for objects in the flow.