You can push process design changes to the “sleeping” process instance(s). 

These design changes can affect workflow steps that have already been completed or are in progress. 

Note: A process workflow can assign tasks, route forms, and generate documents through its process and form instances. Tasks and forms assigned to users can also be attached to files. These files and documents are stored in the application file server or in the DMS file storage folder, whose configuration is defined in the “Start” process step. Therefore, renaming a process definition or instance, or updating the design, shall also trigger changes to the process and form instances in the DMS file storage folder. 

Let's examine the workflow example below. 

Create and execute a new process instance. Click the “View Instance” hyperlink to view it. 

The process instance is displayed on a new page, and its status is “sleeping” at the “Task” step. 

Navigate back to the process designer and modify the workflow. Save the process definition. Note: Design changes are significant when applied to a process path that has not yet been executed. 

On the process instance page, select the “sleeping” instance, then click “Utils > Update > Design” to apply the design changes. 

Also, apply the design changes to the Render Instance page. Select “Utils > Update > Design”. 

A pop-up window appears for confirmation. Choose to re-execute “All, Changed or No” waiting steps by selecting the appropriate buttons. Then click OK.  

The design changes have been applied, and an alert is shown below. 

Render the process instance to view the design changes. 

Design changes are recorded in the process instance's history log. Select the process instance, then click “Utils > History”. 

The “Process Instance > View” history tab shows the design updated event, as shown below. Note: Values passed to variables or globals in a process instance via the API are retained by default, regardless of whether they are correct.