Publisher Channel Policies; Publisher Channel Web; A.7 Publisher Channel Web Page Templates - Novell IDENTITY MANAGER 3.6.1 - MANUAL TASK SERVICE DRIVER Implementation Manual

The replacement tokens used in an e-mail template dictate the elements that must be
<item>
supplied as children of the < > element that is constructed by the Subscriber
replacement-data
channel policy that constructs the < > element. For example, if the e-mail template has the
mail
replacement token $employee-name$, there must be an < > element
item name="employee-name"
in the replacement data for the < > element. If the employee name item is not present, the
message
resulting e-mail message body has no text in the location occupied by the replacement token in the
template.
E-mail templates can be used to generate message bodies that are plain text, HTML, or XML.
If an e-mail template generates a plain text message, it must be processed by a style sheet that
specifies plain text as its output type. If the style sheet does not specify plain text as its output type,
undesirable XML escaping occurs. The default Manual Task Service driver style sheet,
, is normally used for processing templates that result in plain text.
process_text_template.xsl
A.6 Publisher Channel Policies
In most implementations of the Manual Task Service driver, no Publisher channel policies are
needed. This is because is it possible to construct the Web page and XDS templates so they result in
exactly the XDS required and the XDS doesn't need additional processing by policies.
If policies are required, they are very specific to an installation.

A.7 Publisher Channel Web Page Templates

Web page templates are XML documents containing boilerplate and replacement tokens. Web page
templates are used to generate Web page documents (typically HTML documents). See "Templates"
on page 13 for general information about templates.
Replacement tokens in Web page templates dictate what replacement data is supplied as URL query
data on the Subscriber channel. Replacement data on the Publisher channel is obtained from the
URL query string for HTTP GET requests and from the URL query string and the POST data for
HTTP POST requests.
As an example of the flow of replacement data from the Subscriber channel to the e-mail message
and then to the Publisher channel Web server, consider the following scenario:
The Manual Task Service driver is configured so that a new employee's manager is asked to assign a
room number to the new employee. The trigger for the e-mail to the manager is the < > command
add
for a new User object that is processed by the Subscriber channel Command Transformation policy.
When the manager clicks a URL in the e-mail message, a Web page is displayed in the manager's
Web browser. The Web page must indicate for whom the manager is entering a room number.
To accomplish this, the < > element on the Subscriber channel contains a replacement
url-query
data item that identifies the new user by name:
<item name="subject-name">Joe the Intern</item>
This causes the URL query string to contain (among other things) "subject-
name=Joe%20the%20Intern". The "%20" is a URL-encoded space.
The manager's Web browser submits the URL to the Publisher channel Web server when the
manager clicks the URL in the e-mail message. The Web server constructs a replacement data item
named subject-name with the value Joe the Intern.
Driver Settings, Policies, and Templates 37