The Version Control System (VCS) integration functionality is only limited per standard STEP functionality, meaning that not all configurations can be exported / expressed in STEPXML, 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
- Workbench bookmarks
Known import limitations:
- Deletions can only be performed for products, entities, classifications, and assets. STEPXML for deleting such objects in a target system would, with the current solution, have to be produced by a configured Jenkins job, or a job in a similar tool, upon identifying objects present in the target system not present in the source system.
- 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 single update mode.
- Workflow definitions can, in some cases, not be updated if there are tasks for objects in the flow.