User Guide Version: 8.
User Guide Version 8.5 Last Revision: 4/12/2017 Objectif Lune, Inc. 2030 Pie-IX, Suite 500 Montréal, QC, Canada, H1V 2C8 +1 (514) 875-5863 www.objectiflune.com All trademarks displayed are the property of their respective owners. © Objectif Lune, Inc. 1994-2017. All rights reserved. No part of this documentation may be reproduced, transmitted or distributed outside of Objectif Lune Inc. by any means whatsoever without the express written permission of Objectif Lune Inc. Inc. Objectif Lune Inc. Inc.
Table of Contents Table of Contents 4 Welcome to PReS Workflow 8.
About Documents 43 Debugging and Error Handling 44 The Plug-in Bar 55 About Printing 57 About Processes and Subprocesses 70 Using Scripts 79 Special Workflow Types 125 About Tasks 170 Task Properties 171 Variable Properties 172 Working With Variables 534 About Configurations 542 About Related Programs and Services 547 The Interface 551 Customizing the Workspace 552 PReS Workflow Button 561 The Configuration Components Pane 562 Other Dialogs 589 The Debug Information Pane
The Message Area Pane 615 The Object Inspector Pane 616 The Plug-in Bar 617 Preferences 619 The Process Area 659 The Quick Access Toolbar 670 The PReS Workflow Ribbon 671 The Task Comments Pane 673 Copyright Information 675 Legal Notices and Acknowledgements 676 Page 6
Welcome to PReS Workflow 8.5 This PDF documentation covers version 8.5. To view the documentation of previous versions please refer to the PDF files available in the Downloads section of our website: http://www.objectiflune.com/OL/Download/DownloadCenter. Workflow is the heart of all of our solutions. Working in conjunction with PReS Connect, PReS Capture, CaptureOnTheGO, PReS Imaging, PReS Fax, and a variety of plug-ins, it helps improve your communications processes.
Technical Information that may require specific knowledge to understand. Warning Information that is potentially critical to using PReS Workflow. Pay close attention.
System Requirements These are the system requirements for PReS Workflow 8.5. Operating System (64-bit only) l Microsoft Windows 2008/2008 R2 Server l Microsoft Windows 2012/2012 R2 Server l Microsoft Windows Vista l Microsoft Windows 7 l Microsoft Windows 8.1 l Microsoft Windows 10 Note Windows XP, Windows 2003 and older versions of Windows are not supported by PReS Workflow.
Basics PReS Workflow is a tool for the automation of the processing, the distribution and the printing of your business documents. Once installed on the server, it can be set up to automate all tasks related to document processing. Setting Up the Working Environment Setting up the working environment has to be done the first time you start PReS Workflow. 1. Defining the printer (see Activate Your Printers). 2. Configure PReS Workflow Services (see Workflow Services).
To add a PReS Workflow startup process: l l In the Ribbon, go to the Home tab and click the Startup Process button in the Processes group. In the Configuration Components pane, right-click on any process or the Processes folder and select Insert Startup Process. Note You can only have one Startup Process in any given configuration and cannot add more. Considerations l l l l l While your configuration is limited to a maximum of 512 processes, any given process can have as many tasks as necessary.
If PReS Workflow service is running when you send a new configuration, it stops and restarts automatically with the new configuration. If the service is stopped, it will not start automatically. To send a Configuration to the local server: 1. Open the configuration you want to use as a new configuration. 2. Edit the configuration, if required. 3. When the configuration is ready to be used, from the PReS Workflow button, choose Send Configuration, then Send Local.
Features PReS Workflow are input driven applications designed to output data in a variety of ways through diverse means to various applications and devices. PReS Workflowcan be used as simple go between, passing along input data to output devices, but it can also perform various types of data processing. You can combine the various PReS Workflow services to set up versatile automated processes to print jobs as well as generate other types of output.
Branches A branch is effectively a doubling of your job file. As your job file goes down the process, when it encounters a branch it will go in that branch, process all tasks up to the output, and return to the main trunk to continue processes. You can have branches within branches, and all branches must have an output. For more information on branches, see Branch. A branch is represented as a crossing . Conditions A condition will either execute the branch it creates or the main trunk, but never both.
Available Resources l Data Mapping Configurations: Displays a list of data mapping configurations used with the Execute Data Mapping task. Each of the templates have been sent from PReS Connect using the Send to Workflow tool. For each template in the list, the following two items appear within them: l l l l l Data Model: Displays the data model used in the data mapping configuration. Double-click on the data model to view it in your default XML viewer (generally, Internet Explorer).
package are extracted and placed in the folders noted above. Resource Archives From version 8.2, PReS Workflow maintains an archive of previous versions of resources, in the following location: %PROGRAMDATA%\Objectif Lune\PReS Workflow 8\PReS Watch\OLConnect\Archive , each in their own folder: l datamapper contains archives of the data mapping configurations (.OL-datamapper) l jobcreation contains archives of the Job Presets (.OL-jobpreset) l outputcreation contains archives of the Output Presets (.
Note Null characters present in the data may not be displayed properly when using PReS Workflow Configuration program, and that they may also be printed differently by different printers. To ensure consistency, you should consider filtering out such characters. Data File and Job File Whichever source it may come from, a serial port, an e-mail message, or an LPR request, for instance, and whatever its format, data entering a PReS Workflow process via an input task is always referred to as a data file.
Job File Names and Output File Names When an input task sends a new data file down a process, it gives it an internal file name referred to as the job file name (associated with the %f variable). The new job file typically keeps the same name until the end of the process. l l If the job file comes to a branch in the process, PReS Workflow makes a copy of the job file and give the new file a new job file name.
example, will generate three JPEGs or TIFFs called Invoice0, Invoice1 and Invoice2. Note that this does not apply to multiple TIFFs, which can include multiple images in a single file. Note You can change the name of a previously named file using a Rename action task (see "Rename" on page 296). About Data Selections A data selection could be compared to an address. It indicates a location within a data file using coordinates.
Note It is strongly recommended to use the automatic method, as it returns precisely the same selections but is generally more reliable Text-Based Data Selections These selections are used for text data files such as Line Printer, ASCII and Channel Skip emulations. The selection refers to a rectangular selection that may contain multiple lines, rows, columns on a given page.
The alternate "quick" syntax lets you grab data from a single line from the first data page in the file. Here is a breakdown of the syntax (all options are mandatory): l @(): Always surrounds a data selection. l Line Number: The line from which to get the data. l From Column: the leftmost character position of the data selection. l To Column: the rightmost character position of the data selection.
Syntax lookup(group, return key, lookup key, lookup value) Here is a breakdown of the syntax (all arguments are mandatory): l l l l group: The name of the group in which to retrieve the value. Does not need to be surrounded by quotes. return key: The name of the key where the information you want to retrieve is located. Does not need to be surrounded by quotes. lookup key: The name of the key in the group with which to look up the value.
l Trim Option: Can either be "Trim" if you want to trim empty spaces before and after the data selection or "NoTrim" if you want to retain the extra spaces. Metadata Selections These selections are used with any type of file, as long as a metadata file was created by a previous task. Syntax GetMeta(Field Name [, Option Flags, Metadata Path]) Here is a breakdown of the syntax: l l GetMeta(): Always surrounds metadata selections.
The Data Selector The Data Selector is the tool you use to choose your sample data and metadata files, to select the appropriate emulation, make data selections, and to stabilize your data. The Data Selector is divided in two tabs: Data and Metadata.
Database Emulation l l The Database emulation changes the Browse button ( ) for the Database Emulation Configuration button ( ), which displays the Database Emulation Configuration (see Database Emulation). Once a database has been opened and query entered, the Data pane displays the results of the SQL Query in a grid format, which each line representing a single returned row from the database. Each column represents a field returned by the query, with its field name as a row header.
Metadata tab The Metadata tab allows users to either generate the metadata file for their active sample data file, or to associate an existing metadata file to their document. The Sample Metadata file name is the path to the metadata file describing the current sample data file. Buttons on the right can be used to load metadata from a file or to save the current metadata to a file.
The Search options defines how to retrieve the value of a given metadata element (attribute or field) when it is not present at the current metadata level. The possible search options are: l l Search from a specific location only. Search from level X to Job, where X can be any metadata level (Job, Group, Document, Datapage, Page).
The emulation that is used in your process can change during the process, and can be different than the one used in any PlanetPress Design document used in your process. PlanetPress Design documents use their own emulations, as defined in the document itself from PlanetPress Design. Emulations in PReS Workflow: l Line Printer l ASCII l CSV l Channel Skip l Database l XML l PDF Warning PDF Emulation, also called Document Input, is only available in PReS Workflow.
This section covers issues relating to the sample data used to create your PReS Workflow configuration and to the actual data that PReS Workflow will send to PlanetPress Design documents. It is an important section which you should fully understand before you start creating your configuration. Also included in this section are procedures that let you make data selections as well as get data from the sample data file.
To choose a sample data file: 1. Click the Debug tab in the PReS Workflow Ribbon. 2. Click on Select in the Data group. 3. Use the Data Selector to choose your sample data file and emulation options. 4. Click OK on the Data Selector. PReS Workflow also keeps the last 9 used data files in memory, which you can reopen to use in the same process, or a different one. To reopen a sample data file used previously: 1. Click the Debug tab in the PReS Workflow Ribbon. 2. Click on Reopen Data File in the Data group.
your documents beforehand. Metadata structure Metadata in PReS Workflow introduces the following concepts for adding information to a job: l Page: 1 side of a physical paper sheet. l Datapage: 1 atomic unit of content that produces zero, one or more pages. l l l Document: group of 1 or more ordered datapages intended to the same recipient from the same source (ex: invoice).
A single JOB can be composed of GROUPS of DOCUMENTS, which themselves are composed of physical PAGES produced by executing a PlanetPress Design document on one or more DATAPAGES. Metadata Elements Each metadata node (i.e. Job, Group, Document, etc.) is described with a series of elements, that is, system-defined attributes or user-defined fields holding static or dynamic information about the node they are attached to. Each element has a name and a value.
In addition to attributes and fields, each node of type group, document or datapage have a Boolean property called selected that indicates whether or not to produce the pages under that node. By default, this property is set to true for all nodes. Metadata Attributes Reference Here is a description of the Metadata attributes. The attributes are categorized as either Production, Finishing or Index/Count. Production attributes describe the production of the job and/or metadata (e.g.
Attribute Description Categor y J o b Gro up Docum ent Datap age Pa ge the data file used by the PlanetPress Design Document. Date Date the metadata was created in ISO format. Producti on X X X Time Time the metadata was created in ISO format. Producti on X X X Title Title of the source document. Producti on X X X Producer Name of the software that created the metadata. Producti on X X X Creator Name of the software that created the source of the metadata.
Attribute Description Categor y J o b Gro up Docum ent Datap age Pa ge device for which the metadata and associated data is intended. on Dimension Two floats separated by a colon indicating the media size in typographical points (ex: 612:792). Finishin g X X X X X Orientation "Rotate0", "Rotate90", "Rotate180" or "Rotate270", indicating respectively portrait, landscape, rotated portrait and rotated landscape.
Attribute Description Categor y J o b Gro up Docum ent Datap age Pa ge page is on the front or the back of the paper sheet. This attribute is a "best effort" and is devicedependent. Duplex "None", "DuplexTumbl e" or "DuplexNoTu mble"; indicate a change of the duplex status. Finishin g X X X X X InputSlot Devicedependent identifier of the media source. Finishin g X X X X X OutputBin Devicedependent identifier of the media destination.
Attribute Description Categor y J o b Gro up Docum ent Datap age Pa ge weight of the media. MediaColor Devicedepedent color of the media. Finishin g X X X X X MediaType Devicedependent type of the media. Finishin g X X X X X X X X X X X X X Index Index/C ount IndexInDocument Returns the Absolute index of the node within all the node under the parent Document. Index/C ount IndexInGroup Returns the Absolute index of the node within all the node under the parent Group.
Attribute Description Categor y IndexInJob Returns the Absolute index of the node within all the node under the parent Job.
Attribute Description Categor y SelectedIndexInDo cument Returns the Absolute index of the node within all the selected node under the parent Document. Index/C ount SelectedIndexInGr oup Returns the Absolute index of the node within all the selected node under the parent Group. Index/C ount SelectedIndexInJo b Returns the Absolute index of the node within all the selected node under the parent Job.
Attribute Description Categor y J o b Producti on X Gro up Docum ent Datap age Pa ge printing using a Windows driver. Author Name of the user who printed the job initially, as available in the spool file, and as the first job info of the Windows capture input. Metadata Tools PReS Workflow includes a complete set of metadata-related functionality, which can be referred to as Metadata Tools.
Metadata Generation using Data Capture with PReS Printer The Objectif Lune Printer Driver (PS) allows end-users to print directly to PlanetPress Design from any Windows application, by using the familiar File|Print option. At the other end, PlanetPress Design can capture the incoming stream and convert it internally into a PDF file along with its metadata. By default, capturing a document input using a PReS Printer will generate a PDF along with its metadata.
The Metadata Selector allows to view and select metadata elements.
Metadata tab in the properties of a PlanetPress Design document allows to easily define documents or groups. Metadata Fields Metadata Fields in the properties of a PlanetPress Design document allows to easily define documents or groups. About Documents A Document is a file sent to PReS Workflow by PlanetPress Design and is used to produce an output when merged with data. A Document can be an invoice, a report, a receipt or anything else, but by itself it is empty and without any variable data.
Import Documents This procedure describes how to import variable content documents created in PlanetPress Design. Importing documents can be useful when transferring configurations between PReS Workflow installations. To import documents into PReS Workflow: 1. Choose File | Import Documents. The Import PlanetPress Design Document dialog box appears. 2. In the File type box, select the desired file type. 3. Navigate to the document you want to import, select it and click Open.
from the PReS Workflow Configuration Tool, in order to detect and resolve issues with your process. Error Handling, on the other hand, occurs when your configuration has been sent to PReS Workflow services, and are running in "production" mode. On one hand the manual task is critical when creating a process, on the other the automated handling of errors within your processes will have a large impact on recovering from errors as they happen during production.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc.
Note Local variables in the process are not sent to error processes, even if the error process has a variable of the same name. Accessing the Logs If your process is running live in PReS Workflow service, you have two ways of seeing what is happening, now or in the past. To view what processes are running and processing data as it happens: 1. In the PReS Workflow Ribbon, click on the Tools tab, then select Service Console in the Services group. The PReS Workflow Service Console opens. 2.
page 638. To view logs for jobs that have already processed By default, the logs are available in the following folder: C:\Documents and Settings\All Users\Application Data\Objectif Lune\PlanetPress 7\PlanetPress Watch\Log You can access this folder more quickly by using this procedure: 1. From PReS Workflow Configuration software, press CTRL+SHIFT+ALT+F4 simultaneously. The PReS Workflow working folders are opened. 2. Double-click on the folder called Log. 3.
But if, for a given input task, you did select this option and something goes wrong and an original input file is lost or corrupted, you will have the option to use the Resubmit Job command to pull the backed up input file into the process. Granted that you have back up copies of the files polled by an input task, you may resubmit them as required.
5. Using the From page and To page boxes, select the data pages that you want to resubmit. If you want to resubmit all the data pages from the selected input file, enter 0 in both boxes. 6. Click Send to resubmit the data. 7. To resubmit backed up input files for the same process or for a different one, repeat step 2 to step 6. 8. To close the File Resubmission dialog box, click Close. Warning The From page and To page boxes are only useful for printer queue (or printer capture) inputs.
In PReS Connect: l Somewhere at the bottom of each document page, add a Data Selection object defined as a custom data selection that contains a reference to the job info variable sent from PReS Workflow and a current page marker. You can use, for example, =&watch.jobinfos[6] + '-'+intostr(¤t.datapage)' Debugging your PReS Workflow Process Debugging a process is separated in two parts.
Configure Services dialog is used instead and this may lead to unexpected behaviors. Please See "Workflow Services" on page 590 for more details. Note The sample job file should generally be the exact same format as the data that you will receive when PReS Workflow is processing the job at run-time. For more information on how to capture your sample data file properly, please refer to the PReS Trigger and Data Capture Guide.
l l l l l Click on the Stop button to stop the debugging process. If you use Run, Step or Skip after stopping the process, debugging starts over from the top. Use the Set Breakpoint button to tag the currently selected task, branch or condition as a breakpoint. When you click Run in your process, the process will execute every task until it reaches a breakpoint and will stop just before the task that is set as a breakpoint.
l l Stop the process, and select the file you saved as your process' data file. If you need to continue debugging your process after the emulation change, you can still do it by using Skip on all the tasks until the emulation change, inclusively. Then use Step or Run to continue debugging. Lastly, PReS Workflow 7.
The default categories lists plug-ins according to what type of task each achieve. Therefore, when first starting your PReS Workflow Configuration program, the following categories are used: l Inputs l Actions l Outputs l Data splitters l Metadata Related l Process logic l Connectors Note An Uncategorized category is dynamically created if your PReS Workflow finds any plug-in that would not be part of the existing Plug-in bar.
l Move plug-ins from one custom category to another (that you cannot move default plugins from the default categories, you can only copy them) l Copy plug-ins from one custom category to another by holding the CTRL key. l Delete plug-ins from any custom category by using the Delete key. l Revert to default Plug-in bar by selecting Reset to default. To import a plugin: 1. Click on the Popup control ( ) 2. Click on Import Plugin 3. Browse to the location of the plugin DLL file 4. Click on Open. 5.
l Windows Driver Printing: l The Print using a Windows Driver output task lets you send a job to any printer installed on the computer, using its own drivers. In this particular case, the printer does not need to be a PostScript printer. See "Print Using a Windows Driver" on page 520. PReS Workflow provides you with three main printing scenarios: l l Send output data to be printed as is: PReS Workflow sends a file containing only the data to the selected queue.
l l l l Windows Output printer queues are used to send print jobs to local or network printers. See "Windows Output Printer Queue" on page 61. LPR Output printer queues are used to send print jobs to printers via the LPR/LPD protocol. See "LPR Output Printer Queue" on page 62. FTP Output printer queues are typically used to send print jobs to FTP sites. See "FTP Output Printer Queue" on page 63. Send to Folder printer queues are typically used to send print jobs to local or network folders.
l l l l Add: Click to add a new command to the list displayed in the Commands box. You must then edit the new command’s description and value. Note that new commands are shared by all printer queues. Delete: Click to remove a command from the Commands box. Command description: Use this box to edit the description of the command currently selected in the Commands box. Command value: Use this box to edit the code of the command currently selected in the Commands box.
Windows Output Printer Queue Windows output printer queues send print jobs to local or network printer queues set up in the Windows session in which PReS Workflow is running. The corresponding Windows printer driver is used in the printing process. This type of printer queue does not support the transparency and duo-tone features, so you should not use it with PlanetPress Design documents that use those features.
l l Command description: Use this box to edit the description of the command currently selected in the Commands box. Command value: Use this box to edit the code of the command currently selected in the Commands box. Use the right-click menu for a list of standard printer control characters. LPR Output Printer Queue LPR output printer queues send print jobs to LPD-compatible printers using the LPD/LPR protocol.
l l l l l l Commands: The list of available commands appears in this box. Select either Pre-job commands or Post-job commands in the Selected box, and double-click a command from this list to add it to the appropriate list. Selected: Select either Pre-job commands or Post-job commands to add new commands to the appropriate list and to see those commands that have already selected. Double-click a command to remove it from the selected list.
l l l l l l Password: Enter a password associated with the FTP server user name entered above. Use FTP Client default port number: Forces the FTP connection on port 21, the default FTP port. FTP Port: Enter the FTP port to use. This option is disabled if Use FTP Client default port number is checked. The port should always correspond with the server's port number. Directory: Enter the directory to which the print jobs are to be uploaded.
Send to Folder Printer Queue Unlike Send to Folder output tasks, which are typically used to send data files to local or network folders, Send to Folder output printer queues are mostly used to send print jobs. The files generated will always be PostScript files. Properties General tab l l l l Folder: Enter the path of the folder to which the print jobs are to be saved. File name: Enter the name of the print jobs sent to this queue.
l l Command description: Use this box to edit the description of the command currently selected in the Commands box. Command value: Use this box to edit the code of the command currently selected in the Commands box. Use the right-click menu for a list of standard printer control characters. Triggers In PReS Workflow, a trigger is typically a two line piece of PostScript code placed just before the data.
Objectif Lune Printer Driver (PS) Introduction The Objectif Lune Printer Driver (PS) allows end-users to print directly to PReS Workflow from any Windows application, by using the familiar File|Print option. At the other end, PReS Workflow specifically can capture the incoming stream and convert it internally into a PDF file along with its metadata.
PostScript, or PDF. Note that PReS Workflow can only produce EMF or PostScript files. Possible printer properties settings, along with the data file type it will produce: Spool Print Jobs in EMF Format: l This will create an EMF data file. l This format is usually reserved for use with the Windows Print Converter action plugin. l This format can be obtained using PReS Workflow.
6. Send the configuration and start your PReS Workflow service. 7. Start the windows application from which you want to capture data. 8. Open your selected document. 9. Click File | Print. 10. Choose the same Windows print queue as in step 4. Note Steps 6-8 can be performed at any time, even if PReS Workflow is not yet started. This is because every Windows printer queue using Objectif Lune Printer Driver (PS) is paused by default. Once the service has started, it captures every queued job.
About Processes and Subprocesses Processes A process is a single workflow within the configuration. A process begins with a single input task, contains one or more tasks and/or branches, and terminates with one or more output tasks. In its simplest form, a process can simply retrieve data from a given folder and save it in a different folder. In most cases, though, processes are more elaborate and configurations, which may include many processes, can be extremely complex.
by sharing them to the whole configuration file. They can thus be used to perform redundant operations that may need to be executed numerous times; for instance, archiving a copy of a zipped file received as the input job file, then decompressing it before sending the unzipped version of it back to the calling process . Whenever a process calls a subprocess, the main process (the caller) will wait for the called subprocess to finish its execution before carrying on with its own.
l l l l l l Max percentage of threading (%): Determines how many processes you may have running at the same time. This is a percentage of the maximum number of threads specified in the "Messenger Plug-In Preferences" on page 639. For example if the maximum number of thread is 10 and you specify 50% here, a maximum of 5 replications will occur (the original process + 4 copies). As soon as possible: Select to have the process run continuously.
l Poll once per activity period: Select to perform this process’ initial input task no more than once for each set of contiguous blocks (blocks that are on the top of one another). Choosing this option overrides the polling interval option. By default since the Time Grid blocks are divided by hours, this option will make your polling happen once every hour. The Time Grid The PReS Workflow Process Options dialog box includes a time grid that lets you set exactly when you want a process to run.
l Click on any block to select / deselect it. l Click and drag from one block to another to toggle all blocks between the two. l Shift-click on any block to toggle all blocks from the top-left corner of the grid to the block you click.
l l l To select all of the time segments for a given day or date, click the day or date on the top grid ruler. To deselect all of the time segments for a given day or date, CTRL+click the day or date on the top grid ruler. To select all the days or dates for a given time segment, click the time segment on the left grid ruler. To deselect all the days or dates for a given time segment, CTRL+click the time segment on the left grid ruler.
Activate or Deactivate a Process All processes are Active by default, but you may make any PReS Workflow process Inactive as required. Because making a process active or inactive is a change in the configuration, to make the change effective you will have to send the edited configuration to your PReS Workflow service (See "Send your Configuration" on page 11). To activate or deactivate a process: 1. Right-click the process in question in the Configuration Components pane 2.
If any task converted into a subprocess was previously using local variables, these variables must be removed or transferred to global variables or job information to be usable in the newly created subprocess. Import Processes from Another Configuration File You can import individual processes or groups of processes from a PReS Workflow configuration file without having to import the contents of the entire configuration file.
both include a startup process, the one in the imported configuration will become a standard process. Important considerations l l When importing a PReS Workflow configuration file, your PlanetPress Design and PrintShop Mail document are not physically imported as they are not part of the configuration file itself. In order for the documents to be available, you will need to send each document from PlanetPress Design and PrintShop Mail (see their respective documentation for details).
Using Scripts Scripts can be used to perform various operations, such as to manipulate data, for example. PReS Workflow can perform scripts written in four different scripting languages and also provides an interface for editing scripts. Warning While this chapter provides some very useful and detailed information about scripting within PReS Workflow, its focus is to inform you about the features, variables and functions unique to this environment.
Multiple APIs (methods of communicating with PReS Workflow scripting tools) are available through the scripting engine, in all languages. l l l l l The Watch object is used to communicate with your current process and configuration. See "The Watch Object" on page 93. You can manipulate PDF files using the PReS Alambic API. See AlambicEdit Library Reference. Note that the PReS Alambic API is part of the PDF Tools. You can manipulate the metadata in your process using the Metadata API.
Import and Export Scripts Both the Script Editor and XSLT Editor let you import and export scripts. Note When you import a script, it replaces any script currently displayed in the editor. To import a script: 1. In the editor, choose File | Import. The Open dialog box appears. 2. To import a script that uses a different scripting language or that was saved under a different file format, make a selection in the Files of type drop-down list. 3. Navigate to the script you want to import and select it. 4.
To find strings in a script: Note If you only want to search a particular section of the script, you should select it before performing the following procedure. 1. Choose Search | Find, or press CTRL+F. The Find Text dialog box appears. The last used string is displayed in the Text to find drop-down list box. 2. Set the search settings and options. l l l l l l l l Text to find: Enter a new search string or select a previous search from the drop-down list.
selection. When the search reaches the beginning of the script or script selection, the search finishes. It does not loop back to the beginning. l l From cursor: Select to start the search from the position of the cursor. Entire scope: Select to search the entire script or a script selection. The scope croplands to a script selection if you make a selection before executing the Find. 3. Click OK. The first matching string is highlighted in the script. 4.
l l l l l Selected text: Select to find matching text only within a text block you select. The text must be selected before you run the search. Forward: Select to search the script forward, from the location of the cursor or from the beginning of the script, depending on what you choose as the origin (From cursor begins where the cursor is currently located in the script, Entire scope begins from the beginning of the script or beginning of script selection).
To go to a line in a script: 1. Click anywhere in the Script Editor, then choose Search | Go To Line, or press Alt+G. The Go To Line dialog box appears. The last used line numbers are displayed in the Enter new line number drop-down list box. 2. Enter a new line number in the Enter new line number box or select one from drop-down list. 3. Click OK. Toggle Bookmarks Bookmarks help you identify and jump to specific places within your script (see "Jump to Bookmarks" below).
To jump to a bookmark: l From the editor’s pop-up menu, choose Go To Bookmark and a given bookmark number. If the bookmark you selected was displayed on a line, the cursor jumps to that line. SOAP Server API Reference PReS Workflow offers a SOAP server API Reference allowing jobs to be submitted from third party application using the SOAP protocol. Remember that SOAP stands for Simple Object Access Protocol.
Arguments l l l File – base64Binary. This is an array of byte base64 encoded (see http://en.wikipedia.org/wiki/Base64). SubmitJobInfStruc – Structure containing any required information to prepare the file for a valid insertion into a PReS Workflow process. ReturnJobFile – Boolean value. When true, PReS Workflow SOAP server returns the job file. When false, there no file is returned to the SOAP client.
Note To return the file, the process must be completed before the timeout of the server occurs. The Timeout option can be set in your PReS Workflow preferences. SOAP API - PostJob Syntax PostJob (File, PostJobInfStruc , user name, Password) : PostJobResult Description The PostJob method allows users to remotely submit files to PReS Workflow by using the Resubmit from here feature.
Note The task index can be retrieved by using the GetProcessTaskList method. See point GetProcessTaskList for details. Note The PostJob method can never return a file to the calling application. SOAP API - GetProcessList Syntax GetProcessList (user name, Password) : GetProcessListResult Description The GetProcessList function allows SOAP clients to request the list of available PReS Workflow processes, based on their authentication credentials. Parameters l user name – String containing the user name.
Note To obtain access to the complete list of processes for all users, the end-user must have administrator privileges. SOAP API - GetProcessTaskList Syntax GetProcessTaskList (ProcessName, user name, Password) : GetProcessTaskListResult Description The GetProcessTaskList function will allow a user to remotely request the tasks list of a process. This will be useful with the PostJob API since it needs a TaskIndex. Parameters l ProcessName – The Name of the PReS Workflow process.
Note The TaskNames array will be sorted by the execution order of the process with the primary input of the process having an index of 1. SOAP API - GetSOAPProcessList Syntax GetSOAPProcessList (user name, Password) : GetSOAPProcessListResult Description The GetSOAPProcessList function will allow users to request the list of PReS Workflow processes that contain a SOAP Input plug-in with the SOAP action name. This is useful when working with the SubmitJob API since it requires a SOAPActionName.
Note If a user has administrator privilege, he will have access to all processes and therefore he will see all the processes. SOAP API - PostJobInfoStruc PostJobInfStruc Structure containing any required information to prepare the file for resubmission into a PReS Workflow process. l VariableList – Array of complex type, containing pairs of variable names and variables value. The list also contains the JobInfo variables.
l l VariableName – String l VariableValue – String OAPActionName – String containing the name of the Input SOAP task’s action name. The Watch Object PReS Workflow scripting offers a number of methods of communicating with your process by means of PReS Workflow automation object's methods and functions. The automation object is available in all 4 languages through their own syntax - the examples provided here are for VBScript.
Variable Name Description Example Usage (VBScript) "Watch.GetMetadataFilename" on page 99 Retrieves a string containing the job's metadata path and filename. This is useful when using the Metadata API in your script. Example Usage: str = Watch.getmetadatafilename "Watch.GetJobInfo" on page 100 Retrieves the content of a numbered job info (%1 to %9). Example Usage: str = Watch.getjobinfo(9) "Watch.GetVariable" on page 102 Retrieves the content of a local or global variable by name.
Variable Name Description Example Usage (VBScript) Example Usage: str = Watch.inputbox("Caption","Message","default") "Watch.SetJobInfo" on page 101 Writes the value of a string to a numbered job info. Example Usage: Watch.setjobinfo 9, "String" "Watch.SetVariable" on page 103 Writes the value of a string to a local or global variable by name. Example Usage: Watch.setvariable "global.GlobalVar", "Hello World!" "Watch.Sleep" on page 106 Pauses all processing for X milliseconds.
on Desktop" option must be enabled and you must be logged on as the same user as the PlanetPress Watch Service. Examples In the following example, showmessage() displays a dialog box saying “test message”. VBScript Watch.ShowMessage("test message") JavaScript Watch.ShowMessage("test message"); Python Watch.ShowMessage("test message") Perl $Watch->ShowMessage("test message"); Watch.ExecuteExternalProgram Calls and executes an external program through a specified command line.
Flag Effect 0 Hide the execution window. 1 Display the window normally. 2 Display the window minimized. 3 Display the window maximized. 4 Makes the window visible and brings it to the top, but does not make it the active window. WaitForTerminate : A Boolean value that, if true, pauses the script until the command line has been fully executed. Examples VBScript Watch.ExecuteExternalProgram "lpr -S 192.168.100.001 -P auto c:\myfile.ps", "c:\", 0, true JavaScript Watch.
file, for example to replace data within it. If your script writes to this file, the modified contents will be used by the next plugin in your process. Example In the following example, GetJobFileName() retrieves the name of the job file, which is then logged using "Watch.Log" on page 104. VBScript Dim s s = Watch.GetJobFileName Watch.Log "The job filename is: " + s, 3 JavaScript var s; s = Watch.GetJobFilename(); Watch.Log("The job filename is: " + s, 3); Python s = Watch.GetJobFileName() Watch.
Python Watch.GetOriginalFileName() Perl $Watch->GetOriginalFileName(); Watch.GetMetadataFilename Returns the complete path and file name of the metadata file associated with the current job file. Example VBScript Watch.GetMetadataFileName JavaScript Watch.GetMetadataFileName(); Python Watch.GetMetadataFileName() Perl $Watch->GetMetadataFileName(); Watch.InputBox Warning Starting version 7.0, the Watch.
Clicking OK returns the value entered by the user. If no value was entered the default value is returned. Clicking Cancel returns the default value. You must enable the “Run on desktop” option for the PReS Workflow process whose script calls Watch.InputBox. Otherwise PReS Workflow application may stop working and require a reboot. Example s = watch.inputbox("caption", "message", "default") watch.showmessage(s) Examples In the following example,Watch.InputBox requires the user to enter a line of text.
Syntax Watch.GetJobInfo(Index: integer): string Example VBScript Dim s s = Watch.GetJobInfo(3) Watch.Log "Jobinfo 3's value is: " + s, 2 JavaScript var s; s = Watch.GetJobInfo(3); Watch.Log("Jobinfo 3's value is: " + s, 2); Python s = Watch.GetJobInfo(3) Watch.Log("Jobinfo 3's value is: " + s, 2) Perl $s = $Watch->GetJobInfo(3); $Watch->ShowMessage("Jobinfo 3's value is: " . $s, 2); Watch.SetJobInfo Sets the job information index to a specified string value. Syntax Watch.
Python Watch.SetJobInfo(3, "Job info 3 Value") Perl $Watch->SetJobInfo(3, "Job info 3 Value"); Watch.GetVariable Returns the string value of the corresponding variable name. Note that if an undeclared variable is called using this method, an error will be generated. Syntax Watch.GetVariable(Name: String): String Example VBScript Dim s s = Watch.GetVariable("MyVariable") Watch.Log "MyVariable's value is: " + s, 2 s = Watch.GetVariable("global.MyVariable") Watch.Log "global.
Watch.SetVariable Sets the variable to a specified string value. Note that if an undeclared variable is called using this method, an error will be generated. Syntax Watch.SetVariable Name: String; Value: String Example VBScript Watch.SetVariable "MyVariable", "Desired value" Watch.SetVariable "global.MyVariable", "Desired value"/ JavaScript Watch.SetVariable("MyVariable", "Desired value"); Watch.SetVariable("global.MyVariable", "Desired value"); Python Watch.SetVariable("MyVariable", "Desired value") Watch.
Arguments StringToExpand —A regular parseable string that may contain system variables (%u, %f), user variables (%1 to %9), octal codes, and data selections. Example This example results in expanding the string of the variables to the date value in the following format: “YYYY-MM-DD”. VBScript Dim s s= Watch.ExpandString("%y-%m-%d") Watch.Log "Current Date is: " + s, 2 JavaScript var s; s= Watch.ExpandString("%y-%m-%d"); Watch.Log("Current Date is: " + s, 2); Python s= Watch.ExpandString("%y-%m-%d") Watch.
Level Type Text Color in Service Console 1 Error Red 2 Warning Orange 3 Information Black 4 Debug Grey Arguments Message—A string representing the message that is logged in the log file. Note that the text of the message must use the locale encoding of the system where the PReS Workflow software will be running, otherwise it will be unreadable. Level—An integer between 1 and 4, specifying the severity level of the error message.
JavaScript Watch.Log("this is a log", 3); Python Watch.Log("this is a log",3) Perl $Watch->Log("this is a log",3); Watch.Sleep Pauses the process for the specified number of milliseconds. This can be used while waiting for something else to happen when the delay is known. Syntax Watch.Sleep Milliseconds: integer Example In the following example, sleep() pauses the process for 1 second (1000 milliseconds) VBScript Watch.Sleep 1000 JavaScript Watch.Sleep(1000); Python Watch.
Example This example will always return true, as the condition is static. It is, after all, simply an example. You get the idea. VBScript Dim everythingOK everythingOK = true if (everythingOK = true) then Script.ReturnValue = 1 else Script.ReturnValue = 0 end if JavaScript var everythingOK; everythingOK = true; if(everythingOK = true){ Script.ReturnValue = 1; } else { Script.ReturnValue = 0 } Python everythingOK = True if everythingOK == True: Script.ReturnValue = 1 else: Script.
Stopping Execution When using a script, you may come to a point where you'd like the task to fail (raise an error) and trigger your On Error tab under certain conditions. This can be done by using the scripting language's built-in error features, described here. Note that the value or description of the error will not be available to your error process if one is used. However, when available, a description of the error message will be logged in the Watch log. VBScript In VBSCript, the Err.
Python In Python, the raise statement is similar to JavaScript and will stop processing unless an except statement is used. See the python documentation. s = Watch.GetJobInfo(9) if not s: raise NameError('Value cannot be empty') else: # Do something with Job Info 9! Watch.Log("Job Info 9's value is: " + s,5) Perl In PERL, die() raises an exception and triggers the On Error tab, unless the unless command is used. See the perl documentation.
The term ... ... is the same as an Excel ... ... is the same as a Database ... Key Column Field KeySet Row Record Note Group and key names are case-insensitive. API Reference Obtaining an instance of the Repository Object JavaScript var repoObject = new ActiveXObject("RepositoryLib.WorkflowRepository"); VB Script set repoObject = CreateObject("RepositoryLib.
RepoObject.AddGroup("MyGroup","['FirstKey', 'SecondKey']"); Many methods require using the JSONStringArray type but JSON is not natively supported in VB Script. Therefore, for those methods, only JavaScript sample code is provided. There are many resources on the Web that propose ways of implementing JSON parsing in VB Script so you can implement whichever you see fit. However, using JavaScript is highly recommended.
Name Description values for the key, in all keysets for the group, are removed. Note that when the Group contains a large number of KeySets, this operation may take a while. ListKeys Retrieves the list of all Key names and data types in Group GroupName, stored in a JSONStringObject. You should use JSON.Parse() to convert the string into an actual JavaScript object. You can then use the for…in construct to list the different properties for that object (i.e. the keys in the group).
Name Description KeyName to Value for all keysets that match Condition. The condition is specified using basic SQL WHERE syntax. The Condition may be left empty in which case all keysets in GroupName are updated. Note that KeyName must exist in GroupName, otherwise an error is raised. The method returns an array of the keyset ID's that were updated ( [1,2] ), or an empty array ( [] ) if no keysets were updated.
Name Description Condition may be left empty, in which case all keysets in GroupName are deleted. The method returns the number of keysets that were deleted. RemoveKeySetByID Deletes the keyset whose ID equals ID from GroupName. Returns 1 if successful, 0 otherwise. Note that this method is functionally equivalent to using RemoveKeySets() with its Condition parameter set to "ID=ID".
AddGroup Creates a group named GroupName and optionally creates keys listed in keyNames. The keyNames parameter may be empty. Syntax AddGroup(GroupName: string, keyNames: JSONStringArray) Examples JavaScript repoObject.AddGroup("Users", '["FirstName", "LastName"]'); repoObject.AddGroup("Users", ''); VB Script repoObject.AddGroup "Users", "[""FirstName"", ""LastName""]" repoObject.AddGroup "Users", "" AddKey Adds key KeyName to group GroupName. KeyName must not already exist in the specified group.
AddKeySets Inserts a new keyset inside GroupName and assigns values to keys as specified in KeyValues. Every key specified in KeyValues must exist otherwise an error is raised. However, it is not required to specify all available keys in KeyValues. Only the keys specified are updated in GroupName while unspecified keys are set to an empty string. Syntax AddKeySets(GroupName: string, KeyValues: JSONObjectArray): JSONIntegerArray Examples JavaScript repoObject.
repoObject.AddValue("Users", "LastName", "Smith"); VB Script repoObject.RenameGroup "Users", "LastName", "Smith" CheckRepository Verifies the integrity of the repository and recovers unused space left by deleted keysets. Similar to packing a database, the operation is non-destructive but it does require exclusive access to the Repository. You should therefore only perform this operation when you know for sure no other process is accessing the Data Repository.
GetKeySets Retrieves Keys values in GroupName for keysets that match Condition. When Keys is left empty, all keys are retrieved. When Condition is left empty, all keysets are retrieved. Syntax GetKeySets(GroupName: string, Keys: JSONStringArray, Condition: string): JSONStringArray Examples JavaScript repoObject.GetKeySets("Users", '["FirstName","LastName"]', "Gender='M'"); VB Script repoObject.
email for first user named Smith repoObject.GetValue("Users", "email", ""); // retrieves email for first user VB Script repoObject.GetValue "Users", "email", " LastName=""Smith"" AND FirstName=""John"" " // retrieves email for John Smith repoObject.GetValue "Users", "email", " LastName=""Smith"" " // retrieves email for first user named SmithrepoObject.
Examples JavaScript var repoObject = new ActiveXObject("RepositoryLib.WorkflowRepository"); var myList = JSON.parse(repoObject.ListKeys("Internal")); for (var Property in myList) { // Log all key names for group Users to the console Watch.Log(Property,2); } Sample return value '{"ID": "meta", "FirstName": "string", "LastName": "string", "email": "string", "DateC": "meta", "DateM": "meta"}' As shown in the sample, the value associated with each key name is actually the data type for that key.
Syntax RemoveKey(GroupName: string, KeyName: string) Examples JavaScript repoObject.RemoveKey("Users", "email"); VB Script repoObject.RemoveKey "Users", "email" RemoveKeySetByID Deletes the keyset whose ID equals ID from GroupName. Returns 1 if successful, 0 otherwise. Note This method is functionally equivalent to using "RemoveKeySets" on the next page with its Condition parameter set to "ID=ID". Syntax RemoveKeySetByID(GroupName: string, ID: integer): integer Examples JavaScript repoObject.
RemoveKeySets Deletes all keysets in GroupName that match Condition. The condition is specified using basic SQL WHERE syntax. Condition may be left empty, in which case all keysets in GroupName are deleted. The method returns the number of keysets that were deleted. Syntax RemoveKeySets(GroupName: string, Condition: string): integer Examples JavaScript repoObject.RemoveKeySets("Users", 'Gender="M"'); VB Script repoObject.RemoveKeySets "Users", "Gender='M'" RenameGroup Renames group oldName to newName.
newName. Syntax RenameKey(GroupName: string, oldName: string, newName: string) Examples JavaScript repoObject.RenameKey("Users", "LastName", "SurName"); VB Script repoObject.RenameGroup "Users", "LastName", "SurName" SetValue Updates multiple keysets in group GroupName by setting the key KeyName to Value for all keysets that match Condition. The condition is specified using basic SQL WHERE syntax. The Condition may be left empty in which case all keysets in GroupName are updated.
MaritalStatus=""Married"" " repoObject.SetValue "Users", "FormOfAddress", "Miss", " Gender=""F"" AND MaritalStatus="""" " SetValueByID Updates KeyName with Value in group GroupName, where the keyset's ID matches the ID parameter. KeyName must exist in GroupName, otherwise an error is raised. The method returns the ID of the keyset that was updated or -1 if the keyset was not updated.
Syntax Version(): string Special Workflow Types PReS Workflow supports multiple input and output types, in so many different combinations that it would be hard to give example processes for each possibility. However, some types of processes like PDF, HTTP and SOAP are important enough to pay some attention to them. This chapter will describe each of these special workflow types and give at least one example of an implementation that uses them.
a SOAP request as a client. The SOAP Server workflow will show how to create a process that responds to SOAP requests, and where our own WSDL is located. PlanetPress Capture Workflow PlanetPress Capture, introduced in PlanetPress 7.2 and enhanced ever since, is a set of tools that is used to simplify digital archiving processes by capturing information from a special pen which records everything it writes on paper, as long as this paper contains special Anoto Patterns.
Generating the Capture Patterns Once your document is created, the Capture Fields Generator action task is used to apply the capture patterns to each of your documents and send them to the printer. This printing process will consist of: l Retrieving your data file. l Creating metadata (See "Create Metadata" on page 446). l Separating each individual document in the metadata (this can be done in your Design document or through the "Metadata Level Creation" on page 460 action task).
Managing and Post-Processing There are a couple of things that can be done even after documents have been inked. As long as a document remains open, it is still present in the Capture database and be used in a process: l l The "Find Capture Documents" on page 434 input task is used to retrieve a list of documents under specific criteria. The Capture Condition and Get Capture Document tasks are used to effect post-processing and retrieve document from the Capture database.
PReS Workflow. This document specifically refers to the Anoto DP-201 Digital Pen, not other equipment has been tested. Anoto Functionality Statement Statement ('Paper featuring Anoto functionnality') that is automatically placed on the page when a PlanetPress Capture field is present. The statement can also include the Trace Code Anoto Pattern A series of dots placed in a pattern that is unique to each page where the pattern is printed.
pens, however the Client contains the database of documents and patterns. The Clients communicate with the server to authenticate pens. This architecture is only provided to simplify pen licensing for users with a large number of pens. Closed Document A document still within the PlanetPress Capture Database of which all the required fields have been filled by the Capture Field Processor from a PGC.
Pattern Sequence Pattern Sequences enable the multiplication of the number of available pattern by adding an extra identification to the document. A Pattern Sequence is also attributed to each Anoto Digital Pen, such as an incoming PGC file will contain the Pattern, on which the Pattern Sequence is added from the pen database. The pattern and pattern sequence refer to a specific document in the database.
PlanetPress Capture and its functionality. Warning PlanetPress Capture Fields cannot simply be inserted into an existing document as-is and expected to work properly, efficiently or consistently. In order to design a document with Capture Fields, you must review and understand the Critical PlanetPress Capture Implementation Restrictions.
l l Total database size is limited to 4GB of data. l Total size of a single table is 2GB. l May be unstable in large implementations. MySQL l l l l l Database can be in any location, but performance will depend on the speed of the connection between PReS and the MySQL server. MySQL's performance has been slower than SQL Server and SQL Server Express during our tests. By default, MySQL is configured not to allow any SQL request larger than 16 megs.
l In SQL Server, if one of your requests is dropped because of simultaneous accesses, resubmitting the PGC should resolve the issue. Security Considerations PlanetPress Capture introduces new and efficient methods for digitally capturing the contents of ink laded out on physical paper. However, because of its nature, some end users may voice concerns about security and privacy.
between penDirector and PReS Workflow could use software such as a packet sniffer to retrieve its parts and recreate the PGC files. This may be resolvable by create a secure VPN tunnel for each location where penDirector is installed instead of going through regular remote HTTP server. l l l The PlanetPress Capture database, since it can be external to PReS Workflow such as on a MySQL server, will be dependent on your own database security.
In a typical PlanetPress Capture implementation, a process in PReS Workflow generates output (generally, this output is directly printed) and, at the same time, will "lock" one pattern for each page that it generates, if that page contains a pattern. PReS Workflow also stores a copy of each document in the Capture Database, in PDF format.
unless their implementation is missing important parts, such as the "cleanup" process. But this also means a smaller minority of our users may require more than 20,000 patterns, so let's deal with this now. Extending There are actually 2 ways of dealing with extending the number of patterns using the currently available tools, each with its own advantages and disadvantages. Using separate PReS Workflow servers and licenses.
Note It's very important to note here that the Anoto Digital Pen has absolutely no concept of Pattern Sequences. When "attributing" a sequence to a pen, this is fully on the PReS Workflow side, in the Capture Database. This means that if a pen is mislabeled or someone picks up the wrong pen, this pen has absolutely no way to know that it is writing on the wrong paper. more about this in the Contamination section below.
eventually be closed by a manual or automatic procedure. However, the physical document with the pattern still exists even if it is closed in regards to the PlanetPress Capture database. Contamination would happen if a new document is printed with the same pattern, but somehow the "old" document re-surfaces and someone writes ink on it and docks the pen.
reverted. In implementations where the pen signs high number of documents, this can especially be an easy way to do this, as chances are the data will not match in at least one case. Conclusion l PReS Workflow can only generate 20,000 unique patterns l One pattern is used (locked) for each page containing a pattern.
Example: http://127.0.0.1:8080/ProcessPGC Bluetooth Connectivity The Anoto penDirector program can also connect directly to the pen via wireless Bluetooth and receive PGC files directly through the Bluetooth link, without needing to dock the pen. To pair penDirector with an Anoto Digital Pen: 1. Make sure that a Bluetooth dongle is present and enabled on the computer where penDirector is installed. 2.
3. Click on the paired pen that you want to configure 4. Specify a PGC Storage folder 5. Check the PGC POST URL option 6. Enter the URL of your PGC handling process in the box 7. Click OK to save. PlanetPress Mobile Application The PlanetPress Mobile application can be installed on some mobile phones and enable fast and direct connectivity between the Anoto Digital Pen and PReS Workflow.
Paper quality The PlanetPress Capture technology, when generating the Anoto Pattern, already accounts for ink dispersion on laser printers and on general-use laser paper. Therefore, using paper that is not of the same quality (for example, one where the dispersion rate is much higher) or the same type (reflective paper) may not permit the pen's camera to read the pattern properly.
This is because the pen's camera (which captures the position of the pen) is located under the pen tip and must fully see the pattern.
Knowing this, the best practice when creating fields is that they have, at the very least, a 7mm margin on each size of the actual area you want to capture from. For example, an effective 30mm wide pattern will actually be 44mm wide using these margins. The margin should be for both the vertical size and the horizontal size.
the next field. This can cause PlanetPress Capture to detect the ink as being present, and thus trigger whatever that field does. PlanetPress Capture ICR The term "ICR", which means "Intelligent Character Recognition" is an evolution on the popularly-known "OCR", which is "Optical Character Recognition".
required in order for the ICR to work: l l l l In PlanetPress Design, a Capture Field Object must be added and the Perform ICR option must be activated (See the Capture Field page in the PlanetPress Design User Guide). This must be either a Multi-Area Field or a Text Field. The Capture Fields Processor must have the Perform ICR Recognition option checked, and language needs to be selected. Once the ICR data is available, do something with it.
Terminology and Definitions In regards to our ICR technology specifically, the following terminology applies: l l l l ICR: "Intelligent Character Recognition", or the engine that will read the pen data and attempt to recognize the text written using the pen itself. The ICR engine uses the path of the pen, its movement speed as well as the overall shape of each character to determine which character was written. ICR Value: The alpha, numeric or alphanumeric value that was determined by the ICR engine.
Using the Most Restrictive Mask l l Target: Form designer. What: In the Capture Options tab of a Capture object, the mask type indicates the type of character to be recognized. There are 3 possible selections: numeric, alphabet and alphanumeric. The alphabetic mask type allows you to select the letter case.
The following diagram illustrates the available mask types. It is recommended to select the mask type that is the closest to the desired result. An alphanumeric field should be used as a last resort. Guidelines for Capture-Ready Fields l l Target: Form designer What: Only one character per Capture field can be recognized. When expecting multiple characters making up a word or phrase, you must make sure that the user only writes one character per field.
Why: To avoid any ink marks that would spill over from one field to another. If both fields A and B are to close in proximity and the ink marks from field A spill over to field B, then the marks captured on field B would be considered as being part of a character written on field B. For example, if a number spills over and is written over two fields like numbers 9, 1 or 7; then the bottom tip of these numbers could be considered as number 1 in the second field.
How: Make sure there’s enough space between each field. You must re-design the document if that’s the case. There’s no minimum value that is required as the distance between 2 fields, except for the 7mm border that is required in order for the Anoto digital pen to recognize the pattern being used. Writing in a Legible Way l l Target: User. What: It is important to write in a legible way i.e. applying yourself by writing well defined numbers and letter that are easily interpreted.
Why: The available filters to interpret the ink marks done with the Anoto digital pen, allow you to select the engine language to be used. Doing so will give you results that are the closest match to the captured data. Multiple cultural characters can be interpreted with ICR once the correct language is selected such as û, à, é, etc. How: This option is available from the Capture Fields Processor task.
Possibility of Interpretation Error in an Automated Process l l Target: Workflow designer What: We cannot be 100% sure that a character would be recognized by PlanetPress Capture as it should. Therefore, the analysis of a value interpreted with ICR should only occur if the level of confidence is superior to a determined level. Why: An automated process can treat the characters incorrectly due to an incorrect interpretation of a value. This occurrence should be minimized as much as possible.
l Any input task l "Create Metadata" on page 446 l "Capture Fields Generator" on page 420 l Print output PGC Handling Process The second process is the PGC Handling process. It receives data from the Anoto Digital pen, updates the Capture database and releases patterns as appropriate.
l "Get Capture Document" on page 439 l Archive or Print output Capture Post Processing Workflow Though the "Basic Functional Capture Workflow" on page 154 is minimal functional one, it will most likely not be enough for most actual implementations. The goal with PlanetPress Capture (and PReS Workflow in general) being to automate as much as possible, there are some tools within the PlanetPress Capture tasks that can greatly help with this goal.
Task Breakdown: l l l The HTTP Server Input receives a POST request sent either by the Anoto penDirector or the PlanetPress Mobile Application. This requests contains information sent by the pen as well as a PGC file as an attachment. Because we're only concerned about the PGC, the task is configured to ignore the XML envelope as well as loop through each attachments (of which there is only one). So, the output of the task is the PGC file alone.
After Retrieving Information from the Capture Database There are two basic ways in which the Find Capture Document task can be used. First, in an automated process that runs at specified intervals. For example, the following process which sends a daily report of all incomplete and "in error" documents to an agent who would presumably take action on each document through the document manager.
Task Breakdown l l The Find Capture Documents task queries the Capture database for documents that correspond to certain specific conditions. For example, here we would look for all documents that are either in an "Error" or a "Partial" state, which means they received ink but are not completed correctly. To do this, the "Content Status" filter and setting it "Equal to" those states. Two conditions are necessary, and the "Condition is true when" is set to "all items are met".
3. Open the invoice.pp7 document and send it towards your local PReS Workflow server (localhost or 127.0.0.1) 4. Open the configuration file CaptureExampleProcess.pw7 5. Click the PReS Workflow button (File menu) and go in Preferences. 6. In the HTTP Server Input 2 section, check the Serve HTTP resources option, change the Resource action name box to static , and the Resource folder to c:\PReS\http . Then, click OK. 7. Send the configuration to your local PReS Workflow server. 8.
HTTP Server Input tasks are typically used in one of the two following situations: l l HTML Form Action: An HTML Form in the browser that may contain text and attached files can be filled and sent to a process with the HTTP Server Input task. HTTP Data Submission: A custom application or a server sends the request to PReS Workflow using either a POST or GET command. The application or server then waits for a response from PReS Workflow Tools.
l l Enable server for SSL requests: This enables secure communication between the browser and the server via HTTPS. By enabling this option, you will need to provide for the proper certificates, key and password. While this configuration is beyond the scope of this document, there are plenty of resources on the Internet to explain these systems. Serve HTTP resources: This is where you enable static resources in PReS Workflow.
And finally, the HTTP Server Input task properties. While these are described in the "HTTP Server Input" on page 200 task properties page, here are a few considerations to keep in mind when using this task: l l l l l The HTTP Action corresponds precisely to the name immediately following the first slash of your address. That is to say, placing the action myaction here means the process would be triggered by opening http://127.0.0.1:8080/myaction in your browser.
7. The very last file that is active when the process finishes is then returned to the HTTP service. 8. The HTTP service returns the file to the client and then closes the connection. 9. If, during this time, the timeout has expired (if the process takes more than 120 seconds), the HTTP service returns a "timeout" to the client, but the process stills finishes on its own. When the process finishes, the return file is ignored by the HTTP service.
Breakdown of this URL: l l http:// : transfer protocol. This could be HTTPS if the SSL certificates are activated in the preferences. ppworkflowserver : name of the machine. This could also be an IP (192.168.1.123) or a full domain name (www.myserver.com), depending on the connectivity between the client and PReS Workflow Server. l :8080 : The default PReS Workflow HTTP Port, set in the preferences. l /getinvoice : The HTTP Action Name, as set in the HTTP Server Input task.
l l l It checks whether the invoice request exists by checking if the size of the file is less than 1kb using "File Size Condition" on page 356. The condition returns "true" if the file is not found: c:\PReS\archives\pdf\invoices\xmlget('/request[1]/values[1]/invoicenum [1]',Value,KeepCase,NoTrim).pdf Here, the xmlget() function grabs the invoicenum variable from the GET request, which would be INV999999.pdf in the specified folder.
Task Breakdown l l l The HTTP Server Input receives the initial request from the browser. Because this is a demonstration, a backup is made of the XML request. It's not suggested to do this every time, especially on servers receiving a large number of requests, as these files do take some amount of space for each request. A condition checks whether the form has been submitted, by verifying that one of the required fields is empty.
l l l l Modifying Metadata does not immediately modify the data. This is one of the benefits of Metadata because you can sort it, filter it, sequence it, add data to it, without ever modifying the data file itself. This is important because if you, for instance, filter out certain data pages from the metadata and then save your data file with the Send to Folder task, the full data file is saved, not the filtered one. This is resolved through different methods, used in the different examples below.
Daily Sales Report from PDF Files This workflow makes heavy use of both PDF Tools and Metadata, and assume that you are using PReS Workflow version 7.3 or higher. This single process workflow generates a daily sales report for any sales rep inside of a company which made at least one sale. It does this by capturing the invoices generated within a specific day, putting all the invoices for each sales rep in a single PDF and then sending it to the sales rep.
l l l The "Metadata Sequencer" on page 464 acts like a splitter, where the separation happens whenever the Rep ID changes. Since documents are sorted with that field, each sequence can contain one or more document, but they will all be for the same Rep ID. "Create PDF" on page 258 is then used to generate a single PDF for each sales rep.
There are different types of tasks: l l l Input Task: Will either capture data from a specific location, or wait for input from a service or other computer to start processing. Action Task: Will manipulate the data in any number of ways. An action task is any task that is not an input or output task or a branch or condition. Output Task: Will output data to a specific location or send to a different service or computer.
Variable Properties When you edit tasks, you may notice that some of the properties that you can modify have a red (or more precisely, a maroon) title. This means that the property can be dynamically determined whenever your process runs, that is to say it will not remain static. This can be extremely useful when, for example, you want to determine how many copies you will print out depending on your data, or what document will be used in the printout depending on the department it came from.
into 4 items that provide variable properties: l Variables l System: Contains system variables, also called "Standard Variables" on page 535. l Job Info: Contains Job Info variables from %1 to %9 l l l l l l l l l Local Variables: Contains a list of local variables in this process. If no local variables exist, this item is disabled. Global Variables: Contains a list of global variables in this configuration. If no global variables exist, this item is disabled.
l l Field indicates a data selection for a database emulation — field(1,0,0,'Billing_ Email',KeepCase,NoTrim), for example. The lookup() function indicates a lookup in the "Data Repository Manager" on page 610. Unknown Tasks An unknown task is a task location that is not linked to any existing known task. Unknown tasks can have multiple causes: l l l l l Cutting an input or output task will replace it with an unknown task.
Mask Format Here are the different mask formats available: l l Literal characters: Any alphanumerical character is considered literal character and must appear. For example, a mask of "trigger.txt" will not capture any other files than that name. Wildcards: Two wildcards are available in masks. l l l Asterisk (*): Supports any number of characters. *.txt would pick up any text file, file*.txt would pick up any file starting with file and any characters: file1.txt, filetest.txt.
l l Date are entered and displayed as yyyy/MM/dd (2007/06/13, for example). Times are entered and displayed using the 24 hour format as HH:mm:ss (3:38:54 PM, for example, is entered and displayed as 15:38:54).
Input Tasks Input tasks are the starting point to any process and determine what file this process will being with. Each process must begin with an input tasks, and although a given process may have multiple input tasks, no task can have more than one initial input task. Initial Input Tasks Initial input tasks are always at the beginning of a process and are always triggered when the process starts.
time. It is also important that while the Folder Capture input task is processing files it keeps a copy of each file in a temporary folder, and will not delete any of these files until it has finished processing all of them. This may cause issues with running out of disk space. Secondary Input Tasks Secondary input tasks are placed in the process like an action task would and will replace the job file in the process with the file they retrieve.
Create File Create File input tasks are different from other input tasks in that they do not pull in data from a source location. The data that this task passes along to other task is its own: text or values from variables entered when the task was created or last edited. Since Create File input tasks are not dependent on data from external sources, they are performed at every polling interval and the process is thus started every time.
"Other" Tab l Job Information group l l l l l Information elements: indicates what job infos are automatically created by the input task. Add lines before first data page: Using the arrows keys you can add any job information directly at the beginning of your data file. Backup input files: Check this to save a copy of each data file that is captured by your input. These files are saved in the PReS Suite Workflow Tools working folders under the "Backup" folder.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Email Input Email Input retrieves email data through a Microsoft Outlook or POP3 connection. Note If Microsoft Outlook connection is used, Microsoft Outlook 2000 or higher must be installed on the computer where PReS Workflow is located.
using this method. Properties General tab l Data Location group l l l Message body: Select to use the data found in the body of the email. Attached file: Select to use the data found in the email’s attachment. If both the Message body and Attached files options are selected, the message’s body and the message’s attachment are treated as separate data files and processed one after the other. Unzip attached file: Select to unzip the attached files.
Login Tab l Use Microsoft Outlook: Select to use the Microsoft Outlook email account of the current user to receive emails. The current user is the one defined in PReS Workflow Service Logon. l l Move message after processing to folder: Enter the name of an Outlook Folder to keep copies of the emails taken by this email input task. You should enter only the name of the folder as it appears in Outlook’s Folder List area, regardless of whether it is a child of another folder.
Job Information definitions l l %1 - Date received. Contains the date of the reception of the email (and not the date of retrieval by PReS Workflow). The format is YYYY/MM/DD HH:MM:SS. %2 - Sender's name: Contains the name of the sender as defined by the sender himself (or, if the sender is using Exchange, by the name defined in his Exchange server). l %3 - Sender's address: Contains the email address of the sender as defined by the sender himself.
l l l l l l l l Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked.
Folder Capture Folder Capture input tasks retrieve files corresponding to a specified file mask, from a specified folder. Input Folder Capture retrieves all files corresponding to the specified mask. These files may be of any format, even formats that are not readable by PReS Workflow. Processing Each file capture by the input is sent down through the process, one at a time. When the file is finished, the process goes back to the input which feeds another file down, as long as there are files in the queue.
General Tab l Folder list: Enter the full path of the folder from which the input files are to be taken. l Masks: Enter a single or multiple file names or use file name masks. See Masks. l Treat as regular expressions: When ticked, the contents of the Mask field are deemed to be a regular expression. The checkbox is not ticked by default. Please refer to Regular Expressions for more information. Note No Variable Data can be used inside this field if the Treat as regular expressions option is ticked.
"Other" Tab l Job Information group l l l l l Information elements: indicates what job infos are automatically created by the input task. Add lines before first data page: Using the arrows keys you can add any job information directly at the beginning of your data file. Backup input files: Check this to save a copy of each data file that is captured by your input. These files are saved in the PReS Suite Workflow Tools working folders under the "Backup" folder.
l l l l l l l l Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked.
Folder Listing Folder Listing input tasks list the files present in a selected folder and gives you the option to use filename masks, to sort files by name or date, and to list the files present in the selected folder’s subfolders. The lists it generates are in XML format. Input Folder Listing captures nothing, however it does read the input folders (and, if selected, subfolders) and gathers information about each file in that folder.
644037 Note The
Job Information definitions l %1 - Folder: Contains the full path of the base folder from which the files are listed. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
l l Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Output The output to this task is a series of individual files, one after the other. These files are not modified in any way from when they are captured from the source FTP server. Properties General tab l FTP Server: Enter the IP address or host name of the FTP server to poll. l User name: Enter the name of a user account on the FTP server. l Password: If account named in the User name box is password protected, enter the password here. l l Port number: Set to use a specific port number.
l Delete Existing Metadata: Check to remove any metadata from memory. This option is disabled on initial input tasks, and is checked by default on secondary input tasks. Job Information definitions l %1 - User name: Contains the user name that was used to connect to the FTP server. This is useful if this task is used as a secondary input and the information is defined dynamically. l %2 - FTP Server: Contains the FTP address of the server from which the files were retrieved.
l l l l l Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file.
Input This initial input task retrieves a single file as specified in the URL option. This file may be of any format, even formats that are not readable by PReS Workflow. Processing No processing is done by this task. The file retrieved is not changed in any way. Output HTTP Client Input will output a single file which was retrieved from the web. Metadata is not generated by this task.
l Delete Existing Metadata: Check to remove any metadata from memory. This option is disabled on initial input tasks, and is checked by default on secondary input tasks. Job Information definitions l %1 - URL address: Contains the full URL that was requested by the task. This includes any GET variables in the URL. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l l ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Warning It is highly recommended to make all processes using the HTTP Server Input task self-replicating and to reduce their polling interval in the Process Properties. Input The HTTP Server Input task does not, by itself, capture any files. Neither does it directly wait for requests to be received. Actually, it is the HTTP service that receives the requests and places them in a specific location on the drive.
If the Send Immediate Response to client option is selected, the response file is sent back right away and the involvement of the input task ends then. However, if this option is not checked, it means there is a second output that comes out of the HTTP Server Input task: The last output generated by PReS Workflow is sent back to the initial input, which is returned back to the client. Note Starting in version 7.
l Variable containing the response code: The contents of the job information or local variable selected in this drop-down, presumed to be a valid response code, will be returned in the response header. This is the value that is present at the end of the process, not the beginning. "Other" Tab l Job Information group l l l l l Information elements: indicates what job infos are automatically created by the input task.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Processing No processing is done by this task. Output The output of this task is the same as the input - a data file and job infos that are sent from a task that generated an error. General Tab l The Input Error Bin task does not have any specific properties unique to it, since it only receives input directly from tasks in other processes when an error is generated. For more information, see the chapter on "Debugging and Error Handling" on page 44.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
SOAP protocol. Using the SOAP tasks pre-supposes this knowledge and this documentation does not attempt to provide it. The Input SOAP Task only responds to a single SOAP action by the client: SubmitJob. Within this request however, a secondary action (SubmitSOAPActionName) can be specified - this is what the SOAP Action corresponds to in this task's properties. General Tab l SOAP Action: The SOAP action is used with the SubmitJob action. It’s the equivalent of the process name.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Properties General tab l LPD queue name: Enter the queue name specified in the printer queue on the remote computer or computers. "Other" Tab l Job Information group l l l l l Information elements: indicates what job infos are automatically created by the input task. Add lines before first data page: Using the arrows keys you can add any job information directly at the beginning of your data file. Backup input files: Check this to save a copy of each data file that is captured by your input.
not generate output. The On Error tab can be used to overwrite the default behaviors. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Output A single PDF containing as many pages as all the combined input PDFs is generated. If the option is selected, this PDF is optimized. An optional metadata file is also created, containing information about the PDFs. This metadata is divided such that each PDF file is its own document, which can contain multiple data pages. General tab l l l l l l l l l Folder: Enter the full path of the folder from which the input files are to be taken.
captured PDF file. Within each Document, one Data Page containing a single Page is created for each page of the PDF file. Note Metadata can be manipulated with the Metadata Tasks, See "Metadata Tasks" on page 445. "Other" Tab l Job Information group l l l l l Information elements: indicates what job infos are automatically created by the input task. Add lines before first data page: Using the arrows keys you can add any job information directly at the beginning of your data file.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
"Other" Tab l Job Information group l l l l l Information elements: indicates what job infos are automatically created by the input task. Add lines before first data page: Using the arrows keys you can add any job information directly at the beginning of your data file. Backup input files: Check this to save a copy of each data file that is captured by your input. These files are saved in the PReS Suite Workflow Tools working folders under the "Backup" folder.
l l l l l l l Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message.
SFTP Input The SFTP Input task retrieves files from a secure FTP site through an encrypted connection. Masks are typically used to select multiple files to be retrieved from the server. Input The SFTP Input connects to the specified FTP server and path, and retrieves a list of all files corresponding to the specified mask. These files may be of any format, even formats that are not readable by PReS Workflow. The files are not deleted from the server when they are downloaded.
l Port Number Group l l l Use default port: Check to use the default port used by the protocol selected above. Port number: Set to use a specific port number. Note: There is no validation to ensure the port is available. It is the user's responsibility to ensure the selected port is available and not being monitored by another application or another PReS Workflow task. File Options group l Directory: Enter the path of the folder to poll on the FTP server.
l l l Approved Server list: Displays a list of servers that were approved for connection: l Server: The name of the server the certificate belongs to. l Fingerprint: The RSA fingerprint of the server. l Remove: Click to remove the server from the approved list. List of known servers: Displays a list of servers that were connected to, whether they are approved or not. l Server: The name of the server the certificate belongs to. l Fingerprint: The RSA fingerprint of the server.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
emails sent to it. This is due to a technical limitation that will be resolved in a future version. Processing The task reads the incoming SMTP request and provides the data within its body. Output Depending on the Data Location option, the output is different: l l Envelope: The request file in XML format, including all email fields (from, to, cc, bcc, subject, body) as well as additional header fields (email client information, attachments, etc).
l l “From” contains: Select to limit those messages used by this task to those that are sent from a specific address. The address you enter in the box below can include variables and wildcards. “To” contains: Select to limit those messages used by this task to those that are sent to a specific address. The address you enter in the box below can include variables and wildcards.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
l Description: PReS Workflow displays the name of the service or process assigned to the port number entered in the Port box. Note that these are standard Internet Assigned Numbers Authority (IANA) descriptions. "Other" Tab l Job Information group l l l l l Information elements: indicates what job infos are automatically created by the input task. Add lines before first data page: Using the arrows keys you can add any job information directly at the beginning of your data file.
l l l l l l l l l Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process. Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced.
WinQueue Input WinQueue input tasks capture print jobs received by a Windows printer queue. Note Before you go through the following procedure, on the computer running PReS Workflow you will need to create a local printer queue that will be used to receive data files in the form of print jobs. This queue can be shared, so as to be able to receive jobs sent from local as well as remote users.
Properties General tab l l Printer queue: Select the PReS Workflow printer queue (the one to which data files are going to be sent). Printer properties group l l Spool Print Job ins EMF Format (Advanced printing features): Select to create EMF files for Windows Print Converter action tasks (see "Windows Print Converter" on page 321). Note that this option must not be selected when capturing generic text type data.
Job Information definitions l l l l %1 - User name: Contains the user name of the user who sent the job to the printer, or the user un which a software sending the job was logged in under. %2 - Host computer: Contains the name of the computer from which the job was sent. %3 - Printer name: Contains the name of the printer in which the job was received. Is the same for all jobs received on any given printer.
l l l l Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values.
process runs, that is to say it will not remain static. This can be extremely useful when, for example, you want to determine how many copies you will print out depending on your data, or what document will be used in the printout depending on the department it came from. Variable properties may include: l Static data. l Standard Variables. See "Standard Variables" on page 535. l Local and Global Variables. See "Manipulate Local Variables" on page 571. l Job Infos.
l Variables l System: Contains system variables, also called "Standard Variables" on page 535. l Job Info: Contains Job Info variables from %1 to %9 l l l l l l l l l Local Variables: Contains a list of local variables in this process. If no local variables exist, this item is disabled. Global Variables: Contains a list of global variables in this configuration. If no global variables exist, this item is disabled.
Unknown Tasks An unknown task is a task location that is not linked to any existing known task. Unknown tasks can have multiple causes: l l l l l Cutting an input or output task will replace it with an unknown task. See Cutting, Copying and Pasting Tasks and Branches Creating a new branch will create an unknown output task in that branch. See Adding Branches. Using Branch From Here... will create an unknown output task below that branch. See Adding Branches.
l l Literal characters: Any alphanumerical character is considered literal character and must appear. For example, a mask of "trigger.txt" will not capture any other files than that name. Wildcards: Two wildcards are available in masks. l l l Asterisk (*): Supports any number of characters. *.txt would pick up any text file, file*.txt would pick up any file starting with file and any characters: file1.txt, filetest.txt. Question Mark (?): Supports a single character. file?.txt would pick up File1.
Add Document The Add Document action task prepares a printer-centric PostScript job by adding a PostScript version of a selected PReS Connect document and the trigger to execute it before the active data file. Input This task can support files in any emulation, however, the actual file that should be used is one that is compatible with the selected PlanetPress Design document. Processing This task takes the PostScript version of the document (.ps7), ads the trigger and then the active data file to it.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Add/Remove Text Add/Remove Text action tasks can be used to perform the following actions on the data file they receive: l To add or remove characters. l To add or remove lines of data. l To add the content of a text file.
l l l l l l l Content: Select what the task will actually add or remove. Select Text file to add the whole content of a text file to the beginning or end of the job file. Select Characters to add the string of characters entered in the Characters box to the beginning or end of the job file, or to remove a given number of characters from the beginning or end of the job file.
l Action Group: This group is disabled in the initial input tasks and defaults to Stop Process. In all other tasks where the On Error tab is present, the following options are available: l l l l l l l l l Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process. Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Advanced Search and Replace Advanced Search and Replace action tasks are used to locate and replace strings of data within the job file and to replace them with other strings of data.
expressions that specify multiple data lines when this option is selected. l l l l String to search: Enter your search string or regular expression in this variable property box. To enter multiple strings or expressions, press Enter after each one (note that only one string can be entered in the Replace with box). Treat as regular expression: Select to specify that the string or strings entered above are to be interpreted as regular expressions rather than ordinary text strings.
the file. Select one of the occurrence options (described below) in the list box below and enter a value in the Occurrence value box besides it. l l l l l At occurrence: The replacement will take place only when the specified number of occurrences has been reached. Specifying 2 occurrences, for instance, means that only the second occurrence will be replaced. At every specified occurrence: The replacement will take place every time the specified number of occurrences is reached.
l l l l l l l Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message.
Barcode Scan The Barcode Scan task is used to convert barcode data from multiple image formats into text-readable information. This information is placed in the metadata and can be used by the rest of the process.
Barcode types Description EAN13 EAN13 symbology. Used with consumer products internationally, 13 characters. EAN8 EAN8 symbology. Short version of EAN-13, 8 characters. UPCA UPCA symbology. Used with consumer products in U.S., 12 characters. UPCE UPCE symbology. Short version of UPC symbol, 6 characters. Code11 Code 11 symbology. Used to identify telecommunications equipment Code39 Code 39 symbology. U.S. Government and military use, required for DoD applications Code93 Code 93 symbology.
Barcode types Description QRCode The QR Code (Quick Response Code) is a 2-dimensional matrix code. It can encode up to 2509 numeric or 1520 alphanumeric characters. PostNet PostNet symbology. Used by the United States Postal Service to assist in directing mail. RM4SCC RM4SCC symbology. Used by the Royal Mail. Note The fewer barcode types are selected, the faster the plug-in performs. Selecting only the expected barcodes is therefore a good practice.
l Process by: Select to define whether to process the image by page or by file: l l l l l Process by Page: The task is able to handle single or multiple page files (Tiff and PDF) and act as a loop to process each page independently and sequentially. The metadata file will be created separately for each page if it does not exist or will be enhanced with the values on processed Datapage level if it already exists. All supported images will be converted to tiff format.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
l l l l BarcodeValue: Metadata field representing the value of the barcode. When multiple barcodes are present on the page, this field is present multiple times. BarcodeCount:: Metadata field representing the number of barcodes on the page. Barcode_1_Value: Metadata field representing the value of the first barcode on the page. Note that this field (Barcode_1_Value) contains the same value as the first occurrence of BarcodeValue.
l When using a secondary input, a known issue of the Workflow Tool can cause some unexpected behavior, like having the same metadata file reused instead of a new one being created for each data file captured. To work around this issue, simply add a Rename action task to set a unique file name (Ex. %u) to each new file before the Barcode Scan task, after each secondary input.
On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
Processing In the case of regular data files, these files will need to be merged with a PlanetPress Design document. In the case of a PDF data file, two things can happen. The PDF can be used as a data file for a Design document, or it can be part of a straight PDF workflow. When this is the case, this task will rather apply the active metadata to the PDF data file (see "PDF Workflow" on page 167 for more information on this).
l Set document permissions: Select to enter the Permissions password. l l Allow printing: Select to let users print the generated PDF files. l Allow changing the document: Select to let users edit the generated PDF files. l Allow content copying: Select to let users copy content from the generated PDF files. l l l l Allow form filling: Select to let users enter information in the form fields included in the generated PDF files.
pages empty. Select Bookmarks and page to display the contents of the Bookmarks tab (you use data selection objects to create bookmarks in PReS) alongside the PDF pages. Select Page tab and Page to display the content of the Pages tab (thumbnails of each PDF pages) alongside the PDF pages. Select Full screen to hide all screen contents except the PDF page, and expand the PDF page to the maximum size it can occupy onscreen. On Error Tab The On Error tab is common to all tasks.
l l Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
l l l l l l Monochrome images : l Compression: CCITT l Pixels per inch: 1200 Grayscale images : l Compression: Auto l down sampling : Bicubic l Pixels per inch: 300 Color images : l Compression: Auto l down sampling : Bicubic l Pixels per inch: 150 Security : l Allow printing l Allow changing the document l Allow content copying l Allow form filling Font : l Embed all fonts l Subset embedded fonts Open options : l Zoom factor: Fit in window l Default view: Page only Dat
can use a Create File input task as a dummy task at the beginning of your process, and then use a PReS Workflow Database action task to gather your actual data. Technical Database Query action tasks require version 2.5 or higher of the Microsoft Data Access Components (MDAC), including JET 4.0. When adding a Database Query action task, you have two options: l l You can use static properties (properties that will remain the same regardless of the data processed at run-time).
Properties Database Connection tab l Database group l l l Table/Query: Select the table or query containing the information you need as your input data. Range group l l l Location: Enter either the path and name of the database or a database connection string in this box. You may click to navigate to the database and paste the database path and name automatically to this box. You may also click create an ODBC connection string to the data source and paste the string automatically to this box.
l l l Sort on field: If you want the table to be sorted before the data page creation process is started, select the sort field from this box. l Text delimiter: Select the text delimiter to be used in the generated file. l Field separator: Select the field separator to be used in the generated file. l Add a header record with field names: Select this option if you want the generated file to have a header record (a record that includes the field names only).
l l l l l l l l Sort on conditional field: Select this option if you want the table to be sorted using the field selected in the Create data pages as follows box before the data page creation process is started. Data encoding: Select the encoding used in the generated XML file. By default, this option is set to the default encoding of the computer used to create or edit the configuration. You may choose any encoding listed in the drop-down list or enter your own.
Dynamic SQL tab l Use dynamic values at run-time: Select to use a dynamic database connection string and / or SQL statement at run-time. Check this box to enable the options included in this group (this disables the corresponding options in the General tab). l l l l Parse normally: Select to interpret any backslashes included in the database connection string as backslashes. If this option is not selected, any backslash that is not doubled will be disregarded.
l Action Group: This group is disabled in the initial input tasks and defaults to Stop Process. In all other tasks where the On Error tab is present, the following options are available: l l l l l l l l l Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process. Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Decompress File(s) Decompress file action tasks decompress zipped job files (files compressed as zip files).
l l Force directories: Select if you want to allow the system to create new folders when required. If this option is not select and the Decompress file action task tries to save a file to a folder that does not exist, the task will fail. Overwrite existing files: Select if you want decompressed files that have the same name as existing files to overwrite the existing files. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l l ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Differences between Digital Action and Image tasks: l l l Digital Action is an action task and cannot be the last task in a branch or process. Image is an output task, and has to be placed at the end of a process or branch. In PReS Workflow 7.2.4 and older, Digital Action does not update the PReS Search Database, even if a PDI is generated and even if the option is checked in the preferences. This behavior was changed starting in PReS Workflow 7.3. Digital Action can accept PostScript (.
l Run mode group l l l l Output type: Select the output file type that you want. l l l l l Optimized PostScript Stream: Select to merge the selected document with the data received by this task before sending it to PReS Image. Note that some features, such as the Time and Date require that this option be selected. Add job information to the document: Select to add the available job info variables in the “header” of the generated output file.
for all output types except PDF and JPEG. Add page number: Select to put a page number on each page included in the output file. This option goes with the Multiple TIFF option and is only visible if either the AutoStore, DocAccel or KYOcapture format is selected. l Data Stream group: Determines what is output by the Digital Action task: l l l l l l l l Use Digital as new data stream: Use the file generated by the task for the rest of the process.
l XML and PDI: Select if you want this task to add both an XML and a PDI index file to the generated document. Job Options tab If you chose PDF as the output type in the General tab, use this tab to choose the appropriate PDF options. Note that all the options available in this tab are only used with PDF files. l l Job options: Select the PDF output option that best describes your needs. This loads all the standard settings for the selected usage scenario. These settings can be changed as required.
suspect that the data may contain parentheses, you should use a Run script action task (see Run Script Action Task Property) with a Strip() function to strip them out. l l Monochrome images group l l l Keywords: You may enter keywords for the document. Since this is a variable property box, you may use variables and data selections and let PReS Workflow interpret this information at runtime. Monochrome compression: Select the compression to use for the monochrome images.
l l Color images group l l l l Grayscale resolution: Select the resolution to use for grayscale images. Note that this setting has an impact on the grayscale down sampling process. Color compression: Select the compression to use for the color images. Flate is a lossless compression method, so no data is lost in the process. It works well on images with large areas of single shades or repeating patterns, such as screen shots and simple images created with paint or drawing programs.
l l l l PDF open password: Enter a password in this box only if you want to prevent users who does not have this password from opening the generated PDF files. Security Level: The password protection for PDF can be encrypted using one of the available encryption methods (RC4, AES-256 and AES-128). It gives the task the ability to take an existing PDF in input and apply the selected password to the PDF without any change to the quality level of the original PDF.
l Font group l l l Embed all: Select to embed the entire font of all fonts used in the variable content document within the generated PDFs. Using this option may result in large PDFs, especially if many fonts are used. Note that those fonts installed by default with the Adobe Acrobat and Adobe Reader are never embedded. If a font is not embedded in your PDF, opening it on another computer or printing it may cause it to be substituted by another default font.
l l l l l l Connection time-out: Enter the time, in seconds, that the connection to the database is maintained while no action is taking place before the connection is severed. Database directory: Enter the path of the directory in which the Access database is located, or use the Browse button to navigate to, and select, the directory. This option is available only when you select Access database in the Database type box. Data source name: Enter the name of the computer on which the database runs.
Input Any file that you wish to upload to the printer. Note that this task does not attempt to verify that the type of file being sent is compatible with the printer, or is in a supported file format. Processing The currently active data file is converted into postscript. Output A postscript file containing the necessary code to save the data file on the hard drive.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Processing The external program is executed using the parameters provided. Note that the current data file is not "sent" to the executable file, however you can refer to the full path of the data file using %F. Output If the external program modifies the job file using the full path, the modified file is the output of this software. Otherwise, the output is the same as the input. Metadata is not modified in any way. Job Infos may be modified, depending on the options set in the task's properties.
l Exit Code group l l l l l Store the exit code in job info: Use the drop-down to select which variable or job info will be used to store the program's exit code. The exit code is a numerical value generated by the program which will indicate whether its execution was a success or if errors were encountered. Verify return value: Check to enable the group and react whenever specific exit codes are returned by the software. If exit code is: Use the drop-down to select how to compare to the exit code.
l l l l l l Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID.
Input The current data file in the process will be discarded. Processing The external file specified in the task's properties is loaded and replaces the current data file. Output The loaded file is output. Metadata is not modified in any way, neither are job infos. Properties General tab l External file: The path to the file you want the job file to be replaced with. You may browse to the file using the browse button on the right of the field.
l Action Group: This group is disabled in the initial input tasks and defaults to Stop Process. In all other tasks where the On Error tab is present, the following options are available: l l l l l l l l l Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process. Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Mathematical Operations The Mathematical Operations action task resolves a mathematical expression and stores the result in an existing job information or variable.
Output The input data file is returned with no modifications. Metadata is not modified. A single job info or variable is modified by this task. Properties General Tab l l l Mathematical Expression: Variable data field containing the expression to be evaluated. This expression may combine any combination of standard PReS Workflow variables and VBScript mathematical expressions. For example, to multiply Job Info 9 by 2, the expression would be %9*2 .
Processing The XSLT is applied to the XML data file. Output The modified XML data file is output. Metadata and jobinfos are not modified. l l File l Import: Lets you open an existing XSLT script from an XSL, XSLT or TXT file. l Export: Lets you save the current XSLT script as a file. l Print: Prints the current XSLT script. Edit l Undo: Undo the last edit. l Cut: Cut the current selection (only available if there is selected text in the editor).
l Help l Contents and Indexes: Opens the Editor Help (this page) The other options of the window are: l l l The script editor text box: This is where you enter your XSLT Script that will be used. If you use an external script file, this will display the content of the file (note however that modifying the script in this case does not modify the external file and changes are not saved). Script running from: Choose if the script should be run from the editor text box, or from an external script file.
General tab l l Group: Use the drop-down to select into which group the KeySet is inserted, or in which group the KeySet should be updated. Key set: Displays a list of keys for the selected group. l l l l l l l Key: Displays the key name in the group. Value: Enter a value for the key, which will be inserted in the KeySet. This value can be dynamic, including data selections, metadata selections, variables and other data. Update: Check to update the key with new data.
not generate output. The On Error tab can be used to overwrite the default behaviors. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
Output Whatever file the Run Script action generates, metadata it modifies or creates, etc. Technical Note about conditions: When using Run Script as a condition, the output of the task can be within the branch or on the main trunk. To control the output, use the "Script.ReturnValue" on page 106 variable in your script. Properties The Script Editor menu options are as followed: l File l l l Export: Lets you save the current script as a file. l Print: Prints the current script.
l l l Language l VBScript: Select if your script is written in VBScript. l JavaScript: Select if your script is written in JavaScript. l Perl: Select if your script is written in Perl. l Python: Select if your script is written in Pyton. Tools l l Go To Line: Brings up the Go To Line dialog where you can enter a line number and jump directly to that line. Editor Options...: Opens the "Editor Options" on page 655.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Properties General Tab l l l Find: Enter the string of data for which to search. In this variable property box, you may enter static characters, variables, job information elements, data selections, or any combination of these. Replace with: Enter the string of data to use as a replacement. Since this is also a variable property box, the same as above applies. List of words to find and replace: Lists each string to find, and its replacement. These are executed in order, from top to bottom.
l l l l l l l l l Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process. Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced.
Send Images to Printer The Send Images to Printer action task is used to (obviously) send images to the printer so they can be used as resources by documents run on the printer. They are comparable to Download to Printer action tasks (see "Download to Printer" on page 281), but they include image specific options. Furthermore, they can be used to send images not only to printers, but also to the virtual drive of other computers running PReS Workflow applications.
Original.tif and Image_Rotated.tif, for example). The first copy can be processed using a Send Images to Printer action task with the scan orientation set to Side to side, the second one with a different Send Images to Printer action task with the scan orientation set to Top to bottom, each one typically being included on two different branches of the same process. l l l l Color conversion: Select As is to keep the color information included in the images.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Send to Folder Send to Folder action tasks send the files they receive to a local folder.
l l l File name: Enter the name of the output files generated by this task. To prevent each new file from overwriting the previous one, you should use variable names. As with any variable property box, you can use any combination of text, variables and data selections.
l l l l Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values.
Processing This task assigns the defined values to each local or global variables or job information. It does not modify the data file nor the metadata. Output The original data file, metadata and job infos are not modified, they are passed on to the next task. Set Job Infos and Variables action task properties are as follows: General tab l l Var/Info#: Lists all job infos, local variables in the current process and global variables in the configuration. Click on the variable you want to change.
l l l l l l l l l Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process. Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced.
SOAP Client Plug-In SOAP Client Plug-In tasks can be used as input, output and action tasks, although their basic function is to generate output. SOAP (Simple Object Access Protocol) is a light protocol that defines a standard XML format used to communicate among systems across different architectures, languages, and operating systems. A SOAP request is an XML-based Remote Procedure Call (RPC) sent using the HTTP transport protocol.
Note The WSDL Address of a PReS Workflow SOAP server is the following: http://127.0.0.1:8080/wsdl/isoapact (assuming you are on the same machine and did not change the default HTTP port). l l l l l l l l l l l Get: Click to get the WSDL file from the SOAP server and populate the Service box below. Service: Choose an available Web service from this drop-down list to populate the Method box below. You may also enter the service name directly if the WSDL file cannot be found.
Advanced tab l Domain: Enter the domain for the authentication on the SOAP server. The Domain is optional even when authentication is used. l user name: Enter the user name for the authentication, if required. l Password: Enter the password for the above user name. l Allow invalid security certificate: Check to ignore SSL certificates that are invalid. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l l l Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values.
If your print job is bound for an HP compatible printer, it may include these characters even when printing to a PostScript printer that does not recognize them. PReS Workflow provides an easy way to automatically filter these characters through its Standard Filter action. Input Text-based data files such as Line Printer Emulation and ASCII Emulation data files, which contain HP PCL control characters. Processing All HP PCL characters are removed from the data file.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Translator PReS Workflow Translator action tasks can convert your data from its current encoding to a number of different encoding. The same data may be converted back and forth as required.
Properties General tab l l l l Source encoding: Select the current data encoding. Note that the source encoding is not selected automatically and you must therefore select the proper encoding from this list in order for the conversion process to be performed successfully. Target encoding: Select the encoding to which you want the data to be converted. Include target encoding signature: This option is only available when converting to UTF-8 (Windows code page 65001) or UCS-4 (code page 12000 or 12001).
l l l l l l l Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message.
tasks are located below WinQueue input tasks (note that the latter include options specific to Windows Print Converter action tasks). The full conversion process is performed in two phases: l l The Windows print file is first converted into an XML file in which each printable character appears with its horizontal and vertical coordinates. The XML file is then converted into a standard Line Printer file.
distance). To find out if one text passage belongs to the one found before it, first the vertical distance, second the horizontal distance and finally, the font size difference are checked. Only if all three values lie within the tolerance are the two blocks recognized as belonging together.
l l Vertical distance: Indicates the biggest acceptable vertical distance between two text passages so that they're still recognized as belonging together. This is the factor the font's height and size is multiplied with. The value for the font's height therefore is taken from the corresponding font's attributes. For example, if the height of that font example in 10 point size is 0.32 cm. There is a passage found that is positioned 0.15 cm above - which means 0.15/0.31 = 0.48 < 0.
Splitters initiate a recurring cycle that stops only when the original file has been completely processed. When a given splitter creates a file, it hands it down to the task that follows, and all the tasks on the same branch are performed until the output task. Then the splitter task creates yet another file that is again handed down to the next task, and so forth until the cycle ends (when there is no more data in the original file).
Data line1 of page 1 Data line2 of page 1 Data line2 of page 1 Last data line of page 1 But when opened with PlanetPress Design or a PReS Workflow using the ASCII emulation, the data in the generated file would look exactly like the data in the original. The same would hold true for the Channel Skip emulation.
Properties General tab l l l l l Split group: Use this group to indicate how you want the file to be split. Field value change: Select if you want the file to be split based on changes in the values of a selected database field (the value in the ClientID field changes, for example). Field value condition: Select if you want the file to be split based on a condition set for the values of a selected database field (the value in the Order field equals 1, for example).
of pages before the field that matches the set condition. Select Pages after if you want the file to be split a given number of pages after the field that matches the set condition. l l l l Split when condition is found group: Use this group if you want the condition to be met a multiple number of times before splitting the file.
l l l l l l Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID.
The data received by the process is typically prepared for a given output device using a pre-set emulation. In some cases, the data’s original emulation may also have been changed by a Change Emulation action task (See "Change Emulation" on page 256). Using an emulation to format the data before splitting provides the most splitting options, but slows down the process. Splitting a data file containing a few hundred thousand pages may take several hours.
l l l l l l l l l Get: Click to go to the Data Selector and select the location associated with the Word change option. Specific word: Enter the word to use as the splitting criteria. In this variable property box, you may enter static characters, variables, job information elements or any combination of these. You may also use the Get Data button to get a static string of characters from the sample data file.
l CSV Emulation Group l Add header to each output file: This option should only be checked if you are using CSV emulation, and will copy the first line of your data file as the first line of each split file afterward. This is useful only if your first line is a Header line that contains your field names. Examples & Use Cases This task is put into effect in the following use cases and example processes: l Capture Web Manager Workflow On Error Tab The On Error tab is common to all tasks.
l l l l Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values.
with a more appropriate splitter instead. Input Any data file. Processing The file is separated into multiple chunks according to the rules set in the task's properties. Output Multiple data files, sent one after the other to the rest of the tasks in the process. Metadata, job infos and user variables are not modified by this task. Properties General Tab l l l l l Split data file on: Use this box to choose the item on which top split the file.
l Word is between lines group l l Word is between columns group l l l l l From and To: Enter a horizontal search region defined as starting from a given column and ending at a given column. If you enter 1 in the From box and 5 in the To box, the Generic Splitter will search for the string of characters only in the first five column (five first characters of every line selected above).
l Word is between columns group l l l l l l Trim selection: Select to force the Generic Splitter to trim empty characters at the beginning and end of the data found in the search region. If this option is not selected, “DAY” will be considered as different from “DAY”. Pages: Enter exactly where to split the file. Enter 1 to split the file 1 page before or after the string, 2 to split the file 2 pages before or after the string, or 0 to split the file immediately before or after the string.
example, the Generic Splitter will only look in the field named “ID” for the value entered below. In this variable property box, you may enter static characters, variables, job information elements or any combination of these. l l l l Operator: Select the appropriate comparison operator. If you select Equals, the Generic Splitter will only consider that the condition is met when it finds a perfect match (“day“ and “day“, for example).
l Where to split group l l l Pages or records: Enter exactly where to split the file. Enter 1 to split the file 1 page or record before or after the string, 2 to split the file 2 pages or records before or after the string, or 0 to split the file immediately before or after the string. Before or after: In the previous box, you entered where you wanted to split the file.
l l l l l Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file.
Properties General tab l Split data file on page group: Select to split the data file based on pages (rather than on a word found within the data stream) and to activate the options from this group, which are used to tailor exactly how you want the page based splitting process to take place. l l l l Page breaks on form feed: Select if you want to start a new data page whenever a form feed character is found.
l l After: If you entered a value other than 0 in the Where to split box, select this option if you want to split the file a given number of lines after the search word. When word is found: By default, the task splits the file every time the search word is found (the default value is 1). If you want the task to split the file only when the search word has been found twice, for example, enter the number 2 in this box. On Error Tab The On Error tab is common to all tasks.
l l Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Output Multiple data files, sent one after the other to the rest of the tasks in the process. Metadata, job infos and user variables are not modified by this task. Properties General Tab l Split on page: Select to split the data file based on pages (rather than on a word found within the PDF data) and to activate the option from this group, which is used to tailor exactly how you want the page based splitting process to take place.
l l l l l l l Match case: Select to force the splitter to match the character casing. Note that this setting applies both to the On region change and Specific word options. If this option is selected, “DAY” and “Day” will not be considered as matching the search string “day”. Trim selection: Select to force the splitter to strip empty trailing characters.
sequence is ended. The next sequence starts with the next metadata level being processed. For details see the Rule Interface. l l Optimize resulting PDF: Select to specify whether the resulting PDF should be optimized. Optimization can lead to a significant reduction in the size of the PDF, but it may also add a certain amount of time to the process.
l l l l Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values.
Processing The file is separated into multiple chunks according to the rules set in the task's properties. Output Multiple data files, sent one after the other to the rest of the tasks in the process. Metadata, job infos and user variables are not modified by this task. Properties General Tab This tab lets you choose the splitter settings for default PReS Workflow XSLT engine. If you want to use your own XSLT engine, click the Alternate XSLT Engine tab.
l l l l l l l l Keep XML structure: Select if you want the generated files to have the exact same structure as the original XML file (all the way to the root node). Add new root node: Select this option and enter a root node name in the box to the right, if you want the generated files to have a structure that begins with a new root name and that then goes directly to the node on which the file was split, as indicated in the Split on node box below.
automatically added at the current cursor position. These variables will be replaced by the correct information at run-time. l l l l XSLT file button: Click to add the {XSLTFILE} variable to the command prompt displayed in the box above. Data file button: Click to add the {DATAFILE} variable to the command prompt displayed in the box above. Output file(s) button: Click to add the {OUTPUTFILE} variable to the command prompt displayed in the box above.
l l l l l Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file.
the condition and sends the job file down one of the two branches based on the test result. So every time a job file travels down the process, it is either routed down the True or False branch. Technical Branches, Loops and other process logic tasks do not generally modify the job file, though some may change system variables. The only exception is the Run Script action, which can be a condition that also modifies the data. Warning Branches, loops and conditions do NOT modify metadata in any way.
Properties Backup Tab l l l l Backup job file: Select if you want PReS Workflow to use identical copies of the job file for the main and secondary branches. When this option is not selected, the file generated by the output task located at the end of the secondary branch is used as the job file for the main branch. Note that if the secondary branch ends with a Delete output task, the main branch will not receive any job file.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
General tab l l l l l Subprocess: Drop down list containing all the available subprocesses in the current configuration. Backup job file: Select if you want to use identical copies of the job file for the main process and the subprocess. Backup job information: Select if you want to use identical copies of the job file information for the main process and subprocess. Once the subprocess completes its execution, the main process will retrieve the original job information values.
l l l l l l Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID.
Properties General tab l l l l Number of iterations: The number of times the loop should be repeated. Every task after the Loop action task will be repeated this number of times. The number may be static, or use a variables (See Variable Properties). Store current iteration in Job Info #: The Job Info in which the loop's iteration should be stored. Useful for sequential file names or conditions based on the iteration. The value of this Variable Properties box should be a digit between 1 and 9.
l l l l l l l l Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked.
Run Script Run Script tasks are used to run scripts that typically perform some kind of processing on the job file received by the task. Scripts are often simpler to write than programs added with the External Program action (see "External Program" on page 284). However, they can be slower to execute. The Run Script action task can be used either as an action or a condition.
l File l l l Export: Lets you save the current script as a file. l Print: Prints the current script. Edit l Undo: Undo the last edit. l Cut: Cut the current selection (only available if there is selected text in the editor). l Copy: Copy the current selection (only available if there is selected text in the editor). l l l Delete: Delete the current selection (only available if there is selected text in the editor). l Select All: Select all of the contents of the editor.
l l l The script editor text box: This is where you enter your XSLT Script that will be used. If you use an external script file, this will display the content of the file (note however that modifying the script in this case does not modify the external file and changes are not saved). Script running from: Choose if the script should be run from the editor text box, or from an external script file.
l l l l l l l Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message.
Send to Process The Send to Process task transfers job file(s), job information and all related files (metadata, sorted metadata, etc.) to a selected process. This action task is asynchronous, meaning the current process will continue running in parallel to the process chosen in this task and will not wait for it to finish. This task is dual-purpose: It can be used either as an Action task, or as an Output task.
l l l l l l l Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message.
messages that printers send out, such as being out of paper or having low toner. PReS Workflow uses the SNMP protocol in the form of an SNMP Condition, in to ways: l l To check the status of printers on your network against values you set in a condition, and to return a true or false value. This is called setting a Printer condition in the SNMP condition's Properties dialog box.
l l Printer Queue group (displayed when Printer Queue is selected in the Condition Type box) l l l l Condition type: Select Printer Queue to test a standard printer status condition or User Defined to test a status identified using a printer specific identification code. Bear in mind that the failure to comply with any of the test conditions selected below will make the whole condition False. Printer status: Select Idle or Printing to test whether the printer is currently idle or printing.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
referenced location before performing the comparison. l l l l l l l l l Operator: Select the desired operator. Note that neither the “Is found” nor the “Is not found” operator can be used to test XML data. Convert data to uppercase before comparison: This option is only displayed when either “Is found” or “Is not found” is selected in the Operator box. Select to prompt PReS Workflow to convert the string to uppercase before performing the comparison.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l l ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Properties General tab l l l l l Month: Select “All months” if you want the selected time blocks to be valid every month of the year. Select a specific month if you want the selected time blocks to be valid only on that month. Week of month / by date: Select “Date” if you want the selected time blocks to be valid only on specific dates. Select “All weeks” if you want the selected time blocks to be valid every week of the month.
l l l l l l l l l Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process. Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced.
Connector Tasks A Connector, as the name implies, is a task that connects to something outside of PReS Workflow itself. In some cases those are other parts of the PReS Workflow, but in other cases we offer connectors for thirdparty applications or systems. Create MRDX The Create MRDX action task is used to register a job on a Suretrac server using an MRDX file. The MRDX contains information about the job and its finishing, as well as integrity features use by SureTrac.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Input Any data file present on a SharePoint document store, even those not compatible with PReS Workflow emulations, and the properties of these files. Processing The task connects to the selected Document store and retrieves a copy of files according to the specified rules. The files may be deleted or marked as checked out depending on the options selected, otherwise they are untouched. Output The output to this task is a series of individual files, one after the other.
l l Do not download checked out documents: If the document is set as "Checked Out" in SharePoint, it will be ignored. Action Group l l l Download the document: Simply download the document and do not modify it in SharePoint. Download the document and mark it as checked out in SharePoint: Download the document and mark it as Checked Out in SharePoint. This is useful for preventing files to be downloaded more than once.
Job Information definitions l %1 - Source file name: Contains the name of the current captured file. l %2 - Directory: Contains the name of the SharePoint director from which the current file was captured. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Processing A connection is established with the Laserfiche server, the file is uploaded and the metadata in the Laserfiche server is generated correctly. Output The output from this task is the specified file along with the metadata within the Laserfiche server. The file is not directly modified by this task. Task Properties General Tab l Laserfiche configuration group l l Folder: Enter the Laserfiche client repository folder where the documents will be exported.
l l If the PReS Image archive folder field is empty and the option “Use PReS PDF/A” is selected, a warning message will be displayed: "You should insert PReS Image archive folder source". The indexes in the PlanetPress Design document must match the ones in the Laserfiche server. Connection Tab l Server Name: The server name or IP address of the server you wish to connect to. l Repository: The name of the repository you wish to send the files to.
l l l l l l Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID.
l l l l l If a field is checked as Required in Laserfiche administration console, fill the field value. If you want to assign an Informational Tag, do not check the Security tag option in the Laserfiche administration console. If the output repository folder does not have access rights to read and create documents, the task will not be able to export documents to the selected Laserfiche folder.
Output The original data file is unchanged. Metadata is updated according to the specified criteria. Properties General Tab l Excel group l l l l Excel workbook: The full path and file name of a Microsoft® Excel® workbook (.xls or .xslx file). You can use the Browse button on the right to browse to the file on your computer. Excel worksheet: The name of the worksheet you want to use. Once a workbook is open, this drop-down will automatically list all the available worksheets.
l l button: Moves the currently selected line up one place. l button: Moves the currently selected line down one place. Search option group l Match case: Will force the lookup column names to be in exactly the same case as the Lookup column name. This means if you type in "CustomerID" in the lookup column and the actual column is named "customerid", it would not return any result. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l l ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Use Case 2: Translate a list of line items descriptions into a given language A PlanetPress Design document takes as input a transactional PDF file, and reproduces it exactly as it enters. Metadata fields called ItemDesc are created, one for each line item description, at the datapage level. Each ItemDesc metadata field is given the value of a line item description as found on a region of the current data page.
Technical In current versions, the Objectif Lune Printer Driver will naturally add a margin to the PDF generated by this task. While this will be fixed in future versions, if your PDF is full bleed you will not get the desired results using this option. l A DOC (Word Document) file which is the result of the mail merge. This output is only available when doing a mail merge.
l Output Type: l l .PDF File (with metadata): The result will be a PDF file with the number of pages generated by the combination of the template and record set. Metadata is also included that complement the PDF. .DOC file: The result is a Microsoft® Word® document in .doc format. Note that this format is not supported by PReS Workflow as a data file or job file, so this option is only useful if you are simply planning to save the Word document in a specific location.
l l l ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
l l l If using a Microsoft® database such as Access® or Excel®, each software must be installed in the same version. For example, using Microsoft® Word® 2007 with a Microsoft® Access® 2003 database will cause the task to fail. If the database path is specified in the Microsoft® Word® document, the mail merge has to be performed with the settings specified in the document, otherwise the database path provided in the task is ignored and can cause different conflicts.
l Store ID: Enter a valid Capture OnTheGo Server user name (mandatory). l Password: Enter the password (mandatory) that corresponds to the Store ID entered above. l Show password: Check this box if you want to see the password you type in the Password box. Deposit Tab In the Deposit tab, you enter information regarding the document you are making available to Capture OnTheGo users. l Document to Publish group: This is where you specify the document location and type.
button marked with an X. l l Categories: Enter at least one valid Capture OnTheGo document category in this box. Capture OnTheGo documents are listed by categories (Reference, Delivery bills, Satisfaction Polls, for instance) on Capture OnTheGo app. These categories are typically managed via the Capture OnTheGo Repository Management page. Note that there cannot be any spaces before or after each category name and that the names are case insensitive.
this setting. Note that any positive number you enter will automatically be reflected in the Until box below. l l l Until: If you want the document to remain in the repository until a given date, select this option and enter a date in the corresponding box (the date format must be “YYYY-MM-DD” - note that you can use the date picker). The date entered corresponds to the last day of validity (the document is valid until 11:59:59 PM on the date you entered).
Properties General Tab l l l SharePoint Site: The name of the SharePoint site where you want to send the files. You can click on the Refresh button to display a list of sites on your SharePoint server. Document Library: The document library where you want to send the files. You can click on the Refresh button to display a list of libraries on the SharePoint site selected previously. Folder: The folder location in the document library where your files will be sent.
l Number: This type may contain a number (1, 1.0, 100). The decimal separator is “.” in the plugin. l Currency: This type contains the currency ($ …). l Date/Time: Date/Time fields contain a date and time l Yes/No: Yes/No (menu to choose from). If passing a variable, has to be either "Yes" or "No". l Hyperlink or Picture: This type contains an html hyperlink or picture.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Output A TIFF in the CCITT Group 4 compression, and information for the FAX server to know where to send the file. Task Properties General tab l l l l l Host: Select the IP address of the PReS Fax host to which you want the request to be sent. The Fax configuration is set in the PReS Fax User Options on the target host. Refresh: Click to update the list of IP addresses displayed in the Host drop-down list box.
The following describes the properties specific to PReS Image output tasks. For information on those properties shared by various types of tasks, such as Other and On error properties, refer to Configurations, Processes and Tasks. Technical In some combinations of Microsoft Outlook and Windows versions, it is not possible for Outlook to be opened while PReS Workflow is running, so emails are not sent out automatically.
Properties General tab l Host: Select the IP address of the PReS Image host to which you want the request to be sent. l Refresh: Click to update the list of IP addresses displayed in the Host drop-down list box. l Documents: Select a specific PlanetPress Design document if you want all the jobs to be generated with that document. To use a document chosen at run-time for each job, enter a dynamic document name using a combination of text, variables and data selections.
l l l l l l l l l TIFF: The output will be a TIFF file. TIFF is a higher quality format that is one of the standards for document exchange, useful for eventual printing or archiving. You have a choice of the following compressed TIFF formats: TIFF Group 3, TIFF Group 4, and TIFF Packed bits. You can also use the uncompressed TIFF format, which produces the largest files with the highest quality. TIFF is a versatile and platform-independent format.
l l l Filename : Enter the name of the output files generated by this task. To prevent each new file from overwriting the previous one, you should use variable names. As with any variable property box, you can use any combination of text, variables and data selections. When multiple files are generated for a single job (such as for multiple TIFFs), each file name includes a sequence number, such as in Invoice0, Invoice1, Invoice2. If you use file name masks that include dots, such as Statement.%y.
l l l l l l l l Compress text and line art: Select to compress the text and line work in the file using the Flate compression filter. Flate is a compression method that works well on elements with large areas of single colors or repeating patterns, as well as on black-and-white elements that contain repeating patterns. Auto-rotate pages: Select to automatically rotate pages based on the orientation of the text or DSC comments.
l Grayscale images group l l l l Compression: Select the compression to use for the grayscale images. Flate is a lossless compression method, so no data is lost in the process. It works well on images with large areas of single shades or repeating patterns, such as screen shots and simple images created with paint or drawing programs.
The Color resolution you enter in the following box is used to control the down sampling process. Select None to prevent grayscale down sampling. Select Average to average pixel color in each sample area and to replace the entire area with a pixel of the average color. Select Subsample to use a pixel in the center of the sample area and replace the entire area with that pixel value. This method is significantly faster, but results in images that are less smooth.
This option can only be used if the Embed all fonts option is selected. Note that if more than 35% of the characters included in a font are used in the document, the entire font is embedded. This option often produces smaller PDF files and ensures proper PDF display. l Initial view group l l Zoom factor: Select the magnification at which you want Adobe Acrobat or Adobe Reader (or other PDF viewer) to open the generated PDF.
l l Use Windows NT Integrated security: Select to use your Windows user name and password to log onto the SQL database. User ID: Enter the user id required to access the database to which you are adding new PDI files from the generated PDF files. If you are using an SQL database, enter the login name you chose when you configured the SQL database (refer to the “Using PReSSearch with an SQL Server Database” section of the PReS Search User Guide).
including but not limited to US6663008, US7172131, US7248250, US7281668, JP3872498, JP3842283, CN1595440, SE517445, RU2256225, and AU773011. Capture Condition The Capture Condition checks the status or field contents of a capture document that has been processed by the Capture Field Processor action task. Input A data file in PGC or PDF format that is accompanied by valid Metadata.
l Condition based on Document Status: Select this to base the condition on the state of the document l l l l l l l Document is closed: Condition will be true if the document is closed (all relevant Capture Fields are filled). Document is complete: Condition will be true if the document is still open, but all appropriate Capture Fields are filled. Document is partial: Condition will be true if the document is still open but only part of the appropriate Capture Fields are filled.
on a Capture field to automatically add its name to the Field Name box. l Condition: Defines what should trigger the condition: l Ink is Present: Triggered by the presence or absence of ink in the field. l None: No ink should be present in any field with this name. l Any: Ink should be present in at least one field of this name in your document. l All: Ink should be present in all fields of this name in your document. l l Pidget setting: Triggered by specific pidget settings.
l Complete: The field contains ink and no error was detected. l Empty: No ink was found in the field. l l l l Error: A logical error was detected in the field. This can happen, for example, if a field was re-written when it should not, a List Field set to only accept one option contains ink in both options, etc. ICR Value: Triggered when the value given by the ICR engine compares with the specified value.
l Capture Post Processing Workflow l Capture Web Manager Workflow On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
ID. l Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
document. This means that this task must be preceded by at least the Create Metadata task. This metadata must also be correctly separated at the documents level, either in the Capture-Ready document's properties or through the Metadata Level Creation task. You may also use a Metadata Sequencer task in order to split the job into multiple parts. This both creates multiple smaller outputs, as well as multiple smaller PDFs in the Capture database.
Properties Pattern Generator action task properties are as follows: l l l Capture Document: Choose the PlanetPress Design capture ready document that will be used to generate the output including the capture fields. Document Title: Enter a name for the document that will be saved inside the PlanetPress Capture Database. This name should be unique and recognizable and will be used later to retrieve the document form using the Get Capture Document action task.
l Basic Functional Capture Workflow l Capture Web Manager Workflow On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
ID. Reset to defaults: Resets all options in this tab to their default values. l If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
Processing The PlanetPress Capture Fields Processor action task receives and processes the information sent by the Anoto digital pen and updates all the documents in the PlanetPress Capture Database using the information from the pen. Any ink in the pen is added as an EPS (image) layer on the PDF inside the Capture Database. If a specific document needs to be closed to release its pattern, this task does so.
l CapOpenDate: The date at which the document was created by the Capture Field Generator. l CapPatternSequence: The value of the pattern sequence assigned to the document.
l l l l l l l Custom Pattern Sequence: If you choose Custom in the Type drop-down, enter a manual Pattern Sequence or a data selection that contains the Pattern Sequence to be used. ICR Settings group l l Custom: Overwrite the pen's information and specify a Pattern Sequence manually or use a data selection. Perform ICR Recognition: Triggers the PlanetPress Capture ICR engine. For more information, see PlanetPress Capture ICR.
l Basic Functional Capture Workflow l Capture Web Manager Workflow On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
ID. l Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
Input A PGC file received from an Anoto digital pen. Processing The PGC file is split by document, if a document can be matched for each pattern ID found in the PGC. The match is made by comparing each Pattern ID with the information found in the Capture database. If more than one pattern is used in a document (pattern on multiple pages of the document), all of the information for this document (more than one Pattern ID) is sent down as a split.
not generate output. The On Error tab can be used to overwrite the default behaviors. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Properties General Tab l l Document ID: A variable data field that corresponds to the database ID of the document from which you want to retrieve ICR data. The Document ID is generated by the system through the Capture Fields Generator. The ID must correspond to a document in the Capture database, or the task will fail with an error. Metadata Level: A drop-down list containing all of the levels of Metadata. Choose the one where the ICR data will be added.
l l l l Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values.
Technical The Find Capture Document task makes multiple simultaneous statements to the database when requesting a list of documents. For this task to work, the option "Allow multiple statements" must be checked in the ODBC connection setup done in the control panel. Input Because this task in an input task, it does not use the current job file in your process, even when used as a secondary input task.
l Condition Grid: Displays the list of current condition criteria that were set for document retrieval. l Filter: The selected filter type. This can be any of the following: l l l l Date Generated: The date, in YYYY-MM-DD format, when the document was generated through the Capture Field Generator. Date Closed: The date, in YYYY-MM-DD format, when the document was closed by the Capture Field Processor or Get Capture Document tasks. This field is empty in documents that are still open.
l l l l l l l l l l l l l Less than or equal to: Numerical comparison, where anything lower or equal to than the specified value is included. Greater than or equal to: Numerical comparison, where anything higher or equal to than the specified value is included. Contains: Inclusive string comparison, documents where the specified value is present within the chosen filter are included.
are aware of the loss of performance and actually need to access each field's properties individually! Examples & Use Cases This task is put into effect in the following use cases and example processes: l Capture Post Processing Workflow l Capture Web Manager Workflow On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l l l Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values.
Processing One PDF, corresponding to the information present either in the metadata or specified in the task, is extracted from the Capture database. When retrieving documents from the database, the PDF from which the document is obtained will remain in the database until each document contained in it is retrieved from it. For example, if a 10-page PDF contains 5 documents, the 10 pages remain in that PDF until all 5 documents have received ink, been closed and retrieved from the database.
Properties General Tab l Document Origin group: l Document to process: Determines where the document information is read l l l l l From Specific ID: Select to specify an exact Document ID from the database. This document does not need to be loaded as a data file or its metadata manually obtained, as this task simply looks up the information directly in the PlanetPress Capture database.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. PGC to PDF Converter The PGC to PDF Converter tasks extracts the digital ink located in a PGC file and adds it to a blank PDF, creating one page per document in the PGC.
Note This task was built using a custom plugin system and does not display the On Error tab in the regular view. To access the On Error tab, right-click on the task and select "Advanced Properties...". Examples & Use Cases This task is put into effect in the following use cases and example processes: l PlanetPress Capture Workflow On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l l l l Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file.
Create Metadata Creates all the metadata that is either the result of the merging between a data file and a PlanetPress Design document, or the information about a PDF File. Input Either a data file in any supported Emulation, or a PDF File. Processing If a data file and document are selected, the metadata is generated by merging the data file and document and retrieving only the metadata generated by this merge.
Properties General Tab l l Documents: Select a specific PlanetPress Design document you want all the jobs metadata information generated for. Add job information to the document: Select to prompt your PReS Workflow to add the available job information elements in the header of the generated file. Note that this option is only enabled if a document was selected.
l l l l l l l l Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked.
Input A PDF File, either with no metadata and along with metadata that presumably corresponds to the PDF file, or a PDF file with embedded metadata. Processing If the Embed option is used, the metadata information is embedded directly into the PDF File as binary data. This does not change the way the PDF is viewed by any PDF viewer. If the Extract option is used, metadata present inside of the PDF file is extracted from it. If no metadata is embedded, the task generates an error W3976.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Metadata Fields Management The Metadata Fields Management task can be used to add new fields into your metadata, either for every element or through conditions.
l l l l l Duplicate: Create a new metadata field. If the fields already exist, a new instance is created. Append: Append the new value at the end of the current one. If no field with that name exists, a new one is created. Sum: Calculate the sum of all values found in all fields of a given name, at a given level. The resulting number is formatted by default with the dot decimal separator. Delete: Delete the metadata field if it exists and disables the Field information column's Field value option.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Input This task takes any file as input and does not modify it. Process This task does not execute any change to the process, its files or variables. It only executes the selected action on Metadata. Output This task outputs the exact same data that was given to it. Its metadata will either be missing (Delete Metadata), Changed (Load Metadata) or the same (Save Metadata). Properties l Chose an action group l l l l l Load metadata file: Loads an external metadata file that was previously saved.
not generate output. The On Error tab can be used to overwrite the default behaviors. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Properties General Tab l Filter levels: Rules for deselecting nodes at the Group, Document or Data page level. Note that currently unselected nodes are ignored. l l l l l Group: Select the metadata Group nodes (the nodes only) based on the specified rule(s). Document: Select the metadata Document nodes (the nodes only) based on the specified rule (s). Datapage: Select the metadata Datapage nodes (the nodes only) based on the specified rule(s).
l l l l l l l l Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked.
Special Considerations l l The task CANNOT re-select unselected nodes if the condition is false for those nodes. Filter rules cannot be based on the following metadata attributes: SelectedIndexInJob, SelectedIndexInGroup, SelectedIndexInDocument and SelectedIndex. Metadata Level Creation Conditionally create new metadata groups or documents. This task is only functional if metadata already exists for the current job.
Note Attributes and Fields are deleted for all new Group levels created. l l Delimiter defines if the Condition parameter is triggering the beginning or the end of a Group or Document. If the delimiter option is set to None, the action is not performed. Rules enable the user to define on which criteria the action must to be performed. The condition must be TRUE to execute the action. If the condition is not met at least once, the rule is not applied.
l l l l l Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file.
For example, in a PDF emulation, the format of a selected region would look like this: region(?,0.59375,2.21875,1.85416,2.51041,KeepCase,NoTrim) where "?" represents the current page. Using this expression, if the metadata structure has 3 data pages, then the task will proceed 3 times sequentially, with ?=1 for the first data page, ?=2 for the second and ?=3 for the third and last data page index from the metadata structure.
Metadata Sequencer Although the Metadata Sequencer acts as a splitter, the data file itself remains untouched, as neither the data nor the metadata are actually being split through this task. With each sequence, the entire data file still gets carried from one task to another. Metadata records are simply selected / deselected, which has the same effect. Input Any data file with accompanying metadata.
l The following rule: Determine if a new sequence starts or if the current one ends. For each metadata level, the current value of the specified metadata attribute / field is compared with the one in memory. If they are different, either a new sequence starts or the current sequence is ended. The next sequence starts with the next metadata level being processed. For details see the Rule Interface.
l l Order: Choose Ascending (orders like a,b,c, or 1,2,3) or Descending (orders like 3,2,1 or c,b,a) order. If the Numeric sorting option is not checked, numbers are sorted like this: "1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9". Numeric Sorting: Check to sort numerically instead of alphabetically (only supports whole numbers. Currency with thousands separator and decimal points will not work). If any non-numeric value is found in the field or attribute, in any instance of the level, the task raises an error.
l l l ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Processing The metadata is read and PDF indexes are located. These indexes are defined in the PlanetPress Design document as data selections, in which the Archive / Email / Fax properties define the data as an index with a name. When all the indexes are collected, a PDI file is generated with those indexes. Output The output is the same as the input, no modification is done to either the data file or the metadata. However, a PDI file is generated and saved in the location specified in the task.
l Action Group: This group is disabled in the initial input tasks and defaults to Stop Process. In all other tasks where the On Error tab is present, the following options are available: l l l l l l l l l Ignore: The task is ignored as if it did not exist, and the job file is passed on to the next task in the process. Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Metadata-Based N-Up The Metadata-based N-Up action task works in conjunction with the PlanetPress Design tool's N-Up functionality.
General Tab l l Number of virtual pages that appear on each physical page: This is equivalent to the N in N-Up. This number should be equal to the total number of virtual pages in your PlanetPress Design document. For example, a 2 horizontal x 3 vertical is 6-up, so this number should be 6.
l l l l Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values.
All In One The All In One action task is a combination of 4 different OL Connect tasks within a single one. This makes creating Print content faster and more easily, as the task is optimized for this specific purpose with less data exchanged with the server as well as multi-threading support. The task is build with 3 tabs that represent the 3 main steps of the creation of a Print Output: Data Mapping, Content Creation and Output Creation.
l Filter: l l l l l l l Switch conditions: Click to swap two conditions on the same level, or two groups of conditions. Delete the selected condition: Click to delete the currently selected conditions in the list. Clear the rule: Click to delete all rules in the list. Note: This cannot be undone. Import a rule: Click to open the Browse dialog and load a Rules file. This will load its rules into the list. Export the rule: Click to open a Save dialog and save the Rules file to disk.
l l l Template Names: Select the appropriate template name from the list. Adding templates is done from the Send to Workflow option in the Designer Module. Preview: Displays a preview of the output generated by the Print context of the selected Template. Not available for the PDF/VT or dynamic template names. Section: Use the drop-down or type in a variable name to execute a specific section.
On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
Create Email Content Set The Create Email Content task generates a set of email content items from a template's Email Context, which are then sent directly to the recipient set in each record. Input This task must receive the information regarding a valid Record Set. This can be the output of the Create Record Set task, or a Record Set retrieved using the Retrieve Entities task. Processing This task loops through each record in the Record Set.
l Email information group: l l l l l Sender Address: Enter the email address that appears in the "From" field of the email. Mail host: Enter the address of the SMTP server through which emails should be routed. This information should be available from your IT staff. Send emails to sender (test mode): Check to ignore the email address from each record and send all emails to the address entered in the Sender Address field instead.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Properties General Tab l Job Preset file: Select which Job Preset to use to generate the job. To be used in this dialog, a preset must have been sent to PReS Workflow using the Package File function in PReS Connect. l l l Default: The IDs in the metadata are used instead of a job preset file. Select this option if the Print Content Set is the result of the "Retrieve Items" on page 503 task. "%o": Select to use a dynamic preset name.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Create Output The Create Output action task generates Print output in a format specified by a Connect Print Preset and sends this output to the appropriate target location.
l Through Workflow: Select to replace the current job file with the output produced by the server. Every option in the Output Preset is still used, except for the output location. Connect Proxy Tab This tab is common to all OL Connect tasks and defines where to process the jobs send through these tasks. When these fields are empty, they use the defaults set in the OL Connect User Options page of the preferences. Note Defaults are not used unless the configuration is sent to the Workflow service.
l l l l l l l l Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked.
Create PDF/VT The Create PDF/VT, similar to the Create PDF task, creates PDF/VT files from a PReS Document. This PDF/VT is compatible with the Create Print Content directly without the use of a Connect Template (PDF/VT mode). Input Any data file supported by the selected PReS Document. Processing The input data file is merged with the selected PReS Document. Output The output is a PDF/VT with default quality settings. The metadata embedded within the PDF/VT is the one generated by the PReS Document.
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Properties General Tab l Template File: l l l l l "None" File name: Select to accept a PDF/VT file as an input and automatically create content items based on the PDF/VT. "%o": Select to use a dynamic template name. Click on %o to change the expression that determines the name of the template to use. Template Names: Select the appropriate template. Adding template is done through the Send to Workflow option in the Designer Module. Record ID: Enter a valid ID for a record.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Properties General Tab l Template File: l l l l l "%o": Select to use a dynamic template name. Click on %o to change the expression that determines the name of the template to use. Template Names: Select the appropriate template. Adding template is done through the Send to Workflow option in the Designer Module. Record ID: Enter a valid ID for a record. This record must be valid for the template used.
On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
Output The output to this task is twofold. On the OL Connect Server side, a Record Set containing multiple records is created and saved. On PReS Workflow side, metadata is returned with information about each record set. Alternatively, it is possible to ignore creation of the Record Set on the OL Connect Server and simply return an XML file containing the full Record Set structure. Properties General Tab l l l Data mapping configuration: Enter the full path to a valid data mapping configuration (.
Note Defaults are not used unless the configuration is sent to the Workflow service. l OL Connect Proxy Address: Enter the machine name or IP Address where the OL Connect Server resides. l Port: Enter the port to use to communicate with the OL Connect Server. Default: 9340 l User name: Enter the user name expected by the OL Connect Server. l Password: Enter the password expected by the OL Connect Server for the above user name. On Error Tab The On Error tab is common to all tasks.
l l l l l Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file.
Input The task requires a valid metadata file containing items for deletion, including Job Sets, Content Sets and Data Sets. These can be created by the Execute Data Mapping, Create Print Content and Create Job tasks. Job Sets, Content Sets and Data Sets are also valid when obtained using the Retrieve Items task. Processing All sets currently active in the metadata are set for deletion. Output The same metadata that is input.
l User name: Enter the user name expected by the OL Connect Server. l Password: Enter the password expected by the OL Connect Server for the above user name. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
ID. l Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window will be available for the rest of your process, or whenever they are overwritten.
Properties General Tab l Metadata file: Enter the full path to a valid Job Metadata file, or use the Browse button to browse to a valid location. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663. 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.
l l l ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
Processing The task requests the items on the OL Connect Server using the conditions set in the task properties. Only the condition information and the return metadata are exchanged. Output The task outputs metadata that is equivalent to the appropriate task that would normally create the items (see the task properties for the list). Properties General Tab l Entity to retrieve: Use the drop-down to select which items to retrieve.
l Output Type group: l l Output IDs in Metadata: Select to only output minimal metadata containing the entity IDs. Output records in Metadata: Select to output IDs as well as record details in the metadata, useful for further sorting and filtering of the metadata. Commingling/Batching Tab Commingling (available only with the appropriate license) is a method by which Print Content Items are merged together to create mail pieces going to each recipient.
Note Defaults are not used unless the configuration is sent to the Workflow service. l OL Connect Proxy Address: Enter the machine name or IP Address where the OL Connect Server resides. l Port: Enter the port to use to communicate with the OL Connect Server. Default: 9340 l User name: Enter the user name expected by the OL Connect Server. l Password: Enter the password expected by the OL Connect Server for the above user name. On Error Tab The On Error tab is common to all tasks.
l l l l l Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message. Store the message in variable: Select in which jobinfo, local or global variable you want to store the message content. ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file.
l Add: Click to add a new line to the list. l Remove: Click to remove the currently selected line in the list. l Move Up: Click to move the currently selected line up one position in the list. l Move Down: Click to move the currently selected line down one position in the list. l Validate Names: Click to check the each of line in the list against the currently active Metadata. Metadata must be loaded in the Data Selector or through the use of the Debugging feature.
l Properties: Add all the properties to be added l Name: The name of the property. l Value: The value to apply to the property. l Add entry: Click to add another line to the Properties list. l Remove entry: Click to delete the currently selected line in the Properties list. l Move entry up: Click to move the currently selected line up in the Properties list. l Move entry down: Click to move the currently selected line down in the Properties list.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Output Tasks Output tasks are exits from PReS Workflow processes. They can be used to send data to specific devices, such as printers, applications, such as email software, or locations, such as folders.
Processing The data file is either deleted directly or sent to the Windows Recycle Bin. Properties General tab l Move to recycle bin: Select to send the deleted files to the Windows recycle bin. When this option is not selected, files are deleted permanently. Examples & Use Cases This task is put into effect in the following use cases and example processes: l HTTP PDF Invoice Request l HTTP Brochure Request l Capture Web Manager Workflow On Error Tab The On Error tab is common to all tasks.
l l l l l l l Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message.
FTP Output FTP Output tasks send job files to other computers using the FTP protocol. It is similar to the Sent To Folder output task but sends to an FTP connection instead of a local drive. The following describes the properties specific to FTP Output tasks. Note that some FTP settings used for all FTP Output tasks are available via the PReS Workflow user options (See "FTP Output Service User Options" on page 649). Input Any data file.
l Connection mode group l l Active: Select to prompt PReS Workflow to use the active mode when sending files to the FTP server. Passive: Select to prompt PReS Workflow to use the passive mode when sending files to the FTP server. On Error Tab The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page 663.
l l l ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not visible in the PReS Suite Workflow Tools' log file. Store the ID in variable: Select in which jobinfo, local or global variable you want to store the error ID. Reset to defaults: Resets all options in this tab to their default values. If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are being forwarded.
In order to access and successfully use Web services, client applications must know how to get them, what operations they support, what parameters they expect, as well as what they return. SOAP servers make this information available via WSDL (Web Service Description Language) files.
l l l l l l l Resolve: Click to apply the options you chose above and to display the arguments of the chosen method in the Arguments box below. As script: Click to apply the options you chose above and to display information on the chosen Web service in JavaScript format in a script viewer. You should use this option if the Web service is too complex to be interpreted correctly by the SOAP Client plugin. Name: Displays the name of the arguments associated with the selected method.
l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked. Lists any process of which the initial input task is the Input Error Bin task. Action Group: This group is disabled in the initial input tasks and defaults to Stop Process.
Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task. These comments are saved when the dialog is closed with the OK button, and are displayed in the Task Comments Pane. Print Using a Windows Driver Printing Using a Windows Driver output tasks are used to send jobs to a local or network printer without going through a PReS Workflow printer queue.
at run-time. l l l Properties: Click to change the current printer queue properties. Note that PReS Workflow generate the job file and hands it over with the available print options to the Windows print driver, which takes the relay for the actual printing part, so there is no way for your PReS Workflow Tool to ensure that all the settings you make will be applied to the printed document. Job name: Enter the job’s file name. By default, the variable %f (Job File Name) is used.
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.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
Properties General tab l l Queues: Select the queues to which you want to send the output. Documents: Select None if you want the data to print as is. Select a specific PlanetPress Design document if you want all the jobs to be printed with that document. To use a document chosen at runtime for each job, enter a dynamic document name using a combination of text, variables and data selections. To enable the dynamic document name box, click inside it. To disable it, press Enter.
l l l l l Round robin: Round robin means that complete jobs will be sent in turn to each one of the selected printer queues. For example, Queue_1 will get the first job, Queue_2 will get the second job, and so forth. Page delimiter group: These options are enabled when you choose Split job or Queue balancing load balancing options. They are used to determine how each job is to be split before being sent to the printer queues. l Form feed: Cuts the job file at every form feed character.
l l l l l l l Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message.
Technical In some combinations of Microsoft Outlook and Windows versions, it is not possible for Outlook to be opened while PReS Workflow is running, so emails are not sent out automatically. To correct this, make sure to logon to Windows on the PReS Workflow server using the same login that PReS Workflow is using, and open Outlook before starting the PReS Workflow services. You could also use a startup process to start Outlook before the rest of the services. Input Any data file.
l Message: Enter the content of the email message. Since this is a variable property box, the text may be personalized using variables and data selections. Note that since this is a variable property box, its content is parsed at run-time. If HTML code is entered or pasted in this box, percent (%) and backslash (/) HTML characters must be doubled otherwise they will be disregarded. Note Different email clients have different support for various features, especially with HTML emails.
Login tab l l l l l l l l l l l Use Microsoft Outlook: Select to use Microsoft Outlook to send emails (and attachments). The host computer must be running Outlook, and PReS must have access to Outlook. Emails generated by PReS Workflow appear in the outbox before being sent by Outlook whenever it is set to send emails. Use SMTP mail: Select to use Simple Mail Transfer Protocol (SMTP) to send the emails (and attachments).
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. l l l Send to Process: Check this option to send the job file to an error management process. Error Process drop-down: Enabled only when the Send to Process option is checked.
Common Errors Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are related more to the system than to PReS itself. Some examples would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission errors on folders or files, etc. Comments Tab The Comments tab is common to all tasks. It contains a single text area (Task comments) that lets you write comments about the task.
l l File name: Enter the name of the output files generated by this task. To prevent each new file from overwriting the previous one, you should use variable names. As with any variable property box, you can use any combination of text, variables and data selections. Concatenate files: If this option is selected, when PReS Workflow tries to save the job file under an existing name, it appends the content of the new job file to that of the existing file, instead of overwriting it.
l l l l l l l Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in the PReS Suite Workflow Tools' log file. Message: Enabled only when the Log Message option is checked. Enter a message that will be logged in the PReS Suite Workflow Tools' log file. You can use any variables available in PReS Workflow to customize the message.
Working With Variables A Variable is basically a keyword that points to specific location in your computer's memory. This location contains data that you decide to place in it, by assigning that data to the variable name. This chapter will help you learn about these variables and how you can use them.
Note You can also access global and local variables from your document using the ExpandString () function. For more information, please see the PlanetPress Design User Guide. There are only 9 Job Infos available numbered from 1 to 9. They can be accessed directly anywhere that accepts variable properties by using the number of the variable preceded by a percent sign (For example, %2 or %9).
Available Standard Variables Variable Name Example value when interpreted %c Content of your job file in its original format. n/a %F Job File Path and Name C:\Program Files\PReS Workflow 7\PlanetPress Watch\Spool\job1D80328.dat %f Job File Name including the file extension. job1D80328.dat %z Job File Size in bytes. 34134 %o Original File Name invoice_june2nd.
Variable Name Example value when interpreted %h Current Hour 18 %n Current Minute 03 %s Current Second 41 %v Current Millisecond 24 %u Unique 13-char string (will be different every time it is used) 0ZIS4CW8U47VI00 %t Current Temporary Folder C:\Documents and Settings\All Users\Application Data\Objectif Lune\PReS Workflow 7\PlanetPress Watch\Spool\6.tmp\ %e Current Metadata Filename job00ZAIZ2C4FXON16CE6C566.dat.meta %E Current Metadata Path and Filename C:\Documents and Settings\A
Initial input tasks do not modify the value of %i. However, the following tasks do trigger the variable: l Barcode scan l Capture Field Processor l All Splitters (Including the Metadata Sequencer) l Get Capture Document l Loop l Capture PGC Splitter l PrintShop Mail Error Handling Variables The following variables are available in error-handling tasks (that start with the Error Bin Input task). Note that these are new in PReS Workflow 7.4 and are not available in previous versions.
Variable Name % {error.process} Name of the process where the error was triggered % {error.tasktype} The type of task that triggered the error % {error.taskname} The name of the task that triggered the error % {error.taskindex} The position of the task in the process % {error.errormsg} The error message, as entered in the OnError tab of the task. This is the same message as appears in PReS Workflow Log file. %{error.errorid} The error ID, as entered in the OnError tab of the task.
itself but not to any other process or instance of the process. For example, you could store the current order ID for the process, a name or an email. You can have as many local variables as you want in any given process. To add a local variable, you can use one of two methods: l l l Select the process where you want to add the variable. Click on the Home tab of the PReS Workflow Ribbon, then click Local Variable in the Variables group.
Manipulate Global Variables Note For information about Local Variables see Local Variables. Global Variables are set at the level of the configuration file and are shared between all processes and tasks. Global variables can be used anywhere that accepts variables by using it's name preceded by "global." and surrounded by curly brackets (for example: %{global.myGlobalVariable}). Global variables are generally used to keep information that applies to multiple locations but need to be changed easily.
2. Enter the new value for your global variable. 3. Click OK to save the new value. Shared tasks These procedures can be used on both local and global variables. To delete a variable l Right-click on the variable name in the Configuration Components Area and click Delete. To rename a variable: l Right-click on the variable name in the Configuration Components Area. l Click Rename l Type in the new name of the variable, then press Enter on your keyboard.
PReS Workflow cannot work without a valid configuration and a PReS Workflow session running on a given computer can only use one configuration at a time. Once you have created a configuration, you must “send” it to the PReS Workflow Service. When you do this, your PReS Workflow forgets its previous configuration and starts executing the tasks included in the new configuration. Note A PReS Workflow configuration must be composed of at least one process, but it may include as many as 512.
configuration. Select the Always save without prompting for confirmation option to automatically save any unsaved work. Open a PReS Workflow Configuration File While PReS Workflow Configuration program always loads the default and current configuration, you may sometimes need to open a Workflow Tool configuration file that is not the current one, for example to load a previous backup or a configuration file saved from another computer. This procedure will show you how. 1.
Saving a Configuration Files created and edited using PReS Workflow can be saved as PReS Workflow configuration files anywhere on your computer or even a network location. To save the current configuration: l l From the PReS button, choose Save. If you were editing the current PlanetPress Watch service configuration or if you were editing a new configuration file, you are prompted with the Save As dialog instead.
1. Open the configuration you want to use as PReS Workflow’s new configuration. 2. Edit the configuration, if required. 3. When the configuration is ready to be used, from the PReS Workflow button, choose Send Configuration, then Send Remote. A list of available PReS Workflow servers on the local network appears. 4. Put a checkmark next to each server where the configuration should be sent. 5. Click OK. If a server is grayed out, this may mean you do not have access to send a configuration remotely to it.
If the default configuration does not include any active process, the PReS Workflow Configuration program asks you whether to continue. When the PReS Workflow Configuration program sends a configuration, the PReS Workflow service is stopped and restarted, if it is currently running, and the new configuration starts being applied immediately.
has its own telnet port number (set in each task). l HTTP/SOAP Server service: Monitors web pages and web sites as well as SOAP servers. Available Output Services Output services are used to output jobs. The output services used by PReS Workflow are: l l l l l l l FTP Output service: Places output jobs on a server via the FTP protocol. LPR (Line Printer Requester) Output service: Sends jobs to an LPD server or LPD compatible printers.
The PReS Workflow Service Console, included in the PReS Workflow Workflow Tools Configuration program, can be used to monitor, start and stop PReS Workflow services (See Users and Configurations and "The PReS Workflow Service Console" on page 608). Start and Stop PReS Workflow Service As with most Windows services, PReS Workflow can be started and stopped automatically when a Windows session is opened and closed.
To pause your PReS Workflow Workflow Tools service via the PReS Workflow Configuration program: 1. Click Tools in the PReS Workflow Ribbon. 2. Click Pause in the Services Status group. The PReS Workflow service temporarily stops performing jobs. Note If you send a new configuration when PReS Workflow is paused, it will continue using the old configuration when you resume processing until you stop and restart it. To resume your PReS Workflow service after pausing it: 1.
The Interface This chapter centers on the PReS Workflow Configuration program, which you use to create and edit your configurations. The basic user interface elements are as follows: 1. The PReS Workflow button. See "PReS Workflow Button" on page 561. 2. The Quick Access Toolbar. See " The Quick Access Toolbar" on page 670.
3. The Ribbon Tabs. See "The PReS Workflow Ribbon" on page 671. 4. A Group within the Ribbon 5. The Process area. See " The Process Area" on page 659. 6. A specific link (aka a "component", "button" or "link"). 7. The Dockable panels including "The Plug-in Bar" on page 617, " The Object Inspector Pane" on page 616 and "The Debug Information Pane" on page 614. 8. The status bar. This displays your current software version and status of the PReS Service. 9. The Configuration Components pane.
The Configuration Components pane, the Object Inspector and the Messages area can each be displayed inside its own window, whether docked or undocked, but they can also be displayed attached or combined inside the same window. l l l When separate areas are displayed simultaneously, they appear in different sections of the Program window. When attached areas are displayed simultaneously, they appear side-by-side or above one another inside sub-windows.
Show or Hide Areas of the Program Window You can choose to hide or display any of the customizable areas in PReS Workflow program. Hidden areas will still contain the same information but will not be visible. To show or hide a Program window area: l In the PReS Workflow Ribbon, click the View tab. l From the Show/Hide group, click on any area name to hide or display it. A "highlighted" (orange) button means the area is displayed somewhere on your screen(s). A dim (blue) button means the area is hidden.
bottom of the rectangle. To switch between combined area: l At the bottom of the combined area, click the tab of the area you want to bring to the top. If all the tabs are not displayed, use the left and right arrows to navigate between them. The left and right arrows lets you show hidden tabs. To reorder tabs in a combined area: l At the bottom of the combined area, click the tab of the area you want to move, drag it to the left or right and drop it at the desired position.
To take an area out of a combined area, do one of the following: l l Click the tab displaying the name of the area you want to take out and move the mouse pointer so as to drag the area away from the combined area. As you drag, a rectangle is displayed to show the landing position. Release the mouse button when the rectangle is away from the combined area. Double-click the tab of the area you want to take out of the combined area. The area will jump outside of the combined area. To attach areas: 1.
3. Resize each part of the new group as desired. Attaching an area to a group of combined areas. The rectangle showing the landing position is not tabbed and the area will therefore be moved next to the combined area. To maximize or restore attached areas, do one of the following: l To maximize a vertically attached area, click the upward pointing arrow on its title bar. l To restore a vertically attached area, click the downward pointing arrow on its title bar.
A) Click to maximize this area. B) Click to restore this currently maximized area. C) Click to maximize this area. D) Click to restore this currently maximized area. To take an attached area out of a group, do one of the following: l l Click the title bar displaying the name of the attached area you want to take out and move the mouse pointer so as to drag the area away from the group. As you drag, a rectangle is displayed to show the landing position.
Resize the Program Window Areas You can adjust the layout of the Program window by resizing one of the Program window areas. This also applies to resizing a combined area (see "Combine and Attach Areas" on page 554). To resize a Program window area: l Move the pointer to the edge of an area you want to resize to display the resize pointer, then click and drag to resize the area.
convert back and forth the letters and numbers used by humans to the numeric characters used by computers). By default, codepage 1252 is used for Latin languages (good for Afrikaans, Basque, Catalan, Danish, Dutch, English, Faroese, Finnish, French, Galician, German, Icelandic, Indonesian, Italian, Malay, Norwegian, Portuguese, Spanish, Swahili and Swedish) and codepage 932 is used for Japanese.
l l l l Send Configuration: Sends the current configuration to the PReS Watch service. See "Saving and Sending" on page 544. Close: Closes the configuration that is currently opened and creates a new configuration, with a single example process and no printer queues. Closing the current configuration is the same as creating a new one. Recent Documents: Displays a list of the 9 most recently opened configuration files. Click on any of them to open it.
l l l l Startup: Triggers whether the process is a startup process (runs before any other process). This option is only available if there is no existing startup process in your configuration. l Group, Ungroup: Triggers grouping functionality. l Properties...: Displays the process' properties, for scheduling and error handling. Subprocesses: Displays a list of subprocesses in your configuration.
l l l l l l Sample Data File(s): Displays a list of sample files that are included in the data mapping configuration. Double-click on a file to use it as a sample data file for the active process. Document Templates: Displays a list of templates that can be used in content creation tasks: Create Email Content Set, Create Web Content and Create Print Content. Job Presets: Displays a list of Job Presets that can be used in the "Create Job" on page 481 task.
l Text Test Page: Prints a text-only test page on the printer. l Properties...: Displays the printer queue properties. Note Deleting a component that is currently used by a process will cause this process to stop working and trigger an error, until the task that causes the error is removed, or changed to point to another existing component.
l l l l l l l Self-Replicating Process: Check this if you want the process to replicate itself in the background when multiple input files are received simultaneously. When this is checked, the input task polls its source once, determines the number of files to process, then replicates itself up to the maximum allowed and treats the files simultaneously. The initial process runs again once it has completed itself and replicates again as necessary, until all files have been processed.
l l Time division: Select the duration of each daily segment in the time grid. If you select 00:15, each segment will represent only 15 minutes and each day will be made up of 96 blocks (4 blocks per hour times 24 hours). If you select 24:00, each segment will represent an entire day. Poll once per activity period: Select to perform this process’ initial input task no more than once for each set of contiguous blocks (blocks that are on the top of one another).
l Click on any block to select / deselect it. l Click and drag from one block to another to toggle all blocks between the two. l Shift-click on any block to toggle all blocks from the top-left corner of the grid to the block you click.
l l l To select all of the time segments for a given day or date, click the day or date on the top grid ruler. To deselect all of the time segments for a given day or date, CTRL+click the day or date on the top grid ruler. To select all the days or dates for a given time segment, click the time segment on the left grid ruler. To deselect all the days or dates for a given time segment, CTRL+click the time segment on the left grid ruler.
Create a New Process You can create a new process in a two different ways: l l In the Ribbon, go to the Home tab and click the Process button in the Processes group. In the Configuration Components pane, right-click on any process or the Processes folder and select Insert Process. Regardless of the method, a new process is created with a default name (Process1, Process2, etc), Input Task and Output Task. The defaults are configurable in the "Default Configuration Behavior Preferences" on page 623 screen.
Manipulate Local Variables Note For information about Global Variables see Global Variables. Local Variables are set at the level of the Process and are not shared with any other process or instance of that process. Local variables can be used anywhere that accepts variables by using it's namee, surrounded by curly brackets and preceded by a percent sign (for example: %{myLocalVariable}).
l Type in the new name of the variable, then press Enter on your keyboard. While renaming a variable will correctly rename all references to it in task properties or wherever else it is used in a task, it will not change the references in any script within a Run Script task. Deleting a variable, on the other hand, does not delete any reference to it.
Convert a Branch to a Subprocess To allow for maximum flexibility and backward compatibility with the subprocess feature, the Convert to subprocess option lets users transform existing processes easily. This option is available whenever a Branch task is selected; right-clicking on it will display the contextual menu, which holds the Convert to subprocess option.
Global Variables are set at the level of the configuration file and are shared between all processes and tasks. Global variables can be used anywhere that accepts variables by using it's name preceded by "global." and surrounded by curly brackets (for example: %{global.myGlobalVariable}). Global variables are generally used to keep information that applies to multiple locations but need to be changed easily.
l Right-click on the variable name in the Configuration Components Area and click Delete. To rename a variable: l Right-click on the variable name in the Configuration Components Area. l Click Rename l Type in the new name of the variable, then press Enter on your keyboard. While renaming a variable will correctly rename all references to it in task properties or wherever else it is used in a task, it will not change the references in any script within a Run Script task.
l l l Document Templates: Displays a list of templates that can be used in content creation tasks: "Create Email Content Set" on page 478, "Create Web Content" on page 492 and "Create Print Content" on page 489. Job Presets: Displays a list of Job Presets that can be used in the "Create Job" on page 481 task. Output Presets: Displays a list of Output Presets that can be used in the "Create Output" on page 484 task.
The archives are saved using the template named followed by a timestamp. A maximum of 30 of each instance of a resource is kept (meaning if you have 10 different templates, a maximum of 300 files will be present in the archive\template folder). Older archives are deleted automatically as new archives are created. PPS/PSM Documents PPS/PSM Documents displays a list of PlanetPress Design and PrintShop Mail Design document that have been imported into PReS Workflow.
l l l Document: The file name of the document, as entered in PlanetPress Design. This is the name of the file saved in PlanetPress Design, or the name you give it when you add a printer-resident document in your PReS Workflow Configuration. It may have a PTK extension (if it has been sent to PReS Workflow from PlanetPress Design), or a PS extension (if it is printer-resident). Version: The version of PReS Workflow in which the document was originally created.
l l Document Update group (enabled only when using printer-centric mode and the document is on the printer) l l l l RAM: Select if the PlanetPress Design document is on the printer's RAM (Random Access Memory). Automatically update: PReS Workflow will send a new version of the document to the printer automatically if the document has been changed since it was last used.
To view an attached data file: 1. Make sure the Documents section is visible by clicking the 2. Expand the document (name.ptk) by clicking the button if it appears. button. 3. Double-click on the data file to open the data selector. Note Double-clicking on the data file does the same thing as right-clicking on it an then selecting Set as sample data file. Clicking Cancel instead of OK after viewing will prevent this action from being taken. To save an attached data file to disk: 1.
To view the Document Preview: 1. Make sure the Documents section is visible by clicking the button if it appears. 2. Expand the document (name.ptk) by clicking the button. The Document Preview has the same name as the document but with a PDF extension. 3. Right-click on the Document Preview, then click Open in PDF Viewer. To save the Document Preview to disk: 1. Make sure the Documents section is visible by clicking the button if it appears. 2. Expand the document (name.ptk) by clicking the button.
To assign documents to PReS Workflow printer queues: 1. In the Documents group of the Configuration Components pane, select either a single document or a group of documents. 2. Drag the selected documents over a PReS Workflow printer queue. The selected document or the group of documents is associated with the printer queue. Each document keeps its default properties.
If you simply wish to change the order in which objects appear in a category or group of the Configuration Components, refer to " Reorder Objects in the Configuration Components Pane" on page 586. As you drag a configuration component, your mouse cursor will change to indicate the action you are performing, as well as whether the location where the cursor is can accept the configuration component you are dragging.
Using the clipboard buttons: l Click on the component you want to move. l Go to the Home tab of the ribbon. l Click the Cut button in the Clipboard group. l Click on the new location where you want the component. l Click the Paste button in the Clipboard group. Using the mouse contextual menu: l Right-click on the component you want to move. l Click on Cut in the contextual menu. l Right-click on the new location where you want the component. l Click on Cut in the contextual menu.
Moving and Copying Details: l l l l l l When moving configuration components, a horizontal line appears where the component will be dropped if the location is valid. At the end of this line will be small "dents". If these dents are on top of the line, the component will be placed at the same level (group) as the component before it. If the dents are at the bottom, the component will be placed at the same level (group) as the component after it.
To rename a process, printer queue or group in the Configuration Components pane: 1. In the Configuration Components pane, right-click the name of an object or group and choose Rename from the pop-up menu. The name of the object or group is highlighted and ready to be edited. 2. Type the new name over the existing name and press ENTER. PReS Workflow Configuration renames the object or group. To rename a resident document: 1.
within a group, this command has no effect. l To Bottom Level to move the item to the bottom level in the hierarchy. To alphabetically reorder objects in the Configuration Components pane: l Click the either a category (Processes, Global Variables, Documents, or Printer Queues) or a group l In the PReS Workflow ribbon, go to the View tab. l In the Arrange group, select Sort by Name. Grouping Configuration Components Groups help you organize processes, documents, and printer queues.
To remove objects from a group: l Drag-and-drop the objects out of the group. The objects are removed from the group. If the group becomes empty, you are prompted to confirm the deletion of the group. To add selected objects to a new group: 1. Select multiple objects that are not part of a group. Press CTRL+G. A new group is added and the selected items are moved to that new group. To ungroup selected objects: 1. Select objects in a group. 2. Press CTRL+U.
In the case of documents, you are first prompted to confirm the deletion. You can turn off this prompt in the Notification Messages User Options. To delete a group of processes, documents, or printer queues: l Click a process group, documents group, or printer queue group, then press the DELETE key. In the case of process groups and printer queue groups, the group and all its members are deleted. In the case of documents, you are first prompted to confirm the deletion of each member of the group.
The printer list displays the following information l l l License Number: Reference number of the activation, linked to your customer account. Magic Number: The magic number generated by the printer. If the magic number is incorrect, your jobs will output with a watermark on that printer. Activation Code: The activation code generated by your license number and magic number. If the activation code is incorrect, your jobs will output with a watermark on that printer.
1. Click on the Tools tab in PReS Workflow Ribbon, then click Configure Services. 2. Set the PReS Workflow applications permissions as required: l l l Local System account: Select to run all the PReS Workflow Services (including PReS Workflow, PReS Fax, and PReS Image) under the Local System account. The Local System account is distinct from the Administrator account. It requires no user name or password, and its privileges may exceed those of the user currently logged in.
The account you choose will be used by PReS Workflow and all its services, as well as by PReS Fax and PReS Image (only PReS Messenger is not affected, since it always uses the Local System account). If you install PReS Fax or PReS Image on the same computer after performing this procedure, you will have to perform it once again, so as to choose the same account for all the installed applications.
l l l l l As soon as possible: Select to have the process run continuously. Clear to enable the Time Grid to fine-tune the schedule of the process. Day(s) to keep backup: Indicate the number of days to keep backups of jobs processed by input tasks. Note that backups will only be kept for those input tasks that have the Keep backup file option selected and that they are required to resubmit input files.
activate the Time Grid, the "As soon as possible" option must be unchecked. In the Time Grid, a blue block will indicate that the process is active within that time block. While blocks mean the process will not be active.
l Click on any block to select / deselect it. l Click and drag from one block to another to toggle all blocks between the two. l Shift-click on any block to toggle all blocks from the top-left corner of the grid to the block you click. l l l To select all of the time segments for a given day or date, click the day or date on the top grid ruler. To deselect all of the time segments for a given day or date, CTRL+click the day or date on the top grid ruler.
l l Description: A one-line box to give a title or short description to your process. Comments: A multi-line box to give more detailed information, for example the file format expected, explanation of the system in general. Advanced SQL Statement Dialog The Advanced SQL Statement dialog is available by clicking the Edit SQL button from the Database Query action task. You can enter a custom SQL query in this dialog, using the language supported by the database you select in the Database Query action task.
Access Manager The Access Manager controls what rights are granted to other machines (clients and servers) on the same network. It grants access to functions such as sending documents and jobs to the server. Technical Messenger communications (between different part of the PReS Workflow) is limited to within the same Class C subnet. This means that PReS Workflow on 192.168.1.23 cannot send a job to a PReS Image on 192.168.100.54. This limitation has been removed in PReS Workflow 7.3 and higher.
To manually add a new entry in the list l Open the Access Manager l Make sure you are in the Messenger tab. l In the IP address box, enter the IP address of the remote machine. l Click on the l Add the necessary permissions l Click OK l Restart the Messenger service. button.
Technical The format of the IP address must be one of the following: l l 127.0.0.1: The local computer. Typically this IP should have all the accesses checked. 255.255.255.255: Everyone on the same subnet. This is equivalent to hard-coding the current subnet, such as 192.168.1.255 or 10.0.0.255. l 192.168.0.42 : A single IP address. This can be any valid address on the same subnet. l 10.0.255.255: Any IP in the 10.0.X.X range. To automatically detect machines on the network and add them 1.
the first entry should be 255.255.255.255 with the Allow checkmark in the HTTP Input box. PReS does not continue processing after it has found an "Allow" checkmark. There is no concept of "Deny", meaning if any "Allow" permission is given, there is no way to later remove it for certain IPs or IP ranges. l l l The configuration of the Access Manager is saved in a file on the hard drive which can be edited manually. See Access Manager hosts.allow File.
Note In order for the changes made here to be effective, you will need to restart the PReS Messenger service. This can be done via the PReS Workflow Service Console. SOAP Access The SOAP tab of the Access Manager controls access from SOAP clients to local processes and SOAP processes. Each user name entered in this dialog can have access to one or more processes.
To add a new SOAP user 1. Click on the button. 2. Enter the following information under the Username column for the new entry that was created: l l l User name: An alphanumerical user name for the user. Password: A password to protect the user. Note that the password will always revert to ******** (8 stars) when clicking outside of this box - that is normal and is meant to protect the length of the password as much as its contents.
service. This can be done via the PReS Workflow Service Console. PDF Viewer The PDF Viewer, introduced in PlanetPress Tools 7.3 in some areas and expanded for use throughout the configuration tool, displays any PDF used in the configuration or process. Because this PDF viewer is integrated with the suite, it is not necessary to have any third-party tools such as Adobe Acrobat installed on the operating system.
The PDF Viewer
To open the PDF Viewer: In the Documents section of the Configuration Components pane, expand a document present in the list. Then, right-click on the document's Preview, and click Open in PDF Viewer. The PDF Viewer is accessible through one of the following methods: l l l In the Documents section of the Configuration Components pane, expand a document present in the list. Then, right-click on the document's Preview, and click Open in PDF Viewer. Click View as PDF in the Debug toolbar.
To open the PReS Workflow Service Console via the PReS Workflow Configuration program: l Choose Tools | Service Console. A) The PReS Workflow services monitored by the PReS Workflow Service Console. B) The run-time information provided by the console. Note The log window only displays the 1000 most recent lines. Older lines are hidden as new ones appear to replace them. To view the log messages generated by a service: l Click the service in question in Services pane, on the left hand side.
To clear the Messages area of the PReS Workflow Service Console: l Click in the Messages area of the Service Console, and from the right-click menu choose Clear. To save the information from the Messages area of the PReS Workflow Service Console: 1. Click in the Messages area of the Service Console, and from the right-click menu choose Save to file. The Save As dialog box appears. 2. Navigate to a location, enter a file name, then click OK. The complete content of the Messages area is saved.
To open the PReS Workflow Service Console via the PReS Workflow Configuration program: l Choose Tools | Service Console. A) The PReS Workflow services monitored by the PReS Workflow Service Console. B) The run-time information provided by the console. Note The log window only displays the 1000 most recent lines. Older lines are hidden as new ones appear to replace them. To view the log messages generated by a service: l Click the service in question in Services pane, on the left hand side.
To clear the Messages area of the PReS Workflow Service Console: l Click in the Messages area of the Service Console, and from the right-click menu choose Clear. To save the information from the Messages area of the PReS Workflow Service Console: 1. Click in the Messages area of the Service Console, and from the right-click menu choose Save to file. The Save As dialog box appears. 2. Navigate to a location, enter a file name, then click OK. The complete content of the Messages area is saved.
Feature Name Database Terminology Equivalent Description Group Table A Group is defined by its Keys (columns), and may contain 0 or more KeySets (rows) within it. Key Column/Field A Key is defined only by its name. Data Repositories only support STRING values and any data inserted into it is converted to string automatically. The maximum size of a single key is 1 billion bytes.
Toolbar Buttons l Group section l l l l l l Add KeySet: Click to add a new KeySet to the currently selected group. Displays a dialog with all the Keys in the group, asking for a value for each of the keys. Enter the values then click OK. The KeySet will display in the right part of the repository manager. Delete KeySet: Click to delete the currently selected KeySet in the Group. Warning: This action cannot be undone. Edit KeySet: Click to edit the currently selected KeySet.
Repository Structure Pane This section of the Data Repository display a tree view of all groups in the data repository as well as all the keys under each of those groups. Group KeySets Pane This section of the Data Repository displays the current KeySets in the group. Each horizontal row is a KeySet, and each vertical row is a key defined in the group. l To edit a KeySet, double-click on it. l To delete a KeySet, press the Del key. l To add a new KeySet, press CTRL+N.
Virtual Drive Manager When you use the Send images to printer action in a given process, you have the option of, at the same time, sending the images to the virtual drive (a local storage folder used by PReS Workflow applications) of any computer included in your network. You need to do this, for instance, if you plan to run documents that contain dynamic images on those computers (using the Optimized PostScript Stream option).
Variables" on page 571). l Evaluate Expression: Lets you enter a custom expression and displays its value at run-time. You can use the Evaluate Expression section to see the result of any combination of variable properties (see Variable Properties). To add a new expression, simply right-click in the window and select Add Expression. Click in the box on the left to edit the expression and add any variable properties or static text you want, and click outside of the box to save it.
l Messages in Gray are job info and variable changes. l Messages in Black are debug information and processing information. There are various actions you can execute in the Message area. Here they are: l l l l l l l Click any line to select it. While a line is selected, press Delete on your keyboard or right-click on the line and select Delete to delete the line. While a line is selected, press CTRL+X on your keyboard or right-click on the line and select Cut to place the line in the clipboard.
To edit properties of processes, documents, and printers in the Object Inspector: l l l In the Configuration Components pane, select a process, a document (either a document in the Documents category or a document assigned to a printer queue) or a printer queue. The selected object’s properties appear in the Object Inspector. In the Object Inspector, click an editable property.
expected to execute some sort of task, they are always referred to, in this documentation, as "tasks", except in the specific case of importing a new plug-in or customizing the Plug-in bar. Categories The default categories lists plug-ins according to what type of task each achieve.
Furthermore, the Plug-in bar can be customized using the Popup indicator control ( ). Customizing the Plugin bar is mostly for third party or legacy plug-ins. Using the contextual menu displayed by the pop-up indicator, you can: l Insert, delete and rename custom categories. l Move categories up or down. l Import third party or legacy plug-ins.
l l l "Configuration Components Pane Appearance Preferences" on page 622 Behavior: l "Default Configuration Behavior Preferences" on page 623 l "Notification Messages Behavior Preferences" on page 623 l "Sample Data Behavior Preferences" on page 626 l "Network Behavior Preferences" on page 626 l PlanetPress Capture l OL Connect l PDF Text Extractor Plug-in: l "General Plug-In Preferences" on page 638 l "Messenger Plug-In Preferences" on page 639 l "HTTP Server Input 1 Plug-In Preferen
Other Preferences and Settings l l The PReS Workflow Services dialog lets you select the account that PReS Workflow Service uses to communicate on the server and the network. See "Workflow Services" on page 590. You can change the appearance of the Run Script and XSLT Editor through the Editor Options dialog. General Appearance Preferences Ribbon Color Scheme l Blue: Sets the general interface color scheme to a blue color. l Silver: Sets the general interface color scheme to a silver (gray) color.
Object Inspector Appearance Preferences Colors l This window lets you set the color of individual Object Inspector elements. To change the color of a given element, select it in the list box above and then choose a color from the drop-down list below. Options l l Vertical line 3D: Select to display the vertical line between property names and their values using a 3dimensional effect. Use groups: Select to organize the display of properties into groups.
l l l l l Button Style: Select whether to show the expansion links as either an arrow (points right for a closed tree, down for an open tree) or a square (shows a minus symbol for an open tree, plus symbol for a closed tree). Show Tree Lines: Check to choose whether or not to display the lines that connect the different objects in the Configuration Components pane. Show Grid Lines: Check to choose whether or not to display grid lines between each object in the Configuration Components pane.
Preferences l l l l l l l l l l l l l User mismatch: Select to have PReS Workflow display a prompt when a different user opens the application. Task deletion: Select to prompt for confirmation when deleting a task. Document deletion: Select to have PReS Workflow prompt for confirmation when deleting a document.
l l l l l l l l l l l PReS Watch 3 documents and job commands transfer: Select to have PReS Workflow display a prompt when you import a configuration from PReS Watch 3 that allows you to transfer documents and job commands. Plugin not found: Select to have PReS Workflow display a prompt when you import a configuration, and one or more of the plugins used in the configuration are not found on the computer running the software.
l l l Prompt on Saving with Unknown Task: Select to have PReS Workflow prompt for confirmation when saving a configuration file or sending the configuration to the PReS Watch service, when any process contains Unknown Tasks. If an Unknown Task is present, such as when a process was created with a PReS Workflow license that is not the same as the current one, the settings for this task will be lost when saving or sending to the service.
NDS options group (these properties are optional) below to properly log in to NetWare. l l l l l Username: Enter your NetWare user name. This is the user the PReS Workflow service uses to log in to NetWare at run-time. The service accesses resources as configured for this user. Password: Enter the NetWare password corresponding to the user name you entered in the previous text box. Tree: Enter the NetWare Directory Services (NDS) tree where the user resides.
The available PlanetPress Capture user options are: l Mode: Choose between Server and Client mode. Client and Server mode are used for multi-server architectures. See PlanetPress Capture Server/Client. l Port: Select the port used to connect two servers together. The default value is 5864. l Document and Pattern Database group l l l l Status: Displays the status of the database.
Note The Server/Client mode is only used for managing pen licenses and has no impact on the Capture Database itself. The database can be stored locally or remotely, regardless of the Server/Client mode specified. PlanetPress Document Manager The PlanetPress Capture Document Manager dialog is used to manage all the documents present in the PlanetPress Capture database that are currently open.
l l l l l Greater than: If the mask and database information are both numbers, the mask will be a larger number. Less than or equal to: If the mask and database information are both numbers, the mask will either be smaller or equal to the database information. Greater than or equal to: If the mask and database information are both numbers, the mask will either be larger or equal to the database information.
PlanetPress Capture ODBC Settings This dialog is used to set up the connection to a PlanetPress Capture Database through an ODBC connection. To access this dialog, See "PlanetPress Capture User Options" on page 627. Settings l l Name: Click to displays and choose from a drop-down of each DSN (Data Source Name) available on the system, along with it's source (User DSN or System DSN) and the driver it uses (database type). Type: Click to display a drop-down of supported database types.
Database Considerations (ODBC) Technical On 64-bit operating systems, the ODBC Data Sources created by the Data Source (ODBC) icon in the Administrative Tools will not appear here, as PReS Suite is 32-bit and cannot access the 64-bit data sources. In order to create an ODBC connection visible by PReS, you will need to access the 32-bit version of the ODBC manager, available in C:\Windows\SysWOW64\odbcad32.exe .
l l l By default, MySQL is configured not to allow any SQL request larger than 16 megs. In the event where 2 requests are made simultaneously on the same record, MySQL will queue one of the requests and execute it once the first one is done. In extremely rare cases this may cause a timeout on very large requests. MSSQL (Microsoft SQL Server) l l l l All versions of the SQL Server are supported, including all Express versions.
l l Pattern Sequence: The pattern sequence the pen is assigned to. You can double-click this area and edit the pattern sequence as required. User ID: The name of the user assigned to this pen. You can double-click this area to edit the user ID. This can also be custom information. Bottom Toolbar l l l Button: Click to add a new line in the Pen Data List, then edit the information on this new line.
l Pen ID: Displays the Pen ID (serial number) to identify the pen l Old desc.: Displays the content of the User ID field for the pen as it is now. l New desc.: Type the new description to identify the pen l Replace: Click to save the modification to the description l No Change: Click to save the registration without modifying the description. l l Modify: Click to enable edits in the Old desc. field. The current information can then be modified.
l License List: Displays the licenses that have been added to this system. l Pen License: The identification of the Pen Pack. l Quantity Of Pens: The number of pens that can be registered with this pack. PlanetPress Production Group l Server Type: The type of server installed, normally PlanetPress Production Server. l Total pens: The total number of available pens on this server, each Pen Pack being added together.
Accepted values range from 0 to 1. The default value is 0.3, recommended values are between 0.05 and 0.30. Delta Height Defines the tolerance for the height and position difference between two target fragments. The higher the number, the more difference between the fragment's height (the tallest font character's height) will be accepted and the more vertical distance between fragments are accepted. Exponents, for example, are higher and lower.
OL Connect User Options These options control some of the features in the OL Connect Tasks. This is valid both for PlanetPress® Connect and PReS® Connect. Warning OL Connect User Options are not applied immediately. In order for these changes to be applied, the Workflow Configuration must be submitted to the Workflow Service. Otherwise, these options will not be accounted for in Debug mode. The available OL Connect user options define the default behavior of OL Connect tasks' OL Connect Proxy tab.
l Log level group l l l l Startup and shutdown: Select to only track when the PReS Workflow service is started and stopped. Task failure: Select to only track when tasks in the processes running in a PReS Workflow configuration fail. Task success and failure with details: Select to track when the tasks in processes running in PReS Workflow succeed and fail, with details. Details can include why tasks fail and how successful tasks are executed.
l Logging options group l l Delete log files after: Enter the number of days after which to delete the Messenger service logs. Each log covers a 24-hour period and is kept in the Log folder, which is located in the installation folder. Verbose log: Select this option if you want the log to contain a maximum amount of information. HTTP Server Input 1 Plug-In Preferences HTTP server input 1 plug-In preferences control the server protocol aspects of the PReS WorkflowHTTP Server Input tasks.
l l l l l l l l Certificate: Enter the absolute path to the site Certificate. The file generally ends with a .crt extension and is provided by a certificate provider, or through the use of certificate generators such as openssl or makecert.com. Key: Enter the absolute path to the Private Key File. This file generally ends with a .key extension. Password: Enter the password (or passkey) for the Private Key File.
Resulting XML Structure in HTTP Request Envelope email@example.
HTTP Server Input 2 User Options The HTTP Server Input 2 user options are used to enable serving static HTTP resources, as part of an HTTP Server workflow. These resources are referred to within the HTML response file and do not pass through a process to get served so the process is very quick. Static resources are especially useful for additional formatting of HTML files such as JS (JavaScript) scripts, CSS files and images, since they are not dynamic and generally shared between multiple dynamic files.
Preferences l Protocol options group l l l l l Log all Winsock and network messages: Select to have PReS Workflow keep a log of all Winsock and other network messages that occur through the LPD service. These are messages related to jobs being sent from other systems through LPR, and being received by PReS Workflow via LPD. Since these messages can accumulate, you have the option of not logging them. Log files are kept in the Log folder, which is located in the PReS Workflow installation folder.
Preferences l Serial settings group l l l l l l l l Serial port: Select the port of the computer where the Serial input is connected to (COM1 through COM8). Baud rate: Select the baud rate of the Serial input. The baud rate is the number of bits transferred per second. The transferred bits include the start bit, the data bits, the parity bit (if defined), and the stop bits. Data bits: Select the number of data bits defining the incoming data file on this serial port.
Telnet Input Plug-In Preferences The Telnet input plug-in preferences controls the log of the PReS Workflow Telnet Capture service. Since PReS Workflow lets you monitor multiple Telnet inputs simultaneously, the port setting for all Telnet input tasks cannot be set in the Preferences. Preferences l l Log all Winsock and network messages (very verbose): Select to have PReS Workflow keep a log of all Winsock and other network messages that occur from the Telnet input.
the following: l WinFax Pro l Dialing format: Select how you want PReS Fax to read the fax number in the data selection and send it to WinFax PRO. The dialing format you select here must be identical to the one you set in WinFax PRO; a discrepancy between the two may result in WinFax PRO dialing incorrect fax numbers. Select Default to have PReS Fax set the dial prefix, long distance prefix, area code, and fax number according to the content of the data selection, and send the result to WinFax PRO.
exceeded the maximum number of retries. This folder can then be used as an input for a PReS Workflow process for monitoring the status of PReS Fax jobs. The postscript (PS) file for the job is also copied with the report file and can be printed, sent by e-mail, or archived as specified by the PReS Workflow process. l l l Expand folder paths in UNC (Universal Naming Conventions) format: Select to have PReS Fax use complete network server path names (\\servername\sharename\path\filename).
local naming system (such as the DOS naming system in Windows) would result in “File not found” error messages. l Dialing options button: Click to set the appropriate options as required. Since these options are specific to the faxing program, refer to the faxing program’s documentation for more information. Captaris RightFax options l l l l l RightFax Printer: Select a RightFax printer. A RightFax printer is a fax driver that makes it possible to send faxes automatically.
numerical format. Note that changing this option also affects the log displayed in the PReS Workflow Service Console. l l l Interval: Select the interval (in seconds) at which the FTP service is to dispatch jobs from the ftpPut folder to the FTP sites. Back up job on error: Select to move the job file to a local folder ftpPut\error if an error occurs while sending a job via the FTP output. This folder is relative to your install folder.
l l l l l l l l Error Log: Select to send an email that includes the current error log to the administrator when an error occurs. The error log is sent to all addresses you enter in the Administrator’s address(es) text box. Error file: When enabled, sends an e-mail with an attachment of the offending file when an error occurs in the PReS Image output task. Additionally, a backup of the job is created in the Error folder, which is located in the PReS Workflow installation folder.
l l l l l Database directory: Enter the path of the directory in which the Access database is located, or use the Browse button to navigate to, and select, the directory. This option is available only when you select Access database in the Database type box. Data source name: Enter the name of the computer on which the database runs. This option is available only when you select SQL Server database or Oracle database in the Database type box.
l l l l l l Name: Enter the name of the user sending the error messages to the administrators. Organization: Enter the name of the organization of the user sending the error messages to the administrators. Email address: Enter the email address of the user sending the error messages to the administrators. Reply address: Enter the reply address that recipients use to reply to the error messages. Outgoing mail (SMTP): Enter the IP address of the server that PReS Workflow uses to send the emails via SMTP.
l l l Print up to: Select the maximum number of files that can be simultaneously sent to print by the LPR output service. Error handling group l l l l No source port range restriction: Select to remove any restrictions on the port PReS Workflow uses to send the job file via the LPR/LPD protocol. Clear to restrict the port used to send the job to one in the range between 721 and 731. Max.
Note It is also mandatory to send your configuration to your PReS Workflow service since the PrintShop Web credentials are included in the *.cfg file (See "Send your Configuration" on page 11), which is updated every time the configuration is sent to the service via the Send Configuration button. Editor Options The Script Editor is used to edit scripts used in Run Script and the XSLT Editor is used to edit scripts used in Open XSLT action tasks. Most of the options listed below are valid for both editors.
l l l l l l l l l l l Cursor through tabs: Select to move one by one through the spaces of tabs using the left or right arrow keys. Clear to have the arrow keys treat the tab as a single character. You must select Use tab character to use this option. Group undo: Select to set the undo feature of the Editor to undo the last group of editing commands entered. An editing command is defined as a mouse click, a press on ENTER, or a press on any other key.
l l l l Find text at cursor: Use to set the behavior of the Find dialog box. Select to automatically copy the word under the pointer into the Text to find box when you open the Find dialog box. Clear to prevent the copy. If no previous search terms appear in the Text to find drop-down list, the Editor performs the copy regardless of whether this option is selected or cleared. Block indent: Enter the number of spaces to jump for each block indent. The default is 2 and the maximum is 16.
l l l l l l Right margin position: Enter the position of the right margin indicator, in number of characters, relative to the left margin. For example, if you enter 80, the distance from the left margin to the right margin indicator is 80 characters. Use the drop-down list to select a previously-entered margin position. Gutter: Select to have the Editor display a gutter between the Commands and Code areas. Use the Gutter width option to set the width of the gutter.
l Attributes Group l l l Bold: Select to bold the element highlighted in the Element list box when it is displayed in the Script Editor. Italic: Select to italicize the element highlighted in the Element list box when it is displayed in the Script Editor. Underline: Select to underline the element highlighted in the Element list box when it is displayed in the Script Editor.
l " Undo a Command" on page 669 l " Redo a Command" on page 670 Zoom In or Out within Process Area You can do a zoom out in the PReS Workflow Process area to see more tasks at the same time. In zoom out mode, you can perform the exact same functions as in normal view mode. To zoom in or out on the PReS Workflow Process Area: 1. Click on the View tab of the Ribbon. 2. Click on Zoom Out in the Navigate group to zoom out, and Zoom In to zoom in.
There are a few things to keep in mind when dropping tasks: l l You can insert input tasks anywhere in the process except in output task locations. When you add an output task, a new branch leading to that new task is added above the selected task or branch, except when replacing an existing output task. l Dropping a task on top of another one replaces it. l Dropping a task between two tasks will insert it at that location.
Replacing Tasks, Conditions or Branches You can replace existing tasks either by dropping a new task on it, or by pasting another task over it. To replace an existing task with a new task, see Adding Tasks. To replace an existing task with another existing task or its properties, see Cutting, Copying and Pasting Tasks and Branches. Note You cannot replace a task by a branch or a condition. Trying to paste or drop a branch or condition over a task will insert it before the task instead.
Note You cannot use the Delete option to remove an input or output task, but you can right-click on them and click Cut instead. This replaces the task with an unknown task (see Unknown Tasks) To delete the path below a branch crossing (instead of the path to the right of the branch): l Press Shift+CTRL+Delete. l From the right-click menu, choose Edit | Delete| Delete Below the Branch.
l l l l Stop Branch: If the task is in a branch of the process, the branch is stopped and the job file is returned to the process after the branch. The branch will not produce any output. Stop Process: The process is stopped and no more processing is done. No further output is produced. Log Message: Check this option to enable logging a custom error message in PReS Workflow' log file. Message: Enabled only when the Log Message option is checked.
To copy and paste tasks or branches: 1. In PReS Workflow Process area, select the task or branch you want to copy and paste. 2. From the Home tab in the Ribbon, choose Copy (or right-click and select Copy from the drop-down menu). 3. To paste the task or branch to a different process, select that process. 4. Select the task or branch crossing above which you want the task or branch to be pasted. 5. From the Home tab in the Ribbon, choose Paste (or right-click and select Paste from the drop-down menu).
Note You can only paste the properties of an input task on the initial input task of your process. Similarly you can only paste the properties of an output task on another output task. Also, you cannot paste the properties of a task on a branch and vice-versa. Note You can paste only the properties of the On Error tab of any task or branch on another one. To copy and paste the On Error properties of a task or branch: 1. Copy or cut a task or branch from which you want the On Error properties. 2.
3. Release the mouse button to drop the dragged item. The dropped task or branch is moved above the item over which it was dropped. To duplicate a task or branch, the same method applies but with a slight difference: 1. In PReS Workflow Process area, click the icon of the task or branch you want to duplicate. 2. While holding down the mouse button, press and hold down the CTRL key and drag the icon task or branch over another task or branch. 3.
To disable or enable a task or branch: 1. In the PReS Workflow Process area, click the icon of a task or branch. 2. From the Debug tab in the Ribbon, click Ignore. If the task or branch was enabled, it is now disabled, and vice versa. Resize Rows and Columns of the Process Area Resize the rows and columns of PReS Workflow Process area in which tasks are located to better visualize the organization of your process. To resize rows and columns of the PReS Workflow Tools Process area: 1.
Variable Document Name The Variable Document feature is used to dynamically determine which document is merged with the data in your output. The document name can come from any of the variable properties (see Variable Properties). Note If the data contains an extension, it will be replaced by .ptk. To use a variable document: 1. Click on the %o entry in the document list 2. Type the variable properties or use the right-click menu to insert the correct variable properties. 3. Click OK on the dialog.
To undo a command: l From the Quick Access Toolbar, choose Undo. Redo a Command The Redo command can be used to redo commands that were just undone using the Undo command. For example, if you used the Undo command three times in a row and immediately thereafter decided to redo those commands, you could use the Redo command three times in a row to redo those commands. Note that all commands in PReS Workflow Configuration can be redone. To redo a command: l From the Quick Access Toolbar, choose Redo.
To move the Quick Access Toolbar below or above the Ribbon: 1. Right-click on the Quick Access Toolbar, or click on the downwards arrow at the rightmost end of the Quick Access Toolbar. 2. Click on Show Quick Access Toolbar Below the Ribbon or Show Quick Access Toolbar Above the Ribbon, depending on where you want it. Note The Quick Access Toolbar buttons cannot be moved or re-ordered. If you wish to re-order them, you will need to remove all the buttons and re-add them in the desired order.
l l l l l The Arrange group contains the Group/Ungroup, Sort by Name and Order controls, allowing to reorder objects in the Configuration Components pane. It also includes the Undo/Redo controls, as well as a Rename control, to modify a given component's name.
l l l l l l The Services Status control allows to start, pause and stop PReS Workflow service. The Configure Services control loads the PReS Workflow Services dialog to configure the user account PReS Workflow should use. The Service Console button opens the The PReS Workflow Service Console, allowing to monitor real-time information on the configuration execution. The PlanetPress Capture group contains: l The Document Manager button opens the PlanetPress Capture Document Manager.
The Task Comments pane cannot be used to edit the comments themselves - only to see them. to edit the comments, the properties of the task must be opened, and the comments changed in the Comments tab.
Copyright Information Copyright © 1994-2017 Objectif Lune Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any other language or computer language in whole or in part, in any form or by any means, whether it be electronic, mechanical, magnetic, optical, manual or otherwise, without prior written consent of Objectif Lune Inc. Objectif Lune Inc.
Legal Notices and Acknowledgements PReS Workflow, Copyright © 2017, Objectif Lune Inc. All rights reserved. The license agreements for the associated open source third party components can be downloaded here. This application uses the following third party components: l l l l l l l Apache Javascript Support (Rhino) version 1.7.3 which is licensed under the terms of the Mozilla License Version 1.1. The source code can be obtained from the following location: https://developer.mozilla.
l l l l l l l l l l l l JavaX Mail which is distributed under the terms of the Common Development and Distribution License (CDDL) Version 1.1. The source code for this can be obtained from the following location: https://java.net/projects/javamail/downloads/directory/source Jersey which is distributed under the terms of the Common Development and Distribution License (CDDL) Version 1.1. Information on how to obtain the source code can be found at the following location: http://repo1.maven.
l l l l l l l l Servlet API developed by Sun as part of the Glassfish project and licensed under the terms of the Common Development and Distribution License (CDDL) Version 1.0. Information on how to download the Glassfish source (as part of Java EE platform) can be obtained from here: https://wikis.oracle.com/display/GlassFish/Java+EE+7+Maven+Coordinates Spring Framework which is distributed under the terms of the Apache Software License Version 2.0.
l Apache Commons CLI l Apache Commons Codec l Apache Commons Collections l Apache Commons Configuration l Apache Commons DBCP l Apache Commons Discovery l Apache Commons FileUpload l Apache Commons Imaging l Apache Commons IO l Apache Commons Lang l Apache Commons Logging l Apache Commons Net l Apache Commons Pool l Apache Commons VFS l Apache Derby l Apache Felix and dependencies l Apache Geronimo l Apache Jakarta HttpClient l Apache Log4j l Apache Neethi l Apache O
l Google Collections l Google GSON l Jetty l LMAX Disruptor l OPS4J Pax Web l org.json.simple l Spring Dynamic Modules l StAX l XMLBeans Eclipse Technology: This Software includes unmodified Eclipse redistributables, which are available at www.eclipse.org. The Eclipse redistributables are distributed under the terms of the Eclipse Public License - v 1.0 that can be found at https://www.eclipse.org/legal/epl-v10.html.
This application uses Java Advanced Imaging which is part of the Java SE framework and platform and which is distributed under the terms of the Oracle Binary Code License Agreement for the Java SE Platform Products and Java FX. Copyright 2013, Oracle America ,Inc. All rights reserved. Use is subject to license terms. ORACLE and JAVA trademarks and all ORACLE- and JAVA-related trademarks, service marks, logos and other brand designations are trademarks or registered trademarks of Oracle in the U.S.
