2021.1

Generating Web output from Workflow
Generating Web output from Workflow requires you to send a template with a Web context to
Workflow; see "Sending files to Workflow" on page446.
Next, you will have to create a process in Workflow that serves one or more web pages; see
"Web processes with OL Connect tasks" on page188.
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.
Note
With a trial or reseller license, Connect Web output is limited to the localhost. This means
that the Connect Server and Workflow must be on the same workstation in order to create
Web output.
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1278.
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.
Page 1491