# ActivitySubtaskDefinitionType (Complex Type)

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

How the part is realized via subtask.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
taskName | property string | [0,1] | How to derive names for the partition task.
executionEnvironment | container TaskExecutionEnvironmentType | [0,1] | Execution environment configuration to use for partition task.
copyMasterExtension | property boolean | [0,1] | Whether to copy task extension from the master task.
durable | property boolean | [0,1] | Whether the subtasks for parts should be durable i.

- ### Items

  - #### taskName

    Flags: RAM,runtime

    Multiplicity: [0,1]

    How to derive names for the partition task. It is possible to use substitution strings of {masterTaskName}, {masterTaskHandlerUri} and {index} here. Overrides the pattern specified for all parts.

  - #### executionEnvironment

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Execution environment configuration to use for partition task.

  - #### copyMasterExtension

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Whether to copy task extension from the master task. Overrides the value specified in the parent element.

  - #### durable

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Whether the subtasks for parts should be durable i.e. whether they should persist through master task restarts. This is useful e.g. for partitioned validity scanner because each partition keeps its own last scan timestamp.