8.3. Investigation of the Sensitive Event

If the sensitive event is submitted for further investigation, the assigned investigator will receive a notification in their Pending Tasks, prompting them to handle the case.

*An email notification will also be sent to alert them of the task. For more information on email notifications and their role in the application, click here.

Clicking on either the subject in Pending Tasks or the button in the email will direct users to the Investigation of the Sensitive Event form. In this form, users can conduct and document the investigation of the event and take appropriate actions for its resolution.

*For guidance on common form functions, please refer to the dedicated section in the manual.

1. Investigation Notes: This is a rich text field that allows users to document findings, observations, and relevant details gathered during the investigation.
2. Investigation Files: This is a file attachment field that allows users to upload documents, evidence, or other files that support the investigation.
3. Contain / Correct Issue Owner: This is a single-select dropdown field that retrieves the list of active users, roles, and groups in the system. It allows for the selection of the party responsible for containing or correcting the sensitive event.
   

   !!To submit the event for immediate containment, users must select a task owner from this dropdown.

4. Action Items: This grid allows users to define actions aimed at addressing and resolving the reported event.
   • Add: This button allows users to add an action item to the report.
     • If selected, it will display the Add Action Item form.
       • This form is a modified version of the New Action form found in the Action Items application. Although adapted for use in various contexts, it retains almost all the original fields and functionalities.

       • Add Action Item – Key Form Features

         When the Add Action Item form is adapted for use in the Sensitive Event application, several configurations are applied automatically.
         

         
         

         • Source of the Action: By default, this field is set to Sensitive Event.

           **Please note that the grid for assigning a specific instance from the chosen source is not included in this form because it applies only to actions created independently. Actions generated from other application sources are automatically linked to the relevant instance.

           
           
         • Form Submission Options: At the bottom of the form, users have access to the following options:
           
           
           
           • Save and Return: This button saves the action item and returns users to the Review of the Sensitive Event form.
             
           • Save and New: This button saves the action item and opens a new form to create another action item.
           
           

         **As actions are added, they populate the grid. To perform additional customization and review, users can either click on the Edit ( ) icon beside each action or double-click on the action itself.
         
         
         

5. Delete ( ): This button allows users to delete an action.
   

   **To confirm the deletion of items in the grid, click on the Save Changes button or simply click outside the grid. To undo deletion, click either Discard Changes or Undo ( ).

6. Comment(s): This field allows users to provide comments or notes on the reported event. It also allows them to review and respond to comments left by previous stakeholders.
   

   **The Comment control functions similarly to a discussion board, facilitating collaborative discussions with stakeholders involved in the workflow.

7. Close (No Issue): This button allows users to close the report, indicating that no further action is necessary.
   • This concludes the Sensitive Event Management workflow.
8. Send for Immediate Containment: This button allows users to submit the event for immediate containment.
   • If selected, the assigned owner will be tasked with implementing the necessary containment or correction measures.
     
     *

     Users can opt for immediate containment if the issue requires urgent intervention to prevent further damage.

     • This approach prioritizes quickly stabilizing the situation, with further investigation or corrective actions addressed later, if necessary.
9. Execute Action(s): This button allows users to trigger the defined actions for execution.
   • If selected, the assigned owners (whether internal team members, external parties, or supplier representatives) will be responsible for executing the actions.
     
     *

     If the action item involves a Supplier Corrective Action Request (SCAR), the workflow will bypass the standard execution; instead, the supplier representative will be assigned the task of investigating the SCAR.

     • For more information on the Action Item Management workflow and its connection to the SCAR Management workflow, refer to the Action Items Application User Manual.