[#CAM-6713] Filter created with Java API initially not working

[CAM-6713] Filter created with Java API initially not working Created: 06/Sep/16
Updated:
09/Sep/16
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Open
camunda BPM
tasklist
7.5.2
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Bug Report
Casper Biever
Unresolved
None
Not Specified
None
Priority:
Assignee:
Votes:
L3 - Default
Unassigned
0
Not Specified
Not Specified
Description
Consider following code snippet:
Filter filter = filterService.newTaskFilter("Test");
TaskQuery query = taskService.createTaskQuery();
query.taskAssignee("${currentUser()}")
filter.setQuery(query);
The filter appears, but no tasks are shown. If however an administrator opens the edit dialog and
saves, tasks are being shown.
Other filters created using the API, but without EL, work as expected.
Comments
Comment by Matthijs Burke [ 06/Sep/16 ]
Hi Casper,
Thanks for contacting us with this issue.
A short question: was this issue meant to be raised in our support project?
The difference between the Support project and the Camunda BPM project is that when raising
issues in the Camunda BPM project, they are not subject to the agreed SLAs and they can be
viewed by all users. In contrast, issues raised in the Support project can only be seen by your
authorized support contacts and us. You can find more information in our documentation.
If you intended to raise a support issue, please let us know and we'll move this issue to the
support project.
Thank you and best regards,
Mat
Comment by Casper Biever [ 06/Sep/16 ]
Guten Tag Matthijs,
Gemeint war das Camunda BPM Projekt, also ausserhalb vom SLA.
Mit freundlichen Grüssen
Casper
Comment by Casper Biever [ 09/Sep/16 ]
Hätte:
query.taskAssigneeExpression("${currentUser()}")
sein sollen.
Ticket kann geschlossen werden.
Generated at Thu Apr 06 13:18:24 CEST 2017 using JIRA 6.4.6#64021sha1:33e5b454af4594f54560ac233c30a6e00459507e.