CDT in Process model

RE: CDT in Process model

sarathkumar13 — Sat, 11 Nov 2023 16:08:48 GMT

Understood. I will revisit those changes and analyze
Thanks Stefan for helping out

RE: CDT in Process model

Stefan Helzle — Sat, 11 Nov 2023 15:33:08 GMT

It is a bit difficult to analyse this from remote. What I want to say is, that depending on what exactly you are doing, you might get into a situation as you described.

E.g. a datastore can get a new version at deployment time, but that new version is not published. Typically because the automatic schema management is not enabled. Then you end up in a slightly inconsistent state. The CDT is not deployed because the data store cannot make the changes in the DB. And your processes then still use the last published version instead of the new one.

RE: CDT in Process model

sarathkumar13 — Sat, 11 Nov 2023 15:19:31 GMT

I am not able to catch fully but you are saying that if i have opened a process model and in the parallel background, CDT has been deployed. Now if I try to start the process model, it will still run with the old CDT since I had opened it in the first place.

Sorry if I misunderstood it but I am not able to understand why this issue is occuring in higher environments and not in dev. Especially that data store still having the old CDT version. We even published the datastore in higher environment, but the issue has not yet been resolved.

RE: CDT in Process model

Stefan Helzle — Sat, 11 Nov 2023 15:09:15 GMT

When the documentation says "immediately begin using the new version of the data type", the actual behaviour depends a bit on the type of the dependent object. A process model will be re-deployed automatically, same for data stores. Expressions und Interfaces pick up the new type automatically.

So, when you open the process modeller on your higher environment, then, in parallel, deploy a modified CDT from the lower environment, a new version of the model is created in the background. When you now start the process, you run the old version.

Does this resonate with you?

RE: CDT in Process model

sarathkumar13 — Sat, 11 Nov 2023 14:53:31 GMT

, I was debugging the issue. I found that test datastore is still having the old cdt(showing with ^ symbol) even though the new CDT has been deployed to test. I am not able to understand this behaviour. Any insights on this?

RE: CDT in Process model

sarathkumar13 — Fri, 10 Nov 2023 17:57:33 GMT

Its an existing application. So thats why these CDT changes

RE: CDT in Process model

Stefan Helzle — Fri, 10 Nov 2023 17:56:35 GMT

No, it does not matter how you change the CDT.

BTW, is this an existing app? For new apps I go all in on records and avoid CDTs and data stores.

RE: CDT in Process model

sarathkumar13 — Fri, 10 Nov 2023 17:54:57 GMT

Got it, thanks stefan
Just one more doubt. Could this issue might be caused since the CDT was not modified by downloading the XSD and modifying it and reuploading?

RE: CDT in Process model

Stefan Helzle — Fri, 10 Nov 2023 17:46:42 GMT

Documentation says: "After updating the data type, a new version is created unless the only change is to the data type description or its visibility in data type pickers. When a new version of a data type is created, all objects (excluding running processes) immediately begin using the new version of the data type."

docs.appian.com/.../Custom_Data_Types.html

RE: CDT in Process model

sarathkumar13 — Fri, 10 Nov 2023 17:39:35 GMT

Hi stefan,
thanks for replying. Actually the cap symbol is coming in new process instances only. Thats why I am little confused on it.

RE: CDT in Process model

Stefan Helzle — Fri, 10 Nov 2023 17:36:46 GMT

Active process instances will keep the old version indicated by the ^. Instances created after the deployment will pick up the new version.

You write "its not working as expected". What exactly is your expectation?