Change nested CDT version

RE: Change nested CDT version

oanas — Tue, 21 Nov 2017 10:19:59 GMT

Hello Puspendu Pal ,
Thank you for your answer. I have only changed the data type from text to Clob.

RE: Change nested CDT version

Puspendu Pal — Mon, 20 Nov 2017 12:55:32 GMT

Hello,

There are chances the process instance may break( even if not passed by reference), depending on
1) The kind of changes done to the CDT
2) The kind of operation done on the CDT in the long running process instance.

Example, - If you remove an column or change the data type of a column from text to integer and in the process instance you are trying to access that removed column, then there would be a failure.

But in your case, since CLOB can accept Text data, I think you should be good.

RE: Change nested CDT version

Jamal Case — Sat, 18 Nov 2017 12:45:44 GMT

You should be good if you updated the CDT using impact analysis one you made that change.

RE: Change nested CDT version

oanas — Tue, 14 Nov 2017 13:50:47 GMT

Hello,

The CDT is not passed as reference in any of the Subprocesses...it is only given as input/output variable.

RE: Change nested CDT version

Vinay Kumar Rai — Tue, 14 Nov 2017 13:35:12 GMT

Hi,
did you pass the CDT variable by reference?, if yes then the Process should break, Appian strongly recommend not to pass the CDT as reference