Assign an audit to an auditor¶
Premium-audit workflow detail.
| Field | Value |
|---|---|
| Operation ID | OP-007 |
| Trigger | Assignment manager or caller chooses a specific auditor |
| Inputs | Audit, auditor, optional explicit assignment date |
| Outputs | Audit updated with auditor, office, assignment date, and assignment weight |
| Primary components | clsAudit.AssignAuditToAuditor |
| Entry point | Business\SAIF.Business.Policy.Audit.Premium\clsAudit.vb |
Steps¶
- Default the audit office from the fallback office when the explicit office is blank.
- Stamp the auditor identifier and either use the supplied assignment date or derive one from policy-region context.
- Recalculate assignment weight and add that workload to the auditor inventory.
- Traceability summary. Primary rules: BR-014, BR-015, BR-018, BR-019, BR-020, BR-021, BR-032, BR-035, BR-036, BR-037, BR-055, BR-057, BR-064, BR-065, BR-066. SQL and Oracle calls: SQL-001, SQL-003, SQL-004, SQL-005, SQL-008, SQL-018, SQL-019, SQL-020, SQL-021, SQL-022, SQL-023, SQL-024, SQL-026, SQL-032, SQL-076, SQL-077, SQL-079, SQL-088.
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