2018.1

Table Of Contents
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).
Contexts
Contexts are parts of a template that are each used to generate a specific type of output: Web,
Email or Print.
l The Print context outputs documents to either a physical printer a PDF file; see "Print
context" on page385.
l The Email context outputs HTML email, composed of HTML code with embedded CSS.
See "Email context" on page422.
l The Web context outputs an HTML web page. See "Web Context" on page442.
When a new template is made, the Context appropriate to that new template is automatically
created, including one section. After a template has been created, the other two contexts can be
added to it; see "Adding a context" on the facing page.
Tip
If an Email context is going to be part of the template, it is recommended to start with an
Email Template Wizard; see "Creating an Email template with a Wizard" on page419.
After creating a template, contexts can be added to it, but that can not be done with a
wizard.
Page 373