Output Management, Redefined

In previous versions, B2Win Suite and B2Mail-Merge typically handled the complete document output process.

B2Win Suite 7.0 introduces a different model.

Document Output Management can now be treated as a series of connected capabilities:

Generate → Format → Route → Deliver → Track

Customers can use the complete process, but they do not have to.

They may use B2Win Suite for document generation and distribution.

Or only for distribution.

Or to extend an existing DOM process.

Or to retrieve documents from IDM and route them through additional delivery channels.

Or to add dynamic recipients, attachments, user interaction, monitoring, or other capabilities to an existing document process.

This is the principle behind the broader composable automation architecture introduced with B2Win Suite 7.0: customers choose the capabilities they need and combine them with technologies that are already part of their environment.

Perhaps the most important change is philosophical as much as technical.

The new B2Win Suite Output Management Solution is designed to work with the Infor technology stack - not around it.

WITH Infor Report Designer

Customers that already design their documents using Infor LN Report Designer can keep those layouts.

B2Win Suite can generate PDF or Excel documents based on the existing Infor report output and continue the process from there - enriching, splitting, routing, distributing, and monitoring documents as required. NAZDAQ’s current Document Output Management solution specifically supports professional PDF and Excel documents based on existing Report Designer layouts.

And Report Designer is not mandatory.

B2Win Suite 7.0 can also generate PDF documents and Excel reports directly from Infor LN reports, even without using Report Designer, while preserving and extending the original report output.

WITH Infor DOM

DOM remains valuable when document distribution is predictable and rule-based.

For standardized processes such as generating a document, applying predefined rules, and emailing, printing, or archiving it, DOM may already provide what the organization needs.

The challenge comes when requirements become more dynamic.

Organizations may need users to review a document before sending it, change recipients at runtime, attach documents dynamically, distribute immediately, deliver through additional channels, or understand exactly where a process failed.

These are among the challenges identified in our earlier article, 7 Common DOM Challenges in Infor LN and Infor CloudSuite.

With B2Win Suite 7.0, the answer is no longer necessarily to replace the DOM process.

B2Win Suite can complement it.

A workflow can determine which stages remain within DOM and where B2Win Suite should provide additional automation, flexibility, distribution, user control, or monitoring.

WITH Infor IDM

IDM can also become part of the same workflow.

B2Win Suite can retrieve context-related documents from IDM and dynamically add them as attachments to the document being processed.

It can also distribute generated documents to IDM as one of several possible destinations.

That means IDM does not sit outside the B2Win process. It can participate directly within it - as a source of documents, a destination, or both. NAZDAQ’s current Output Management solution supports dynamic attachments from IDM and distribution to IDM alongside other destinations.

This composable approach changes the conversation with customers.

The question is no longer:

“Do we replace our existing output management process with B2Win Suite?”

It can now be:

“Which parts of our current process already work well, and where do we need more?”

A customer might already have:

• Report Designer for document layouts
• DOM for standard distribution rules
• IDM for document storage

But still need:

• Dynamic recipient resolution
• Context-based attachments
• User intervention and interactive control
• Immediate processing
• Additional delivery destinations
• Document splitting
• Enhanced PDF or Excel output
• Better monitoring and traceability
• More complex workflow logic

B2Win Suite can provide those missing capabilities without requiring the customer to discard the rest of the architecture.

This is what makes the new OMS fundamentally different.

Composable does not mean disconnected.

The common layer is the B2Win Suite workflow.

In B2Win Suite 7.0, workflows visually define how the different components participate, which stages are required, what happens next, how information moves between them, and how execution is monitored.

A process could therefore look like:

Infor LN → Report Designer → DOM → B2Win Suite → Email + IDM

Another could be:

Infor LN → B2Win Suite → PDF → Dynamic Attachments from IDM → User Review → Email + SharePoint

And another customer may use B2Win Suite for the complete process from document generation through final delivery.

The architecture adapts to the requirement - rather than forcing every requirement into the same architecture.

B2Win Suite 7.0 does not assume that every customer needs the same Output Management architecture.

Some organizations need an end-to-end solution.

Others already have most of the pieces and need only one missing capability.

Many will sit somewhere in between.

That is why Output Management in B2Win Suite 7.0 has been redefined around a simple principle:

Keep what works. Add what you need. Connect it through workflow.

Use Report Designer.

Use DOM.

Use IDM.

Use your existing enterprise tools.

And use B2Win Suite to bring the missing capabilities together into one controlled, adaptable document process.

Output Management, redefined for the way modern Infor environments actually work.