[
http://jira.jboss.com/jira/browse/JBESB-1237?page=comments#action_12384550 ]
Burr Sutter commented on JBESB-1237:
------------------------------------
Yes, if you try to build something that uses the jBPM console for human task management,
then you'll see the issue. There is not checked in test case at this time but it is a
feature that should work.
Note: I believe it is related to -
http://jira.jboss.com/jira/browse/JBESB-1236
bpm_orchestration4 - updates to the variables in the jBPM Admin
Console doesn't work
------------------------------------------------------------------------------------
Key: JBESB-1237
URL:
http://jira.jboss.com/jira/browse/JBESB-1237
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1
Reporter: Jaroslaw Kijanowski
Assigned To: Mark Little
I changed the Customer Status to 65 (in the jbpm console), but when I clicked on
"Save & close", the console showed the previous value:
12:45:50,723 INFO [STDOUT] Platinum Customer - High Priority - Higher discount
12:45:50,724 INFO [STDOUT] Customer Status: 60
12:45:50,724 INFO [STDOUT] Order Total: 64.92
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira