SAIF.Business.Claim.SupportOrder dependencies

Internal dependencies

Dependency	Reference Type	Usage
SAIF.Business	NuGet Package (same-repo)	Supplies shared business-layer utilities used by claim BOF components.
SAIF.Resources	NuGet Package (same-repo)	Provides shared resource and constant assets.
SAIF.BOF.Framework	NuGet Package	Provides BOF base classes, criteria contracts, and portal infrastructure.
SAIF.Framework.Common	NuGet Package	Provides common framework helpers.

External dependencies

Dependency	Version	Usage
Oracle.ManagedDataAccess	21.5.0	Provides Oracle connectivity for support-order CRUD operations.
FluentValidation	5.6.2.0	Supports validation infrastructure in the packaged component.
log4net	2.0.14	Provides logging support for the packaged component.
BouncyCastle	1.8.9	Provides cryptography support pulled into the package set.

Transitive dependencies

Dependencies in this section are inherited from dependency framework libraries. They are not directly referenced by this library but are required at runtime through framework packages.

Dependency	Source framework	Type	Usage
clsBusinessBase	SAIF.Framework.Core	Transitive	Supplies entity edit-state management and rules-engine ownership.†
clsBusinessCollectionBase	SAIF.Framework.Core	Transitive	Supplies traversal, deleted-item tracking, and save orchestration for collections.†
IBusinessCriteria	SAIF.Framework.Core	Transitive	Defines the CRUD SQL contract implemented by support-order criteria types.†
IDataPortalInfo	SAIF.Framework.Core	Transitive	Routes support-order requests to the configured data-access layer.†
IDataRequest / clsSAIFDataReader / clsSmartDate	SAIF.Framework.Core	Transitive	Provide request, reader, and date-helper behavior in the BOF persistence path.†

Dependency risks and notes

• The library is tightly coupled to the CL_CLAIM_SUPPORT_ORDER and CL_CLAIM_SUPPORT_ORDER_CONN schemas because CRUD is implemented as inline SQL.
• Optimistic concurrency relies on UPDATE_NUM; stale clients will fail updates by design.
• Support-order and connection lifecycles are separate entities, so consumers must persist both layers consistently when editing linked claims.

Related documentation

• Index
• Overview
• Architecture
• Operations and processes
• Business rules
• Database tables
• SQL catalog
• API reference

Note: Statements marked with † are derived from dependency library documentation via the Legends CLI. They describe inherited behavior from the indicated origin library and should be verified if the dependency version changes.

Sources

• Business\SAIF.Business.Claim.SupportOrder\clsClaimSupportOrder.vb
• Business\SAIF.Business.Claim.SupportOrder\clsClaimSupportOrderCollection.vb
• Business\SAIF.Business.Claim.SupportOrder\clsClaimSupportOrderConnection.vb
• Business\SAIF.Business.Claim.SupportOrder\clsClaimSupportOrderConnectionCollection.vb
• Business\SAIF.Business.Claim.SupportOrder\packages.config
• Business\SAIF.Business.Claim.SupportOrder\SAIF.BOF.Business.Claim.SupportOrder.nuspec