Version control mechanism for Mappings and ETL components in ADMM

In Syniti ADMM, there is no built-in version control mechanism for mappings and ETL components. As a result, any changes made at the UI level are not versioned or historically tracked, making rollback or recovery through the UI infeasible in case of code loss, corruption, or unintended modifications.

Due to this limitation, recovery cannot rely on application-layer features and must instead be handled at the database level. This includes maintaining backups or scripts of underlying objects such as mappings, transformations, and ETL logic stored in the database.

Client is looking for a feature where the versions can be controlled for Mappings and ETL components in ADMM