The Metadata Bundle allows you to use document metadata in your workflow. Included within the Bundle are:

• Metadata Routing: Routes files based on the metadata associated with the document. Multiple rules for metadata routing can be easily set up. For example, you could set up this node to search within all incoming documents for Bates stamps that contain the word "confidential," routing only those files that contain that "confidential" stamp to a specific folder on the Desktop.
• Metadata to File: Creates a file that contains document metadata as its content to be used for record keeping or importing into other systems. You can extract a variety of metadata including, but not limited to:
• Bates stamps
• Email
• LPR
• SMTP
• OCR
• Standard Barcode and 2D Barcode
• Values from regular expression search operations from Parse and Distribute processes.
• Index form values
• System, File, and User data
• Custom Metadata





• Metadata Scripting: Metadata Scripting is an advanced process used to manage metadata associated with files in the workflow. With this node, you can modify, copy, delete, or add new metadata. For example, this node could be used to remove trailing spaces from metadata. Some examples of use cases for Metadata Scripting include:
• Converting page level metadata variables to document level variables
• Manipulating metadata values along with splitting or merging values
• Creating new metadata from existing metadata values
• Counting pages or documents
• Reformatting metadata values for other nodes or processes in a workflow
• PJL Print Preferences: The PJL Print Preferences process allows you to specify basic and advanced PJL print preferences for your job. These preferences can be applied automatically or specified directly at the MFP. This process is designed to be used as part of Dispatcher Phoenix's Release2Me solution. To allow users to specify print settings at the MFP after their print jobs have been released from the queue, you can attach a PJL Print Preferences index form to a Release2Me node. In this case, you must make sure that the PJL Print Preferences node comes after the Release2Me node in the workflow. You can also use this node to add, replace, or remove advanced PJL headers from your print files.
• PDF Data Extraction: The PDF Data Extraction process extracts metadata from incoming PDF files for future use by other nodes in the workflow (i.e., routing on specific Document Properties, etc.) or for import into other systems for search purposes. With this process, the user must specify what metadata to extract. Files that cannot be opened as PDFs will leave this node on an "Error" transition. For example: When batch processing PDF forms, data from the fields in the form needs to be extracted and inserted into a database. A workflow that collects files from an Input Folder, processes them through the PDF Data Extraction and ODBC Processing nodes, and distributes them to an Output Folder automates this process.

Other Add-Ins