8.4
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.4.1
- Basics
- Features
- The Nature of PReS Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
Create MRDX
The Create MRDXaction task is used to register a job on a Suretrac server using an MRDXfile. The
MRDXcontains information about the job and its finishing, as well as integrity features use by SureTrac.
This task requires a PDFfile as an input, along with metadata generated through a document that contains
PitneyBowes Scan Codes.
Properties
General Tab
l Register Job to the SureTrac Server group:Check this option to enable the group.
l Server Name:The complete URLof the SureTrac server.
l Process Verification Job Name:The SureTrac job that this PDF should fall under. Use the
button next to the list to retrieve a list of available SureTrac jobs from the server.
l Mailrun ID:Aunique identification for the current job. This IDmust never be the same between
two mail runs - we suggest using either %f or %u , which are both always unique as they are
based on date and time.
l Use Job ID:Check to send the Job IDchosen in the PitneyBowes Scan Code utility along with
the job.
l Use External MRDX and PDF:Check this option to ignore the MRDXcreation and use an existing
PDFand MRDXinstead.
l Files Location:Enter the path and file name (without extension)of the PDF and MRDXfile, or
use the Browse button to select either. The PDFand MRDXfile must have the exact same name
apart from the extension.
l Use MRDXas new data file:Ignore the PDFfile and use the MRDXas a job file after this task. The
PDFis discarded. If this is unchecked, the PDFand metadata are used.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on " Task Properties Dialog" on page 584.
By default, any action task, branch, splitter or condition that generates an error will simply be ignored, and
the task just under it (not within a branch)will be given control of the job file without any modification. Any
initial input task that generates an error will stop the process from running as a whole, and output tasks will
not generate output. The On Error tab can be used to overwrite the default behaviors.