Skip to end of metadata
Go to start of metadata

MidPoint is able to postpone selected actions (for example, role assignment) until they are approved by appropriate authority or authorities. The overall process looks then like this:

  1. Alice creates a role assignment to Bob.
  2. After receiving the request for role assignment (via "Save" button in GUI), midPoint finds out that assignments of this role have to be approved by Chuck, who is a person (in some way) responsible for this role. Therefore, Alice gets a message that the operation execution will be postponed until approved.
  3. In order to get the approval, a new approval process instance is created by midPoint. In its most simple form, the approval process consists of only one step: just asking the approver and obtaining his decision. So, in this case, a work item is created for Chuck, asking him to approve or reject the particular role assignment request. Optionally, a mail notification can be sent to Chuck, letting him know that there's something for him to do.
  4. When Chuck logs in, he can see that he has a work item to resolve. So he opens it, reads it through, and clicks on "Approve" button. (Or "Reject", as he decides.)
  5. As Chuck was the only approver, the process instance ends here. The operation is executed, and Bob is assigned the requested role. Optionally, Alice and/or Bob may be notified by mail about the result.

The workflows are usually used to implement approval processes. This usage is so frequent that midPoint has a special mechanisms to make approval implementation easy. See the Approval page for more details.

Notes

  1. The original operation may contain more changes, not only single role assignment. There are basically two approaches to executing these changes:
    1. The default one is such that each of these changes must be approved (or rejected), and after all approvals are in place, the operation is carried out. Modifications that were rejected, are simply left out from the operation. Modifications that do not require approvals (e.g. changing Bob's name or title) also wait until all approvals are done.
    2. Alternatively, each change may be executed as soon as possible, i.e. changes that do not require approvals could be executed immediately, and others just after they are approved.
  2. The approval process may involve multiple approvers, in many arrangements. E.g. After Chuck approves, there may be a requirement that Dan should approve as well. Or, either one of Chuck and Dan are sufficient to approve. Or, both Chuck and Dan must approve, but in any order (e.g. Dan before Chuck would be OK as well.)
  3. Within the process, not only concrete persons might be engaged, but organization units (e.g. "board of directors") or roles (e.g. "security manager") may be as well. (This is not implemented yet - MID-1465)
  4. Also, it is possible to specify an approver using an expression - like "the approver is Bob's boss".
  5. As an ultimate level of flexibility, a custom BPMN 2.0 approval process might be used. However, this option should be needed to use in only rare situations.

For more information

  1. Current status and future plans
  2. Approval examples
  3. Approvals examples (legacy)
  4. Architectural description of the Workflow component
    1. Information on implementing customer-specific workflows
    2. Workflow auditing
  5. System manager's view on workflows (i.e. workflow configuration)
  6. Notes
    1. How to use workflows in a self-service scenario

See Also

  • No labels