SAIF.Business.Claim.SupportOrder business rules¶

This page captures business rules enforced by this library.

BR-001: Support-order updates require a current row version¶

Field	Value
Statement	Updating a support-order row requires the caller's `UPDATE_NUM` value to match the current database row.
Trigger	When `clsClaimSupportOrder` performs an update.
Enforcement	`clsClaimSupportOrder.Criteria.UpdateSQL` constrains the update by `WORKER_ID` and `UPDATE_NUM`.
Outcome	Stale updates affect zero rows and are treated as contention.
Tables	CL_CLAIM_SUPPORT_ORDER
SQL	SQL-006
Source	`Business\SAIF.Business.Claim.SupportOrder\clsClaimSupportOrder.vb`

Field	Value
Statement	Support-order insert and update operations must report exactly one affected row.
Trigger	After a support-order insert or update completes.
Enforcement	`clsClaimSupportOrder.AfterInsert` and `AfterUpdate` raise BOF contention errors when `RowsAffected <> 1`.
Outcome	Consumers receive an explicit concurrency failure instead of assuming success.
Tables	CL_CLAIM_SUPPORT_ORDER
SQL	SQL-001, SQL-006
Source	`Business\SAIF.Business.Claim.SupportOrder\clsClaimSupportOrder.vb`

Field	Value
Statement	Deleting a support-order connection must affect exactly one connection row.
Trigger	After a connection delete request finishes.
Enforcement	`clsClaimSupportOrderConnection.AfterDelete` raises a contention error when the delete does not affect one row.
Outcome	Delete failures are surfaced to the caller.
Tables	CL_CLAIM_SUPPORT_ORDER_CONN
SQL	SQL-008
Source	`Business\SAIF.Business.Claim.SupportOrder\clsClaimSupportOrderConnection.vb`

Field	Value
Statement	Creating a support-order connection must insert exactly one link row.
Trigger	After a connection insert finishes.
Enforcement	`clsClaimSupportOrderConnection.AfterInsert` raises a contention error when `RowsAffected <> 1`.
Outcome	Connection-save failures are visible to consumers.
Tables	CL_CLAIM_SUPPORT_ORDER_CONN
SQL	SQL-002
Source	`Business\SAIF.Business.Claim.SupportOrder\clsClaimSupportOrderConnection.vb`