[
https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug...
]
Maciej Swiderski commented on JBPM-2506:
----------------------------------------
you can leave JBPM-2840, I have already solved that.
But thanks for pointing me to that issue so I will mark it as well when I am done.
I am considering custom type variables as well, as a matter of fact I will make some tests
today to see how difficult will it be.
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: Maciej Swiderski
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