8.5
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.5
- System Requirements
- Basics
- Features
- The Nature of PReS Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Variable Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
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. These comments are saved when the dialog is closed with the OKbutton,
and are displayed in the Task Comments Pane.
Create Web Content
The Create Web Content action task generates the output of the HTMLContext of a specified template and
returns the HTMLcode to PReS Workflow for further processing and return to the requester. Generally, this
task is placed within an HTTP Server Workflow.
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
For a single record, this task generates the output for the HTMLContext of the specified template. Any
external resources such as images, css stylesheets or JavaScript files, are also produced and put aside on
the OLConnect Server component.
Output
The task outputs HTMLcode as a job file. Within this HTMLcode, references to external resources point to
the local OLConnect Server and are served to the requester directly when the HTMLfile is opened in a
browser.