# LiveSyncWorkDefinitionType (Complex Type)

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

Supertype: ResourceWorkDefinitionType
Definition for a live sync activity.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
resourceObjects | container ResourceObjectSetType | [0,1] | Specifies a set of resource objects to be processed.
batchSize | property int | [0,1] | Batch size for live sync operations: if specified as N > 0, live synchronization fetches at most N records during each provisioning.
updateLiveSyncTokenInDryRun | property boolean | [0,1] | Indicates if the LiveSync token should be updated when running in dry run mode.
updateLiveSyncTokenInPreviewMode | property boolean | [0,1] | Indicates if the LiveSync token should be updated when running in preview (simulation) mode.

- ### Items

  - #### resourceObjects

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Specifies a set of resource objects to be processed.

  - #### batchSize

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Batch size for live sync operations: if specified as N > 0, live synchronization fetches at most N records during each provisioning.synchronize() method execution - i.e. during any live sync task run. (Currently, it leaves unprocessed changes for the next live sync task run. This may change in the future.) USE WITH CARE. This feature assumes that the connector provides LiveSync capability with preciseTokenValue = true, i.e. that it assigns sync tokens to individual changes "incrementally" so it can resume live sync operation on each individual change. This can be the case of SQL connectors, but e.g. not for CSV or LDAP ones.

  - #### updateLiveSyncTokenInDryRun

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Indicates if the LiveSync token should be updated when running in dry run mode. If false (the default) then LiveSync will not update token to a new value so it will process objects fetched on the next run (either dry or normal). If true, it will update the token, and therefore marks objects as processed.

  - #### updateLiveSyncTokenInPreviewMode

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Indicates if the LiveSync token should be updated when running in preview (simulation) mode.