<task xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-3">
<!-- ... -->
<activity>
<!-- ... -->
<reporting>
<simulationResult/>
</reporting>
</activity>
</task>Simulation Result
This item defines whether we want to create a simulation result object for this particular activity run, and how it should look like.
Some examples:
Listing 1: Creating a simulation result using the default definition
This causes the creation of a simulation result using the default definition.
Listing 2: Creating a simulation result using a specified global definition
<task xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-3">
<activity>
<reporting>
<simulationResult>
<definition>
<super>standard-result</super>
</definition>
</simulationResult>
</reporting>
</activity>
</task>This uses a global definition named standard-result.
It can be customized by providing further properties within the definition item, if needed.
Listing 3: Creating a simulation result using a custom definition
<task xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-3">
<activity>
<reporting>
<simulationResult>
<definition>
<metrics> <!-- ... --> </metrics>
<useOwnPartitionForProcessedObjects>true</useOwnPartitionForProcessedObjects>
</definition>
</simulationResult>
</reporting>
</activity>
</task>This creates a custom definition of the simulation result that will be used.
See also Simulation Result Definition for more information.
Was this page helpful?
YES
NO
Thanks for your feedback