Guard a rate file master delete¶
clsRateFileMaster.CanDeleteRateFileMasterRecord (clsRateFileMaster.vb:494-534)
| Field | Value |
|---|---|
| Operation ID | OP-008 |
| Trigger | Maintenance wants to delete a rate file |
| Inputs | WCIS rate file sequence number |
| Outputs | Boolean eligibility |
| Primary components | `clsRateFileMaster.CanDeleteRateFileMasterRecord (clsRateFileMaster.vb:494-534)` |
| Entry point | Business\SAIF.Business.Policy.Rating\clsRateFileMaster.vb |
Steps¶
- Execute the scalar probe
- Return
Falsewhen the count is greater than zero — the rate file still has manual classes - Wrap any exception as
ApplicationException(clsMessages.ErrMsgMediaFilesCheck & ex.Message, ex). - Use the related data-access statements and tables for this operation: SQL-032, MANUAL_CLASS_BASE.
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([Trigger: maintenance wants to delete a rate file]) --> S1[Execute scalar probe: count manual classes on the rate file]
S1 --> D1{Count greater than 0?}
D1 -->|Yes| S2[Return False - rate file still has manual classes]
D1 -->|No| S3[Return True - eligible for delete]
S1 -.->|Exception| S4[Wrap as ApplicationException ErrMsgMediaFilesCheck]
S2 --> Done([Boolean eligibility])
S3 --> Done
S4 --> Done
Failure and edge-case behavior¶
- Review the linked business rules and SQL documents for the validation or data-access conditions that can block this operation.
Related documentation¶
Note: Statements marked with * were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts. Statements marked with ** could not be confirmed; treat as unknown until verified.
Sources¶
Business\SAIF.Business.Policy.Rating\clsRateFileMaster.vb