I’d like to talk you out of your approach, but if that fails i’ll help you with the apis you need to invoke…
I’m not sure the size of the active tasks, but classically this will be a very slow performing query. I doubt that your users will be happy with the responsiveness.
Assuming you can’t change this requirement, i’d like to explore the exception that you see.
If the exception is during the rendering phase of the table, then maybe you can do a permissions check prior to rendering each row and filter out the rows that the user doesn’t have permissions to see.
After all, if you do impersonate a super-user, what happens when the end user attempts to click on one of those tasks that they don’t have permission to see? They’ll get some sort of Access Denied error and will be frustrated about what tasks they can and can’t click on.
Regards,
–mark
#MWS-CAF-Task-Engine#webMethods-BPMS#webMethods