Optimize Workflow Size by Referencing SmartWizard Definitions

I'm logging this idea on behalf of Pieter Cronje (pieter.cronje@nintex.com) who did not have access to the Ideas Portal at the time of posting this idea.

To reduce costs and improve system performance, especially in cloud environments, we should change how SmartWizard steps are stored in K2 workflows.

The issue:

Right now, every time a SmartWizard is used in a workflow, a full copy of its definition is embedded. So, if SmartWizard A is used 10 times, the workflow holds 10 identical copies. This results in larger workflow definitions, which leads to:

• Increased storage requirements

• Slower load and save operations

• Higher memory usage

• More network traffic during workflow operations

The idea:

Instead of copying the same definition multiple times, we reference it once and link all SmartWizard A steps to that single definition. This approach already works well for SmartObjects and Forms.

The benefit:

• Smaller workflow definitions

• Faster performance when loading or saving workflows

• Lower memory footprint

• Less bandwidth used, ideal for cloud-hosted solutions

• Easier to manage changes, since updates apply to all references

This is a straightforward change that brings real efficiency without adding complexity.