[
https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2506:
-------------------------------------------
When declaring variables already in the process definition it is possible to specify
whether or not they should be taken into account for the history. So the same
configuration should be possible via the API for variables which are created during
run-time.
btw: Why is the history disabled by default? What are the reasons against enabled by
default?
add variable declarations
-------------------------
Key: JBPM-2506
URL:
https://jira.jboss.org/jira/browse/JBPM-2506
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0
Reporter: Hauke Rabe
Assignee: Tom Baeyens
Priority: Optional
Fix For: jBPM 4.4
Original Estimate: 4 hours
Remaining Estimate: 4 hours
When variable declarations, also the ability to trace the history can be exposed and
documented.
add following element to process the group activity
<variable name="" [type=""] [history=""] />
type should refer to the types defined in jbpm.variable.types.xml
history = {enabled, disabled} (disabled is the default)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira