BPM Authorization
Jump to navigation
Jump to search
Home > Administration > Business Process Designer > BPM Authorization | Index |
IntroductionThis BPM automation allows you to add authorizations to a workflow. One or more Hornbill Users can be added to a single authorization and the workflow is suspended until an outcome for the authorization has been provided. |
|
Authorization Owner
The owner of an authorisation is someone that that may not be participating in the authorization, but require visibility and control of the authorization. An example of this may be the manager of the person that is providing the authorization or someone who is overseeing the authorization and requires the ability to authorize on behalf of the authorizers.
- User
- Use this option to select from available users that have access to authorizations. Basic Users are not available to be selected.
- Variable
- Using variables can be a great way to allocate authorizers where the participants are not static. It is still important to remember that only Users with a Collaboration Subscription can participate and you need to assure that users that don't have a subscription are not accidentally allocated as an authorizer. The provided variable must contain the Users ID
Authorizers
In order for someone to participate in an authorization, they must be set up as a User and have a Collaboration subscription.
- User
- Use this option to select from available users that have access to authorizations. Basic Users are not available to be selected.
- Variable
- Using variables can be a great way to allocate authorizers where the participants are not static. It is still important to remember that only Users with a Collaboration Subscription can participate and you need to assure that users that don't have a subscription are not accidentally allocated as an authorizer. The provided variable must contain the Users ID.
- Weighting Level
- This is a powerful option to allow you to allocate the level that each individual contributes to the overall authorization. For each authorizer, a default 100% weight level is given. Independent of the number of authorizers, someone with a 100% weight level is able to complete the authorization on their own. If you have two authorizers, and both are set to a 50% weight level, then both authorizers must provide a response. When including multiple authorizers, you must assure that any combination of weighting levels must total up to 100% in order for the authorization to proceed.
Task
- Title
- The title of the Authorization is displayed in a number of places and will typically be a short descriptive title that clearly describes to the user what the authorization is for. This title will be available on the Hornbill Notifications, Email Notifications, Task View, and on the different apps that use authorizations.
- Category
- Set a category for the authorization, which can be viewed by the user within their Task List View
- Priority
- Setting a priority will allow users to view and filter their authorizations from their Task List View.
Outcome Settings
- Enable Tentative Authorization
- Authorize
- Reject
- Within your BPM workflow an Authorisation can be followed by a Decision Node where you can branch on the outcome of your authorization. This allows you to take different actions or paths based on the outcome.
Life Span Settings
- Start
- Due After
- Expires After