Updating CDT impacting live process instances

RE: Updating CDT impacting live process instances

arunt205 — Thu, 08 Apr 2021 12:59:06 GMT

Got it. Right now, I am handling this by manually editing the process instances which have this requirement(number higher than 2147483646). Just wondering is there is any other way. Thank you.

RE: Updating CDT impacting live process instances

Stefan Helzle — Thu, 08 Apr 2021 12:38:53 GMT

I do not see a way to do that. If this is a deal-breaker I think there would be a way, but then things become complex. Is a cost/risk/benefit trade-off.

RE: Updating CDT impacting live process instances

arunt205 — Thu, 08 Apr 2021 12:35:31 GMT

Hi Stefan,

Thank you very much for the answer. A follow-up question: Since the in-flight instances still refer to the old version of the CDT, it would not accept any value higher the upper limit of integer i.e., 2147483646

Is there way to circumvent this limitation for in-flight instances?

RE: Updating CDT impacting live process instances

Stefan Helzle — Thu, 08 Apr 2021 06:42:21 GMT

I think the most important best practice is to implement short living processes. My designs restrict the live time of a user input task to around 3 days. After 3 days, it means that the task can not be completed "now" because something is missing. Then the user can create a follow-up which is persisted to DB and restart working on that task a later time.

This results in a way lower number of active processes in general.

In your specific case, I can think of a two-step transition. First, change the type in DB and CDT. Things will still just work. As all old processes are completed, you can update the interface to use a floatingpointField.