-
Task
-
Resolution: Unresolved
-
Major
-
None
task history and all history in general should be configurable in a declarative manner.
on a task definition, a process or in the process-engine context, it should get a boolean audit attribute. if audit for a task is enabled, all variable updates for that will be recorded.
for now, it is sufficient if the audit attribute has potential values
{enabled,disabled}. In the future, the value for the audit attribute could get more fine grained specification based on individual (commaseparated list of) use cases.
it must be possible to combine audit with the isHistoryEnabled on the variable declaration.
- is related to
-
JBPM-2855 Task comment must have a userId to enable discussion between members of a group participating in a task
- Open
-
JBPM-2417 allow for programmatic way to specify authentication through service api
- Open
-
JBPM-2568 review history based on user feedback
- Open
- relates to
-
JBPM-2415 add declaration of process variables
- Resolved