Step 6. Create business rules for a Security Case
Create required business rules for a Security Case.
Before you begin
Role required: admin
Create the three following business rules for the new source table Security Case (sn_ti_case). These business rules are required to maintain the consistency in behavior with base system provided source table such as Security incident (sn_si_incident).
Business rules for the new source table:
- Deactivate link when inactive: Once the security case is closed, related information will no longer be shown in Major Security Incident Management workspace page.
- Sync up team info on update: Major Security Incident details tab shows the information about the all the active teams and users working on different tasks. Once we update assigned to user or assignment group is changed in the security case, we need to update security case team information in the Major Security Incident active team section. These business rules will update new assigned to user and assignment group in the active team section.
- Sync up team info on delete: Major Security Incident details tab shows the information about the all the active teams and users working on different tasks. Once we close the security case, we no longer need to show security case team information in the Major Security Incident active team section. These business rules will remove the assigned to user and assignment group from the active team.
Create business rules for new source table:
Procedure
-
Navigate to System definition > Business Rules.
-
Run the filter option to filter business rules criteria with below information:
- Name: Deactivate link when inactive
- Table: sn_si_incident [Omitted image "business-rules-step6.png"] Alt text: Business rules
-
Open record and change the table name to a new source table: sn_ti_case.
-
Select and hold (or right-click) the menu on the page and select Insert and Stay to create the record.
[Omitted image "change-table-name-step6.png"] Alt text: Change the table name
-
Repeat the procedure for another two business rules as well.
- Sync up team info on delete
- Sync up team info on update
Parent Topic:Rollup example use case implementation for a Security Case
---
title: Step 6. Create business rules for a Security Case
description: Create required business rules for a Security Case.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/security-management/security-incident-response/creating-required-business-rules-for-security-case.html
release: brazil
product: Security Incident Response
classification: security-incident-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Rollup example use case implementation for a Security Case, Rollup Framework for MSIM, Major Security Incident Management, Security Incident Response, Enterprise security case management applications, Security Operations]
---
# Step 6. Create business rules for a Security Case
Create required business rules for a Security Case.
## Before you begin
Role required: admin
Create the three following business rules for the new source table Security Case \(sn\_ti\_case\). These business rules are required to maintain the consistency in behavior with base system provided source table such as Security incident \(sn\_si\_incident\).
Business rules for the new source table:
1. **Deactivate link when inactive**: Once the security case is closed, related information will no longer be shown in Major Security Incident Management workspace page.
2. **Sync up team info on update**: Major Security Incident details tab shows the information about the all the active teams and users working on different tasks. Once we update assigned to user or assignment group is changed in the security case, we need to update security case team information in the Major Security Incident active team section. These business rules will update new assigned to user and assignment group in the active team section.
3. **Sync up team info on delete**: Major Security Incident details tab shows the information about the all the active teams and users working on different tasks. Once we close the security case, we no longer need to show security case team information in the Major Security Incident active team section. These business rules will remove the assigned to user and assignment group from the active team.
**Create business rules for new source table:**
## Procedure
1. Navigate to **System definition** > **Business Rules**.
2. Run the filter option to filter business rules criteria with below information:
- **Name**: Deactivate link when inactive
- **Table**: sn\_si\_incident
\[Omitted image "business-rules-step6.png"\] Alt text: Business rules
3. Open record and change the table name to a new source table: sn\_ti\_case.
4. Select and hold \(or right-click\) the menu on the page and select **Insert and Stay** to create the record.
\[Omitted image "change-table-name-step6.png"\] Alt text: Change the table name
5. Repeat the procedure for another two business rules as well.
- Sync up team info on delete
- Sync up team info on update
**Parent Topic:**[Rollup example use case implementation for a Security Case](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/security-incident-response/use-case-for-a-security-case.md)
| title | Step 6. Create business rules for a Security Case |
| description | Create required business rules for a Security Case. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/security-management/security-incident-response/creating-required-business-rules-for-security-case.html |
| release | brazil |
| product | Security Incident Response |
| classification | security-incident-response |
| topic_type | task |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | Rollup example use case implementation for a Security CaseRollup Framework for MSIMMajor Security Incident ManagementSecurity Incident ResponseEnterprise security case management applicationsSecurity Operations |