I am using a!queryProcessAnalytics for showing 'User tasks report' in grid

@Tom Ryan I guess it's all about context in the queryProcessAnalytics(). If you take a quick look at the https://forum.appian.com/suite/help/7.11/System_Functions.html#a!queryProcessAnalytics.28.29, you can see that a query can just have pagingInfo and all the remaining arguments aren't necessary.

Ideally when an Appian report object has context (such as Processes per Process Model has Process Model as context, Tasks Per Processes has Process as context), the same kind of context should be sent as an argument while invoking queryProcessAnalytics. Still we can pass an other context which is different from the context of report object, but queryProcessAnalytics doesn't throws any exception and safely skips it which thereby doesn't make any difference in the results we obtain.

@Tom Ryan I guess it's all about context in the queryProcessAnalytics(). If you take a quick look at the https://forum.appian.com/suite/help/7.11/System_Functions.html#a!queryProcessAnalytics.28.29, you can see that a query can just have pagingInfo and all the remaining arguments aren't necessary.

Ideally when an Appian report object has context (such as Processes per Process Model has Process Model as context, Tasks Per Processes has Process as context), the same kind of context should be sent as an argument while invoking queryProcessAnalytics. Still we can pass an other context which is different from the context of report object, but queryProcessAnalytics doesn't throws any exception and safely skips it which thereby doesn't make any difference in the results we obtain.