SAIF.Services.Imaging.Import architecture¶
SAIF.Services.Imaging.Import is intentionally small: the library contains one serializable class, clsImageImport, and no additional services, managers, controllers, or persistence components. Its architectural role is to hold import metadata in memory and to flatten that metadata into the outbound text format consumed by downstream printing and distribution logic.
Responsibilities¶
- Hold claim, policy, document, task, and legal metadata on a single DTO.
- Publish shared OnBase classification constants to callers.
- Serialize the DTO into a fixed-order newline-delimited
KEY=VALUEpayload.
Component boundaries¶
clsImageImport: Entire public surface of the library, including constants, properties, and theToString()serializer.SAIF.Services.Printing.clsPrint: Downstream consumer that storesclsImageImportinImportInfoand callsToString()when composing a print/distribution request.
Interaction model¶
- A caller creates and populates
clsImageImport. - The caller or a downstream service passes the populated DTO into printing/distribution logic.
clsPrintconverts the DTO to text by callingclsImageImport.ToString().- The serialized text is embedded in the outbound request payload.
Architecture diagram¶
The following diagram shows the library's high-level relationship to its observed downstream consumer.
flowchart TD
Caller[Calling component] --> DTO[clsImageImport]
DTO --> Print[SAIF.Services.Printing clsPrint]
Print --> Payload[Outbound request payload]
The following diagram shows the primary serialization sequence.
sequenceDiagram
participant Caller as Calling component
participant DTO as clsImageImport
participant Print as SAIF.Services.Printing clsPrint
participant Payload as Outbound payload
Caller->>DTO: Populate public properties
Print->>DTO: ToString()
DTO-->>Print: KEY=VALUE lines
Print->>Payload: Embed ImportInfo text
Design constraints¶
- The library performs no network, database, or configuration access in its code path.
- The public serialization contract is defined entirely by the order and formatting inside
clsImageImport.ToString(). - The library's runtime behavior depends on callers supplying meaningful values before serialization; no validation layer exists in this project.
Related documentation¶
Sources¶
Services\SAIF.Services.Imaging.Import\clsImageImport.vbServices\SAIF.Services.Imaging.Import\SAIF.BOF.Services.Imaging.Import.vbprojServices\SAIF.Services.Printing\clsPrint.vb