Available Change Type Selections
The following change types are available for each of the listed activity, event, and gateway types:
Subprocesses.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.
Call Activities. 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.
Task activities. You can select from:
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.
Start events. You can select from:
None, Message, or Signal. To change to any other step type, you must delete the start event and add the new step manually.
Intermediate events. You can select from:
None, Message, or Signal. To change to any other step type, you must delete the intermediate event and add the new step manually.
End events. You can select from:
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.
Gateways. You can select from:
Complex, Inclusive, Exclusive, or Parallel. To change to any other step type, you must delete the gateway and add the new step manually.
Boundary Intermediate Events. 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.
