]
Sebastian Schneider commented on JBPM-2416:
-------------------------------------------
How is this issue related to JBPM-2417? I don't see the connection. Could anyone
clarify? Thanks.
introduce task audit capabilities
---------------------------------
Key: JBPM-2416
URL:
https://jira.jboss.org/jira/browse/JBPM-2416
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.x
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: