Fiery JobFlow Ticket Mapper

JobFlow XML Ticket Mapper allows users to map XML ticket properties to Fiery job properties via a visual interface. If a ticket mapping has been defined, this mapping can be selected in the Input module configuration.

To define a mapping, select ‘User’ > ‘Resources’ > ’Ticket Mapper’ and import an example of the XML tickets one would like to process via a JobFlow workflow. Ticket Mapper will list all source ticket properties that can be mapped. For each ticket property, JobFlow will list default target properties that can be mapped. These target properties include job file path, Fiery job properties, Fiery XF workflow and media and JobFlow Collect and Pages module properties.

A ticket source property can be mapped to multiple target properties. In Ticket Mapper, select the ‘+’ icon to add additional target properties.

For simple XML tickets, the provided list of Fiery job properties should suffice to map properties like file location and quantity. For more complex use cases, users can customize the list of target properties by changing Ticket Mapper configuration files on the system where JobFlow is installed. More information below.

When exporting a workflow that has a ticket mapping defined, the ticket mapping will be part of the exported workflow.

Multi-order, multi-file support

Introduced in JobFlow 2.9.2, XML Ticket Mapper now support complex tickets. If an XML ticket has multiple orders, each order will be processed as individual jobs. If an order has multiple file references, all referenced files will be merged to a single job. In addition to supporting more complex tickets, XML Ticket Mapper now also supports mapping XML ticket properties to a Fiery Impose template.

warning

For JobFlow to correctly process multiple tickets, the XML ticket needs to have a correctly formatted list of either tickets or files. Learn about XML here

Multi-order example

Example of ticket with two jobs, one with 100 copies and one with 50 copies. Two jobs will be created by JobFlow XML Ticket Mapper.

<ticket>
 <customer>
   <name="Hans">
 </customer>
 <jobs>
  <job>
  <file url="job1.pdf"/>
  <amount="100"/>
  </job>
  <job>
   <file url="job2.pdf"/>
   <amount="50"/>
  </job>
 </jobs>
</ticket>

Multi-file example

Example of ticket with multiple files with 100 copies. Both files will be merged.

<ticket>
 <jobs>
  <job>
   <amount="100"/>
   <files>
     <file url="job1.pdf"/>
     <file url="job2.pdf"/>
   </files>
  </job>
 </jobs>
</ticket>

Ticket Mapper customization

To customize the target properties shown in the Ticket Mapper dropdown menu, one can update the Ticket Mapper configuration files:

1. If JobFlow is installed on a Fiery: E:\EFI\server\httpd\Neem\Neem\Neem\Neem\TicketMapping.
2. If JobFlow is installed on a separate Windows environment: C:\Program Files (x86)\Apache Software Foundation\Apache2.2\Neem\Neem\TicketMapping.

There are two configuration files that can be updated:

JobSettingsMetadata.json

JobSettingsMetadata.json defines the content of the dropdown with target properties. One can add Fiery specific job properties or target properties one would like to set for Correct or Connect modules.

Example of configuration that creates a target property for Pitstop Enfocus variables txtJobId and txtEmail used in the Correct module.

{
  "Job Location": [
    {
      "File path": "File path",
      "Description": "The path of the job. This is mandatory field"
    }
  ],
  "Fiery": [
      {
        "Job Title": "JOB_NAME",
        "Description": "Name of the job"
      },
      {
        "Copies": "num copies",
        "Description": "1-9999"
      },
   ...
  ],
  // New properties for Correct module
  "Correct": [
    {
      "Job ID": "txtJobId",
      "Description": "Job ID"
    },
    {
      "Email": "txtEmail",
      "Description": "Email"
    }
  ]
}

JobSettingsCustomdata.json

For use cases where in addition to ticket properties, ticket values also need to be mapped to different target values, users can update JobSettingsCustomdata.json.

In below example configuration, JobFlow will automatically map the values sourcevalue1 and sourcevalue2 for source property sourceproperty for the ticket mapping called SampleTicket-1. sourcevalue1 and sourcevalue2 are mapped to targetvalue1 and targetvalue2. This is especially useful for mapping bespoke ticket values to Fiery job property values.

JobSettingsCustomdata.json

{
 "tickets": [{
  "ticket_name": “SampleTicket-1",
  "tag_value_mapping": {
   “sourceproperty": {
    “sourcevalue1": "targetvalue1",
    “sourcevalue2": "targetvalue2",
   }
  }
 },{
  "ticket_name": “SampleTicket-2",
  "tag_value_mapping": {
   “sourceproperty": {
    “sourcevalue1": "targetvalue3",
   }
  }
 }]
}