Skip to content

Commit f057899

Browse files
authored
Create README.md
1 parent a81a30b commit f057899

File tree

1 file changed

+14
-0
lines changed
  • Server-Side Components/Business Rules/Attachments check High-Risk or High-Impact Change request

1 file changed

+14
-0
lines changed
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
This Before Update business rule acts as a safeguard in a Change management process,
2+
ensuring that critical changes(those marked as high impact or high risk)
3+
are properly documented before progressing to key implementation stages.
4+
5+
**What It Does**:
6+
-The BR triggers before a change request record is updated, specifically when the state changes to either Scheduled or Implement.
7+
8+
-It checks whether the change is classified as high impact or high risk.
9+
10+
-If the change meets either of those criteria, it verifies that at least two attachments are present on the record.
11+
These attachments are expected to be essential supporting documents like an Implementation Plan or Backout Procedure.
12+
13+
-If the required documentation is missing, the rule blocks the state change and displays an error message to the user,
14+
preventing the change from moving forward until compliance is met.

0 commit comments

Comments
 (0)