SAIF.Claims.Intake is an ASP.NET Web Forms application on .NET Framework 4.8
whose dependency surface splits cleanly in three. Six internal libraries carry
the intake capabilities themselves, four of which live in this repository and
two of which arrive as NuGet packages built elsewhere in the SAIF estate. The
external surface is small and old: Infragistics for the grid and date controls
used on every screen, log4net for logging, and the .NET Framework web service
stack. The application holds no direct database connection — all claim and
claimant data is read and written through the claims web service — so a
schema change reaches this application only through a service contract change.
Validates claim numbers, policy numbers, date-of-injury ranges, and required-field combinations before any service call is made.
SAIF.Claims.Intake.Web.Controls
Project Reference
SAIF.Claims.Intake
Shared user controls (claim header banner, claimant picker, jurisdiction dropdown) used across the nine intake screens. No documentation set was generated for this project.
Dependencies in this section are inherited from dependency framework libraries. They are not directly referenced by the application but are required at runtime through framework packages.
Dependency
Source framework
Type
Usage
SAIF.Framework.Core
SAIF.Framework.Validation
Transitive
Supplies ValidationComponentBase, framework tracing, and the initialization guard that the validation engine inherits.†
SAIF.Framework.Policy.Types
SAIF.Framework.Validation
Transitive
Provides the PolicyPeriod and JurisdictionCode value types the policy number and date-range rules evaluate.†
SAIF.Framework.Environment
SAIF.Framework.Core
Transitive
Resolves the environment key that selects the claims web service endpoint at application start.†
SAIF.Framework.Diagnostics
SAIF.Framework.Core
Transitive
Provides the trace listener that framework component trace entries are routed to.†
Pipe-delimited file of claims recorded since the previous run
SAIF.Claims.Intake.Capture
Written to the shared extract share each evening and consumed by the state reporting job that files first reports with the Oregon Workers' Compensation Division.
Adjuster queue notification
SMTP
Queue name, claim number, and severity indicator
SAIF.Claims.Intake.Triage
Sends a notification to the receiving adjuster team distribution list when a claim is triaged as urgent.
The Infragistics 20.1 control suite is out of support and is the single
largest upgrade blocker for this application. Every screen binds at least one
Infragistics control, so a version change is an application-wide regression
test, not a per-screen one.
log4net 2.0.15 is the version pinned across the SAIF .NET Framework 4.8
estate. Upgrading it here alone would produce assembly binding redirect
conflicts with SAIF.Framework.Validation.
SAIF.Framework.Validation is consumed as a NuGet package, so a rule change
reaches the intake screens only when the package version is bumped in the
project file and the application is redeployed. The batch consumers of the
same library can be running a different version.
SAIF.Claims.Intake.ServiceProxy is consumed as a same-repo NuGet package
rather than a project reference. Building the solution does not rebuild the
proxy, so a service contract change requires an explicit package rebuild and
version bump.
SAIF.Claims.Intake.Web.Controls has no documentation set, so the shared user
controls used on every screen are undocumented. It is a project reference in
the same repository and should be added to the documentation scope.
All five service endpoints are ASMX and are called synchronously on the
request thread with a 90-second timeout. A slow claims service therefore ties
up ASP.NET worker threads rather than failing fast.
AjaxControlToolkit 19.1.0 is used for a single confirmation popup. Replacing
it with a plain client-side confirmation would remove a dependency from the
application entirely.