Replacement Data; Template Action Elements; Subscriber Channel E-Mail - Novell IDENTITY MANAGER 3.6.1 - MANUAL TASK SERVICE DRIVER Implementation Manual

1.5 Replacement Data

Replacement data consists of strings that take the place of replacement tokens in the output
document generated from a template. Replacement data is either supplied by Subscriber channel
data, Publisher channel HTTP data, or it is supplied automatically by the driver. An additional type
of replacement data is data retrieved from eDirectory via Identity Manager (query data).
Replacement data is more fully described in
Subscriber channel data: Subscriber channel replacement data is of two types. The first type is
used as replacement values for replacement tokens in templates for creating e-mail messages. The
second type is placed in the query portion of a URL so that the data is available for use on the
Publisher channel when the URL is submitted to the Publisher's Web server.
HTTP data: Replacement data is supplied to the Publisher channel Web server as URL query string
data, HTTP POST data, or both.
Automatic data: The Manual Task Service driver supplies automatic data. Automatic data items
are described in
Query data: Replacement tokens that start with query: are considered to be requests to obtain
current data from eDirectory. The portion of the token that follows query: is the name of an
eDirectory object attribute. The object to query is specified by one of the replacement data items
association
preceding sentence.

1.6 Template Action Elements

Action elements are namespace-qualified elements in the template that are used for simple logic
control or that are used to create HTML elements for HTML forms. The namespace used to qualify
the elements is http://www.novell.com/dirxml/manualtask/form. In this document and in the sample
templates supplied with the Manual Task Service driver, the prefix used is
Action elements are described in detail in

1.7 Subscriber Channel E-Mail

The Subscriber channel of the Manual Task Service driver is designed to send e-mail messages. To
accomplish this, the driver supports a custom XML element named <
Subscriber channel construct a <
creation of a user. An example <
<mail src-dn="\PERIN-TAO\novell\Provo\Joe">
<to>JStanley@novell.com</to>
<cc>carol@novell.com</cc>
<reply-to>HR@novell.com</reply-to>
<subject>Room Assignment Needed for: Joe the Intern</subject>
<message mime-type="text/html">
<stylesheet>process_template.xsl</stylesheet>
<template>html_msg_template.xml</template>
<replacement-data>
<item name="manager">JStanley</item>
<item name="given-name">Joe</item>
<item name="surname">The Intern</item>
<url-data>
16 Identity Manager 3.6 Manual Task Service Driver Implementation Guide
Appendix C, "Automatic Replacement Data Items," on page
, , or
src-dn src-entry-id
> element in response to some eDirectory event, such as the
mail
> element appears below:
mail
Appendix B, "Replacement Data," on page
. The items are considered in the order presented in the
Appendix D, "Template Action Elements," on page
41.
47.
.
form
>. Policies on the
mail
49.