2019.1

Note
Athough Workflow can serve both static and dynamic resources to a web browser, it is not meant to
be used as a fully featured web server as it is not built for responsiveness nor guaranteed uptime. It
is recommended to use a common web server (for example, IIS or Apache) to serve your contents
and to let Workflow process things only it can do.
For more information on how to serve HTML and PDF generated by Connect through IIS, watch
the Connect with Evie - IIS series.
Aborting content creation
You may want the content creation process to be aborted in certain situations; for example,
when a template script fails to load remote content. To abort the content creation process, you
may raise a fatal error from within a script in the template; see "fatalError(message)" on
page1259.
When a script calls this function in Preview mode, the script that triggers it is marked with an
error icon in the Scripts pane, and the given message is displayed in a hint.
When generating output from the Designer, the Designer will log the error and display an error
dialog with the given message. Content creation is aborted.
When generating output from Workflow, the entire job fails. Workflow will log the error and
execute any follow-up actions that are defined in the On Error tab of the respective OL Connect
Content Creation task (All in One, Create Email Content, Create Print Content, Create Preview
PDF, and Create Web Content ). For more information about how to set up follow-up actions,
see Using the On Error tab in the Workflow Help.
Optimizing a template
This topic describes some ways to optimize a template in order to speed up the output process.
However, the template itself is not the only factor to be taken into account. The server
configuration and hardware configuration have an influence on the output speed as well. For
advice on server configuration and hardware configuration, see "Performance considerations"
on page30.
Page 1361