Deploy CDT with out disturbing existing instances

RE: Deploy CDT with out disturbing existing instances

Nagashankar Nallavalli — Thu, 08 Feb 2018 17:32:44 GMT

we should put condition on form based on process instances date to show added fields in the form or not
rest of the things (CDTand DB nodes ) will take old versions
thank you all for your answers

RE: Deploy CDT with out disturbing existing instances

Nagashankar Nallavalli — Thu, 08 Feb 2018 16:57:17 GMT

Thre is no code just it is complete process instancess on this example
created CDT A with only one field as name used in process model's user Input Task (form has only one text field for name)
I run the process model two times
I have modified CDT by adding extra field name as Type and modifgied form(this time form has two text fields for name and type )
I run the process model
I opened the previous instance but its taking newer CDT (which has two values)and newer form(which has two text fields )
but in my case previous instances should run on old versions (it should take old CDT and old Form not new one )

RE: Deploy CDT with out disturbing existing instances

chandu — Thu, 08 Feb 2018 16:07:42 GMT

It will not be possible. once you started a process the process instance will run on the old cdt(means the latest version of the cdt in your case its old one) and old form(assuming that the task is already assigned to the user).
Can you share your code and the steps that u did to update the CDT. when you update a CDT and if you update the out date dependents , all the process models that are using the cdt will be published.

RE: Deploy CDT with out disturbing existing instances

Nagashankar Nallavalli — Wed, 07 Feb 2018 16:35:27 GMT

I opened the old instances and its taking newer CDT and newer form instead old versions of CDT and Form

RE: Deploy CDT with out disturbing existing instances

viveku3486 — Wed, 07 Feb 2018 16:07:42 GMT

Only the newly created tasks will have new CDT available

RE: Deploy CDT with out disturbing existing instances

viveku3486 — Wed, 07 Feb 2018 16:06:17 GMT

You mean your previous instances should run on old process model version with newly configured CDT? If that is the case then its not possible as I said the instances which were launched on older version will use same variables/CDT's which it was using earlier.

RE: Deploy CDT with out disturbing existing instances

Nagashankar Nallavalli — Wed, 07 Feb 2018 16:01:04 GMT

I took CDT A with only one field as name used in process model user Input Task
I run the process model two times
I have modified CDT with extra field name as Type and form which is using this CDT
I run the process model
I opened the previous instance but still its taking newer CDT and newer form
but in my case previous instances should run on old version

RE: Deploy CDT with out disturbing existing instances

viveku3486 — Wed, 07 Feb 2018 15:50:27 GMT

Hi Nagashankar,

You can implement the new CDT in your process model. As the process models are working on versions, The processes or tasks which are already generated will continue using the older version of process model(During the time when they were launch) and the process which will be executing after implementing the new CDT will use the new process model. So there is nothing to worry about

RE: Deploy CDT with out disturbing existing instances

chandu — Wed, 07 Feb 2018 14:12:31 GMT

There will Problem with the SubProcess.
1. New CDT is treated as latest version. So the process model which use the cdt will pick the latest version when that process instance starts. Sub Process will always pick the latest version of the CDT.
2. suppose there are some running process instances that are using the old CDT Version then the Process Variables will display with
^[Version of the CDT] symbol eg: AMS_AnimalData^7
3. Suppose you have a Parent Process model let the name is A and you are using the older version of CDT. This process model contains a subprocess B a and you are passing that CDT value to B doing some modification to the CDT with the including the newly added fields then getting back to A. Now For some reasons the are many nodes(may be user Input tasks) between A and B.
In this case the process instance of A is running in other environment with old CDT Version and now the process flow hasn't reached to subprocess B. If you deploy your latest version of your CDT, along with the change in the Subprocess B using the newly added CDT fields, then the subprocess B will pick your latest version.
Now the changes that are updated to the rest of the three fields will not get back to Parent Process A.and this may result unExpected behaviour in Parent Process A.

So if you add only the CDT fields and you haven't changed anything in the Process Models that are using that CDT. I think there will not be any impact for your instances.

RE: Deploy CDT with out disturbing existing instances

Jayapriya Muthu — Wed, 07 Feb 2018 12:23:09 GMT

Here is the documentation links for your reference

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

docs.appian.com/.../Application_Deployment_Guidelines.html