other_stuff:remote_authorisation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
other_stuff:remote_authorisation [2026/01/16 17:18] – [Assign the users as authorisers] Gary Willettsother_stuff:remote_authorisation [2026/01/16 17:26] (current) – [Assign the users as authorisers] Gary Willetts
Line 98: Line 98:
   * **Uses auto-authorisation:** If this is checked then, after the number of days set in the **Auto-authorisation period (days)** field, any requisition lines that are waiting for authorisation by this user will be automatically authorised.    * **Uses auto-authorisation:** If this is checked then, after the number of days set in the **Auto-authorisation period (days)** field, any requisition lines that are waiting for authorisation by this user will be automatically authorised. 
     * **Auto-authorisation period (days):** The number of days after which any requisition lines waiting for authorisation by this user will be automatically authorised by the system.     * **Auto-authorisation period (days):** The number of days after which any requisition lines waiting for authorisation by this user will be automatically authorised by the system.
-  * **Approval level:** +  * **Approval level:** A whole number starting from 1. Level 1 authorisers will approve first. When they have approved then level 2 approvers can see and approve or reject a requisition. When they have approved a requisition then level 3 authorisers will be able to see and choose whether to approve or reject the requisition. The lines from the requisition on an assigned master list will only be authorised when a highest level authoriser has authorised them. There can be as many authorisation levels as required. A higher level authoriser will not be able to see requisitions awaiting approval unitl a lower level authoriser has approved it.
   * **Store approval:** This is not checked by default. If this is checked, you can set the rule to only need approval if the request comes from the stores checked in the list. If store approval and no masterlist is set, then all items for the requisition need approval. If masterlist and store approval are both set, then only require approval if from the requesting store and if the item is part of the masterlist. A request from facility (not a store) can also be included by adding a tag "remoteAuthorisation" in the name.   * **Store approval:** This is not checked by default. If this is checked, you can set the rule to only need approval if the request comes from the stores checked in the list. If store approval and no masterlist is set, then all items for the requisition need approval. If masterlist and store approval are both set, then only require approval if from the requesting store and if the item is part of the masterlist. A request from facility (not a store) can also be included by adding a tag "remoteAuthorisation" in the name.
     * **Allow to authorise existing pending requisitions:** If checked then the user can authrosie requidsitions that are already exist and are pending authorisation. If not checked then the user will only be able to authorise requisitions that are created after this time.       * **Allow to authorise existing pending requisitions:** If checked then the user can authrosie requidsitions that are already exist and are pending authorisation. If not checked then the user will only be able to authorise requisitions that are created after this time.  
  • Last modified: 2026/01/16 17:26
  • by Gary Willetts