Yes I need it too, and also for the process.
Actually I use the description tag for process and task since version 3.2.1 like this :
and I parse the description of GraphElement with a regular expression :
I also think some sort of properties would be helpful.
I also would like to see properties for variables. I have added a few extras to my forms.xml, to set certain securities and other info for my variables. This way, my framework knows which variables are allowed to be seen, and by who.
<forms> <form task="Request For New Employee" form="form.requestForNewEmployee.jsp" order="1"> <variable name="IsReplacement" displayName="Is Replacement" /> <variable name="EmployeeReplaced" displayName="Employee Replaced" /> <variable name="JobDescription" displayName="Job Description" /> <variable name="CostCentre" displayName="Cost Centre" /> <variable name="ExpectedCost" displayName="Expected Cost" securityGroup="Payroll" securityRoleInGroup="Team Leader"/> <variable name="Motivation" displayName="Motivation" /> </form> </forms>
As you can see the Expected Cost variable, for example, would not be displayed to any user except the Team Leader of the Payroll group.
I would prefer this sort of functionality to be added on the processdefinition.xml, perhaps as properties, as was mentioned above.
@All: You can try to develop your own taskcontroller which supports all of your individual needs. Then you can add anything you want to the processdefinition
Ok, but if we all develop task controllers (and extend Task class, etc.) we all do the work many times instead of it being done once and available to all.
But I can see maybe more discussion is needed to see what the common needs are.
Perhaps someone can take a crack at what Ronald suggested and, if it works out well, offer it as a prototype for the new feature.
Or perhaps we could create a download area where we can share solutions in toolkit form.
Sorry, I did not mean all separately. If you all agree on co-developing an extended taskcontroller, we can post that on the wiki.... for everyone to use. If it proves to be a real need for many more people, we can think of including it in the core