Name | Type | Multiplicity | Description |
---|---|---|---|
name |
property string |
[0,1] | |
description |
property string |
[0,1] | |
extension |
container ExtensionType |
[0,1] | Place for non-standard object properties. |
trace |
property boolean |
[0,1] | |
authoritative |
property boolean |
[0,1] | |
exclusive |
property boolean |
[0,1] | |
tolerant |
property boolean |
[0,1] | When set to true, allows attribute/property values that are set outside of this mapping. |
strength |
property MappingStrengthType |
[0,1] | |
channel |
property anyURI |
[0,-1] | |
exceptChannel |
property anyURI |
[0,-1] | |
timeFrom |
property MappingTimeDeclarationType |
[0,1] | |
timeTo |
property MappingTimeDeclarationType |
[0,1] | |
source |
property VariableBindingDefinitionType |
[0,-1] | |
expression |
property ExpressionType |
[0,1] | |
target |
property VariableBindingDefinitionType |
[0,1] | |
condition |
property ExpressionType |
[0,1] | |
inputFilter |
property ValueFilterType |
[0,1] | |
outputFilter |
property ValueFilterType |
[0,1] | |
range |
property ValueSetSpecificationType |
[0,1] | Specifies the range of the mapping (in mathematical sense). |
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: dyn,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]
When set to true, allows attribute/property values that are set outside
of this mapping. I. e. it allows other values than those set by this mapping.
The default value for tolerant setting depends on when the mapping is used.
It is assumed to be false for all mappings. However, for outbound mappings
the real behavior of reconciliation is determined by the tolerance of the
attribute and not tolerance of the mapping (see below).
This default setting was chosen to maintain behaviour
which is compatible with previous midPoint versions.
Note: Mapping tolerance is an interim feature. In fact it is mostly
redundant. The same behavior can be achieved by using mapping
range. However, mapping range is not fully supported in all mappings
and all situations. Therefore mapping tolerance can be used in the
meantime to achieve the desired functionality. However, mapping
tolerance will get deprecated in the midPoint version in which
mapping range achieve full functionality. Therefore it is recommended
to use mapping tolerance only as a last resort. It is recommended
to use mapping range instead of tolerance if the range can be used.
Note: Do not confuse with tolerant setting that applies to the
resource attribute (schemaHandling). If in doubt, use that other
setting instead. That resource attribute tolerance is usually the
right answer.
Support for this setting is currently EXPERIMENTAL.
Flags: RAM,runtime,AVals:3
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
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]
Specifies the range of the mapping (in mathematical sense). I.e. this specifies the values
that the mapping can produce. Range specification makes sense only for authoritative mappings.
If the range is specified then the mapping will scan existing values of the target property.
It will look for values that are there and that are also in the range of the mapping. If such
values are not in the expression results, then such values will be removed (placed in the minus set).
DEPRECATED. Do not use. Use the set definition in mapping target instead.