Introduction
We have long wanted to change the policy module, the review process and include a new workflow feature. This feature will in theory cover these three topics at once.
The current review process will change for an approval + review process.
- The “Approval Workflow” will control that any change on the policy or its attributes (title, etc) has to be approved to become “Published”. All new Policies will be on “Draft” by default. Internally we call it Versioning. This feature is very likely to be used on other modules.
- The “Review Workflow”, is simply a reminder to regularly trigger the previously mentioned “Approval Process”.
Approval Workflow (New)
The “Approval Workflow” process will be very simple and can apply to any module when an item is created and edited:
From a “Approval Process” perspective there are three possible status for an item:
- Draft (default)
- Pending Approval
- Approved
Workflows will be enabled on the following modules to start with: All Risk Modules, Assets and Policy, it can easily be expanded to almost any (parent) module in eramba later on.
Workflow Settings:
We need some basic settings on every module for workflows, the basic settings will be:
- Workflows enabled / disabled (default for all except policy, risk and asset)
- Timeout in days/hours (what happens if no-one approves or rejects a workflow for that period of time)
Review Workflow (Upgraded)
The “Review Process” is optional, it just basically triggers the “Approval Workflow” process based on some frequency defined by the user. The “Review Process” begins at step E1 from the “Approval Process” and it finishes at step F1 (Draft) or E1 (Approved) from the “Approval Process”.
If the “Review Process” is enabled, there are then two additional statuses:
- Expired Review (which also trigger the “Draft” status)
- Review Deadline Soon
Review Settings:
We need some basic settings on every module for Reviews, the basic settings will be:
- Reviews enabled / disabled (default for all except policy, risk and asset)
- We will need to migrate the current Review setting (who inherits the review) - MISSING
Migration to new Reviews:
During the Approval or Review process we need to generate records, a bit like we have today with Reviews Records.
Approval Process:
-
C1- date when requested, by which user, what changes happened on the item, final policy text
-
D1- date when approved or rejected CREATION, approval notes, who approved, final policy text
-
H2- date when approved or rejected EDITION, approval notes, who approved, final policy text
-
G1- date when approval withdraw, who withdrew the approval
-
R2- date defined for the next review, who decided that
-
D1- is part of the approval process
How we migrate reviews? customisations? notifications? Comments/Attachments? MISS!
Policy Module Form (Upgrades)
1/ the policy editor needs to move from the 90s, we are likely be using TipTap ( Tiptap Rich Text Editor - the Headless WYSIWYG Editor ) or this too Introducing our new composer, making writing on Discourse easier than ever - Announcements - Discourse Meta
Policy Portal
TBD
