Novell IDENTITY MANAGER 3.6.1 - UNDERSTANDING POLICIES 05-06-2009 Manual

Also see for IDENTITY MANAGER 3.6.1 - STAGING BEST PRACTICES GUIDE 2010: Installation guide Reporting guide Overview Manual Manual

Contents

Novell IDENTITY MANAGER 3.6.1 - UNDERSTANDING POLICIES 05-06-2009 Manual Manual pdf 44 page image

44 Understanding Policies for Identity Manager 3.6novdocx (en) 13 May 20094.4 Variable ExpansionMany conditions, actions, and tokens support dynamic variable expansion in their attributes orcontent. Where supported, an embedded reference of the form $$ is replacedwith the value of the local or global variable with the given name. $$ must be alegal variable name. For information on what is a legal XML name, see W3C Extensible MarkupLanguage (XML) (http://www.w3.org/TR/2004/REC-xml-20040204/#NT-Name).If the given variable does not exist, the reference is replaced with the empty string. Where it isdesirable to use a single $ and not have it interpreted as a variable reference, it should be escapedwith an additional $ (for example, You owe me $$100.00). See the Identity Manager 3.6 DTDReference for the content attributes that support variable expansion.4.5 Date/Time ParametersTokens that deal with dates and times have arguments that deal with the format, language, and timezone of the date and time representation. Date format arguments can be specified with a ‘!’ characteror without a ‘!’ character. If the format begins with a ‘!’ character, then the format is a namedformat. Legal names are defined in Table 4-3 on page 44.Table 4-3 Legal Date/Time Parameterscurrent-op policy local/node set The current operation. Setting this variableusing the

element causes the first operation specifiedby

to become the currentoperation for the remainder of the currentpolicy execution or until it is set to anothervalue. The new current operation must be anelement sibling of the original currentoperation and must have been added by thecurrent policy.Name Description!CTIME Number of seconds since midnight, January 1, 1970. (Compatiblewith eDirectory time syntaxes).!JTIME Number of milliseconds since midnight, January 1, 1970.(Compatible with Java* time).!FILETIME Number of 100-nanosecond intervals since January 1, 1601(Compatible with Win32 FILETIME).!FULL.TIME Language-specific FULL time format.!LONG.TIME Language-specific LONG time format.!MEDIUM.TIME Language-specific MEDIUM time format.!SHORT.TIME Language-specific SHORT time format.!FULL.DATE Language-specific FULL date format.Name Type Description