Hi all,
I want to display all the tasks which are assigned to xyz groups.I have used process report for the same and also getting the task lists which are assigned to that xyz group and also getting same task more than 4 times for the same assignee. Can someone suggest on the same?
Thanks in advance.
Discussion posts and replies are publicly visible
this is how grid now
Is your issue is that you expect that task to show only one time? I assume you did not implement any kind of aggregation.
Is that on a DEV environment? Did you check how many active process instances there are?
I have never seen a single task instance to show up more than once in a report.
yes I want to show one task since it is the same task repeated more than 4 times.
local!report: a!queryProcessAnalytics( report: cons!CR_RPT_ACTIVE_TASKS_FOR_USER_REPORT, contextUsers: getdistinctusers( { cons!MAKER_GROUP, cons!CHECKER_GROUP, cons!MANAGER_GROUP } ), query: a!query( logicalExpression: a!queryLogicalExpression( operator: "AND", logicalExpressions: { a!queryLogicalExpression( operator: "OR", filters: { a!queryFilter( field: "c13", operator: "in", value: touniformstring( { cons!ALL_PROCESS_MODEL_NAMES, cons!APP_TXT_ALL_PROCESS_MODEL_NAMES, cons!LA_TXT_ALL_PROCESS_MODEL_NAMES, } ) ) } ),
The trick is not to try to reduce the number of tasks shown in the report, but to understand why the number of tasks in the system is higher than expected. Solve that first and your report will be fine.
Yes Can someone suggest how to get single task instead of multiple task with the same action?
Can you please make sure that there is only a SINGLE active process instance with that given task. Then check the report again.
yes there is one process instance .But when I checked it from the process report by enabling of the process model, it is showing more than 4 tasks.
OK. Can you please also check the number of task instances from process monitoring. Could it be that this task is configured to spawn one instance for each assignee?
Sorry,I didn't get this and the report which I have used is process report ,sorry If am wrong with the question understanding.
Can anyone suggest solution for the above issue?
Stefan is attempting a solution but you need to follow his troubleshooting steps. It is unlikely that you only have 1 task but it is showing 4 times in the report, and more likely that there are 4 active tasks in the system.
To verify how many tasks you actually have in the system, he is suggesting to open your /design environment and locate the process instance using Monitoring -> Process Activity. Right click on the task(s) to see how many are active:
Chris said:It is unlikely that you only have 1 task but it is showing 4 times in the report, and more likely that there are 4 active tasks in the system
I'm wondering whether it might be a process report showing a 4-layer process hierarchy with the "include subprocess data" option enabled? That would show 4 results for the same task instance, IIRC.
Hi Chris,thanks for the suggestion and I have looked into the process monitoring->process Activity it is one like here
Hi I have checked the report as well,I have not enabled the data from subprocess data.
The process report having report context as loggedInUser and I have written this logic for the groups.
Is this causing the issue?
I ran a few tests here and I do see the same when using contextUsers, what this is doing is pulling one task per user, when each of the 4 users have the same task (assigned to their group), it is listing one for each user.
I believe you can resolve by changing the context from users to groups, utilizing contextGroups instead. This will pull one task each for the group(s).
The only catch there will be that once the task is accepted by a user, it will drop from the report since it is no longer assigned to the entire group - which may fit your use case.?
At any rate, try changing:
contextUsers: getdistinctusers( { cons!MAKER_GROUP, cons!CHECKER_GROUP, cons!MANAGER_GROUP } ),
To:
contextGroups: { cons!MAKER_GROUP, cons!CHECKER_GROUP, cons!MANAGER_GROUP },
It looks like they beat you to it (and starting a brand new thread for some reason), and now having a different issue apparently.