Versions of a Workflow

Start of the Workflow Builder

When the Workflow Builder is started, the last processed workflow in the last processed version is displayed as standard. For more information, see Calling the Workflow Builder.

Saving and activating workflow definitions

When a workflow definition is saved, the old version is overwritten automatically. After being saved, the workflow definition has the status revised.

To set the workflow definition to status active, you select . The workflow definition is first subjected to a syntax check. Any errors and warnings discovered are displayed in the message area of the Workflow Builder. Only if errors are found, is the workflow definition not activated. If no errors are found (no red traffic lights in the message area), the workflow definition is saved and activated.

Generating a runtime version of a workflow definition

You can generate a runtime version without activating the workflow definition. To do this, choose Workflow  Activate  Generate Runtime Version.

New version of a workflow definition

To generate a new version, you choose Workflow  Generate Version. The workflow definition is set to status new, saved.

In order not to increase the memory space requirements for workflow definitions excessively, you should only generate a new version under the following circumstances:

• If you have made incompatible changes

• If there are productive workflows running that refer to the current version.

Transporting a workflow definition

If a workflow definition is transported into another system, only the active version is transported. If the workflow definition exists in the target system with the same version number, it is overwritten by the transported version if it has no workflows running. Otherwise, the transported workflow definition is saved with a free version number. The transported workflow definition becomes the active workflow definition in the target system.