Skip to main content

Introduction to priint:cloud Data-Agents

What are priint:cloud Data-Agents ?​

The most typical tasks for data agents

  • collect relevant data in the content system and converting them into the data.xml format
  • collect relevant media assets in the content system or MAM
  • trigger rendering calls and receiving the results
  • expose endpoints for notifications "callback", "error", and "upload"
  • cache generated PDFs or persist them for long term

Since data agents expose a web interface (for webhooks at least) they could also be used for

  • exposing a synchronous endpoint for rendering as alternative to the asynchronous one that priint:cloud is currently offering (async-to-sync)
  • exposing an endpoint for reading images if direct priint:cloud access to the MAM is forbidden due to security considerations (mediaproxy)

Extended Data Agents​

The REST API of priint:cloud allows for more than to trigger renderings and receive the result. If the scope of the authorization that a data agent uses allows to manage projects, then it could be used for

  • automated creation and initialization of priint:cloud rendering projects, incl. creation of users

Currently, this is only used in projects managed by priint.com itself.

Content systems connected with such an extended data agent may expose a Web UI where admin users of the content system can create new rendering projects on the priint:cloud side and automatically adapt their onwn data scheme to optimally support such solution. Think for example about a multi-tenant PIM in the cloud environment where PIM instances for individual customers can be made "priint-ready" with just a single click.