The structure of the mapping files is quite simple. Each file contains a list of mapping nodes. A mapping node exists for each ticket item in the default PRISMAdirect ticket. The mapping rules are:
PRISMAdirect attempts to process each mapping node in the file.
PRISMAdirect starts processing the next mapping node, when:
A mapping node has successfully mapped one item from the JDF ticket to an item of the PD ticket, or vice versa.
If PRISMAdirect cannot process a mandatory mapping node:
The mapping of the items stops and the submitted job is not added to the list of orders.
If PRISMAdirect cannot process an optional mapping node:
PRISMAdirect skips the mapping node and continues with the next mapping node in the file.
When all mapping nodes, or at least the mandatory mapping nodes, are processed:
A PRISMAdirect ticket is created and the submitted job is marked as "New".
A mapping node is mandatory when the attribute Optional is set to "false". It is recommended to use Optional="false" only for debugging a mapping file. A mapping node is optional when the attribute Optional is set to "true". It is recommended to use Optional="true" for normal operation.