Novell Designer for Identity Manager 3.5, Manual, Page: 18 / 510

18 Policies in Designer 3.5
no
vd
ocx
(e
n)
13
Ma
y 20
09
Š
Actions can have dynamic arguments that derive from tokens that are expanded at runtime.
Š
Tokens are broken up into two classifications: nouns and verbs.
Š
Noun tokens (see Chapter 14, “Noun Tokens,” on page 313 ) expand to values that are
derived from the current operation, the source or destination data stores, or some external
source.
Š
Verb tokens (see Chapter 15, “Verb Tokens,” on page 353 ) modify the concatenated
results of other tokens that are subordinate to them.
Š Regular expressions (see “ Regular Expressions ”) and XPath 1.0 expressions (see “ XPath 1.0
Expressions ”) are commonly used in the rules to create the desired results for the policies.
Š
A policy operates on an XDS document and its primary purpose is to examine and modify that
document.
Š
An operation is any element in the XDS document that is a child of the input element and the
output element. The elements are part of the Novell
®
nds.dtd
; for more information, see
“ NDS DTD ” in the Identity Manager 3.6 DTD Reference .
Š
An operation usually represents an event, a command, or a status.
Š The policy is applied separately to each operation. As the policy is applied to each operation in
turn, that operation becomes the current operation. Each rule is applied sequentially to the
current operation. All of the rules are applied to the current operation unless an action is
executed by a prior rule that causes subsequent rules to no longer be applied.
Š
A policy can also get additional context from outside of the document and cause side effects
that are not reflected in the result document.