The application depends on six internal SAIF packages and seven external packages, calls one REST API through SAIF.Web.API.Clients, and consumes one SOAP service. It has no database dependency.
This application: ImagingApiClient.MarkRetentionClaimsAsProcessed → SAIF.Web.API.Clients: JsonHttpClient.PutJson<T>
Marks a batch of retention records as processed†
JsonHttpClient authenticates with NTLM, sends Client-Name, Application-ID, and Client-User headers, and retries up to three times after one second on status 0, 502, 503, and 401.† The leading slash differs between the two paths as written in source; see Tech debt.
All six internal packages are declared as stable versions in the project file, which sets RestoreProjectStyle to PackageReference. The legacy packages.config was removed, so the project file is the only package manifest, and its versions are expected to govern restore.* What the CI restore step runs is defined outside this repository.* See Tech debt.
SAIF.Framework.Data.NHibernate and SAIF.HashUtil are unused, and the NHibernate stack adds dependencies the application does not need.
There are no database connections, so no database section applies.
Note: Statements marked with † are derived from dependency library
documentation via the Legends CLI. Statements marked with * were inferred
from code structure or contextual evidence.