Non-Conformance Report (NCR) Advanced Approval Workflow

The NCR Advanced Approval Workflow is for projects that require a more comprehensive approval workflow for their NCR that include an Internal Review Process and a Feedback Loop or Conditional Completion, in addition to the Standard Approval Review process. 

You'll find three videos explaining the three main parts of the workflow:

• Internal Review Process
• Standard Approval Review
• Conditional Completion

At the end of this article, you can also download the NCR Advanced Approval Workflow template.

Related Links:

Create Basic Workflows for Approvals

Create Advanced Workflows for Approvals

Status and Actions 

Before you start watching the videos, it is important that you understand the components of an approval workflow - namely Steps ('status') and Actions. 

Steps are represented by oblongs / rectangles - click on each Step to view and edit its properties on the right panel:

Actions are represented by the joining arrows between Steps - click on each arrow to view and edit its properties on the right panel:

Part 1: Standard Approval Review 

Key Points For Part 1: 

• Actions lead one Step to the next
• 'Complete' Steps have no actions leading from them i.e. Rejected, Manually Approved and Released
• The main differences amongst these three statuses (Rejected, Manually Approved and Released) are:
  • who can perform the action; and
  • the Step ('status') of the approval once completed.
• Step properties:
  • 'Alert step' - highlights approval red, identifying this approval requires urgent attention and action; and
  • 'Complete' - indicating it is an endpoint and will not proceed further in the workflow.
• Action Properties:
  • 'Requires Comment' - when this action is selected during the workflow, the user will be required to add a comment (minimum 25 characters)
  • 'Priority' - this determines the order in which the action will appear in the action drop-down menu when actioning the Approval
  • 'Requestor Can Action' - user requesting the Approval can assign this action
  • 'Addressee Can Action' - user/s addressed in the Approval can assign this action
  • 'Users Can Action' - nominated user/s that can assign this action, regardless of whether they are a Requestor or Addressee. Each User listed will be notified when an Approval is raised that they can action.
  • 'Roles Can Action' - nominated Role/s that can assign this action, regardless of whether they are a Requestor or Addressee.  Notifications will not be automatically sent to everyone with this role. 

Part 2 : Conditional Completion or Feedback Loop

Key Points For Part 2 : 

• Conditional Released (no resubmit) – Requires comment to state what the condition is, the requestor can then move it to 'Released'
• Conditional Released ( resubmit) - Addressee has requested a resubmit when the condition is complete, and can be released when the condition completion is accepted. Alternatively, it can move to 'Review Required' if the condition completion is not accepted. 
• Resubmit is basically a feedback loop that directs the approval for resubmission until the condition is met or the action is taken to rectify the issue. 
• Action Permissions for Conditional Completion are mostly: Requestor can action and/or Addressee can action
• Do not use 'Users can action" or "Roles can action" to replace users who have left the project. You can bulk update the approval requestors via the Approval Register. Refer to Reassign an Approval to a new Requestor / Reassign an Approval to a new Requestor (D)  

Part 3: Internal Review or Pre-Approval Process

Key Points for Part 3: 

• Internal Review Request - Step Properties - Private, First Step
• Private - Until a non-private step is reached, the approval will not appear on the register for a collaborator. It is also hidden from users who do not have the authority 'Approval View Private' in their roles.
• For privacy reasons, Internal Review Request can be made available to specific users only for action. This is one such situation when you can use the action permission 'Users can action' and 'Roles can action'.
• Please note that 'Roles can action' will not send out any automatic notification as it targets every user in that role. You will need to send out the notification manually. 'Users can action' will notify the users selected.   
• Updating the users in 'User can action' will not change the requestor of existing approvals. You'll need to update via the approval register.  Refer to Reassign an Approval to a new Requestor / Reassign an Approval to a new Requestor (D)  

 

Full Approval Process Demo using the NCR Advanced Approval Workflow

Download the NCR Advanced Approval Workflow Template 

For your convenience, you can also the download the NCR Advanced Approval Workflow template (cpx. file) attached at the end of this article into your CivilPro and use that as a base template to customize to your requirements. 

Select the relevant project, and navigate to Other Setup, then Approval Workflows register. 

Go to Global Action and select Import Templates. Select the cpx file from the folder where you have downloaded.  

Tip: if you can't see the options under Global Action, select and unselect an item on the register.