Configure Linked Records in Major Security Incident Management

concept brazil Updated Sep 29, 2026 3 min read configuring-linked-records-in-major-security-incident-management.md
Raw file servicenow.com

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.

    [Omitted image "linked-record-config.png"] Alt text: Linked Record configuration

  2. On the Linked Record Configuration page, select New

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

    [Omitted image "linked-record-new-form.png"] Alt text: Create record

  3. On the record configuration form, fill in the fields.

Field

Description

Source Table

Indicates the task table that must be linked and rolled up to Major Security Incident.

Order

Allows you to control the order of the current source table in MSIM workspace drop-down. Following is an example of the order.Refer to image 1, which is provided after this table.

Model ListView

Select 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. Following 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. Therefore, it does not show up in the MSIM workspace linked record tab drop-down list.

Note: If this check box is cleared, the Model ListView and MSI Field Mapping fields are hidden on the form, because these fields apply only to records that can be promoted directly to a major security incident.

MSI Field Mapping

Write 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.

\[Omitted image "linked-record-config-order.png"\] Alt text: Order of the dropdown list
\[Omitted image "linked-can-promote-to-msi.png"\] Alt text: 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

Search documentation
Search document titles and file paths on the brazil branch