Difference between revisions of "BPM Authorization"

Revision as of 22:36, 22 July 2021

Home > Administration > Business Process Designer > BPM Authorization

Introduction

This 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.

Related Articles

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 required 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

Task

Title

Category

Priority

Outcome Settings

Enable Tentative Authorization

Authorize

Reject

Life Span Settings

Start

Due After

Expires After

Authorization Details

Set Stage Checkpoints

@@ Line 2: / Line 2: @@
 {{IntroAndLinks|This 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.|
 :* [[Business Process Designer]]
-:* [[Request Variables]]}}
+:* [[Request Variables]]
+:* [[External Authorisation]]}}
 == Authorization Owner ==
-{{bullet1|User|}}
+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 required the ability to authorize on behalf of the authorizers.
-{{bullet1|Variable|}}
+{{bullet1|User|Use this option to select from available users that have access to authorizations.  ''Basic Users'' are not available to be selected.}}
+{{bullet1|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.
 {{bullet1|User|Use this option to select from available users that have access to authorizations.  ''Basic Users'' are not available to be selected.}}
-{{bullet1|Variable|Using variables can be 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.}}
+{{bullet1|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.}}
 {{bullet1|Weighting Level|}}