Message configurations

Sample 1 – XML Input Data (using an existing form template)

This Message uses a static template (purchase order.xdp). The form template uses an XML data file as input.

The Message has an Event and a Process configured. The Event uses a pattern to detect the data file type for the Message. The pattern is /batch to match the root node of the Purchase Order.xml data file. The Process links to a form template when the input data matches the pattern of the Event. The form template Purchase Order.xdp from the resource set is loaded in the Process.

Settings:

•	Record mode is used with the record trigger transaction.

•	StreamServe variable mapping is used to map the SOM Expression $record.header.txtPONum to the StreamServe variable $ponum. The variable is used in the Runtime settings to sort the forms in the batch input file.

Sample 2 – ASCII Input Data (using a template created from scratch in Design Center)

The input data to the form template is a text file. The Event uses the PageIN tool to detect the data file type and to extract the content of the data file into a StreamServe Message.

The sample file invoice.grb (from the resource set) is used to configure the Event. A pattern is used to detect the string INVOICE in a set of coordinates in the page. The Field Tool in PageIN has been used to extract data from coordinates on the page to the Message.

The Process uses the setting Add the Message as a Data Connection in the Data View (See Settings dialog box) to present the content of the Message in the ADEP Designer Data View. The content of the Data View has been used to create bindings to the fields in the form template.

Sample 3 – Invocation by ADEP (remote invocation of Production Print)

The Input data to the XMLIN Event is the XML file Dunning Notice.xml. The pattern is set to detect the element <transaction>. The process is configured to load a template dynamically. The variable $template will be assigned a template from the input connector automatically.

Sample 4 – Dunning Notice Generate (remote invocation of Production Print)

This Message configuration is identical to Sample 3. The difference is how it is used in the runtime.

Sample 5 - AFP2PDF

This Message configuration uses PreformatIN and PageOUT to convert AFP files to PDF files using the AFP2LXF filter in the platform.