To change a subprocess to a different type, you must delete the subprocess and add the new step manually. However, you can change a BPMN subprocess (the default) to a webMethods subprocess. For more information, see About Subprocess Types.

To change a call activity to a different type, you must delete the call activity and add the new step manually. However, you can change the invocation behavior of a call activity step between callable process behavior and webMethods referenced subprocess behavior. For more information, see Call Activity Concepts.

Abstract, Service, Receive, Send, User, Rule, or Manual. To change to any other step type, you must delete the task and add the new step manually.

None, Message, or Signal. To change to any other step type, you must delete the start event and add the new step manually.

None, Message, or Signal. To change to any other step type, you must delete the intermediate event and add the new step manually.

None, Message, Signal, Error, or Terminate. To change to any other step type, you must delete the end event and add the new step manually.

Complex, Inclusive, Exclusive, or Parallel. To change to any other step type, you must delete the gateway and add the new step manually.

In BPMN 2.0, boundary intermediate events can be interrupting or non-interrupting. Designer does not support both behaviors for all boundary intermediate events. Only the supported behavior is available in the Change Event Type selection menu. To change to any other step type, you must delete the boundary intermediate event and add the new step manually.

The available change types for boundary intermediate events vary depending on the placement of the boundary intermediate event. For specific information about the supported interrupting behavior, see About Interrupting Behavior for Boundary Intermediate Events.