Features described on this page
| Excerpt | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Consistent BPMN Element Naming through Field Definitions and Field Objects
| Status | ||||
|---|---|---|---|---|
|
|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
Navigate to the Settings for Space Admins, e.g. by using the sidebar while being in the space in question and following Apps → BPMN Modeler Enterprise. Subsequently, navigate to "Managed Data Fields Mapping." There, you can create a mapping between a BPMN element type and a field definition using the “Add map” button. Select the respective BPMN element type for which you want to disable free text labeling. Currently, available options include Pool, Lane, Data Store, and Data Object. Then select the desired field definition.
...