clsCaseNotesManager.DeleteNote¶
Delete a case note only when category and creator restrictions allow it.
| Field | Value |
|---|---|
| Operation ID | delete-case-note |
| Trigger | A case-note delete is requested. |
| Inputs | Current manager state, current claim/case context, and workflow-specific parameters or collections. |
| Outputs | Updated collections, messages, or side effects specific to the operation. |
| Primary components | clsCaseNotesManager.DeleteNote |
| Entry point | SAIF.Application.Claim.Legal\LegalNet\clsCaseNotesManager.vb |
Steps¶
- Locate the targeted note in the current note collection.
- If the note category is not
DOCCO, require the privilege needed to delete non-DOCCO notes. - If the note was created by
SYSTEM, block the delete unconditionally. - Delete the note only when both checks pass.
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([Trigger]) --> S1[Load current state]
S1 --> S2[Apply workflow rules]
S2 --> D{"Validation or security<br>issue?"}
D -->|Yes| EndErr(["Return message or block<br>action"])
D -->|No| EndOk(["Return updated workflow<br>state"])
Failure and edge-case behavior¶
- System-created notes can never be deleted.
- Unauthorized deletes leave the note collection unchanged.
Related documentation¶
- Index
- Operations and processes
- Business rules
- Security and authorization
- Database tables
- SQL catalog
- Procedures
- API reference
Sources¶
- SAIF.Application.Claim.Legal\LegalNet\clsCaseNotesManager.vb