Create an expression that provides an assignment based on search results.
Note: search expression evaluators have changed default for includeNullInputs. Null inputs are NOT processed by search expression evaluators by default. The reason is that null inputs are usually insignificant for search expression and skipping them results in fewer search operations.
Name | Type | Multiplicity | Description |
---|---|---|---|
description |
property string |
[0,1] | Free-form textual description of the object. |
documentation |
property string |
[0,1] | Technical documentation for a particular object or construct. |
trace |
property boolean |
[0,1] | Explicitly trace the execution of this expression. |
relativityMode |
property TransformExpressionRelativityModeType |
[0,1] | Relativity mode of an expression, whether expression is processed in relative or absolute more. |
includeNullInputs |
property boolean |
[0,1] | If set to true (which is the default) the script will be evaluated with null value as argument when the input is changed from or to an empty value. |
condition |
property ExpressionType |
[0,1] | Condition driving whether this expression is evaluated at all (for given inputs). |
targetType |
property QName |
[0,1] | |
oid |
property string |
[0,1] | Fixed OID. |
filter |
property SearchFilterType |
[0,1] | |
searchStrategy |
property ObjectSearchStrategyType |
[0,1] | |
defaultTargetRef |
reference ObjectReferenceType |
[0,1] | Reference that will be used if no target is found. |
createOnDemand |
property boolean |
[0,1] | |
populateObject |
property PopulateType |
[0,1] | TODO |
populate |
property PopulateType |
[0,1] | Populate assignment, association,. |
assignmentProperties |
container AssignmentPropertiesSpecificationType |
[0,1] | Properties of the new assignment. |
Flags: RAM,runtime
Multiplicity: [0,1]
Free-form textual description of the object. It is supposed to describe
the object or a construct that it is attached to.
This information may be presented to midPoint users, even to ordinary end users.
For example role description may be presented to users when they are selecting
roles to request. Therefore the description should be written in a language that
the users can understand.
Description is assumed to be a plan, non-formatted text.
Amount of white space is considered insignificant. E.g. leading and trailing
white space may be skipped, multiple spaces can be collapsed to one and so on.
Flags: RAM,runtime
Multiplicity: [0,1]
Technical documentation for a particular object or construct.
The purpose of this element is to document system configuration and behavior.
The documentation will not be presented to end users. In fact, it will probably
not be presented at all in midPoint user interface. This documentation element
is supposed to be a part of the technical documentation of midPoint deployment.
The tools than generate deployment configuration will look for these elements
and combine them to compiled documentation document.
AsciiDoc formatting is assumed for this element. Any leading or trailing
whitespace is skipped. Indentation equivalent to he indentation of the first
non-blank line of text is also skipped.
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime,AVals:2
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime,AVals:3
Multiplicity: [0,1]
Flags: RAM
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]