Output Types

BLOX Total CMS automated can product the following file types:

  • .pdf (Adobe Acrobat PDF file)
  • .ps (PostScript file)
  • .eps (Encapsulated PostScript file)
  • .jpg (JPEG file)

In addition, BLOX Total CMS can automate the Printing of Adobe InDesign documents by hiding the user interface.

Finally, JPG previews and either proof or final quality PDF files, can be sent to PageTracker by the integrated BLOX Total CMS Output function. Page Tracker can also trigger NITF output of the assets on the page.

Follow the various output configuration options to learn how to set up each type of output.

Other Output Related Functions

In addition to physically outputting pages from a user’s Adobe InDesign to the file types listed above, BLOX Total CMS’s integrated output functions can also do these tasks:

  • Force Ad Statuses to be launched before output to insure that the latest ad information is attached to each page.
  • Advance the process of the page’s workflow.  
  • To advance assets in the workflow process to the Final Process in Page Tracker, add <forceFinalProcess>true</forceFinalProcess> to the Output Preferences XML.  Using this means assets do not need checked out on the page.  If they are checked out, the function can't operate as it will not modify any locked asset. Thus, a site could combine this feature with the <checkInAssets> to advance all assets.
  • Trigger an NITF output of the assets on the output pages if the page’s workflow has reached the final process.
  • Produce separate or combined output files based on configuration and file format options.
  • Change the workflow of all checked out assets that are placed on the pages being output.
  • Control if subsequent outputs overwrite or replace previous versions.
  • Send multiple copies of the output (useful for proofing at some sites).
  • Issue Warning when sending pages to Output when they have not yet reached the Print Ready status.  This is done with the Output Preferences XML tag of <warnWhenNotPrintReady>true</warnWhenNotPrintReady>.  This is used for .PDF files and PageTracker Output.
  • Issue Warning if Output is requesting Page Tracker when Page Tracker is not active.
  • Output Menu Groups and Presets do not have to be included in PDF or PageTracker Output.  By default, the Adobe InDesign PDF Preset will be assumed so that Output is not disabled.
  • For sites using the <checkInAssets> option in Adobe InDesign, an Asset Flag will be added in every Workflow Group in the <checkInAssets> Group.  If Flags are used, each <name>, <process> must have an associated <flag> tag.  Only a single flag can be added to assets through an output method. If the asset type doesn't support the flags, they will be ignored.
  • PDF Exports can be viewed when adding in <viewPDFafterExport>true</viewPDFafterExport> to any PDF Export Menu Group or Method in the Output Preferences XML file.  The PDF will automatically open when export is completed.
  • In Adobe InDesign Creative Cloud, you can request an automatic preflight of the document prior to the beginning of the output process, add <preflightProfile>installedProfile</preflightProfile> to the Output Preferences XML.  If preflight fails, the output request will not be stopped. The users will be warned and they can cancel the output at that point.  All actions are logged.
  • In Page Tracker, there is an option for the SavePage web-service, a flag called 'force_final_process' and this will set the workflow process for all 'unlocked' assets on the page to the Final Process, in their assigned workflow.  All successful and failures will be logged and show a revision comment.

Chain Structured Output

Sending the same PDF to multiple locations. This works with InDesign Client and Page Tracker using a <chain> with <chainLink> and sends it with what ever name you need (ie: <validateName> or <namingConvention>).

  • <chain>
  •     <chainLink>
  •         <linkName>One</linkName>
  •         <folderPath>~/Desktop/One</folderPath>
  •         <folderPathMacOS>~/Desktop/One</folderPathMacOS>
  •         <validateName>OutputNaming_01</validateName>
  •     </chainLink>
  •     <chainLink>
  •         <linkName>Two</linkName>
  •         <folderPath>~/Desktop/Two</folderPath>
  •         <namingConvention>YY_MM_DD_S_GG_sampletwo</namingConvention>
  •     </chainLink>
  • </chain>

