Skip to content

SAIF.Services.Appworx overview

Documentation context: Embedded library compiled directly into the LegalMaintenance web application. Documented via: LegalMaintenance.sln, consumed through SAIF.Business.Claim.Legal and SAIF.Application.Claim.Legal.

SAIF.Services.Appworx is a small, single-purpose integration/service library that lets in-repo business and application code submit a batch job to the Appworx enterprise job scheduler by calling the Oracle stored procedure submit_appworx_job.

Purpose

  • Translate a "run this batch job with these arguments" intent into the Appworx scheduler's Oracle submission contract (submit_appworx_job), normalizing argument handling (fixed 20 positional slots, empty-slot suppression, defaults for requestor and printer).
  • Consumed by SAIF.Business.Claim.Legal and SAIF.Application.Claim.Legal; in this repository every observed call originates from SAIF.Application.Claim.Legal/LegalNet/ managers (clsCreateFileManager, clsMailDateManager, clsRequestManager) submitting the LGN0002_LEGALNET_LETTERS module.

Responsibilities

  • Provide a stateful instance API (clsRequestAppworxJob) and a stateless shared convenience overload (SubmitBatchJob) that constructs a fresh instance per call.
  • Reset argument state between submissions (InitArgs) so a reused instance cannot leak arguments from a previous job (BR-007).
  • Optionally redirect submissions to a fixed, hard-coded Appworx-hosting Oracle database/schema (PRADT on WCISPROD/WCISDEV1) instead of the caller's own data portal, via the inUseWCISDEV1AppworxForAllDevEnv flag (BR-001, BR-002).

Key components

  • clsRequestAppworxJob: the sole hand-written type; exposes the instance API (constructor, properties, SubmitBatchJob, InitArgs) and the Shared SubmitBatchJob convenience overload used by all in-repo callers.

Sources

  • SAIF.Services.Appworx/clsRequestAppworxJob.vb
  • SAIF.Services.Appworx/SAIF.Services.Appworx.vbproj