• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 13 replies
  • Subscribers 6 subscribers
  • Views 9107 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Process

How to update process variable type with the latest version of the CDT for the in-flight process instances?

Arun Theja Muthyalu
Certified Lead Developer

We had to add two new columns for an existing CDT. New process instances post deployment are fine as they refer to the latest version of the CDT. But in-flight process instances refer to the previous version of the CDT. However there is a related action available where the end user can capture the data for the newly added fields. But the business is more aligned with the option of the data entry on the tasks from the in-flight process instances.

Hence, hiding the section based upon the deployment date is ruled out. Please let me know other possible options to handle this scenario. Thanks in advance.

  Discussion posts and replies are publicly visible

  • 0 in reply to Arun Theja Muthyalu
    Well I was throwing ideas, after a second look FI you have the option just to hide that is a good approach since you don’t have to mess with all other stuff.

    In my previous post I said something like affecting the process model of the related action and affect the interfaces to read from different sources, keep the information in two different places and when all the process models are done then you can copy the information from one table to another and rollback the precios mentioned changes. Trying to make the change seamless to the user. But I am not sure that is a worth solution if your user can agree just to hide the section based on the deployment date it might be a really good approach, because you do it and forget about it.

    Sorry for throwing ideas without thinking it twice.

    Jose
  • 0
    Certified Lead Developer
     in reply to josep
    Don’t be sorry Jose. You help is very much appreciated. Thanks again.
  • 0 in reply to Arun Theja Muthyalu
    Hi Arun,

    You can try creating a stored procedure(which only gets called in the specific process model you mentioned) and in the script you can design to get the new field values from the required tables and give them as the values when you are updating the table with new record values.

    You can call this stored procedure inside your process model(using execute stored procedure) and set conditions so that it only gets executed for your active instances, before the deployment.

    After this you need to run Process upgrade so that these changes can be actually seen in the active instances.(need to create a new process for this).

    PS: Never tried this, just a thought.

    Thanks,
    Sai Kiran

© 2024 Appian. All rights reserved.