Introduced in 16.3 - New CDT import functionality and its impact to active process instances and byreferenced CDTs passed into sub-processes.

Will the new CDT import feature introduced in Appian 16.3 break process instances that are passing CDTs byreference into sub-processes?

In Appian 16.2 and lower, when I import a CDT into an environment, a new version of that CDT would not be created.

In Appian 16.3 and higher, when I import the CDT into an environment, a new version of that CDT is automatically created, regardless of the lack of changes to that CDT.

Is there a CDT version rollback procedure available in case a new version of the CDT was created when someone accidentally imported that CDT into an environment?

Lastly, I know that passing CDTs into a sub-processes byreference is not a best practice and should not be done. Please reserve those comments. Thanks.

OriginalPostID-263443