Details
-
Feature Request
-
Resolution: Won't Do
-
L3 - Default
-
None
-
None
-
None
-
None
Description
User Tasks are unique in the sense that they have a strong user case for Expression based Name fields (where the Name of the User Task is defined by a expression and evaluated at runtime for each creation action of the UT). VERY OFTEN modellers will set longer/complex expressions that are concatenating multiple variables, or navigating json, etc. This leads to the Name field to be very message and unreadable.
There should be two "name" fields: A field for the BPMN render, and a field for the User Task Name that is evaluated at runtime. This would allow BPMNs to remain clean and business readable, and allow the execution of the BPMN to still have the context specific user task name
