Audit lifecycle status transitions¶
Premium-audit workflow detail.
| Field | Value |
|---|---|
| Operation ID | OP-010 |
| Trigger | Callers cancel, revise, complete, or derive audit status |
| Inputs | Audit state, result payloads, cancel reasons, and prior-audit context |
| Outputs | Updated status, result state, and duplicate-audit checks |
| Primary components | clsAudit.CancelAudit, DeriveStatusCode, NewRevisedAudit, DuplicateAuditExists |
| Entry point | Business\SAIF.Business.Policy.Audit.Premium\clsAudit.vb |
Steps¶
- Use the public lifecycle helpers on
clsAuditto cancel audits, derive status, seed revised audits, and manage result payloads. - Call the duplicate-audit query before creating or revising audits that could overlap an existing period and type.
- Drive status changes from the current audit dates, completion state, review state, and cancellation inputs.
- Traceability summary. Primary rules: BR-020, BR-021, BR-032, BR-035, BR-036, BR-037, BR-057, BR-058, BR-067. SQL and Oracle calls: SQL-001, SQL-002, SQL-004, SQL-006, SQL-007, SQL-018, SQL-019, SQL-020, SQL-021, SQL-022, SQL-023, SQL-024, SQL-030, SQL-031, SQL-070, SQL-071, SQL-072, SQL-076, SQL-078, SQL-088, SQL-089.
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([Trigger]) --> S1[Load context]
S1 --> S2[Run core logic]
S2 --> EndOk([Outcome])
Failure and edge-case behavior¶
- Review the linked rule and SQL documents for operation-specific validation failures and persistence behavior.
- Remote-wrapper SQL and not-found Oracle references are documented in the linked SQL and procedure pages where applicable.
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.Audit.Premium\clsAudit.vb