SAIF.Services.Appworx dependencies

Internal dependencies

SAIF.Services.Appworx.vbproj declares no same-repo <ProjectReference> elements — this is a leaf/foundation library with no outbound in-repo project dependencies. Within this repository it is consumed (inbound) by SAIF.Business.Claim.Legal (<ProjectReference> plus project-level Import Include="SAIF.Services.Appworx") and by SAIF.Application.Claim.Legal (<ProjectReference>). Its internal dependencies are the organizational SAIF NuGet packages below.

Dependency	Reference Type	Usage
SAIF.BOF.Framework (Bindable, Connection, Core, DNS, Logging, Mail, Security, Security.EnvironmentApi)	NuGet Package	Supplies IDataPortalInfo, IPortalRequest, IDataRequest, DataRequestType, clsMSOracleDataLayer, AppGlobal, ApplicationEnvironment used throughout clsRequestAppworxJob.vb*
SAIF.Framework.Common	NuGet Package	Supplies clsSmartString, the type backing all 20 argument slots*
SAIF.HashUtil	NuGet Package	No usage found in source
SAIF.Web.API.Clients / SAIF.Web.API.Core	NuGet Package	No usage found in source

External dependencies

Dependency	Version	Usage
Oracle.ManagedDataAccess	21.5.0	Not referenced by name in source; used at runtime as the ODP.NET managed provider registered in App.config/Web.config and consumed indirectly by clsMSOracleDataLayer*
Newtonsoft.Json	8.0.3	No usage found in source
RestSharp	106.12.0	No usage found in source
Microsoft.Bcl.AsyncInterfaces, System.Buffers, System.Memory, System.Numerics.Vectors, System.Runtime.CompilerServices.Unsafe, System.Text.Encodings.Web, System.Text.Json, System.Threading.Tasks.Extensions, System.ValueTuple	see packages.config	Transitive/BCL shims; no direct usage in source
System, System.Core, System.Data, System.Numerics, System.Web, System.Xml, System.Xml.Linq, System.Data.DataSetExtensions	BCL	System.Data used (CommandType.StoredProcedure, via project-level Imports System.Data); the remainder are unused by this project's single source file

Dependency risks and notes

• Several referenced packages (Newtonsoft.Json, RestSharp, SAIF.HashUtil, SAIF.Web.API.Clients/SAIF.Web.API.Core) have no confirmed usage in the single hand-written source file — these are referenced but unused, representing unnecessary reference surface/risk*.
• The build fails with an explicit EnsureNuGetPackageBuildImports error if System.Text.Json.6.0.3 is not restored, since the project imports ..\packages\System.Text.Json.6.0.3\build\System.Text.Json.targets directly.
• The shared SubmitBatchJob overload can bypass the caller's configured IDataPortalInfo entirely and construct its own clsMSOracleDataLayer("PRADT", "WCISPROD" | "WCISDEV1"), hard-coding a schema/owner and database aliases directly in this library rather than relying on configuration — a coupling and environment-portability risk.
• The library depends on the Oracle stored procedure submit_appworx_job (schema WCIS_DBA) as its only application-layer SQL statement; the procedure's own behavior (see Database tables and SQL catalog) is an external, database-side dependency not versioned alongside this library's source code.
• No logging, retry, or compensating action exists in this library if the stored-procedure call fails; failures are only wrapped and rethrown as ApplicationException.

Related documentation

• Index
• Overview
• Architecture
• Operations and processes
• Business rules
• Database tables
• SQL catalog
• Procedures
• API reference

Sources

• SAIF.Services.Appworx/SAIF.Services.Appworx.vbproj
• SAIF.Services.Appworx/clsRequestAppworxJob.vb
• SAIF.Business.Claim.Legal/SAIF.Business.Claim.Legal.vbproj
• SAIF.Application.Claim.Legal/SAIF.Application.Claim.Legal.vbproj
• SAIF.Application.Claim.Legal/LegalNet/clsRequestManager.vb
• SAIF.Application.Claim.Legal/LegalNet/clsMailDateManager.vb
• SAIF.Application.Claim.Legal/LegalNet/clsCreateFileManager.vb