Processes are based on data that is going in, is processed, and coming out. This data is specified by data types.
Data types can be structured into packages or interfaces. They are defined by classes and their properties, and have related operations and their parameters.
Icon | Element | Description |
---|---|---|
package | ||
interface | ||
class | ||
property | ||
operation | ||
parameter |
To describe the data that is used during a process, you can
The Designer provides six base types: Blob, Boolean, DateTime, Float, Integer, String in a standard library that is imported as per default into all service models.
All these types derive from the seventh, general type Any.
All built-in base types are located in a dedicated package Base Types that is provided with the Designer. You can find more details on the base types and simple examples on Base Types. |
The data types provided by a library are listed in the Service panel. You can find more details on developing libraries on Libraries. |
Besides the Base Types and types from libraries, you can define your own data types in folder Implementation.
User defined classes can be structured the same way imported classes are. How to do this is described in detail on Modeling Data Structures. The Implementation folder also contains a locked package Message. This package has been generated by the Designer, and holds all classes related to the forms you have created in your service model. You cannot change these generated classes. |
You can use all data types, regardless of where they reside - Bridge Base, imported library, or Implementation, in your service model in the following places:
Execution diagrams describe what is actually done in a BPMN task. Execution diagrams contain an UML activity flow that can be adorned with incoming and outgoing data items.
Concerning data items, you can
Handling of local and persisted variables is described on Adding Variables and Persisting Data.
Also, data types from imported libraries and from the user-defined Implementation may have operations associated that can be used with variables of that type. Data items can go into an operation via parameters, or as a self object.
Refer to
You can also create your own class operations in the Implementation and implement action script on them. See Action Script below for more details.
Mapping diagrams describe how to transform source data to a target. The types of the source and the target are defined via the input resp. output parameters of the mapping operation.
Refer to
You can create your own class operations in the Implementation and implement action script on them. In a script like fashion, you can use the xUML Action Language to implement purposes that are not covered by plain modeling.
You can
Some basic information on the xUML Action Language regarding the syntax scheme, object references, local variables, NULL values, and constructors are listed on Basics of the xUML Action Language.