Process variable referring to Old CDT version.

RE: Process variable referring to Old CDT version.

Chris — Fri, 28 Jun 2024 19:28:20 GMT

Personally I would force a small change to the process models (update a comment, etc) and push them up with the CDT to force an update, assuming all looks good in the Dev environment.

I'm not sure why yours didn't update, as Appian is supposed to update all objects automatically to use the new CDT version. This is somewhat newer functionality, in the past only some objects would natively take the latest CDT version (Data Stores), but Appian has been building around this. I ran some light tests in my environments and I can't replicate this currently (23.3), even with having the process models open with saved drafts on the target server, etc. I'm guessing something about how the CDT was updated and/or used in the models caused an issue with the automatic update. Otherwise, might be useful to review additional server logs as well.

RE: Process variable referring to Old CDT version.

GauravSingh — Fri, 28 Jun 2024 18:09:54 GMT

Yes, no errors/skipped objects in the the logs.

RE: Process variable referring to Old CDT version.

Chris — Fri, 28 Jun 2024 18:02:32 GMT

Have you reviewed the import/export logs after deployment to ensure no errors were noted?

What version of Appian are you working on?

RE: Process variable referring to Old CDT version.

GauravSingh — Fri, 28 Jun 2024 16:42:48 GMT

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.

RE: Process variable referring to Old CDT version.

Mike Schmitt — Fri, 28 Jun 2024 16:22:01 GMT

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?