---
sourceDocument: Zurich Security Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/security-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Configure Rollup Records in Major Security Incident Management

# Configure Rollup Records in Major Security Incident Management {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Configure Rollup Records in Major Security Incident Management

This guide explains how to configure rollup records in Major Security Incident Management (MSI) within ServiceNow.
Rollup records control the information aggregated when a source record is linked, proposed, or promoted as a Major Security Incident.
Proper configuration enables efficient data consolidation relevant to major security incidents, improving incident tracking and management.
Show full answer Show less  
**Roles required:** admin and snmsi.workspaceadmin. System administrators can create configurations, while MSI workspace admins can update them.

## Configuration Process

* Navigate to **Major Security Incident Response \> Linked Records Configuration**.
* Select or create a linked record configuration.
* In the **Rollup Record Configuration** section, create a new rollup record.
* Fill in necessary fields including Name, Active status, Linked Record Configuration reference, and Source Table (read-only).

## Rollup Types and Fields

There are two rollup types:

* **Relationship:** Data appears as a related list. This type enables a script-based rollup where you write a script to retrieve and aggregate data from relationship tables into the Linked Record (snmsim2mchild) table.
* **Reference:** Data is present in a reference field on the source table form. You select a Source Field (reference field in the source table) and a Target Field (reference field in the Linked Record table) to map the data directly.

## Scripting for Relationship Rollups

If you choose the **Relationship** rollup type, you must write a script that:

* Receives inputs: `sourceSysId` (Sys ID of the source record) and `msiSysId` (Sys ID of the major security incident).
* Queries ServiceNow relationship tables to gather relevant data linked to the source record.
* Uses the MSIRollupEngine utility to roll up the data into the Linked Record (snmsim2mchild) table.
* Does not return any output value.

## Practical Use

This configuration allows ServiceNow customers to:

* Control exactly what information is consolidated when incidents are linked or promoted in MSI.
* Customize data rollup either by direct field reference or by scripting complex relationships.
* Ensure accurate and relevant data aggregation for improved incident management visibility and reporting.

## Related Configuration and Use Cases

* Configure Linked Records in Major Security Incident Management.
* Configure List Layout in Major Security Incident Management.
* Implement rollup examples for Security Cases.
* Perform on-demand atomic rollups.  
Configure Roll up records in Major Security Incident Management to control the
information, which will be rolled up when the source record is linked/proposed/promoted as Major
Security Incidents.  
Role required: admin and sn_msi.workspace_admin.  
Note:  
The system admin can create the record and MSI workspace admin can update it.  
Procedure

1. Navigate to Major Security Incident ResponseLinked Records Configuration. The Linked Record Configurations page displays.
2. Select or create a new linked record and navigate to the Roll up Record Configuration section from the same page.Figure 1. Rollup Record Configuration section
3. Select New.

4. On the configuration page, fill the details.{#roll-up-record-configuration-in-major-security-incident-management__table_sbs_d1v_h5b__entry__2}

   | Field Name | Field Description |
   |-|-|
   | Name | Indicates the name of the rolling up record. |
   | Active | Select this check box to implement the current configuration when rollup of source record happens. |
   | Linked Record Configuration | Indicates a unique number, which refers to your parent linked records configuration and read-only. |
   | Source Table | The source table name used in the Linked Record configuration, which is read-only. |
   | Rollup Type | Describes the type of information which should be rolled up. * Relationship: Select this option if the data need to be present as a related list. * Reference: Select this option if the data is present as a reference field on the source table form. {#roll-up-record-configuration-in-major-security-incident-management__ul_gzn_y1v_h5b} |
   | Rollup Script | If the rollup type is: Relationship, then the Rollup Script field is enabled, which allows you to write script and can be used to rollup information. Here the script will receive the inputs which contains information of the source record and major security incident. The script should be able to find the information from the relationship tables and rollup to Linked Record (sn_msi_m2m_child) table. |
   | Source Field | If the rollup type is: Reference, then the Source Field is available. This enables you to select the Source Table reference field which contains the information that needed to be rolled up. |
   | Target Field | If the rollup type is: Reference, then the Target Field is available. This enables you to reference field from the Linked Record(sn_msi_m2m_child) table and will store the data which is present in the selected Source Field and in the Source Table record. |
   [Table 1. Rollup Record Configuration]

   {#roll-up-record-configuration-in-major-security-incident-management__table_sbs_d1v_h5b}
{#roll-up-record-configuration-in-major-security-incident-management__ol_pry_3ws_h5b}

Writing script for rollup
{#roll-up-record-configuration-in-major-security-incident-management__table_zmh_yjc_35b__entry__2}

| Name | Description |
|-|-|
| Inputs | * sourceSysId: Sys ID of source table record which is either getting linked / proposed / promoted. * msiSysId: Sys ID of major security incident to which source record is getting linked / proposed / promoted. {#roll-up-record-configuration-in-major-security-incident-management__ul_bfc_1kc_35b} |
| Output | No output return value. |
| Responsibility | Script should rollup information to Linked Record(sn_msi_m2m_child) table. * Use sourceSysID to query data from ServiceNow relationship tables. * After the data is fetched, roll up the data to a Linked Record (sn_msi_m2m_child) using MSIRollupEngine utility to roll up data. {#roll-up-record-configuration-in-major-security-incident-management__ul_mkc_fkc_35b} |
[ ]

{#roll-up-record-configuration-in-major-security-incident-management__table_zmh_yjc_35b}
**Related concepts**   

* [Configure Linked Records in Major Security Incident Management](https://www.servicenow.com/docs/IKfS4xCWgPLYWEHMw0YrrA "Use Linked Records Configuration to store the information of task tables that can be used to link/promote/propose to Major Security Incident.")
* [Configure List Layout in Major Security Incident Management](https://www.servicenow.com/docs/FxyvRX__TrCKA2iVvIVKYw "Configure list layout to customize the layout and labels used in Major Security Incident Management workspace such as Incident Impact, Linked Records, and Threat Intelligence tabs.")
* [Rollup example use case implementation for a Security Case](https://www.servicenow.com/docs/jvyHFKYepPVr748jH1uoDQ "The following steps explain an example use case on how to add support to link/propose/promote to Major Security Incident for a Security Case table.")
* [Perform on demand atomic rollup](https://www.servicenow.com/docs/~iFY0HqpO4VZRSyU7OY2fw "Rollup framework cannot handle updates to the existing linked records. In such cases, on demand atomic rollup should happen for linked records, which can be achieved via business rules.")

*[\>]: and then