3.2.0.19

Owned by Malcolm Mackay (Unlicensed)
Last updated: May 22, 2016
3 min read

Purchase Requisitions

  •     Technical Review schemas made optional:

Previously if a workflow had a technical review, this had to be reviewed by the last reviewer in order to go to the next step in the workflow (Value review or Approval).

We have made this technical schema optional, which will enable an approval from a financial point of view, to start happening, without the need of a Technical review completion.

In the Technical Workflow Schema set-up screen, a check box called ‘Review Optional’, has been added.  

There could be 2 possible scenarios:

  1. If this check box is NOT selected, then all the business rules are as they currently are. Last technical review has to review, in order for the next step of the workflow to start (being this Value review or Approval).
  2. If this check box IS selected, then:
    • Value Review/Approval can start and Technical review status does not matter. A technical reviewer gets notified and can go and review (with Review button), but this review becomes irrelevant for the rest of the PR process.
    • The PR is Read only for the technical reviewer. Technical reviewer is not allowed to make any changes.
    • Cannot reject or send back. Only Review button should be available.
    • Workflow schema history on the PR will still be updated to reflect the review in the case the user actually reviewed. Just for audit/trace purposes.
    • Once the PR has been approved, it will no longer appear in the optional technical reviewer's list to be reviewed even if it is still pending. This is because the status of the PR has changed from 'I' (In Progress) to 'A' (Approved).
  • Alternative PR Approvers:

Users with role ‘Purchase Requisition Administrator’, now have the ability to assign a PR that is to be approved, to a different approver, in case the assigned approver is not available, and has not set the delegation. Alternative approvers will be set in the Workflow schema, with the same limit value as the person that is the original approver. All approvers will be set in a sequence. Sequence must be different and in ascending order, for ALL approvers in the workflow schema, starting at seq 1.

Once the PR is assigned to an alternate approver, the original approver, will become one of the possible approvers in the list, in the case the PR has to be reassigned to another approver again.

 

Purchase Requisition Administrator will find the PR under Approvals & Workflow/Review/Approval List and open it. In the 'Workflow/Messages' screen, the approver name will be a drop-down which will show the available alternative approvers and their $limit. A new save button should be added to the screen. The new approver should receive an email notification with the PR to be approved.

Once the PR has been approved, it will no longer appear in the optional technical reviewer's list to be reviewed even if it is still pending. This is because the status of the PR has changed from 'I' (In Progress) to 'A' (Approved). 

The logic for being able to re-assign an Approval is based on the 'PR Admin Review/Approval' Permission, which is part of the PR Administrator role. If the user has this Permission for the given PR then they will be able to change the assigned Approver for 'Pending' Approvals. 

 

 

 

Once the PR is assigned to someone else, the original approver, will become one of the possible approvers in the list, in the case the PR has to be reassigned to another approver again.

Purchase Requisition Administrator will find the PR under Approvals & Workflow/Review/Approval List and open it. In the Workflow/Messages screen, the approver name should be a drop-down which will show the available alternative approvers and their $limit. A new save button should be added to the screen.

Â