This customer story describes how DRT Holdings, a manufacturing and engineering company based in Dayton, Ohio, used B2Win Suite to extend its existing StreamServe document output and automate email distribution without redesigning its document templates.
StreamServe was widely used as an output management system for producing outgoing documents from Baan and Infor LN environments. Over time, StreamServe became part of OpenText's customer communications portfolio, while Baan and Infor LN continued on a separate product path under Infor. As the alignment between these solutions became less direct, DRT needed a practical way to reuse its existing StreamServe document library for automated email distribution, without rebuilding templates originally designed for printing and faxing.
Goal
The goal was to automate document distribution with B2Win Suite, converting and emailing existing StreamServe output while preserving the document templates customers had already built.
Solution Overview
B2Win Suite was used to monitor a network location for files generated by StreamServe:
- A PCL file, containing the print data to be converted.
- An STR file, containing control information such as recipient details.
For each document, B2Win Suite matched the related PCL and STR files, converted the PCL file to PDF, and emailed the PDF using recipient information extracted from the STR file.
The workflow handled real-world file conditions: STR and PCL files could arrive in either order, multiple file pairs could be copied at once, and network storage could be slow or temporarily incomplete.
Workflow Mechanism
B2Win Suite uses a workflow-based architecture, with each processing step configured as a node. This solution used the following nodes:
File Listening Trigger
This node monitors the configured location and starts a workflow run only when the matching PCL and STR files for a job are ready to process.
The listener matched related files regardless of arrival order, waited for stable file size and availability, and used read timeouts to avoid processing partial copies or temporary NAS delays.
Custom Script — Read STR File Contents
This script reads the STR file and extracts job information, such as the recipient email address from the ${FAX} variable.
Because some STR files used unusual encoding, this step filtered and normalized the content before extracting recipient details.
Custom Script — PCL to PDF Converter
This node converts the PCL print data into PDF format.
Rename File
This node renames the generated PDF according to the required naming convention.
Delivery by Email
This final node emails the converted PDF using recipient information extracted from the STR file and passed through the workflow as a property.
Additional Requirements
Additional error-handling and file-management logic made the solution more reliable.
Error Handling
Conditions and branches handled successful processing, conversion failures, delivery issues, and temporary file-read problems.
The workflow included an on-success branch for completed jobs and an on-failure branch for conversion or delivery errors.
For transient failures, the workflow retried the job. B2Win Suite's workflow model made this possible without manually reconstructing failed conversions.
The failure branch notified the administrator when conversion or delivery did not complete successfully, making exceptions visible instead of leaving failed jobs unnoticed.
A Conditions node routed each job based on the success or failure status of the preceding step.
File Archiving
The Archive - Server node moved successfully processed source files to the SENT folder on the B2Win Suite server.
To ensure idempotency, each report was marked complete only after conversion, email delivery, and archiving, preventing duplicate sends if the same source files were encountered again.
Result
The solution now processes hundreds of documents daily. It lets customers keep existing StreamServe document designs while adding reliable PDF conversion, email delivery, retry handling, administrator notification, and duplicate-processing protection.
“When our legacy document delivery solution reached end-of-life, we needed a reliable way to continue delivering hundreds of purchase orders, invoices, and other business documents directly from our Infor Baan environment. NAZDAQ helped us modernize our document delivery process while preserving business continuity. Their team was responsive, knowledgeable, and demonstrated a level of commitment to our success that is increasingly rare among software vendors.”
— David Geis, IT Manager, DRT Holdings
See how B2Win Suite can modernize document delivery from Infor LN, Baan, or CloudSuite — while preserving the templates you already rely on.
Request a Demo
Jamal Saad
Jamal Saad is the CTO and Development Manager at NAZDAQ with 15+ years of experience architecting and delivering enterprise software. He defines the technology roadmap, drives product strategy, and manages team to deliver scalable, AI-driven platforms and data integration tools. Passionate about innovation, he champions R&D and agile practices to align technical excellence with business impact.
About the company
