Page Comparison

For example :

• A Risk assessment with potential high hazard and risk levels might require "2 reviewers and 2 approvers" whereas another risk assessment with relatively lesser levels of potential hazard and risk would require only 1 reviewer and 1 approver. There might also be risk assessments which require only self approval.
• The Approval workflow/process required for any assessment thus depends on the type of the risk assessment and it is not necessary that all risk assessments would require the same persons/number of persons  to approve the assessment. 
• The same number of steps in the approval process may also vary with respect to the assessment type.

Thus, the limitation in the existing system is that it restricts the approval process to a single approval workflow. Hence, all risk assessments ,irrespective of their severity or importance need to be passed through the same approval workflow.

Approval Workflows :

1. Approval workflows in Risk Assessment will allow the users to configure various approval workflows ie select the required number of approvers, reviews and evaluators. 
2. In Module setup, there will be a set of pre-defined approval workflow definitions available for system administrators [Module Administrators, precisely] to choose from. These definitions can subsequently be used to configure various kinds of approval workflows.
3. Once any approval workflow is set up in the Module Setup ,the same would be available for the users in the risk assessment set up screen.
4. Users can create any number of workflows by choosing the number of approvers and reviewers in the module set up screen. 

Available  Workflow Definitions :

• The following workflows definitions will be available for the users to set up in the Module Setup : 
  
  • Submit ,Review,Submit ,Approve, Submit, Complete
  • Review and Approve
  • Self Approve
  • Submit ,Review and Approve
  • Submit and Approve
  • Submit,Review,Evaluate,Approve
• Each of the above mentioned approval workflow definitions can be further used to configure the actual workflow.
  • For example ,the users can define the number of Reviewers and number of Approvers in the Review and Approve workflow.
  • Similarly, the users can define the number of Reviewers ,Evaluators and Approvers in the Submit,Review,Evaluate,Approve workflow.
• Thus,every workflow definition can be used to configure any required workflow as per the business / functional requirement

• . 
• However,system will provide the flexibility to choose one created workflow in the

• Module Setup as a default workflow.
• If any workflow is defined as a default workflow in the

• Module Setup, then the same will be selected by-default

• in the Risk

• Assessment creation screen when the user is setting up a new assessment. 

Defining Approval Timelines :

• Users can define the time frame for approvals.Based on the values entered for fields of

• the approval due date will be calculated.
  • For example : In the screenshot below,the approval due date for the first review is two days after the assessment is submitted .The approval due date for the final approval is 3 days after the first review is completed.
• Based on the approval time frames,  the notifications for escalations will be generated from the system. 

Image Modified

• Below is the list of created workflows.As mentioned above any number of workflows can be created from the basic workflow definitions shown above.
• The default is marked for the 2 Reviewer ,1 Approver workflow below.

Image Modified

• In the Risk assessment Set up ,the workflow will show as shown below .
• Users will need to select the actual Reviewer and Approver names here
• Users also need to enter the Reviewer Due Dates and the Approval Due Dates.

Image Modified