Hi Team,
I have recently deployed a new version of CDTs to my staging environments along with multiple other objects, the newly added Object are referring to latest version of the CDT however there are multiple process which are still pointing to CDT which is 4 version older.
What could be the reason behind this issue ?
I tried to find if there are objects depending on older version of the CDT but nothing as such in the warning from CDT.
We are not supposed to manually map the latest version of CDTs in the staging environments and when we are trying to compare and deploy these objects from Dev they are getting ignored as No change is detected in theses objects.
Please Advise.
Thanks,
Gaurav Singh
Discussion posts and replies are publicly visible
New process instances automatically refer to the most recent version of a CDT, unless there's been some sort of unusual error AFAIK. In your screenshot is that an old process instance (which we'd expect to see referring to the old CDT version), or something else?
The screenshot I have shared is from the Edit mode of the process model itself which is quite strange to us as in normal scenario reopening process makes it to refer the latest version of the cdt.