SAIF.Business.Claim.Person dependencies

Internal dependencies

Dependency	Reference Type	Usage
SAIF.BOF.Business.Claim	NuGet Package (same-repo)	Provides shared claim-domain business-layer conventions consumed by the person library.
SAIF.BOF.Business	NuGet Package (same-repo)	Supplies shared business-layer utilities and common claim patterns.
SAIF.BOF.ResourceFiles	NuGet Package (same-repo)	Supplies shared resource and constant assets.
SAIF.BOF.Framework	NuGet Package	Provides BOF base classes, criteria contracts, and data-portal services.
SAIF.Framework.Common	NuGet Package	Provides common framework helpers used across BOF packages.
SAIF.Web.API.Clients	NuGet Package	Provides client infrastructure associated with the CCClaimDataApi DTO surface.

External dependencies

Dependency	Version	Usage
Oracle.ManagedDataAccess	21.5.0	Provides Oracle connectivity for person, history, and phonetic-name operations.
FluentValidation	5.5.0.0	Supports validation infrastructure in the packaged library.

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	Hosts business-object edit lifecycle and rules-manager ownership for entity objects.†
clsBusinessCollectionBase / clsBusinessCollection(Of T)	SAIF.Framework.Core	Transitive	Provides traversal, deleted-item tracking, and typed collection behavior for child lists.†
IBusinessCriteria	SAIF.Framework.Core	Transitive	Defines the CRUD SQL contract implemented by nested criteria classes.†
IDataPortalInfo	SAIF.Framework.Core	Transitive	Routes scalar and result-set requests to the configured data-access layer.†
clsAddress / smart-value types	SAIF.Framework.Core	Transitive	Supplies shared address behavior and DB-null-safe value wrappers used by person records.†

Dependency risks and notes

• Availability of pk82028_phonetic_name.createPhoneticName directly affects name-save behavior.
• Person history tables and the primary CL_CLAIM_PERSON row must remain transactionally aligned during updates.
• Framework-owned address and smart-value behavior is inherited rather than implemented locally, so framework changes can alter runtime semantics.

Related documentation

• Index
• Overview
• Architecture
• Operations and processes
• Business rules
• Database tables
• SQL catalog
• Procedures
• 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.Person\clsWorker.vb
• Business\SAIF.Business.Claim.Person\clsClaimPersonName.vb
• Business\SAIF.Business.Claim.Person\clsClaimPersonAddress.vb
• Business\SAIF.Business.Claim.Person\clsClaimPersonAuditHistory.vb
• Business\SAIF.Business.Claim.Person\clsPersonTaxIDHistory.vb
• Business\SAIF.Business.Claim.Person\clsAwardEligibility.vb
• Business\SAIF.Business.Claim.Person\clsBeneficiary.vb
• Business\SAIF.Business.Claim.Person\clsGuardian.vb
• Business\SAIF.Business.Claim.Person\clsPowerOfAttorney.vb
• Business\SAIF.Business.Claim.Person\clsWorkerHealthIssue.vb
• Business\SAIF.Business.Claim.Person\CCClaimDataApi\clsBeneficiaryAddress.vb
• Business\SAIF.Business.Claim.Person\packages.config
• Business\SAIF.Business.Claim.Person\SAIF.BOF.Business.Claim.Person.nuspec