I have a question about the Security Policies module.
One of the built-in fields is ‘Status’, where you can chose either ‘Draft’ or ‘Published’.
To suit our documentation workflow, I would like to have a third option here, ‘Obsolete’.
This would be for when a policy is withdrawn or replaced by a different document (e.g. sometimes the contents of one policy is merged into another one).
At this point, the old policy is only for historical reference and it would no longer apply to staff, or need to be reviewed any more. (I guess we would set it to no longer appear in the eramba policy portal either)
I wouldn’t simply want to delete an obsolete policy from policy module, as we would want to keep in on file for future reference.
Is it possible to configure this kind thing?
By default, it seems it is mandatory for a policy to have a future review date, and the only way to stop that is to delete it altogether.