In order to minimise errors, prevent misuse and ensure quality, the solution has a control mechanism.
This mechanism ensures that at least two people confirm or approve changes to data or configurations. The person making a change and the person checking it must always be different users. In this way, these persons act as a control authority and assume joint responsibility for the confirmation or release.
Via configuration, either the basic workflow, which includes all possible status and status transitions, or a simplified workflow, which does not allow post-processing or the rejection of a release task, can be set.
In addition, it is also possible to parameterise certain changes in a way that no control mechanism is run through.
Changes, that require a 4-eyes approval, run through a corresponding workflow as a (release) task. Such a task includes the specific change requests. The task itself logs which user triggered the transition (e.g. an approval) and when it was triggered. Task-specific information texts can also be recorded, to inform the involved users about the current status.
Release tasks should be completed promptly, as the basis on which a change was made can change over the course of the day. Tasks are therefore highlighted and presented to the respective user for processing.
The solution also has access protection, which is transferred from the respective entry screen to the release task: A user only sees the release tasks that they are authorised to process.