Combine payloads binary

Combine payloads binary

The advanced, utilities workflow component, Combine payloads binary can be used for a binary 'concatenation' of multiple payloads. This component saves the current payload for a later 'concat'. You should run this component for each of the payloads, that you want to combine.

This can e.g. be used to split up very large print outs (to ensure that the printer does not run out of memory), merge each part into a PCL or ZPL file (With create PCL document or Create ZPL document) and then combine them again to ensure that the print sequence is kept.

For concatenating the accumulated payloads (and turning it into a new payload) you use the component, Combined payload get and close.

The Combine payloads binary has no parameters.

    • Related Articles

    • Workflow file types/payloads

      The workflow of InterformNG2 is able to handle many different file types. The file type is also referenced as the payload of the workflow. Another way to express it like so: When you call a workflow, then most workflow input types expects, that the ...

    • Release log

      This is the list of the InterformNG2 releases and the major new features in each release: The manual now clearly reflect the status of support for the printer language: Direct Protocol. Direct Protocol is a legacy printer langauge and the support is ...

    • SPLF (spooled files)

      Spooled files (splf) is one of the file types/payloads, that can be handled by the InterformNG2 workflow. This is only relevant to the IBM i platform. The support for spooled file is covered here.

    • Printable

      Printable is one of the many file types/payloads supported by InterformNG2. Printable simply means, that the file format in the payload is one of the printable print data streams (mime-types), which means: DP PCL PDF PS ZPL The printable payloads can ...

    • Call external HTTP(s) rest apis

      In InterformNG2 it is possible to call (most) external HTTP REST APIs / Webservices and form submits using workflow components. The calls are based on RFC2616 Hypertext Transfer Protocol HTTP/1.1 https://www.ietf.org/rfc/rfc2616.txt The external HTTP ...