Another way to solve the problem of user defined ticket items is by modifying the mapping table and including mapping nodes for these items also. The mapping mechanism is driven by the mapping table, so a new mapping node for a new item means that at submission the value for that item will be automatically taken from the JDF if possible.
Example:
If a customer wants to allow job submitters to specify the output type for a printed job, he can add a new ticket item from JTE called OutputType. It is created as a choice item and has the following options: Finisher, Tray, Booklet_Maker, Perfect_Binder.
Once the ticket definition is updated, the mapping file can be extended to cover also this item.
The following node can be added to the mapping xml:
<jc:EnumMapping Name="OutputType" Optional="true">
<jc:JdfFieldXPath="/jdf:JDF/jdf:ResourcePool/jdf:DigitalPrintingParams/@OutputBin"/>
<jc:EnumValueMapping JdfValue="Finisher" AccessEnumValue="Finisher"/>
<jc:EnumValueMapping JdfValue="Tray" AccessEnumValue="Tray"/>
<jc:EnumValueMapping JdfValue="BookletMaker" AccessEnumValue="Booklet_Maker"/>
<jc:EnumValueMapping JdfValue="PerfectBinder"AccessEnumValue="Perfect_Binder"/>
</jc:EnumMapping>
Now the mapping file is updated. Let’s say the next job that is submitted to PRISMAdirect contains the following fragment in the attached JDF ticket:
<JDF Types="... DigitalPrinting ..." ...>
<ResourcePool>
<DigitalPrintingParams ID="NodeIDDPP" Class="Parameter"Status="Available" OutputBin="PerfectBinder" ...>
</ResourcePool> ... ourceLinkPool>
<DigitalPrintingParamsLink rRef="NodeIDDPP" Usage="Input" />
...
</ResourceLinkPool> </JDF>
After the mapping process is complete, in the new job created the item OutputType will have the value “Perfect_Binder”.