A consumer obtains document preview and distribution by holding a DocumentServiceProxy instance for the lifetime of SAIF.Services.Utilities.Documents.DocumentService, which is itself consumed by SAIF.Services.Web.Proxies and, through that library, by SAIF.Services.Web.Proxies consumers documented at SAIF.Services.Web.Proxies overview, including several DependencyMaps/SAIF.DependencyMaps.Web.* Autofac registrations and the PrintAPI controllers.
The app.config<client><endpoint name="clsGenerateSoap"> entry (Services/SAIF.Services.Web.Proxies/app.config:59, address eexprod4) is present but is not used at runtime, because the wrapper supplies an explicit Binding and EndpointAddress to the generated constructor.
Not supported — no cancellation on any of the six call sites
—
DocumentServiceProxy.cs:37-146
Yes
Message size limits
MaxReceivedMessageSize and MaxArrayLength raised to int.MaxValue; ReaderQuotas.MaxStringContentLength keeps the 8192 default*
Yes
DocumentServiceProxy.cs:24-27
Yes
The message-size limits were raised to accommodate large rendered PDFs, but the timeouts were not raised alongside them, so a large document distribution can still time out under the default one-minute send timeout*.
DocumentService instances constructed per request in Services/SAIF.Services.WebApi/PrintAPI/Controllers/ReportsController.cs:30,61,92,110 and HomeController.cs:24 are never disposed*, so the underlying DocumentServiceProxy/clsGenerateSoapClient chain is also left undisposed for those call paths.
// Preview a document package as a PDFvarpdfBytes=documentService.GeneratePdf(package,xml,profile);// Distribute a document package by email and image importdocumentService.DistributeDocument(docConfig,imageConfig,mailMessage,printConfig,deferredPrintConfig);
Scenario
Operations used
Notes
Preview a rendered document as PDF
previewDocument
Reached through DocumentService.GenerateDocument/GeneratePdf
List categories and packages for the caller's application
categoriesForUser, documentsForCategory
Reached through DocumentService.GetCategories/GetPackages
Distribute a document by print, email, fax, or imaging
distributeDocument
Reached through the four DocumentService.DistributeDocument overloads
Note: Statements marked with † are derived from dependency library
documentation via the Legends CLI. Statements marked with * were inferred
from code structure or contextual evidence.