Unable to assign a modeled DataObject with the same identifier different localized name and description values

Description

Currently the DataObject identifier is used as the key to look up the localized name and description values for a DataObject. Use of the DataObject identifier as the key presents several issues/questions when multiple DataObjects exist in the same process definition.

1) Where should the localized name and description be stored in the BPMN file? Should it store the same localization information on all DataObjects of the same name? Should it store the localization information on the DataObject closest to the root of the process? Where should it be defined when the DataObject is defined in two subprocesses that are siblings of each other?

2) How should the Designer UI handle this limitation? Should it automatically update the localization information for all DataObjects of the same name? Should it only allow the localization information to be modified on the DataObject that defines it?

One approach to resolving these questions/issues might be to change the key used for storing and retrieving the localization values to be based on the id of the process or subprocess element allowing for different localizations to be defined for each DataObject.

Environment

None

Status

Assignee

Joram Barrez

Reporter

Robert Hafner

Labels

None

Components

Affects versions

6.0

Priority

High
Configure