Step 1. Create linked record configuration for a Security Case
Create a Linked Record configuration for a Security Case.
Before you begin
Role required: admin and sn_msi.workspace_admin
Note: The system admin can create the record and MSI workspace admin can update it.
Procedure
Search for the Linked Record Configuration from the left navigation.
Select New.
Fill the form with the required columns and write a field mapping script.
Fill the form
- You have now created a linked record configuration for the Security Case by adding the values as described in the following table.
Create
| Name | Description |
|---|---|
| Source Table | Security Case \(sn\_ti\_case\). Here in this example, link/promote/propose a security case as MSI. |
| Order | Input value: 300Note: Lower the order takes precedence over higher orders. As a Security Case have a higher order than the Security Incident and Remediation Task, it will appear in the last sequence. |
| Can promote to MSI | True, select this check box to promote the security case to MSI.Note:
|
| Modal List View | msim_sn_ti_case_model_viewNote: This view contains fields and fields order shown in list view on the Link Record Modal in MSIM workspace. For more information, see Step 2. Create a view for modal window for a Security Case Refer to the below image 2 to view from the Linked Records page. |
| Field Mapping Script | This script describes the fields from source tables record will mapped to newly created major security incident when source tables record is getting proposed or promoted.which will receive inputs: - sourceGr: security case glide record object - msiGr: major security incident glide record object Script will read from the short description of the security case and copy it over as title to major security incident. |
Parent Topic:Rollup example use case implementation for a Security Case