Making changes to the cdt which is already in use

RE: Making changes to the cdt which is already in use

Brazil Vibanco — Mon, 14 May 2018 07:47:08 GMT

Hi rohitr303 ,

I can suggest you to focus your implementation as a Case Management, where you will build every phase or every action as a new subpocess, this will help you when you change your cdt, every new instance will get the new structure, even you have started the process before.

By this frame, you will have an scalable platform that you could adapt every time in your needs.
Here you can see a little page about it. I hope it could help you.
www.appian.com/.../

RE: Making changes to the cdt which is already in use

Sandeep Deshmukh — Mon, 14 May 2018 06:00:31 GMT

Hi rohitr303 ,

I am not sure for you what convincing answer is. But I can help you on this if you are not satisfied with above answer.

We have "IFM Manager" smart service available to update :
- Target process models for mass update, or a specific instance
- Update PV and CDT values
- Reassign Tasks
- Start Tasks
- Cancel Tasks
- Restart Tasks
- Start task if no running instance
- Update process instance security
- Add new PVs to an instance
- Batching of instances.

Please PFB url :
forum.appian.com/.../summary

Hope this will help. :)

Thanks,
Sandeep

RE: Making changes to the cdt which is already in use

rohitr303 — Fri, 11 May 2018 15:33:12 GMT

Still Waiting to receive a convincing answer.

RE: Making changes to the cdt which is already in use

rohitr303 — Mon, 30 Apr 2018 14:07:24 GMT

Thanks chandu The first suggestion might work in my case as i don't have much of user input tasks here thanks.

RE: Making changes to the cdt which is already in use

chandu — Mon, 30 Apr 2018 13:45:19 GMT

Hi Rohit,
Instead of Requesting the client to create new instances, you can do inflight modifications but this is hectic process if you do have huge number of process instances. Or you can cancel the running process instance and restart the new instance. In this way the new instance will pick the newer version of CDT(This will be a bad idea if your process model does have multiple user input tasks).
If the above requirement does not suffice, will it be possible to give outline of the nodes configured in your process model so that we can see any other approaches might can apply for your case.

RE: Making changes to the cdt which is already in use

bryant.st39 — Mon, 30 Apr 2018 11:39:15 GMT

You can also migrate inflight processes to new the new process model versions using a plugin or even new process models using "helper" process models.

RE: Making changes to the cdt which is already in use

arikd — Mon, 30 Apr 2018 11:22:54 GMT

Hi rohitr303 ,

Please find below the list of few things that you must consider while making changes in a CDT and publish that CDT which is also being refered by the active instances.

1.Avoid using (.) DOT operator while accessing the fields of a cdt instead use index function to access the same.

2.Inorder to avoid Process model failure make sure that before publishing the CDT there is not active instances which is refering the old CDT.

3.Incase a sail or Process model is refering a CDT then create a new version of that sail and PM like _v2 and then do the changes in that case so it will avoid the active instances refering the new sail or PM which is using that new CDT.

RE: Making changes to the cdt which is already in use

Sandeep Deshmukh — Mon, 30 Apr 2018 11:17:11 GMT

Hi @rohitr303,
I have no idea what type of data and process it is but I guess the only option you have is to make a changes manually on existing inflight instances. As you know cdt modification will never update existing instances.