Rollup example use case implementation for a Security Case
On this page
Rollup example use case implementation for a Security Case
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.
-
Step 1. Create linked record configuration for a Security Case
-
Step 3. Create UI actions for the Source Table for a Security Case
-
Step 4. Create a view for a new Linked Record Tab for a Security Case
-
Step 5. Add Access Control Lists (ACLs) for Major Security Incident Management workspace users
-
Step 1. Create linked record configuration for a Security Case
Create a Linked Record configuration for a Security Case. -
Step 2. Create a view for modal window for a Security Case
Create a view for modal window for a Security Case. -
Step 3. Create UI actions for the Source Table for a Security Case
Create UI actions for the source table for a Security Case. -
Step 4. Create a view for a new Linked Record Tab for a Security Case
Customize the List layout for a Security Case table when it is displayed on the Link Records page with the Major Security Incident Management workspace. -
Step 5. Add Access Control Lists (ACLs) for Major Security Incident Management workspace users
Add Access Control Lists (ACLs) for Major Security Incident Management workspace users. -
Step 6. Create business rules for a Security Case
Create required business rules for a Security Case. -
Step 7. Create rollup record configurations
Create rollup record configuration to link and unlink additional records to MSI.
Parent Topic:Rollup Framework for MSIM
Related topics
{Configure Linked Records in Major Security Incident Management}[]
{Configure Rollup Records in Major Security Incident Management}[]
{Configure List Layout in Major Security Incident Management}[]
{Perform on demand atomic rollup}[]
Keep exploring.
Find another answer, or bring this documentation into your own tools.