Skip to content

Insert an output-log entry

Call the legacy print-request stored procedure and return its output file name and copy count.

Field Value
Operation ID OP-006
Trigger Caller invokes clsCorrespondence.InsertOutputLog.
Inputs A correspondence object and program name.
Outputs otFileName and otCopies returned by reference.
Primary components clsCorrespondence.InsertOutputLog
Entry point Business\SAIF.Business.Policy.Correspondence\clsCorrespondence.vb

Steps

  1. Create a non-query portal request and point it at the stored-procedure name pk77001_output_log.insert_output_log (SQL-003).
  2. Bind policy number, period effective date, endorsement code, endorsement sequence number, and calling program name.
  3. Bind the ot_file_name and ot_copies output parameters and send the request through ProcessPortalRequest.
  4. Copy the returned parameter values back into the ByRef outputs after the portal request completes.
  5. Treat this path as possibly dead code: the referenced Oracle object was not available in the reviewed Oracle source extract, so the method depends entirely on a missing procedure.*

Process flow

The following diagram summarizes the control flow for this operation.

flowchart TD
    Start([Legacy print request]) --> Bind[Bind procedure parameters] --> Call[Call SQL-003] --> Copy[Copy output values] --> Return([Return file/copies])

Failure and edge-case behavior

  • Validation and framework state errors surface through the BOF error collection unless the called dependency throws directly.
  • Database-dependent operations rely on the caller-supplied data portal context and Oracle connectivity.
  • Imaging reconciliation and stored-procedure wrappers defer cross-system behavior to their external collaborators.
  • The legacy output-log path should be treated as possibly dead until the missing Oracle object is confirmed.*

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

  • Business\SAIF.Business.Policy.Correspondence\clsCorrespondence.vb