Package Window

The Package Window is where you visit to collect the pieces of your job and get reports and previews.

It contains the following sections-

Package Options

Suppress Enclosing Subfolder – when this is enabled, all jobs packaged will go into the same folder. Thus they will share a common images and fonts folder. This may be useful for some people who wish to have all of their jobs packaged as a group. Please be aware that if you use images or fonts that have the same name, but are different versions, the last image or font packaged will overwrite earlier versions.

Compress/ZIP package – when this is enabled, FlightCheck will compress the entire packaged job, including fonts, images, any page preview and reports into a single ZIP archive.

Open Package in – When enabled, you can select an app that supports ZIP archives. Any example of this might be, you set up your own workflow so that when you create a zip archive of your job, it starts up your email application and attaches the zip archive. Another example may be you set an FTP or file upload app to open the zip archive created by FlightCheck and send the zip to your desired location.

Documents Section –

You can configure what gets packaged by enabling or disabling the checkboxes under each of the Package sections.

Allows you to enable or disable whether to package the file you are preflighting

You can also Enable the IDML box. In order for an IDML to be created you must have the appropriate Markz product. If you have OmniMarkz installed you can creates IDMLs for InDesign, QXP, PDFs and Illustrator files.

*If you have only IDMarkz installed you can only create IDML files for InDesign files.
If you only have QXPMarkz installed, you can only create IDML files for Quark files
If you only have PDFMarkz installed you can only create IDML files for PDFs or Illustrator files.

Fonts Section –

Allows you to collect found fonts. FlightCheck cannot package missing fonts as they cannot be found.

*Found Fonts do not need to be active to be seen by FlightCheck. If you want to edit a document for which FlightCheck has detected inactive fonts, you will need to activate those fonts if you need to edit the document.

Images Section –

Allows you to collect found images. FlightCheck cannot package missing images. However, if you create an IDML FOR YOUR FILE AND ENABLE CREATE LO-RES PREVIEWS FOR MISSING IMAGES, you MAY be able to get lo-res previews as place-holder images.

Page Previews Section –

This section allows you to create a PDF or bitmap preview of each page in your document. By default GIF and PDF are enabled. The GIF preview is used as a thumbnail on the HTML report so you can get an idea of what the first page of your file looks like while viewing the HTML Report. **If you have long documents, it can take a bit of time to generate previews for each page. As an example, if you have a 200 page book and select GIF and PDF formats for Page Previews, you will end up with 200 GIF files and a single 200 Page PDF file. This takes time to generate unless you have a very fast system.

Reports Section-

There are three types of reports FlightCheck can generate to add to your package.

The FlightCheck Report – This report is the same information shown in Preflight Mode View. It shows which items triggered which Ground Controls. This is a good report to use if you want someone to make fixes to issues with the file as it gives details on the problems found. If the person has FlightCheck they can be taken directly to images that have triggered a Ground Control. [In future versions of FlightCheck there may be the ability to be taken to Fonts and Colors as well]

The Inventory Report – This report is the same as what you see in Inventory Mode View. It lists out info regarding your job as well as Fonts, Colors and Images. Similar to the FlightCheck report if you generate a GIF preview of your document, the html version of this report will have a thumbnail of the first page in the upper right of the html report.

The Package Report – This report shows an inventory of what was actually packaged with your job. Missing fonts and Images will be as “packaged = false”, where as fonts and images that were found and able to be packaged will show a status of “packaged = true”

Each of the three types of reports can be output in any of the following formats:

HTML – The html reports generated can have collapsible sections and if you selected a GIF preview, will contain a thumbnail of the first page of your file in the upper right of the report.

JSON – This format can be useful if you want to feed it into an automated system, such as a CRM system (Customer Relationship Management System- a system for tracking interaction with your customers, in this case most likely about the job being printed) or a job tracking system. JSON for most people appears as unreadable format raw html code or XML. JSON is an acronym for JavaScript Object Notation.

RTF – This format of reports adds some formatting, however in many cases, it is easier to read the html version of the report

TXT – This is a plain text report, it has no color. Plain text may be good if you want to parse through the reports for specific traits, yet have an easily readable form.

XML – This format similar to raw HTML code and can be useful if you want to feed it into an automated system, such as a CRM system or a job tracking system. XML for most people appears as unreadable. XML is an acronym for Extensible Markup Language

*You can generate multiple versions of the same report type in different formats. For example, you may want the Inventory report as both an html report and an RTF report.

On the right side of the Package Window is the Package Detail area. This is an overview of what is in your packaged job.

Documents Summary –

This is a summary of how many documents as shown in the Document Section are packaged. Normally this is equal to one. For example, you preflight an InDesign file with 88 pages. This counts as a single document. If you have OmniMarkz loaded and select to create an IDML, then the document count would increase to two.

Reports Summary –

Gives a count of the number of reports packaged with your job. This can range from zero to fifteen. By default it is three as the html version of each of the three report types is enabled automatically, unless you change it in FlightCheck’s Package Preferences window.

Page Previews Summary –

Shows the number of Page Preview formats selected for output.

Images –

Shows the count of images that have been packaged

Fonts –

Shows the count of fonts that have been packaged

Missing Images –

Shows the count of Missing Images. These cannot be packaged.

Missing Fonts –

Shows the count of Missing Fonts. These cannot be packaged

File Count –

Is the total of the Documents + Reports + Page Previews counts

Size (estimated) –

Estimated size of your packaged job.This is only an estimate as Page Previews and reports do not exist yet.