How would be the new print integration with priint:suite ?

[former_member356707]

I see in the release notes of Hybris Distribution 5.6, the print extensions (print, printcockpit, printsampledata, printhmc) will be removed from hybris distribution with the Q3 2017 release. And the new print integration will be entirely with priint:suite via hybris Extend Marketplace.

I appreciate your help to understand:

• For future integrations with hybris distribution and priint:suite we will still using the Priint Comet Plugin, nothing else ?

• This new strategy will support previous versions of hybris platform, like 5.4.x or customers with this version should be continue using the current Print Module ?

Thank you so much.

[former_member356707]

Recently I exchanged some emails with the Print team (Christoph Wesselburg) and they gave me some answers for these questions:

The new integration with priint:suite only will require the Comet Plugin and InDesing software?

The new integration is scalable from a single workstation to an enterprise solution with multiple sites and workstations. The basic setup includes:

• 1 x publishing hub

• 1 x hybris connector

• 1 x InDesign Desktop Plugins

The publishing hub is middle ware which provides API’s to both systems, the data source System (hybris PCM) and the publishing system (priint:suite V4). It provides both, push and pull actions that can be used to communicate between the both worlds.

The strategy of integration will be compatible with previous version of the Comet Plugin, I mean: 3.4 or 4.x ?

Yes and no. As the integration of 3.4 was based on simple on-data connection via ODBC and views to the datasource, it cannot just be adapted to the new system. That is, because the placeholders are setup differently in Version 4.

What is reusable (import from an InDesign document) is the basic set of templates, if you manually update the contained placeholders. Basically that means, that an update to Version 4 of priint:suite requires some integration as well as implementation tasks. A migration path is in the making, but not yet available.

In terms of architectural designs, could you please tell me any suggestions about the correct use of your priint:suite, e.g: client or server machines, standalone or web strategy, etc.?

The solution is scalable. In the solutions with more than just one workstation, components such as an InDesign server (not provided by WerkI/priint US) may be used. Templates for the desktop Version or the Server Version of InDesign are the same. This means, at any point in time a customer can upscale to a server without having to touch the implementation of placeholders or templates.

Also it is possible to upgrade to publishing hub pro version with the ability to connect to multiple datasources (CRM, ERM, PIM, statistical data, warehouse, etc, etc.), additional connectors, the publication planner, workflow module, and whiteboard. These components enable the users to communicate to the publishing system via browser, integrate external agencies and combine more than one datasource to the publishing system.