# ProcessInstanceModificationInstructionDto ## Properties Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **_type** | **String** | **Mandatory**. One of the following values: `cancel`, `startBeforeActivity`, `startAfterActivity`, `startTransition`. * A cancel instruction requests cancellation of a single activity instance or all instances of one activity. * A startBeforeActivity instruction requests to enter a given activity. * A startAfterActivity instruction requests to execute the single outgoing sequence flow of a given activity. * A startTransition instruction requests to execute a specific sequence flow. | **variables** | Option<[**crate::models::TriggerVariableValueDto**](TriggerVariableValueDto.md)> | | [optional] **activity_id** | Option<**String**> | Can be used with instructions of types `startTransition`. Specifies the sequence flow to start. | [optional] **transition_id** | Option<**String**> | Can be used with instructions of types `startTransition`. Specifies the sequence flow to start. | [optional] **activity_instance_id** | Option<**String**> | Can be used with instructions of type `cancel`. Specifies the activity instance to cancel. Valid values are the activity instance IDs supplied by the [Get Activity Instance request](https://docs.camunda.org/manual/7.13/reference/rest/process-instance/get-activity-instances/). | [optional] **transition_instance_id** | Option<**String**> | Can be used with instructions of type `cancel`. Specifies the transition instance to cancel. Valid values are the transition instance IDs supplied by the [Get Activity Instance request](https://docs.camunda.org/manual/7.13/reference/rest/process-instance/get-activity-instances/). | [optional] **ancestor_activity_instance_id** | Option<**String**> | Can be used with instructions of type `startBeforeActivity`, `startAfterActivity`, and `startTransition`. Valid values are the activity instance IDs supplied by the Get Activity Instance request. If there are multiple parent activity instances of the targeted activity, this specifies the ancestor scope in which hierarchy the activity/transition is to be instantiated. Example: When there are two instances of a subprocess and an activity contained in the subprocess is to be started, this parameter allows to specifiy under which subprocess instance the activity should be started. | [optional] **cancel_current_active_activity_instances** | Option<**bool**> | Can be used with instructions of type cancel. Prevents the deletion of new created activity instances. | [optional] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)