Sergio,
The objects you've listed plus EPX workflows can all be extracted in Migration files. Configurations that are in repositories (such as DAMConfig, DAMVariants, Scheduled Exports, etc.) can be exported as either XLSX or CSV files. The resulting migration zip files and XLSX export files can be stored withing a source control system, but the associated comparison tools won't be of much help with the binary files. Exports of configuration repository records may not exported in a consistent order so even if exported to CSV files, the comparison of different versions may not be very effective.
A way to augment these loadable files would be to use the Compare Extract scripts (which can be found in the Services Framework deployment folder) which will extract the contents of the data model (and EPX workflow) into human-readable files. The information is extracted in a consistent way that makes it easy to compare different versions of the same file as well as compare extractions from the different environments (such as DEV, QA, and PROD) to ensure the definitions are the same in each environment (or the differences are expected such as when there are in-progress changes). If the results of the Compare Extract scripts are uploaded to the source control tool at the same time the migration and export files are uploaded, then the Compare Extract files can be used to identify when changes were made and then the accompanying binary files can be submitted if there's a need to "revert" any objects. Some definitions, such as the VTL script or bulk callout validation rules can be copied from the Compare Extract scripts and then pasted into the EnterWorks UI.
I have uploaded a document that describes how to use the Compare Extract scripts using the open source comparison tool WinMerge (any comparison tool can be used to perform the comparisons).
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
------------------------------
Original Message:
Sent: 03-22-2021 09:17
From: Sergio Rojas
Subject: Source Control
We are looking for ways to enhance governance around our EnterWorks MDM implementation. Does anyone have experience tying Enterworks to a source control system? Looking for ways to govern changes to code sets, validation rules (e.g. VTL code), etc.
------------------------------
Sergio Rojas | IT Manager
McNichols Company | 813-282-3838 x2421
------------------------------