---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/security-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia 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}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

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.  
Nota:  
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.Figura 1. Rollup Record Configuration section
3. Click 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. |
   [Tabela 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}
**Conceitos relacionados**   

* [Configure Linked Records in Major Security Incident Management](https://servicenow-prod.fluidtopics.net/bDECzoGEKRbmWBIVzw0cdQ "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://servicenow-prod.fluidtopics.net/Cpj_de835MN323W_djfGcA "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://servicenow-prod.fluidtopics.net/pvOTI9IuUp80g~01dhrl9Q "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://servicenow-prod.fluidtopics.net/WJk5fu26crzPCgosT30w6w "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.")