2018.2
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 2018.2
- Installation and setup
- Basics
- Features
- About Workflow Configurations
- Workflow Configuration resource files
- About data
- Data Repository
- Debugging and error handling
- About printing
- OL Connect print jobs
- PlanetPress Suite print jobs
- PReS Workflow printer queues
- Shared printer queue properties
- Windows Output printer queue
- LPR Output Printer Queue
- FTP Output Printer Queue
- Send to Folder printer queue
- Load balancing
- Associating PlanetPress Design documents and PReS printer queues
- Triggers
- Objectif Lune Printer Driver (PS)
- About processes and subprocesses
- Using Scripts
- Special workflow types
- About Tasks
- About variables
- Special workflow types
- About related programs and services
- The user interface
- Customizing the Workspace
- PReS Workflow Button
- Configuration Components pane
- Components Area Sections
- Process properties
- PlanetPress Design document properties
- Moving and copying configuration components
- Renaming objects in the Configuration Components Pane
- Reordering objects in the Configuration Components pane
- Grouping Configuration Components
- Expanding and collapsing categories and groups in the Configuration Component...
- Deleting something from the Configuration Components pane
- Dialogs
- The Debug Information pane
- The Message Area Pane
- The Object Inspector pane
- The Plug-in Bar
- Preferences
- Other Preferences and Settings
- General appearance preferences
- Object Inspector appearance preferences
- Configuration Components pane appearance preferences
- Default Configuration behavior preferences
- Notification Messages behavior preferences
- Sample Data behavior preferences
- Network behavior preferences
- PlanetPress Capture preferences
- OL Connect preferences
- PDF text extraction tolerance factors
- General and logging preferences
- Messenger plugin preferences
- HTTP Server Input plugin preferences 1
- HTTP Server Input plugin preferences 2
- LPD Input plugin preferences
- NodeJS Server Input plugin preferences 1
- NodeJS Server Input plugin preferences 2
- NodeJS Server Input plugin preferences 3
- Serial Input plugin preferences
- Telnet Input plugin preferences
- PReS Fax plugin preferences
- FTP Output Service preferences
- PReS Image preferences
- LPR Output preferences
- PrintShop Web Connect Service preferences
- Editor Options
- The Process area
- Cutting, copying and pasting tasks and branches
- Highlight a task or branch
- Disabling tasks and branches
- Moving a task or branch using drag-and-drop
- Redo a command
- Removing tasks or branches
- Replacing tasks, conditions or branches
- Resizing the rows and columns of the Process area
- Undo a command
- Zoom in or out within Process Area
- The Quick Access Toolbar
- The PReS Workflow Ribbon
- The Task Comments Pane
- Additional Information
- Copyright Information
- Legal Notices and Acknowledgments
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 .
The following considerations should be kept in mind while working with ODBC Databases in
PReS Suite.
l
All databases
l
User Rights: During normal operation, Read/Write to tables should be sufficient.
However, during the initial setup, the Create/Drop tables rights is necessary.
l Minimum 100MB of database size is required as a minimum, but the space
requirement depends on the implementation. The more active documents in the
database, the more space is used - note that this progression is rather linear.
l Regular database maintenance is required, such as database compacting, is
required by a system administrator.
l It is recommended to create an IT process that backs up the database regularly.
l The recommended ideal setup is a dedicated SQL Server PC, accessed by PReS
Workflow through an ODBC connection on the local network.
l
Microsoft Access
l Database file (mdb) must be local to the PReS Workflow computer. It cannot be
located on a network drive or another server.
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.
l
MySQL
l Database can be in any location, but performance will depend on the speed of the
connection between PReS and the MySQL server.
l MySQL's performance has been slower than SQL Server and SQL Server Express
during our tests.
l By default, MySQL is configured not to allow any SQL request larger than 16 megs.
l 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.
Page 585