Contents x
      Lasernet Meta
      • 30 Apr 2025
      • 1 Minute to read
      • Contributors
      • Print
      • PDF
      Contents

      Lasernet Meta

      • Updated on 30 Apr 2025
      • 1 Minute to read
      • Contributors
      • Print
      • PDF
      Article summary

      Introduction

      Lasernet 10 includes a Meta module, which gives the ability to create custom solutions which can interact via web services in Lasernet Server.

      From Lasernet Meta, running on client site, you will be able to exchange your documents together with metadata and send them via queues defined in the Lasernet Server, to any destination supported by Lasernet.

      You can send documents to the Lasernet Meta client via a Windows printer or a file folder. Documents printed as Lasernet EMF via a local install driver, will be converted to PDF on the fly before they are transferred to the Lasernet server.

      Licensed per server installation and for a number of clients running the Lasernet Meta app.

      Note

      Lasernet 11 does not include the Meta module.

      Dependencies

      Lasernet Base Server Package incl. XML in & out

      Applications Included

      • Lasernet Meta app

      • PDF Engine as an embedded executable in the Lasernet Meta app

      Windows Printer Components on Client

      • Lasernet EMF Printer Driver

      • Lasernet Meta Proxy Service

      Modules

      Type

      Module

      Description

      Input

      Meta Input

      A module that enables the Lasernet Meta API on the Lasernet Server and allow the Lasernet Meta app to connect to and upload documents with meta data to the Lasernet workflow. In the module you can define a logic queue name, the meta field names and type, that can be entered and validated as meta data in the Lasernet Meta app user interface.

      Output

      Meta Output

      Uploads a document processed by the Lasernet Server to the Lasernet Meta app.

      Example of Usage (Meta Input)

      A user working on a desktop wants to upload a document with meta data to an external cloud service. The user has no integration from the desktop application, like Microsoft Word, to the cloud server. The Lasernet Server is configured to receive the documents via the Meta Input port, pass the document through a Lasernet workflow and authenticate and upload the document via a module like the HTTP module supporting REST Web Services (included in the Communication Package and must be licensed separately).

      The Lasernet Meta app adds a printer queue with a Lasernet EMF driver, converts the document to PDF and uploads the document to the Lasernet Server on demand. The Lasernet Server connects to the cloud service for a final delivery.

      Example of Usage (Meta Output)

      A user working on a desktop wants to preview a document processed by the Lasernet Server and manually enrich the delivery of the document with additional meta data (JobInfos) before sending the document to any output channel added to the Lasernet Server.

      What's Next