Tabs: Page Shift

Note: This node works with PDF files (version 1.3 or later).

The Tabs: Page Shift Node is used to change the specified pages to tab sheets. This node supports only Letter Tab or A4 Tab page sizes. If Letter Tab is selected, the Page Size must be Letter. If A4 Tab is selected, the Page Size must be A4.

The inserted tab sheet information is updated in the metadata and carried with the job to the next node of the workflow.

This node supports two metadata key-value pairs. These key-value pairs are set (predefined) in the PDF prior to being input to this mode:

• job:tab.page (Required): The list of page(s) to which the tab shift should be applied.

• job:tab.paperweight (Optional): The Paper Weight of the tab sheets. If the Tab Paper Weight metadata is invalid then the Tabs:Page Shift Node displays a message in the Activity Log of the workflow and the file is moved to the Error Folder.

  Note: This Help file contains detailed information about supported Job Ticket Metadata and the JDF XPaths and Value Ranges. Refer to Job Ticket Metadata. When launched, the Metadata Browser window displays the pre-defined Job Ticket Metadata, the system-defined variables (such as Date, File, System and User info), and the metadata values from the active node.

Using the Tabs: Page Shift Node

Add the Tabs: Page Shift Node to the workflow by dragging the node’s icon onto the Workflow Builder canvas, and then double-clicking on the icon to open the Tabs: Page Shift Node’s window:

• Select the Enabled checkbox so that the process will run. When unchecked, this process is ignored. Documents pass through as if the node were not present (i.e., continue along the default or positive path). Note that a disabled node will not check for logic or error conditions.

• In the Node Name field, enter a meaningful name for the Tabs: Page Shift Node.

• In the Description field, enter a description for the Tabs: Page Shift Node. This is not required, but can be helpful with multiple collection points. If the description is long, hover the mouse over the field to read its entire contents.

• Click the Save button to save the changes. If Cancel is selected and the window is closed, the changes are not saved.

• Click the Help button to access online help.

Settings for Tabs: Page Shift Node

In the Settings for Tabs: Page Shift node panel, specify the following:

• Number of Tabs: Select the number of Tabs from the drop-down. Tab height is delimited based on the number of Tabs selected.

• Tab Paper Size: Specify the size of the tab sheet from the drop-down options: Letter Tab, A4 Tab (12.7mm), or A4 Tab (15.0mm) from the second drop-down menu.

• Shift Position: Use this option to specify the position of the content of the tab pages. The contents of the specified page are shifted based on the value entered here.

  Note: When the Orientation is Portrait, the shift is to the right. If the Orientation is Landscape, the shift is to the bottom.

• Tab Page Number: Specify the metadata input for the Tab Page Number. Click the Browse for metadata button (), then drag-and-drop a metadata keys onto the Tab Page Number field. Only one value may be entered. The metadata key may also be manually entered.

Sample of a Tabs: Page Shift Workflow

The purpose of this workflow is to receive XML files, parse the job ticket into XML metadata, add tabs to the file based on the chapter information contained in the XML job ticket, and then send the modified document to AccurioPro Conductor for printing. When the job prints, the tabs are included.

Note: This node produces metadata output with key name as “Job”.

A detailed explanation of each node of the workflow follows:

Input Folder Node: Configure the Input Folder to collect XML job tickets and forward them to the Job Ticket Parser: XML Node. The forwarded XML job ticket files contain the job ticket attribute information. They also contain the chapter information for tab creation which will be used in the Tabs: Page Shift Node. Below is a sample job ticket that contains the chapter information:

<Ticket>
 <Media>
	<Weight>40</Weight>
	<Width>8.5</Width>
	<Height>11</Height>
</Media>
<Paper>
	<Unit>inch</Unit>
</Paper>
<Tab>
	<Weight>40</Weight>
	<ChapterInfo>
	  <Page>
	    <Chapter>1</Chapter>
	    <Chapter>4</Chapter>
	  </Page>
	</ChapterInfo>
</Tab>
<File>file</File>
<Src>C:\\test files\\10Pages_Letter.pdf</Src>
</Ticket>

Job Ticket Parser: XML Node: If the document is formatted as XML, the XML information is converted to job ticket metadata and sent forward in the workflow. If a document is not formatted as XML, that document is moved to the Error Folder.

1. Open a text editor then copy the sample XML code noted is the sample job ticket above.

2. The Source Path <Src> noted in the sample job ticket needs to be changed so that the path is valid.

3. Save locally as XML_Tabs_Shift.XML.

4. Double-click on the Job Ticket Parser: XML Node. The settings screen opens.

5. In the left panel, set the following values:

   • Enabled checkbox: Select to enable the node to accept jobs
   • Node Name: Assign a name value to the node in the text field
   • Measurement unit: Select the radio button that corresponds to the measurement unit required for the node

6. In the Job Ticket Reference panel (far-right), locate the Open icon:

7. Click the icon. On the screen that opens, navigate to and select the file saved in Step 3 above (XML_Tabs_Shift.XML).

8. When the file opens, its contents (or XPaths) display in the Job Ticket Reference panel (far-right).

9. In the Category panel (far-left), click on Basic Settings. The Parameter Name, Metadata Keys, and Job Ticket Paths columns display in the main panel:

10. Values from the Job Ticket Reference panel need to be moved to the Job Tickets Paths column, to the open cell that corresponds to the value’s Parameter Name.

11. Drag-and-drop /Ticket/Media/Weight to the Job Ticket Paths cell of the Paper Weight row.

12. Drag-and-drop /Ticket/Media/Width to the Job Ticket Paths cell of the Paper Width row.

13. Drag-and-drop /Ticket/Media/Height to the Job Ticket Paths cell of the Paper Height row.

14. Drag-and-drop /Ticket/Paper/Unit to the Job Ticket Paths cell of the Paper Unit row.

15. In the Category panel (far-left), click on the Tab Settings option. The Parameter Name, Metadata Keys, and Job Ticket Paths columns display in the main panel:

    

16. Values from the Job Ticket Reference panel need to be moved to the Job Tickets Paths column, to the open cell that corresponds to the value’s Parameter Name.

17. Drag-and-drop /Ticket/Tab/Weight to the Job Ticket Paths cell of the Tab Paper Weight row.

18. Drag-and-drop /Ticket/Tab/ChapterInfo/Page/Chapter to the Job Ticket Paths cell of the Tab Sheet Page Number row.

19. In the Category panel (far-left), click the Job Download option. The Documentation Source and Job Ticket Path: File Type fields and the Retrieve Print File Option checkboxes display in the main panel:

    

20. In the Retrieve from File Option column, select the checkboxes of all four options: Retrieve from Local Path, Download from URL, Retrieve Encoded base64 from Job Ticket, and Retrieve from Network share.

21. From the Job Ticket Reference panel, drag-and-drop /Ticket/Src to the Documentation Source field.

22. From the Job Ticket Reference panel, drag-and-drop /Ticket/File to the Job Ticket Path: File Type field.

23. Once these actions are completed, the screen will appear as shown in the image above.

24. Click Save to apply the changes to the node.

Tabs: Page Shift Node: The Tabs: Page Shift Node will identify chapter break information in a file (e.g., XML_Tabs_Shift.XML), and then add tab pages as chapter markers. This information is then added to the file’s metadata and the file is sent forward in the workflow. In the job ticket example noted at the beginning of this discussion, the first and fourth pages are recognized as chapter breaks and changed to Tab sheets in the document.

AccurioPro Conductor Connector Node: The document (and its Tabs) are sent to the AccurioPro Conductor Connector Node. From there, the documents may be printed.