Usage Summary Report
Hi all,
is there the possiblity to drill the Pega Usage Summary Report in order to divide the users between the different applications?
Our goal is to have these data divided by application name or access group.
We need to discriminate against the results because we have different applications on the same stack.
Thank you for your support
***Edited by Moderator Marissa to update categories***
Pegasystems Inc.
US
Hello,
The data under the Log-ReportStatistics class does not include the active application or access group, but it does include the active operator id. You can use class joins to add these if you like. Using the Report Definition pyReportUsageByUser as an example:
Under the query tab:
Under the Data Access tab:
The conditions for the OP class join:
Hello,
The data under the Log-ReportStatistics class does not include the active application or access group, but it does include the active operator id. You can use class joins to add these if you like. Using the Report Definition pyReportUsageByUser as an example:
Under the query tab:
Under the Data Access tab:
The conditions for the OP class join:
The conditions for the AG class join:
Each added class join will degrade the performance of the report, so use them wisely. You can always group by access group name instead of application and only use the OP class join with OP.pyAccessGroup as your added grouping column.
Archiva
IT
Hi Trevor,
thank you for your reply.
This report you suggest me to try pyReportUsageByUser is about report execution performed by user.
We want instead to achieve the same result of the report you can run in System -> License -> Usage Summary Report but divided by User or Application or Access Group.
Thank you for your support
Pegasystems Inc.
US
Ah, I see the report now. It appears to be the List View StandardLicenseCompliance.
It looks like the data backing that report is summarized in a way that it loses information on user, application, and access group. However, it appears to be a summary of other available data. Each row in the table for class Log-License-Usage-Hourly describes the number of invocations per user per application. I'm not sure how users are divided between "regular" and "occasional", but you can try building your own report from this data.
Try creating a Report Definition that applies to Log-License-Usage-Hourly with the following columns:
Here are all the columns I'm seeing on that class that you can use to add more detail to the report:
Ah, I see the report now. It appears to be the List View StandardLicenseCompliance.
It looks like the data backing that report is summarized in a way that it loses information on user, application, and access group. However, it appears to be a summary of other available data. Each row in the table for class Log-License-Usage-Hourly describes the number of invocations per user per application. I'm not sure how users are divided between "regular" and "occasional", but you can try building your own report from this data.
Try creating a Report Definition that applies to Log-License-Usage-Hourly with the following columns:
Here are all the columns I'm seeing on that class that you can use to add more detail to the report:
Archiva
IT
Hi Trevor,
thank you again for your reply.
This is exactly where we stopped last week, I created a report with the user usage per hour and invocations.
But we must know how to divide users between full, regular, and so on.
i.e.: more than 50 invocationflowcount per day = full user.
Also, what does invocation mean? Is it a simple click on a menù (for example opening the report harness) or is it something about submitting / approving a case?
Thank you for your collaboration and support
Pegasystems Inc.
US
Hmm, for that I'm afraid you would have to create a Function Alias under Embed-UserFunction that uses custom SQL like so:
case
when sum(pzinvocationcount) > 50 then "full"
when sum(pzinvocationcount) > 20 then "regular"
else "occasional"
end
Then add the function as a column. You can add more cases as needed.