Features described on this page

Consistent BPMN Element Naming through Field Definitions and Field Objects SERVER | DATA CENTER

|Since 3.25.0-ENTERPRISE|

Misunderstandings often occur within teams due to differences in BPMN element naming conventions. Likewise, there can be uncertainty about the correct names for process participants or databases during modeling, as well as difficulty in identifying existing ones within the organization. Furthermore, establishing consistent names for BPMN elements can be a challenge. These challenges are common, but a solution is available through the combination of Managed Data Fields and the BPMN Modeler Enterprise Plugin, which provides remedies for these common issues.

Configuration

When creating a mapping between a BPMN Element Type and Field Definition for a particular Confluence Space as documented here, it will no longer be possible to fill in the "Name" and "Description" attributes with free text of the selected BPMN Element Type in your process models residing in the configured space. Instead, when modeling, users can choose between field objects of the mapped field definition. The name and description of the field object will then be mapped to the name and description of the BPMN Element.

For the BPMN Element Type Lane, we can now choose one of the field objects IT, Marketing, HR, or Business Department of the field definition “Department”. After selecting the field object “Business Department” its name and description are mapped to BPMN Element’s name and description respectively. This ensures that modelers consistently utilize the predefined department names rather than inventing their own, while also ensuring they have a comprehensive overview of all departments.