Risk Matrix for Change using Custom Module

Risk Matrix for Change using Custom Module

Overview:

A risk matrix helps in identifying risks based on how likely they are to happen and how serious their impact could be. This makes it easier to decide which risks need urgent attention and which ones can be watched over time. It helps manage and reduce risks more effectively, make better decisions, and communicate clearly about risks.

Table of contents:
  1. Objective
  2. Procedure
    1. Configure the Custom Module
    2. Configure the Risk Matrix
    3. Create Custom Functions
    4. Create a Custom Trigger

Objective:

The goal is to create a risk matrix for changes that automatically calculates the risk of a change based on its priority and impact, similar to the Priority Matrix in the request module.

Procedure:

Step 1: Configure the Custom Module:

      Download and extract the attachment.

      Navigate to Admin > Developer space > Custom module > New, and create a new custom module as outlined below



      In "Form Customizer," create the following single-line text fields: Change Priority, Change Impact, and Change Risk. Refer to the provided screenshot for guidance.



      Go to Configurations > Roles, and associate the desired roles as specified in the screenshot below.



      Edit the custom fields and note their API Field Names for later use.



Step 2: Configure the Risk Matrix:

      Navigate to Admin > Customization > Custom Configurations and configure the risk matrix mapping as needed. Refer to the screenshot provided for detailed instructions.



Step 3: Create Custom Functions:

      Go to Admin > Developer space > Custom Functions > Global function > New > Paste the content from the attachment configuration.txt and save it with a name.

      Update the URL and the technician key accordingly. 

      Go to Admin > Change Custom Functions > Paste the content from the attachment (Update_risk_new.txt) and save it with a name.



      Ensure you modify the global function name, custom module name, and API Field Names as needed.

Step 4: Create a Custom Trigger:

      Set up a Change custom trigger as shown in the provided screenshot.



      By following these steps, we have implemented a risk matrix that automatically calculates the risk associated with changes based on their priority and impact. 


                  New to ADSelfService Plus?

                    • Related Articles

                    • Risk matrix for Change using Custom module

                      UseCase: Risk need to be calculated through Risk matrix (similar to Priority matrix in the request module) Steps to configure: Configure custom module as in the attached screenshot. 1. Navigate to Admin --> Developer space --> Custom module --> ...
                    • Change Risk Assessment Questionnaire using Custom module - Implementation steps

                      We’re excited to share a step-by-step guide( Attached) on implementing a Change Risk Assessment Questionnaire in ServiceDesk Plus using the Custom Module feature. This solution leverages Custom Modules, Change Additional Fields, and Field & Form ...
                    • Notification script using Custom function in custom trigger

                      This is applicable from 10600 builds. From 10600 , Business rules dont have Email notification feature. The same use case be achieved through Custom triggers feature as mentioned below. Script to enable notification of request creation using custom ...
                    • Update Change Roles using Change Custom Function

                      This is a sample Deluge script to set Line Manger field. When a Change Request is created, ChangeRequester's reporting_to user is set as the Line Manager automatically, using Change Custom Triggers. This is achieved by submitting a update request to ...
                    • Script to automatically populate the "Line Manager" role based on the Change Requester

                      "When a Change Request is created, the Line Manager role will automatically be assigned to the user specified in the 'Reporting to' field of the particular Change Requester. Tested in builds: 14300 and 14303. Download the scripts attached. Global ...