Skip to main content
Inspiring
September 10, 2026
Solved

How to Update New Process Variables for Existing Active Process Instances?

  • September 10, 2026
  • 8 replies
  • 72 views

Hi Appian Community,

I have a situation involving a process model and a process report.

I have a process report that retrieves process variables from active process instances and displays the data.

For example, suppose we have an existing process model with several process variables. In the future, we add new process variables and need to populate those variables for existing active process instances.

My understanding is that we can use “Upgrade Process” to upgrade the existing active instances to the latest process model version. However, the newly added process variables remain null because the nodes that populate those variables were not executed in the original process instance.

The challenge is that I cannot simply restart or manually trigger the new node because the process instance are more, and that node was not part of the execution path when the instance originally started we cannot use “Restart Node” smart service.

My requirement is:

  1. Upgrade existing active process instances to the latest process model version.
  2. Execute the newly added node(s) for those existing instances.
  3. Populate the newly added process variables.
  4. Make those values available in the process report for the older active instances.
  5. Ideally, this should happen without manually restarting or creating new process instances.

Has anyone implemented a solution for this scenario in Appian?

Is there a recommended approach to execute a newly added node on already-running process instances after a process upgrade, so that the new process variables can be populated?

    Best answer by mikes0011

    Have you tried the “Get and Set External Process Variables” plug-in functions yet?

    https://appmarket.appian.com/listings/get-and-set-external-process-variables

    8 replies

    harshas2775
    Brainy
    September 10, 2026

    Any newly added process variables will not be available in existing active process instances. The best practice is to have granular processes and not long running active processes to avoid such a situation. See if you can optimize your process design such that they complete sooner, thereby not requiring a need of such a requirement or expectation. With subsequent action latest process instance can trigger. 

    Happy to help. Even happier to optimize.
    Inspiring
    September 14, 2026

    Agree, it was the initial build.. for now I am looking solution for the mentioned problem as a work around. 

    mathieud0001
    Brainy
    September 10, 2026
    Inspiring
    September 14, 2026

    Hi ​@mathieud0001, 

    I’ve tried using this Smart Service by providing the Node UUID as the input, but it hasn’t started the node.

     

    mikes0011
    Brainy
    September 14, 2026

    I’ve used this successfully before - can you share your current configuration when you try, and/or what error message (if any) you get when attempting to use it?

    The Expression Guru
    mikes0011
    mikes0011Answer
    Brainy
    September 14, 2026

    Have you tried the “Get and Set External Process Variables” plug-in functions yet?

    https://appmarket.appian.com/listings/get-and-set-external-process-variables

    The Expression Guru
    Inspiring
    September 14, 2026

    Thanks ​@mikes0011, active instances process variables are getting updated perfectly using the plug-in, but just concerned about the support from product as last update was on 2021-07-30.

    mikes0011
    Brainy
    September 14, 2026

    it still works after 5 years of iterative product versions, so there’s really no reason to be worried about it failing to work due to any updates on Appian’s side in the foreseeable future.

    The Expression Guru