CDT change management strategy

The Configuration Deployment Tool does not enforce checks to restrict configuration data modification on the source or the target schemas using other means. You must develop and enforce your own methodology.

For example, if you use the Configuration Deployment Tool to migrate data from staging to production, it is not expected that the configuration in production is modified by means other than this tool. In such a case those changes are overwritten the next time CDT is run. Also, this could potentially lead to data integrity issues if the changes are performed in either the source or target while CDT is being run.

The Configuration Deployment Tool is not supported for implementations where configuration data is directly modified in production using the Applications Manager or any other means. For exceptional cases like urgent or critical fixes to configuration data in production, you must update the staging database with the same changes.