Community
Participate
Working Groups
When setting the properties of a user task there are discrepancies on the parameters. when I click on the task itself, I'm prompted with the human task editor that has an input field called "Name". This same field in the Properties view is called "Taskname". Also on the Properties view the field "Name" is the one that when changed, changes the description on the bpmn workitem. These fields should all be just one. Kris Verlaenen added a comment - 22/Aug/11 7:36 AM There is a difference between name and TaskName. Name is just the name of that specific node and is shown in the diagram. The TaskName however is like the type of task. For example, in the evaluation example that is included by default, all tasks have the TaskName "Performance Evaluation" (as they all are the same type of task, someone has to fill in details about the performance of a person), but they have a different name (e.g. HR evaluation, self evaluation). It is true however that the popup dialog when double-clicking the human task shows a property "Name" which should actually be "TaskName". Nelson Pereira added a comment - 22/Aug/11 9:13 AM Hi Kris, Thanks for that explanation, but in that case, what is the business function of having have both, name and taskname? Kris Verlaenen added a comment - 22/Aug/11 11:54 AM Think of this in combination with task forms. A task name defines the type of task and thus the form that is shown to the user. So task nodes that share the same task name also share the same task form (except from the dynamic part of the form of course, that is instantiated at runtime based on the available data). This allows you to easily share task forms across nodes or even processes. The name attribute is just the name that is shown in the node, and is not used anywhere else. Note that it is probably important to have this "name" attribute on top of the "TaskName" attribute as described above to avoid all tasks that are of the same type also having to have the same name. The evaluation example for example has names like "HR Evaluation", "Self-Evaluation", etc. as name but the TaskName of those tasks are all "Performance Evaluation" (so they share the same performance evaluation form). Hope this makes sense?
Fixed
