Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi
After doing changes in CDT for newly created requests it will work fine and process will fetch the updated details but for inflight ones it will be still old CDT is there any way to get the updated cdt to inflight instances
Discussion posts and replies are publicly visible
You can try the "upgrade process" smart service found in Process Management Utilities - it's supposed to update a running process instance to the latest version, though I'd recommend you test it on a small number of instances (and preferably in a lower environment) to ensure it gracefully handles CDT versions first.
This is also a good reason to generally try to design process models that are short-lived - if don't have processes that are active for a long time, then you don't need to worry about updates.
Another important note is that this does not happen if you're using record data types - in that case the variable always uses the latest version of the record type.
Interesting - did not know that!
Thanks for this insight. Is this documented?
Here's what we currently have in the documentation:
"When you make changes to the record type object, the record data type is also updated and stays current with any configuration changes you make. For example, if you change the name of a record field on a record type, the change is also captured on the record data type."
That being said, I think we could more explicitly call out that in process models the latest version is always referenced (since it is in contrast with CDTs that don't do that). I'll follow up with our team to see if we can add it to the documentation!