Application dependencies

Claims Legal depends on the SAIF BOF framework, Oracle and SQL Server BDS data access, Infragistics 11.1 UI controls, and several external APIs and services for correspondence, reporting, and downstream claim/policy integration.

Internal library dependencies

Dependency type	Libraries	Role in Claims Legal
Application framework	SAIF.Application, SAIF.Application.Claim	Base manager lifecycle, claim context, security, data portal access
Legal domain model	SAIF.Business.Claim.Legal	Legal case, appeal, schedule, cost, acknowledgement, assignment, and reference-data objects
Policy context	SAIF.Business.View.Policy, SAIF.Business.Policy, SAIF.Business.Utilities	Policy header data, policy security, affiliations, policy lookups, shared formatting
Presentation helpers	SAIF.Presentation.Web.Controls.PopUps.Infragistics111	Popups, message controls, image-move and notify workflows
Document and batch services	SAIF.Services.Appworx, SAIF.Services.Printing, SAIF.Services.Export, SAIF.Services.Imaging.Import	Letter jobs, PDF preview, report generation, CSV export, imaging payloads

Package dependencies

Package	Version	Purpose	Consuming libraries
SAIF BOF framework packages	unspecified*	clsBusinessBase, IDataPortalInfo, security principal, environment service, logging, mail, data portals	SAIF.Application, SAIF.Application.Claim, SAIF.Application.Claim.Legal, SAIF.Business.Claim.Legal
Oracle Managed Data Access	unspecified*	Oracle database connectivity for legal-case and policy retrieval	SAIF.Application.Claim.Legal, SAIF.Business.Claim.Legal, SAIF.Business.View.Policy
Infragistics 11.1 Web UI	11.1	WebDataGrid, WebHierarchicalDataGrid, WebDateTimeEdit, WebNumericEdit, resizing extenders	Legal, SAIF.Presentation.Web.Controls.PopUps.Infragistics111
System.Messaging	unspecified*	MSMQ-backed asynchronous document distribution	SAIF.Services.Printing
Newtonsoft.Json, RestSharp, System.Text.Json, ASP.NET Web API client assemblies	unspecified*	Support libraries for API clients and legacy framework packaging	Multiple libraries across application and service tiers*
Microsoft Exchange Web Services assemblies	unspecified*	Attorney schedule and calendar synchronization support	SAIF.Business.Claim.Legal

API dependencies

API	Type	Direction	Purpose	Consuming libraries
Guidewire matter and activity APIs (GwMatterApi, GWActivityData, GWClaimDataApi)	REST	Outbound	Matter synchronization, activity creation, WCD number updates	SAIF.Application.Claim.Legal
Claim claim-data API (ccclaimdataapi, configured via cc.ccclaimdataapiurl)	REST	Outbound	Registers legal-case-related claim data client	SAIF.Application.Claim.Legal
Appworx job submission (submit_appworx_job)	Batch/procedure call	Outbound	Batch letter and print job submission	SAIF.Services.Appworx
xPression document generator service (documentGeneratorServiceUrl)	REST/SOAP*	Outbound	PDF preview, print, publish, and distribution	SAIF.Services.Printing
SSRS report execution service (sqlReportingServiceUrl)	SOAP	Outbound	Server-side report rendering	SAIF.Services.Printing
SQL Server BDS (BDS_USER, bdsDatabase, BDS_DATABASENAME)	DB	Inbound	Policy-security and policy-list lookups	SAIF.Business.View.Policy

External web applications

Application	Relationship	Navigation type	Screens involved
BusinessOnline help (/BusinessOnline/frmHelpFrame.aspx)	External help site	link/iframe	All screens via the shared help action
Shared provider search popup	In-app popup dependency	popup	frmCaseCost (doSelectProvPopup())
SAIF menu navigation to other BOF applications	Cross-application navigation	redirect	Database-driven SAIFMenu with context values SAIFClaimNum, LegalId, LegalWCBNum

Cross-application integrations

Integration	Protocol	Data exchanged	Libraries involved
Guidewire matter/activity synchronization	REST	Legal case schedule, matter, and WCD update data	SAIF.Application.Claim.Legal
LegalNet letter batch generation	Batch job submission	Case, request, and letter-request data	SAIF.Services.Appworx, SAIF.Application.Claim.Legal
Document generation and distribution	REST/SOAP + MSMQ	Rendered PDF/report content and imaging metadata	SAIF.Services.Printing, SAIF.Services.Imaging.Import
Policy-security lookups	DB (SQL Server BDS)	Policy header, affiliation, and audit-access data	SAIF.Business.View.Policy

Dependency risks

• documentGeneratorServiceUrl, documentMSMQPath, idmFilePath, and sqlReportingServiceUrl are required at runtime, but the library configs provide no local fallback or visible source for those values, risking undiagnosed startup failures.*
• SAIF.Business.Claim.Legal depends transitively on BDS_USER, bdsDatabase, and BDS_DATABASENAME through SAIF.Business.View.Policy, but those keys are not declared in the consuming library itself, creating an undocumented configuration contract.*
• Guidewire integrations are best-effort by design; downstream API outages are swallowed rather than surfaced, which can mask systemic integration failures (BR-APP-006).

Related documentation

• Application index
• Overview
• Architecture
• Configuration
• Operations and processes
• Business rules
• Security and authorization
• Data model
• Tech debt

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

• SAIF.Application.Claim.Legal/SAIF.Application.Claim.Legal.vbproj
• SAIF.Services.Printing/Web.config
• SAIF.Business.View.Policy/Web.config
• SAIF.Services.Appworx/SAIF.Services.Appworx.vbproj