You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users sometimes upload executables or very large files via email or forms. This rule quarantines risky attachments by copying them off the original record, deleting the original, and keeping an audit trail.
5
+
6
+
## Where to use
7
+
- Table: `sys_attachment`
8
+
- When: before insert
9
+
- Order: early (for example 50)
10
+
11
+
## How it works
12
+
- Checks file extension and size against configurable thresholds
13
+
- Creates or reuses a quarantine record (table `x_quarantine_attachment` or default `incident` as a safe example)
14
+
- Copies the new attachment to the quarantine record via `GlideSysAttachment.copy`
15
+
- Deletes the original attachment via `GlideSysAttachment.deleteAttachment`
16
+
- Logs what happened with minimal, readable messages
17
+
18
+
## Configure
19
+
In the Business Rule:
20
+
-`BLOCKED_EXTS`: extensions to quarantine
21
+
-`MAX_SIZE_MB`: size threshold
22
+
-`QUARANTINE_TABLE`: table to hold quarantined items
23
+
-`ASSIGNMENT_GROUP_SYSID`: optional group to triage quarantines
0 commit comments