Approval workflow for Purchase orders – Special and drop ship

Jira Code: TG-27

To create an approval workflow to approve/reject purchase orders

Purchase orders are created by the user and then it is made to approve/reject by the approver. This approver could either be the employee in the Next Approver field in a Purchase order or the supervisor of the employee who created the Purchase order. An email is sent to the approver with a link to view the record in NetSuite. Edit access will not be provided for the user once a Purchase order is submitted.

The approver has provision to approve or reject the Purchase order. If approved or rejected, employees are notified using an email with corresponding messages respectively. If rejected, the user can resubmit the request to approve the Purchase order and the same process continues.

Logic of Workflow

The workflow initiates from Initiation state. In this state, we set Pending Approval, Supervisor into the fields Approval Status and Next approver respectively. The above fields should be disabled and also, a Submit for Approval button has to be visible to the user who created the workflow.

On click of this button, the record moves to Pending Approval where the Purchase order will be available for the supervisor (approver) to approve or reject accordingly. If approver approves, Purchase order moves to Approved state and if rejects in any case, it moves to Rejected state. From both these states, user who created Purchase order will be notified via email. For a rejected Purchase order, it has the provision to resubmit the record using Resubmit for Approval button. Once a Purchase order is approved, the record will be locked.

Leave a comment

Your email address will not be published. Required fields are marked *