BPMN Modeler – Release Notes – April 11, 2019

New and Improved Features:

• Introducing the Operation Library:
  • Allows to defined Interfaces and Operations that can be used in service tasks.
  • Interface and Operation definition is based on the Open API/Swagger standard.
  • The Operation Library let you directly import your Open API/Swagger files.
  • Defined operations can be linked to Service Tasks in the diagram.
• Internal data inputs and outputs of activities and events can now be defined by accessing the contextual menu of an element and selecting Attributes -> Data Inputs/Data Outputs. Please consider the following special cases:
  • If a Service Task is connected to an operation, the Data Inputs/Outputs can’t be modified and are coming from the operation definition.
  • If a Rule Task is connected to a DMN model, the Data Inputs/Outputs can’t be modified and are coming from the DMN model definition at connection time.
• Data transformation can now be defined for Data Associations by accessing the contextual menu of an activity or event and selecting Attributes -> Data Input/Output Mapping. The data mapping re-uses the familiar DMN boxed expression such as Literal, Boxed Context, Relation and List. Please note that the available context for the mapping is dictated by the presence of Data Associations (incoming or outgoing).
• Data Object/Input/Output are now created with the Text type by default.
• Data Inputs/Outputs are now displayed in the scope.

Bug fixes:

• Fixed an issue that sometime would cause Choreography Task magnets to be displayed at the wrong location.