Page History
Data Mapping is a very common task in the integration business. The Designer offers you a powerful tool to define data mappings directly by drawing object flows between the properties of the related classes.
You can create a mapping diagram by creating a mapping operation on a class.
Refer to Modeling Data Structures for more details on how to create a class operation.
Mapping Editor Overview
If you want to create your own data model within the Designer, you need to create a Service and a BPMN model in the Explorer first. Open the BPMN model to display the BPMN editor where you can find the Service panel. Within the Service panel, the folder Data Model is displayed.
Adding a Data Model
In each Service panel you can find the Data Model folder.
Right click the folder to open the context menu and create a new Package. Within a package, you can create all further elements.
| Tip | ||
|---|---|---|
| ||
Apply the same naming conventions to all your models. This makes reading a model much easier. Go to page Naming Conventions and Containment Tree Organization in the Builder User Guide for an overview on practice-approved naming conventions. |
Data Model Elements
On each element in the Data Model folder you can open a context menu. The context menu contains options to create new elements within the current element, and options to edit the current element.
Package
A package is like a directory for the file system. It is used to group data model elements. Packages can have any depth of nesting: To structure your work, you can create packages within packages.
The Package context menu allows you to edit your package and to create further elements.
| Option | Description |
|---|---|
| Add Package | Add another package within the existing package. |
| Add Class | Add a class within the package. |
| Add Interface | Add an interface within the package. |
| Edit Package | Change the package name. |
| Delete Package | Delete the package. |
| Copy Item | Copy the package to paste it elsewhere in the data model tree. |
| Cut Item | Cut the package to paste it elsewhere in the data model tree. |
| Paste Item | Paste the package elsewhere in the data model tree. Available when Copy Item or Cut Item option have been used before. |
Class
In object-oriented programming, each object belongs to a class. A class is a user defined blueprint from which objects are created. Classes have properties (attributes) and operations (interactions of this class).
The Class context menu allows you to edit your class and to create further elements.
| Option | Description |
|---|---|
| Add Property | Add a property to the class. |
| Add Operation | Add an operation within the class. |
| Edit Class | Change the name of the class. |
| Delete Class | Delete the class. |
| Copy Item | Copy the class to paste it elsewhere in the data model tree. |
| Cut Item | Cut the class to paste it elsewhere in the data model tree. |
| Paste Item | Paste the class elsewhere in the data model tree. Available when Copy Item or Cut Item option have been used before. |
Classes can be created in two ways:
- You can create your own classes using the context menu.
- If you model your own forms within the Designer, each form is added as a class to the Data Model folder in a package Message.
Interface
In contrast to a class, an interface has no implementations. Interfaces are used to define common features of multiple classes in one separate class, and then derive from that class.
The Interface context menu allows you to edit your interface and to create further elements.
| Option | Description |
|---|---|
| Add Operation | Add an operation within the interface. |
| Edit Interface | Change the name of the interface. |
| Delete Interface | Delete the interface. |
| Copy Item | Copy the interface to paste it elsewhere in the data model tree. |
| Cut Item | Cut the interface to paste it elsewhere in the data model tree. |
| Paste Item | Paste the interface elsewhere in the data model tree. Available when Copy Item or Cut Item option have been used before. |
Property
Properties are values that are included within a class. Properties always have a type.
The Property context menu allows you to edit your property. It is not possible to create further elements within a property.
| Option | Description |
|---|---|
| Edit Property | Change the name of the property. |
| Delete Property | Delete the property. |
| Copy Item | Copy the property to paste it elsewhere in the data model tree. |
| Cut Item | Cut the property to paste it elsewhere in the data model tree. |
Properties are created in two ways:
- You can create your own properties using the context menu.
- If you model your own forms within the Designer, each form is added as a class and form elements are added as properties of these classes in the Data Model folder in package Message.
Operation
An operation is an action that is carried out to accomplish a given job. Operations can be defined on classes or interfaces. There are several possibilities to implement an operationsss.
The Operation context menu allows you to edit your operation and to create further elements.
| Option | Description |
|---|---|
| Add Parameter | Add a parameter to the operation. Further iniformation see below. |
| Create Implementation | You can choose between two different types of implementation for your class operations:
If an implementation has been added for an operation, the operation icon changes: |
| Edit Operation | Change the name of the operation. |
| Delete Operation | Delete the operation. |
| Copy Item | Copy the operation to paste it elsewhere in the data model tree. |
| Cut Item | Cut the operation to paste it elsewhere in the data model tree. |
| Paste Item | Paste the operation elsewhere in the data model tree. Available when Copy Item or Cut Item option have been used before. |
Parameter
Each operation can have parameters that define the input and output objects. Operation parameters may not only be of complex types but also of base types.
The Parameter context menu allows you to edit your parameter. It is not possible to create further elements within a parameter.
| Option | Description | ||
|---|---|---|---|
| Edit Parameter | Change the name of the parameter.
| ||
| Move Parameter up | Change the order of parameters. | ||
| Delete Parameter | Delete the parameter. | ||
| Copy Item | Copy the parameter to paste it elsewhere in the data model tree. | ||
| Cut Item | Cut the property to paste it elsewhere in the data model tree. |
When you create a new mapping diagram, it is automatically opened in the Mapping Editor:
Use the various functionalities of the BPMN Mapping Editor to design create your BPMN modelmapping diagram:
| Name | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| 1 | Mapping Editor | The Mapping Editor mapping editor is where you design draw your formdata mappings. Go to page Working with the Mapping Editor for detailed information about the features of the Mapping Editoreditor. | |||||||
| 2 | Elements Toolbar | The elements toolbar contains all elements that you can create in the Mapping Editormapping editor. Go to page Working with the Mapping Editor for further details about the usage of the toolbar. | |||||||
| 3 | Model Toolbar | The model toolbar of the mapping editor offers the following:
| |||||||
| 4 | Designer Panels | In the Mapping Editormapping editor, the following panels assist you during modeling:
| |||||||
| Otp | ||||
|---|---|---|---|---|
|
| Rp |
|---|
Overview
Content Tools