Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Configure Linked Records in Major Security Incident Management

Use Linked Records Configuration to store the information of task tables that can be used to link/promote/propose to Major Security Incident.

Role required: admin and sn_msi.workspace_admin.

Note: Admin can create the record and MSIM workspace admin can update the record.

Procedure

  1. Navigate to Major Security Incident Management > Linked Record Configurations.

    The Linked Record Configuration page displays.

Image omitted: linked-record-config.png
Linked Record configuration
  1. On the Linked Record Configuration page, click New

    Note: Ensure that the application is in Major Security Incident Management scope.

Image omitted: linked-record-new-form.png
Create record
  1. On the record configuration form, fill in the fields.
FieldDescription
Source TableIndicates the task table that must be linked and rolled up to Major Security Incident.
OrderAllows you to control the order of the current source table in MSIM workspace drop-down. Below is an example of the order.Refer to image 1 below, which is provided after this table.
Model ListViewSelect a view which can control the list layout that is shown in the Linked Record Modal List.
Can Promote to MSI

Select this check box to confirm whether the record is a primary record. Below is an example of Can Promote to MSI option selection.Refer to the following image 2, which is provided after this table.

If this check box is selected and the value is true, then:

  • you can directly propose and promote a source record to Major Security Incident using the classic environment actions with additional configurations.
  • you can link source records to major security incidents both from the classic environment and MSIM workspace.
  • Major Security Incident Management workspace linked record page displays the linked source table records. Note: If a record can be directly proposed/promoted as a Major Security Incident, then that record is a primary record. For example, in the Security Response task table configuration, the value of Can Promote to MSI is false as you can't directly promote Security Response task to Major Security Incident. Hence, it does not show up in the MSIM workspace linked record tab drop-down list.
MSI Field MappingWrite a script to map the source record fields to a newly created major security incident when the source tables record is in the process of being proposed or promoted.This script executes only when Can Promote to MSI value is true.
Image omitted: linked-record-config-order.png
Order of the dropdown list
Image omitted: linked-can-promote-to-msi.png
Can promote to MSI

Parent Topic:Rollup Framework for MSIM

Related topics

Configure Rollup Records in Major Security Incident Management

Configure List Layout in Major Security Incident Management

Rollup example use case implementation for a Security Case

Perform on demand atomic rollup