]
Kris Verlaenen resolved JBRULES-2733.
-------------------------------------
Resolution: Done
Updated in jBPM5
Groupassignment doesn't work in the gwt console
-----------------------------------------------
Key: JBRULES-2733
URL:
https://issues.jboss.org/browse/JBRULES-2733
Project: Drools
Issue Type: Patch
Security Level: Public(Everyone can see)
Components: drools-process
Affects Versions: 5.1.0.FINAL
Reporter: Csaba Vizsnyai
Assignee: Kris Verlaenen
Labels: assignment, group
Attachments: DroolsFlowTaskManagement.patch, drools_gwt_console.patch,
HumanTaskCustomEditor.patch, HumanTaskNodeWrapper.patch, org.drools.eclipse_5.1.0.jar,
org.drools.eclipse_5.1.1.jar
Groupassignment doesn't work in the GWT-console, because handle of the
groupassignment is missing from source. I visited this problem and I found that
GWT-console always call the getTasksAssignedAsPotentialOwner(idRef, "en-UK",
responseHandler) function without groupIds (in DroolsFlowTaskManagement.java).
So I never get task list of the groups.
I fixed this problem. If I start the jboss server with ant (drools installer created the
install directory, where I can use ant for starting system) under install directory, then
my solution will read the roles.properties file and store the user's role in hashmap.
The modified function call is look like:
getTasksAssignedAsPotentialOwner(idRef,
Arrays.asList(groupListMap.get(idRef).split(",")), "en-UK",
responseHandler)
This solution only work with roles.properties file, which contains all user's roles.
I've attached the patch.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: