--- title: Status of a Process description: >- Processes pass through various statuses, particularly during the release process. search: tags: - konzept - status - zustand - freigegeben - entwurf - gueltig - abgelaufen --- Processes pass through various statuses, particularly during the release process. The life cycle of a process begins with a draft created in Bpanda's integrated **Modeler**, or with the import of a process from a modeling tool. Before the process becomes a valid version for a particular period, it normally passes through a release process, at the heart of which is the **review**. To this end, a **draft** must be submitted as a revision. A process that is imported for the first time also constitutes a revision of that process. Revisions of a process are assessed in the **review** and are then either approved and published or rejected and therefore not published. However, they can also be released without a review and thus published, or discarded during the release process. A process is published as a version for a particular validity period. This results in the statuses "**Valid**" and "**Next**" for exactly one version each, and "**Upcoming**" for all subsequently valid versions. After the validity period has elapsed, the version has the status "**Expired**". Only one version of the process can have the status "**Expired**" at any given time. Validity periods can be changed retroactively in any status of a version. Restrictions arise from the respective subsequent versions. A version can be edited again either in the **Modeler** or in the modeling tool and can then pass through the release process as a new revision of the process. Predecessor versions of the process with the status "**Expired**" have the status "**Invalid**". Several past versions of the process can have the status "**Invalid**". | Status | Description | | --- | --- | | ![Draft](/media/en/draft.png) **Draft** | A **draft** is created in Bpanda as an outline (name, description), a happy path (with a synchronized diagram) or a Modeler diagram, and can be submitted as a process revision. This status is displayed on the page for capturing a process in text form (**Happy Path Editor**) and also in the search results. A process that was created with the **Happy Path Editor** or the **Modeler** can be edited again as a **draft**.
Visibility: Only for the user who creates or edits it | | ![Imported](/media/en/imported.png) **Imported** | The **revision** has been submitted (**draft**) or imported (modeling tool) and can be processed further in accordance with the release process. Normally, the next step is a **review** of the process revision.
Visibility: **BPM Manager**, **Process Owners** and **Process Contributors** of the process | | ![In Review](/media/en/inreview.png) **In Review** | The **revision** is in **review** and is currently being checked by the **Review Participants** for correctness and weaknesses.
Visibility: **BPM Manager**, **Process Owners**, **Review Owners** and **Review Participants** | | ![Approved](/media/en/approved.png) **Approved** | The **revision** has been approved in the **review**. To this end, a positive decision was made on the release of the process after the review had been completed.
Visibility: **BPM Manager**, **Process Owners**, **Review Owners** and **Review Participants** | | ![In Release](/media/en/inrelease.png) **In Release** | The **revision** has been released without a preceding **review**. This status is displayed on the search results page. On the process page, "**Imported**" is displayed.
Visibility: **BPM Manager**, **Process Owners**, **Review Owners** and **Review Participants** | | ![Not published](/media/en/notpublished.png) **Not published** | The **revision** was not approved in the **review** and has therefore not been published.
Visibility: **BPM Manager**, **Process Owners** and **Process Contributors** of the process | | ![Discarded](/media/en/discarded.png) **Discarded** | The **revision** was discarded before it was published.
Visibility: **BPM Manager**, **Process Owners** and **Process Contributors** of the process | | ![Upcoming](/media/en/upcoming.png) **Upcoming** | The **version** was released for a period after the validity period of the next valid version. It will become valid in the future once its validity period becomes relevant. All versions that become valid after the version with the status "**Next**" have the status "**Upcoming**".
Visibility: All users. Users who are explicitly blocked for the process are an exception. | | ![Next](/media/en/nextversion.png) **Next** | The **version** was released for a period directly adjoining the validity period of the currently valid version. It becomes valid once the currently valid process version expires and then automatically changes its status to "**Valid**".
Visibility: All users. Users who are explicitly blocked for the process are an exception. | | ![Valid](/media/en/valid.png) **Valid** | In the last step of the release process, the revision was published as a **version** that is valid for the current period. A version is always assigned a validity period when it is published. Within the validity period, the status is displayed next to the process title.
**Process Owners** are notified six weeks before the validity expires.
Visibility: All users. Users who are explicitly blocked for the process are an exception. | | ![Expired](/media/en/expired.png) **Expired** | The validity period of the **version** has elapsed. The version no longer appears in the search for **Process Users**, but it can be called up via the version history.
**Process Owners** are notified when the validity expires.
Visibility: All users. Users who are explicitly blocked for the process are an exception. | | ![Invalid](/media/en/invalid.png) **Invalid** | The **version** is the predecessor of an expired or invalid version. The version no longer appears in the search for **Process Users**, but it can be called up via the version history.
Visibility: All users. Users who are explicitly blocked for the process are an exception. |