Process security definition
Registered by
Eric Fesler
Not everybody should have the possibility to start any process. Moreover, some sub-process should not be display in the can-do list.
The purpose of this blueprint is to add a notion of role on the process to define who can start it.
A specific role like "system" could be used for the sub-process that should not appear in the can-do list
Blueprint information
- Status:
- Started
- Approver:
- Eric Fesler
- Priority:
- Medium
- Drafter:
- Eric Fesler
- Direction:
- Approved
- Assignee:
- Eric Fesler
- Definition:
- Approved
- Series goal:
- Accepted for 1.4
- Implementation:
-
Beta Available
- Milestone target:
-
1.4rc3
- Started by
- Eric Fesler
- Completed by
Whiteboard
(?)
