01.12.2025
14:47
Hi,
I had a case where a customer wanted to "freeze" the current state of the processes in an application.
"Freeze" in this context means, that it should not be possible, to trigger any path transitions, save the instance or add new attachments.
While this isn't a common situation, it may come in handy to have a support way to reach this , which doesn't require modifying the process:
- Migrating from WEBCON / Carve outs
- Moving a processes to an own database
- High impact bugs where you just need some kind of immediate action to stop everything.
Maybe we could define on process/application level, whether a "read only" mode is active.
This would:
- Take priority over all modify permissions defined on the general process or workflow instance level and "reduce" the current privileges to read only.
- Hide the tasks, if you can't modify them, they shouldn't be visible in the global task list.
- Cause an error when one of those triggers is executed
-- OnPath
-- OnSaving
-- OnDeleting
-- On adding an attachment
The later one would be necessary, to prevent any REST API calls.
Best regards,
Daniel
