2018.2

Generating Web output from Workflow
1. Open a template with a Web context.
2. Send it to Workflow using the Package Files dialog; see " Sending files to Workflow" on
page378.
3. Create a process in Workflow containing at least the following steps:
l Any input that will capture a job file that is compatible with the data mapping
configuration that is used. To capture incoming web requests, such as from a
personalized URL (see "Personalized URL" on page721), use a HTTP Server
Input task (see Workflow Help: HTTP Server Input).
l An Execute Data Mapping task to generate a valid record set (see Workflow Help:
Execute DataMapping Task).
l A Create Web Content task with the appropriate settings, to generate the HTML
output (see Workflow Help: Create Web Content).
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1138.
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 1239