xDashBoard passthrough operations¶
A set of direct 1:1 passthrough methods on clsPrint that forward xDashBoard integration requests to the xPression Design SOAP service with no additional local logic.
| Field | Value |
|---|---|
| Operation ID | OP-PRINT-XDASHBOARD |
| Trigger | Caller invokes any of xpublishDocument, xpreviewHTML, xpublishAndReturnDocument, xdocumentsForCategory, xoutputProfilesForDocument, xcategoriesForUser |
| Inputs | Varies by method (document package/XML, category, user identifier) |
| Outputs | Varies by method (byte arrays, strings, or string arrays) |
| Primary components | clsPrint.xpublishDocument, clsPrint.xpreviewHTML, clsPrint.xpublishAndReturnDocument, clsPrint.xdocumentsForCategory, clsPrint.xoutputProfilesForDocument, clsPrint.xcategoriesForUser |
| Entry point | SAIF.Services.Printing\clsPrint.vb |
Steps¶
- Each method is a direct 1:1 passthrough to the corresponding method on
m_Xpresso(thexpresso.clsGenerateSOAP proxy), with no additional local logic, validation, or state changes.Origin: These steps are implemented in
xpresso.clsGenerate(SAIF.Services.Printing.xpresso) and executed against the external xPression Design server.* - Return values are passed back unchanged (byte arrays, strings, or string arrays depending on the operation).
Process flow¶
flowchart TD
Start([Caller invokes passthrough method]) --> Forward[Forward call to m_Xpresso equivalent method]
Forward --> Soap[SOAP call to external xPression server]
Soap --> Return([Return value unchanged])
Failure and edge-case behavior¶
- No local validation or error handling wraps any of these passthrough calls; SOAP faults propagate directly to the caller.*
Related documentation¶
Sources¶
SAIF.Services.Printing\clsPrint.vbSAIF.Services.Printing\Web References\xpresso\Reference.vb