Swap Order of Chained Output with 'CheckInAssets' based upon current visibility of Trimmed Content

When using a Page Tracker Output Method that involves a <chain> that also uses <checkInAssets> but doesn't use <nextMethod>, the output process will look at the Visibility of the Trimming and modify the order of the check-in and the PDF export. If trimming is visible, the check-in of assets will happen first. This is a big advantage for sites that are experiencing crashing after output. This combined with <chain> should both increase the speed of output and the reliability of Adobe InDesign.  The following is an XML example of creating a Page Tracker Output Method using <chain> in a <menuGroup>.

  • <menuGroup>
  •     <menuGroupName>Chained</menuGroupName>
  •         <outputType>pagetracker</outputType>
  •         <preset>PageTrackerPreview</preset>
  •         <ignoreRecentPageTrackerUpdate>true</ignoreRecentPageTrackerUpdate>
  •         <includeCoordinates>true</includeCoordinates>
  •         <sendAdInfo>true</sendAdInfo>
  •   <chain>
  •     <chainLink>
  •         <linkName>One</linkName>
  •         <folderPath>~/Desktop/One</folderPath>
  •         <folderPathMacOS>~/Desktop/One</folderPathMacOS>
  •     </chainLink>
  •   </chain>
  •   <checkInAssets>
  •     <workflow>
  •         <name>News</name>
  •         <process>Complete to Press and Web</process>
  •         <flag>popular</flag>
  •     </workflow>
  •     <workflow>
  •         <name>Wire</name>
  •         <process>Ready</process>
  •         <flag></flag>
  •     </workflow>
  •   </checkInAssets>
  •   <method>
  •     <menuName>Chain Testing</menuName>
  •         <chain>
  •           <chainLink>
  •             <linkName>Two</linkName>
  •             <folderPath>~/Desktop/Two</folderPath>
  •             <namingConvention>YY_MM_DD_S_GG_sampletwo</namingConvention>
  •           </chainLink>
  •         </chain>
  •   </method>
  • </menuGroup>

Allow Output to Backup Document for Disaster Recovery

This Output Function will backup the document being Output. Doing so sends a backup copy to the standard document Backups folder as well as asking Adobe InDesign to Save over itself (writing a new file). The rewriting file doesn't have the same advantages as creating an .idml version, but it does reduce the file size of the document and that can speed up future saving and the opening of the document. To activate the function include either true or before. The True value causes the backup to be done after the output request has completed. The Before value creates the document backup before output.

  • <menuGroup>
  •     <menuGroupName>backup</menuGroupName>
  •     <preset>PageTrackerPreview</preset>
  •     <method>
  •         <menuName>backupDocument</menuName>
  •         <folderPath>~/Desktop</folderPath>
  •         <outputType>pdf</outputType>
  •         <noLimitDialog>true</noLimitDialog>
  •         <backupDocument>true</backupDocument>
  •     </method>
  •     <method>
  •         <menuName>save as self before</menuName>
  •         <folderPath>~/Desktop</folderPath>
  •         <outputType>pdf</outputType>
  •         <noLimitDialog>true</noLimitDialog>
  •         <backupDocument>before</backupDocument>
  •     </method>
  • </menuGroup>

<noLimitDialog> Function Not Require <limitMultipage> Function

When using <noLimitDialog>true</noLimitDialog>, will force <limitMultipage> to true as well. In addition, you no longer need to use both if you want single pages output but don't want to see the dialog. The exception to this is with Page Tracker output where you are still required to select which pages to send to Page Tracker since Page Tracker is almost always used to specify a page status. Here's an example.

  • <menuGroup>
  •     <menuGroupName>to desktop</menuGroupName>
  •     <preset>PageTrackerPreview</preset>
  •         <method>
  •             <menuName>multipage checker</menuName>
  •             <folderPath>~/Desktop</folderPath>
  •             <outputType>pdf</outputType>
  •             <noLimitDialog>true</noLimitDialog>
  •         </method>
  • </menuGroup>{data}