Skip to main content

Infor LN Split Document Trigger

Overview

The Infor LN Split Document Trigger receives an Infor LN report print request through the B2Win Suite device, splits the incoming report, and emits generated PDF files for the split output.

Purpose

Use this trigger for mass-output workflows where one Infor LN report must be split into separate PDF documents, often by business partner or recipient.

Configuration

FieldDescription
Business Partner Code SourceOptional current-node property that contains the business partner code used for contact lookup.
Address BooksOptional address books used to resolve related business partner contacts.
Display for the iterationOptional expression used as the iteration display label.
Ignore missing imagesContinues rendering when referenced images are missing.
Keep temporary Input filesKeeps temporary XML input files after processing for troubleshooting.
Advanced document optionsShows advanced PDF rendering options.
Render XML colors in the output documentRenders color information from the XML input. Enabled by default.

Outputs

OutputData TypeCollectionDescription
XMLFileNodeFileFalseThe trigger outputs a NodeFile for each generated split PDF document.

Properties

PropertyFlowDataTypeDescription
X-API-KEYStringAPI Key
X-SIGN-DATEStringSign Date
REPORT_IDStringReport Code
REPORT_DESCRIPTIONStringReport Description
CRONJOBBooleanFrom cronjob?
LANG_IDStringLanguage ID
COMPANYStringCompany
LOGIN_USERNAMEStringLogged in user
REMOTE_SYSTEMStringRemote System
REMOTE_CMDStringRemote Command
REMOTE_ACTIONStringRemote Action
REMOTE_MODEStringRemote Mode
XML_FILE_NAMEStringXML File Name

Processing Logic

The trigger parses the incoming Infor LN request payload, validates the API signature in production, processes the XML report with splitting enabled, and emits a PDF file per split. When a business partner source and address books are configured, it looks up contacts and adds business partner/contact properties to the emitted iteration.

Examples

Use this trigger to split a statement or invoice batch into recipient-specific PDFs, then send each output to an email or document management destination.

Notes / Limitations

  • If the business partner code source is blank or the business partner is not found, the contact lookup is skipped.
  • Address-book property names are generated from the address book name by removing non-letter characters and uppercasing the result.
  • The report must be reprinted for configuration changes to affect new output.