In the following, the functionality of the standard release process (two-step) is described. The configuration allows extensive adaptations to this process. These adaptations are carried out by the support of the Aachen model.
- Start discussion creates a discussion state of the released page.
- Every user with editing rights can start or edit a discussion.
- There is always only one discussion per page, in which several people can participate time-delayed.
- As soon as release has been requested, the discussion status is locked for editing.
- As long as a discussion status is waiting for release, no new discussion can be started.
- Each discussion must go through the release process so that the changes are transferred to the released status.
- A new discussion can then be started.
- In the two-stage release workflow, the content release is
- content-related release is carried out by the person responsible for the page.
- formal release is carried out by the QM department.
- Start release workflow
- Save discussion status.
- The document control is located at the end of the page.
- The changes can be checked with Compare with released status.
- Ask for release and select Change status or
- Discard discussion and select Change status. It follows:
- The discussion status is discarded.
- A new discussion can be started.
- If release has been requested, the person responsible for the page automatically receives a message (by email and/or on his or her personal page) with a request for release of the content.
- The changes can also be checked here by comparing them with the released status.
- The person responsible for the page can react to the change proposal in three ways:
- Release content: the next higher instance, e.g. the QM department, is asked for release.
- Ask for further revision: the last author is notified and the discussion status is released for further editing.
- Discard discussion: The released status remains in the old version, the discussion is deleted.
- After the content release, the QM department automatically receives a message with the request for formal release.
- The changes can also be checked here by comparing them with the released status.
- The QM manager can react to the change proposal in three ways:
- Formally release discussion status: The discussion becomes the new released status and a new discussion can be started.
- Ask for further revision: The last author is notified and the discussion status is released for further editing.
- Discard discussion: The released state remains in the old version, and the discussion is deleted.
- After formal release, there is a new released state:
- The version number is incremented by one.
- A new discussion can be started.
Translated with www.DeepL.com/Translator (free version)
Generate discussion status via Start discussion
- Any user with editing rights can start or participate in a discussion.
- There can only be one discussion per page at a time, but several people can participate one after the other.
- As soon as a request for release has been made, the discussion status is blocked for editing.
- As long as a discussion is waiting to be released, no new discussion can be started.
- Each discussion must go through a release process before the changes are transferred to the released status.
- Only then can a new discussion be started
- This manual describes a two-step approval workflow
- release of content by the person responsible for the page
- Formal release by the QM department
Start the release workflow
- If necessary, save the discussion page
- Navigate to the Document Control dialogue at the bottom of the page
- If necessary, compare changes in the discussion status with the released status via comparison with released status
- Ask for release: Click Change status or
- Select Discard discussion: Click Change status
- The discussion status is discarded
- A new discussion can be started
If release has been requested, the person responsible for the process automatically receives a message (by email or on the personal page) with a request for release of the content.
- Compare changes in the discussion status with the released status via comparison with released status
- Three options for evaluating the improvement proposal:
- Release the content of the discussion: the next higher level, e.g. the QM department, is asked for approval.
- Ask for further revision: the last author is notified and the discussion status is released for further editing.
- Discard discussion: The released status remains in the old version, the discussion is deleted.
After the content has been released, the QM department automatically receives a message with a request for formal release.
- Compare changes in the discussion status with the released status via comparison with released status
- Three options for evaluating the improvement proposal:
- Formally release discussion status: The discussion becomes the new released status and a new discussion can be started.
- Ask for further revision: the last author is notified and the discussion status is released again for further editing.
- Discard discussion: The released status remains in the old version, the discussion is deleted.
Only after formal release is there a new released status
- The version number is incremented by one.
- A new discussion can be started