# SimulatedCorrelatorsType (Complex Type)

### Namespace: http://midpoint.evolveum.com/xml/ns/public/common/common-3

Specify what correlators to use for correlation. Note that if the `includeExistingCorrelators` is set to false (default), then at least one correlator has to be specified in the `inlineCorrelators`.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
includeExistingCorrelators | property boolean | [0,1] | Use correlators derived from the resource of given shadows.
inlineCorrelators | container CorrelationDefinitionType | [0,1] | Inline definition of correlators.
additionalItemsMappings | container AdditionalCorrelationItemMappingType | [0,-1] | Definition of additional item inbound mappings, which could be used from the explicitly defined correlators (see above), but which are not stored yet.

- ### Items

  - #### includeExistingCorrelators

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Use correlators derived from the resource of given shadows.

  - #### inlineCorrelators

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Inline definition of correlators. It can be used to explicitly define the correlator, for example in case when we want to simulate suggested correlation (which is not stored yet).

  - #### additionalItemsMappings

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    Definition of additional item inbound mappings, which could be used from the explicitly defined correlators (see above), but which are not stored yet. The example usage is when the smart service suggests some new correlator. In such case the new correlator often uses also some newly suggested mapping. Neither of these is stored in repository yet, thus they need to be explicitly defined in the simulation task work definition.