A common usage pattern in the Camunda tasklist is to the use the User Task documentation element to provide a description of what the task is about for the end user.
BPMN spec shows that 1 or more documentation elements can be supported on all bpmn elements:
8.2.2 Documentation
All BPMN elements that inherit from the BaseElement will have the capability, through the Documentation element, to have one (1) or more text descriptions of that element.
The Documentation element inherits the attributes and model associations of BaseElement (see Table 8.5). Table 8.6 presents the additional attributes of the Documentation element.
Has anyone done something like support more than one documentation element instance on a User Task and providing some sort of extension that “types” the instances so you can do something such as:
- business configuration documentation
- user action documentation
- system/admin
- etc.
The point being that we could start to generate “Documentation” micro-sites for a BPMN file based on the configuration and documentation elements, But when we use the user task documentation element for user docs that are displayed on the tasklist, it starts to become problematic. :).
Thoughts?
@camunda
Thanks!