Prior to performing the following setup, please follow the Workflows Installation Guide for the technical setup.
In order to access Requisition Approval options, first the Workflows Module will need to be enabled. For more information on System Modules click here.
Verify that these modules are also installed: Email Notification Services, File Transfer Notification Services, HTTP Notification Services.
Once the Workflows Module has been enabled, navigate to System > Configuration.
Requisition Approval Configuration
Allows configuration of approval due dates and to customize the content of emails sent for Requisition Approvals. This configuration will be setup to default values - customization is optional. See the Configuration documentation for details on the available options.
In order to be able to send emails for approvals, the Email Configuration must also be populated.
Users that will be submitting requisitions for approval and those that will be approving requisitions do not need Workflow specific permissions, only access to Requisitions. Once Requisition Approval is enabled in the Workflows Configuration, located under the System/Configuration menu, the appropriate options will be added for those users with USAS_REQ access or greater.
Requisition Approver Only
If you would like to grant a user that does not enter Requisitions access to USAS-R only to approve Requisitions, a role with the following permissions can be created.
If the Approver should also have access to update the account code when approving, a role with the following permissions can be created.
Users with Administrator access will automatically be granted access to setup and manage the creation of Groups and Group Chains that determine the Approval path. The following options are available to grant additional access to users without the Administrator Role. In order to grant full access to setup Groups, Group Chains, and manage Requisitions submitted for approval, the following permissions would be needed:
In order to assign Group Chains to Users, the USAS_USER permission would also be needed. This permission is generally kept to Admin users for audit purposes. The following permissions could be used to create and manage the Groups/Group Chains and then an Admin user can assist with assigning the Group Chains to users.
Example Role Setup:
Standard Admin Permission
The USAS_WORKFLOWS_ADMIN permission will grant access to the Workflows > Workflows Admin page. This allows a user to view all in-progress requisitions, the requisition date, the requisitioner, and the due date.
The USAS_WORKFLOWS_BYPASS permission can be used to grant a user access to the Workflows > Workflow Bypass page. This permission will allow instant approval on a requisition while bypassing all other approvals defined in the associated Group Chain. This permission should be granted with caution and only to high level users.
Account Filters applied to a User will be used for Requisition Approval. An Approver must have at least Read Only access to the account code used on a Requisition in order to Approve OR Reject the transaction.
The Groups and Group Chains determine which users will be involved in the Approval process and in what order requisitions should be approved by those users.
A group is made up of one or more users that can be assigned as participants in a Group Chain of the Requisition Approval process. Groups may contain multiple users where all users must approve the requisition before the approval process continues or it may contain multiple users that only one user in the group approves the requisition before the approval process can move on.
See the Groups page for how to create a Group.
A group chain defines how the requisition flows from one group to another throughout the approval process.
See the Group Chains page for how to create a Group Chain.
In order for a User to be able to submit a requisition for approval to a Group Chain, this must be defined on their User setup.