<task xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-3">
<!-- ... -->
<activity>
<!-- ... -->
<execution>
<mode>full</mode>
</execution>
</activity>
</task>
Execution and Execution Mode
The execution of an activity is primarily driven by the executionMode
setting.
Execution Mode
Execution Mode Values
Mode | Meaning | Supported by |
---|---|---|
|
Full execution mode. Changes are computed and also executed. |
All activities. |
|
A preview (simulation) of changes: Changes are computed, but nothing is executed. Used for example to check the thresholds before the full (real) execution or to simulate the execution (since 4.7). |
See note below. |
|
Low-level simulation of shadow classification and correlation. Since 4.7. Experimental. |
See note below. |
|
Nothing is executed. Just metadata are handled. E.g. during reconciliation, only situations in shadows are set. |
See note below. |
|
Items are fetched from repository or resource, but no specific processing is executed.
This is very similar to |
Multi-threading capable activities. |
|
In this mode no items are really fetched. Only the size of individual buckets is measured (if supported by the item provider, e.g. the resource). |
Multi-node capable activities. |
|
Other Execution Definition Items
Item | Description |
---|---|
|
Using |
An example:
<task xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-3">
<!-- ... -->
<activity>
<work>
<!-- ... -->
</work>
<execution>
<mode>preview</mode>
<configurationToUse>
<predefined>development</predefined>
</configurationToUse>
</execution>
</activity>
</task>