---
title: SAIF.Business.CustomerContact dependencies
summary: Internal and external dependencies for this library.
status: draft
owner: SAIF
last_reviewed: 2026-07-24
library: SAIF.Business.CustomerContact
reference_type: package
---

# SAIF.Business.CustomerContact dependencies

## Internal dependencies

No `<ProjectReference>` elements exist in `SAIF.BOF.Business.CustomerContact.vbproj`; the internal library dependency is carried through a packaged NuGet reference.

| Dependency | Reference Type | Usage |
| --- | --- | --- |
| [SAIF.Business](../saif-business/overview.md) | NuGet Package | Provides shared BOF business abstractions and shared code-table/globalization helpers used by this library. |
| SAIF.BOF.Business | NuGet Package | (v2.1.23053.1) Packages the underlying SAIF business-layer types and carries transitive runtime configuration expectations. |
| SAIF.BOF.Framework | NuGet Package | (vSee `packages.config`) Supplies BOF persistence, criteria, and portal interfaces consumed by the aggregate and collection types. |
| SAIF.Framework.Common | NuGet Package | (vSee `packages.config`) Supplies common SAIF framework utilities inherited by the BOF layer. |

## External dependencies
| Dependency | Version | Usage |
| --- | --- | --- |
| Oracle.ManagedDataAccess | See `packages.config` | Registers the Oracle managed provider used by BOF criteria and helper SQL execution. |
| Newtonsoft.Json | See `packages.config` | Imported in `mdlCustomerContact.vb`, but a live JSON-processing path was not confirmed in the supplied findings.* |

## Dependency risks and notes
- This library has no directly owned configuration retrieval logic; required runtime settings are inherited transitively from the packaged SAIF business layer.
- `CCClaimDataApi` is consumed indirectly by `mdlCustomerContact`, so its endpoint and credentials must be registered by the hosting application even though this library does not declare them locally.*
- Other SAIF-internal packages referenced in `packages.config` were not expanded into detailed dependency documentation in the supplied findings, so their runtime configuration expectations remain unknown.**
- Duplicate top-level info-item source files are packaged beside the compiled `InfoItems` versions, which creates a maintenance risk if consumers misread the compile boundary.*

## Related documentation
- [Index](index.md)
- [Overview](overview.md)
- [Architecture](architecture.md)
- [Operations and processes](operations-processes.md)
- [Business rules](business-rules.md)
- [Database tables](database-tables.md)
- [SQL catalog](sql/index.md)
- [API reference](api/index.md)
- [Configuration](configuration.md)

> **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.CustomerContact\SAIF.BOF.Business.CustomerContact.vbproj`
- `Business\SAIF.Business.CustomerContact\packages.config`
- `Business\SAIF.Business.CustomerContact\app.config`
- `Business\SAIF.Business.CustomerContact\Web.config`
- `Business\SAIF.Business.CustomerContact\mdlCustomerContact.vb`
- `Business\SAIF.Business.CustomerContact\mdlCodeMaps.vb`
- `Business\SAIF.Business.CustomerContact\Customer\clsCustomer.vb`
- `Business\SAIF.Business.CustomerContact\Contact\clsContact.vb`