Upgrade your processes

K2 Live Instance Management (LIM) via a GUI

BlueWave product boxes

Overview

BlueWave's process version tools bring K2's Live Instance Management (LIM) to users in a codeless manner.

Everything from the identification of process instances (by process version and current activity), to the visual comparison of process differences, automatic analysis of potential issues, and finally the single-click upgrade of process instances is catered for.


What is K2's Live Instance Management (LIM)?

Live Instance Management (LIM) is an advanced feature of K2, allowing developers to migrate process instances from one version of a process to a later version. BlueWave brings you this capability with an out of the box UI, and supplements it with intelligent tooling to highlight process differences and analyse.

More information ▾

BlueWave facilitates K2 LIM by removing the need to write custom code, which otherwise would have included:

  • The identification of outdated process instances and their respective process version numbers.
  • (Optionally) retrieving current activity information, which is often necessary during upgrades.
  • Invoking of K2's LIM functionality on the affected process instances.

Aside from reducing the development burden, BlueWave's change detection and analysis features help you upgrade process instances in a more informed and safe manner.


Compare Actual Process Instances

Compare K2 process versions side-by-side. Our groundbreaking technology automatically detects and highlights changes in K2 processes - gone are the days of error-prone manual comparisons and meticulous change auditing.

More information ▾

Process change detection is currently available in two areas of BlueWave:

  • Documentation generation, where it enables easy communication of changes between members of the development team. You can find more information about documentation generation on its dedicated page.
  • Process version upgrades, where it enables intelligent decisions to be made about upgrading process versions.

Change detection is also being expanded to include SmartObjects and SmartForms (in conjunction with BlueWave's snapshot capability) in future releases.


Upgrade K2 Processes

Identify outdated process instances, and formulate an upgrade plan using a visual representation of K2 process versions.

More information ▾

In addition to the process name and version number, BlueWave's process version upgrade screen displays process instances grouped by the current activity (or activities). The current activity can play an important role in the decision to upgrade:

  • As an indicator of progress through a particular process, the current activity can indicate whether a special intervention is required for a process. One example might be the addition of a new data field to a process. If this field is required, but only populated at a particular activity, all process instances already past this step will need to be handled differently.
  • Activities where client events have had their actions modified typically need to be refreshed for the changes to correctly reflect after an upgrade.
  • In cases where an activity is removed, it may not be safe to upgrade the process.

Analyse Changes Between Versions

Automatic analysis displays critical changes that may result in errors or a loss of data during process upgrades, such as removed activities or data fields, data type differences, etc.

More information ▾

BlueWave's automatic analysis serves as a basic check for upgrade compatibility, detecting common known issues so that you have more time to perform the intricate checks.


One-Click Upgrade

BlueWave's one-click upgrade feature upgrades all selected process instances from one version to another, including optionally triggering a "goto current activity".

More information ▾

By providing an out of the box process upgrade utility, BlueWave empowers you to make use of K2's powerful Live Instance Management (LIM) functionality without the need to write any code.

The goto current activity option is significant primarily due to the way action permissions are resolved by K2 at the time a client event is started. These are typically not re-evaluated during a process upgrade, leading to actions list being incorrect after an upgrade, if there were changes between the versions. One solution is to force the process to re-evaluate the action permissions by forcing the process instance back into it's current activity.