Releasing and Publishing Processes

Processes need to be released and published so that they can be conveyed as valid processes. Release is normally based on a review rating.

The release workflow essentially sets how may reviews with various objectives need to be carried out before final rating and release. The release workflow that applies to the process space is set up in agreement with the BPM Manager.

The Process Owner needs to release and publish a process version so that all Bpanda users are informed about a process.

A process occurs in various phases in Bpanda. These phases are generally differentiated between by visibility of a process version and its branches.

  • Draft

    A draft is used for portraying a process version that a Process Designer has created but not submitted yet.

    A draft can be a sketch (consisting of name and description), a Happy Path or a process diagram created in the integrated Modeler. Drafts can be saved and are only visible for the respective author before it is submitted as a process revision.

  • Revision

    Processes need to be updated sooner or later. A process version that was imported in the process space or submitted is known as a revision.

    A release workflow which was set for the process space normally occurs after a review. The review is a key part of the release workflow. It evaluates the revision as the basis for a decision on release by the process owner.

  • Released and Published Version

    A review is is normally released as a new process version based on a review rating. Released reviews can be published by the process owner within a validity period they have set.

    All process space users can view a valid process version. It expressly describes a certain workflow.

You need to start the release workflow if you want to release and publish a process version. It normally consists of at least one review used for rating a new process version (revision) to prepare the release decision.

You need to carry out the following assignments when carrying out the release workflow:

  • Setting the Release Workflow

    Bpanda provides various release workflow options which determine the flow and status. One of these options needs to be imported as a base for all reviews. One or more reviews is a key part of the release workflow.

  • Starting the Release Workflow

    Imported processes are initially only visible for certain user roles, e.g. for Process Owners and Collaborators. Only valid processes can be seen by all users. A valid process needs to be released and published so that it is visible to all users within its validity period.

    Each process version (revision) is normally subject to a release workflow. The review is the key component of this process.

  • Creating Reviews

    The review is a key element of a release workflow. It is aimed at rating and release of a process version and is started by the Process Owner. They set both the review's meta data and roles in the review. The Review Owner organizes the review and ensures participants rate it.

  • Rating a Process Version in the Review

    A review is used to discuss and release a process revision. A review provides a release recommendation.

  • Ending Reviews

    The Review Owner ends the review and decides whether the process version should be released based on the aims of the review.

    If another review exists, it can then be started.

  • Publishing Processes

    The Process Owner decides whether the process version should be published once it has been released and all reviews of the release workflow have been carried out.

    The process version is published and can be viewed by users in the process space within the period of validity.

To make things simpler, it is possible for BPM Managers and Process Owners to trigger the next workflow step or discard the revisions for multiple revisions of the same workflow step. They can also create a review for multiple published processes.