Update Existing Running Process Instances

Introduction

When managing Joget applications, especially in a production environment, it is crucial to understand the impact of updates on existing process instances. This page outlines two common scenarios for updating processes and the best practices for each.

Updating a Process within the same app version

When you update a process within the same version of an app, all existing running process instances are automatically updated to reflect the new process flow. This update happens seamlessly in the background, allowing a smooth transition without interrupting ongoing operations.

Using the Process Version Migrator Utility

The Joget Process Version Migrator is a utility to change your app's running processes to a newer version.

Joget automatically updates the running process version when you make changes to the process design.

However, if you import the same app over an existing app, running processes in your old app will remain at the same 'old' process version.

Here is where you can use the Process Migrator utility to upgrade or change your app's older process version to the latest version.

Additional Joget Knowledge Base reading on running processes:

• View running processes
• Update Running Processes

Branching an app to a new version

To ensure stability and continuity for users, it's advisable to branch your app into a new version when making significant changes. Here’s how it affects your processes:

• They will continue running under the old version without disruption, as the new updates do not affect them.
• Once the new version is branched and activated, any new processes initiated will use the updated flow.

Although existing processes continue under their original version, you can manually update running processes to the new version using Joget's JSON API. However, this method involves updating each process individually.