You can drag existing elements from the model content and drop them on certain elements in a diagram. The way this happens depends on the diagram type, the element which you drop and where you drop it.
Drop Area: All Diagrams
| Drag Source Area | Initial Element | n | Drop Target Element | Effect |
|---|---|---|---|---|
| Any | Comment | * | Diagram (free area, comment is not allowed to exist yet) | Adds the comment to the diagram as a node and adds connections to all commented elements displayed in the diagram. |
| Any | Attachment | * | Diagram (free area, attachment is not allowed to exist yet) | Adds the attachment to the diagram as a node and adds attachment references to all assigned elements displayed in the diagram. |
| Any | Requirement | 1 | Any (in accordance with configuration of permissible owner of an realization) | Creates an realization between target element and requirement. |
| Any | Type | 1 | Typable element (type is permitted in accordance with configuration) | The typable element is typed with the type. |
| Model Editor | Any | * | Container | The source element is assigned to the container as content. |
Drop Area: BPMN Diagram
| Drag Source Area | Initial Element | n | Drop Target Element | Effect |
|---|---|---|---|---|
| Any | Process | 1 | BPMN Diagram | A view of the process appears. |
| Any | Collaboration | 1 | BPMN Diagram | A view of the collaboration appears. |
| Any | Use Case | 1 | BPMN Diagram |
A collaboration appears. The following occurs:
|
| Any | Global Task | 1 | BPMN Diagram | A new process exists. A call activity with the global task is created as a called element in the process. |
| Any | Process |
1 |
View on collaboration | A participant is created with the referenced process. |
| Any | Process | 1 | View on process or lane nodes or subprocess nodes | A call activity with the process as a called element is created. |
| Any | Global Task | 1 | View on process or Lane node or Subprocess nodes |
A call activity with the global task as called element is created. |
| Any | Event Definition | 1 | View on process or Lane node or Subprocess nodes |
An event is created and the event definition assigned. |
| Any | Data Store | 1 | View on process or Lane node or Subprocess nodes |
A data object with Data Store Reference data object type is created and the data store is assigned as data store definition. |
| Any | Business Object | 1 | View on process or Lane node or Subprocess nodes |
A data object with Data Object data object type is created and the business object is assigned as business object. |
| Any | Service Operation | 1 | View on process or Lane node or Subprocess nodes |
A Service task is created and the operation is assigned as a service operation. |
| Any | Message | 1 |
View on process or |
A send task is created and the message is assigned to the message property. |
| Any | Mask Definition | 1 | View on process or Lane node or Subprocess nodes |
A user task is created and the mask definition is assigned to the mask definition property. |
| Any | Decision | 1 | View on process or Lane node Or subprocess node |
A task is created and the decision is assigned as the decision used. |
| Any | Classifier | 1 | View on process or Lane node or Subprocess nodes |
A data object with Data Object data object type is created and the classifier's business object is assigned as business object. The classifier's business object either needs to be uniquely identifiable or will be created as new. If more than one business object exists for the classifier, then the suitable business object should be used directly. |
| Any | Stereotypable Element | 1 | Artifact Nodes | The element is assigned to the artifact as a represented element. |
| Any | Process | 1 | Sequence Flow Edge | A call activity with the process as a called element is created. The sequence flow edge is split into two edges by the call activity's node. |
| Any | Global Task | 1 | Sequence Flow Edge | A call activity with the global task as called element is created. The sequence flow edge is split into two edges by the call activity's node. |
| Any | Event Definition | 1 | Sequence Flow Edge | An event is created and the event definition assigned. The sequence flow edge is split into two edges by the event node. |
| Any | Mask Definition | 1 | Sequence Flow Edge | A user task is created and the mask definition is assigned to the mask definition property. The sequence flow edge is split into two edges by the user task's node. |
| Diagram | Sequence Flow Nodes (No Linked Edges Exist) | 1 | Sequence Flow Edge | The sequence flow edge is split into two edges by the sequence flow node. |
Drop Area: Diagram for Business Object States
| Drag Source Area | Initial Element | n | Drop Target Element | Effect |
|---|---|---|---|---|
| Any | Business Object | 1 | Diagram | Adds the business object to the diagram as a node. All states and state transitions contains are automatically extended. |
Drop Area: Business Resources Diagram
| Drag Source Area | Initial Element | n | Drop Target Element | Effect |
|---|---|---|---|---|
| Any | Business Resource | 1 | Diagram | The business resource is shown directly in the diagram. |
Drop Area: Process Map
| Drag Source Area | Initial Element | n | Drop Target Element | Effect |
|---|---|---|---|---|
| Any | Stereotypable element or process definition diagram |
* | Concept node | A concept realization from element to concept arises. The corresponding process is used for a process definition diagram. |
| Any | Concept | * | Concept node | Concepts are added as nested nodes within the selected node. |
| Any | Stereotypable element or process definition diagram | * | Concept diagram | For each element, a new concept and then a concept realization from element to concept are created. The corresponding process is used for a process definition diagram. |
| Any | Concept | * | Concept diagram | Concepts are added as nodes in the diagram. |
| Concept diagram | Concept node (no linked edges exist) | 1 | Concept connection edge | The concept connection edge is split into two edges by the concept node. |
Drop Area: Various
| Drag Source Area | Initial Element | n | Drop Target Element | Effect |
|---|---|---|---|---|
| Any | Resources Element | 1 | Activity (Task or Subprocess) | The resource element is assigned to the resource assignment property. |
| Any | Data Store | 1 | Data Store Reference | The data store is assigned to the data store definition property. |
| Any | Event Definition | 1 | Event | The event definition is added to the event definition property. The result's icon changes according to the type of event definition. If multiple event definitions are assigned, the multiple icon is displayed. |
| Any | Business Object | 1 | Item-Aware Element (Data Object, Data Store) | The business object is assigned to the business object property. Global states cannot be assigned. |
| Any | State | 1 | Item-Aware Element (Data Object, Data Store) |
The state is added to the state (global) property. This sets the uses global state switch. The business object which the state belongs to is also assigned in the business object property. |
| Any | Classifier | 1 | Item-Aware Element (Data Object, Data Store) |
A business object is uniquely identified for the classifier or a new one is created. The classifier is assigned as data structure property for the new business object. The business object is then assigned to the item-aware element as a business object. |
| Any | Resources Element | 1 | Lane | The resource element is assigned to the resource property. |
| Any | Message | 1 | Message Referencing Element (Task, Event Definition, Message Flow) | The message is assigned to the message property. |
| Any | Process | 1 | Participant | The process is assigned to the Process view property. |
| Any | Resources Element | 1 | Participant | The resource element is assigned to the partner role property. |
| Any | Resources Element | 1 | Process | The resource element is assigned to the responsible business resource property. |
| Any | Callable Process Element (Global Task, Process) | 1 | Task | The callable process element is assigned to the called element property as long as the task type is set to no type or call activity. The no type value is automatically changed to call activity. |
| Any | Service Operation | 1 | Task | The service operation is assigned to the service operation property as long as the task type is set to no type, send, receive, user or service. The no type value is automatically changed to service. |
| Any | Mask Definition | 1 | Task | The mask definition is assigned to the mask definition property as long as the task type is set to no type or user. The no type value is automatically changed to user. |
| Any | Decision | 1 | Task | The decision is assigned to the decisions used property. If the task type property has the no type value, then the value is automatically changed to business rule. The task's name is changed to fit the decision's name if the business rule task type does not alter the name and is assigned to precisely one business rule. |
| Any | Location | 1 | Business Resource | The location is added to the business resource below the Location property. |
Drop Area: Decision Diagram (DMN Diagram)
| Drag Source Area | Initial Element | n | Drop Target Element | Effect |
|---|---|---|---|---|
| Any | Decision | 1 | Decision Diagram | The decision is added as a node in the diagram. |
| Any | Information | 1 | Decision Diagram | The information is added as a node in the diagram. |
| Any | Business knowledge model | 1 | Decision Diagram | The business logic is added as a node in the diagram. |
| Any | Knowledge source | 1 | Decision Diagram | The knowledge source is added as a node in the diagram. |
| Any | Structure Definition Structure Group Structure Entry | 1 | Decision or Information or Business knowledge |
Regardless of the source element, the corresponding structure definition is copied as the Variable Type property. |
| Any | Task | 1 | Decision | The decision is assigned to the task under the Used Decisions property. If the task type property has the no type value, then the value is automatically changed to business rule. The task's name is changed to fit the decision's name if the business rule task type does not alter the name and is assigned to precisely one business rule. |
| Any | Global Task | 1 | Decision | The decision is assigned to the global task under the Used Decisions property. The global task's name is changed to fit the decision's name if the business rule task type does not alter the name and is assigned to precisely one business rule. |
| Any | Stereotypable Element | 1 | Knowledge source | The stereotypable element is adopted for the knowledge source as information source property. Precisely 1 element is permissible for information sources. Each additional drop exchanges the element. This property can be configured; an error message then rejects the drop if applicable. |
| Any | Stereotypable Element | 1 | Decision | The stereotypable element is added as the value for the decision in the decision owner property. A list of elements can be entered for the decision owner property. Each additional drop adds to the list. The property can be configured; an error message then rejects the drop if applicable. |
| Any | Structure Definition Structure Group Structure Entry | 1 | Decision Diagram | Information is created and added as a node in the diagram. Regardless of the source element, the corresponding structure definition is copied as the Variable Type property. |
| Any | Stereotypable Element | 1 | Decision Diagram | A new source of information is created and added as a node in the diagram. The stereotypable element is adopted for the knowledge source as information source property. |
Drop Area: Whiteboard Diagram
| Drag Source Area | Initial Element | n | Drop Target Element | Effect |
|---|---|---|---|---|
| Any | Diagram or behavior (not a whiteboard diagram and not an opaque behavior) | * | Whiteboard diagram (free area, diagram or behavior is not allowed to exist yet and must be allowed as diagram contents) | Adds the diagram as a node in the whiteboard diagram. |
