2021.2

Table Of Contents
Some limitations
l Style sheets cannot refer to external resources.
l The Connect Server user needs access to whichever network path is used. If the network
path is on a domain, the Connect Server must be identified with domain credentials that
have access to the domain resources.
For more information on network paths, please see this Wikipedia entry: file URI scheme.
Web resources
Web resources are simply accessed using a full URL. This URL needs to be publicly
accessible: if you type in that URL in a browser on the server, it needs to be visible.
Authentication is possible only through URL Parameters
(http://www.example.com/data.json?user=username&password=password) or through HTTP
Basic Auth (http://username:password@www.example.com/data.json).
Resources can also be called from a PlanetPress Workflow instance:
l "Static Resources", as set in the preferences, are accessed using the resource path, by
default something like http://servername:8080/_iRes/images/image.jpg. (For guidance on
setting the preferences, search for 'HTTP Server Input 2' in the PlanetPress Workflow
help files on: OL Help).
l Resources can also be served by processes: http://servername:8080/my_
process?filename=image.jpg (assuming "my_process" is the action in the HTTP Server
Input).
Runtime parameters
Runtime parameters can pass values from an automation tool - PlanetPress Workflow, usually
- to a template, data mapping configuration or Job Creation Preset. The actual values of the
parameters may be different from one time that a process runs to the next, which means the
output could be different even when the same template, data mapping configuration and/or Job
Creation Presets are used.
Defining runtime parameters for a template
Runtime parameters in a template must be defined on the Parameters pane. This can be found
next to the Data Model pane. If it isn't visible, use the menu: Window > Show View >
Parameters to make it visible.
Page 466