Question

Scheduling report with different criteria values for every subscriber

Hi All,

I have a requirement where the customer wants the reports built in the system to be scheduled. This can be achieved by the OOTB scheduling report feature. But the values for criteria has differnt values depending upon the user to whom the report is delivered.

For example, the application is built for different markets and there is a report that shows the open cases in the system. There are managers from each one of these markets who wants to get email of the report but only for their market. These managers are not users in the system(business is not okay to have these managers as users in the system).

I could built a custom solution where i can give support users an UI to maintain these user details in a table but there are multiple reports and different reports have different schedules(Like Weekly, Monthly, etc).I would have to capture all these inputs and store in a database table, there after use agents to send the reports as email. This seems to be the only option that i could think of and i feel it making the system more complex and increasing the cost of maintenance.

Is there a better way or anything in PEGA that i am missing that i could use.

Comments

Keep up to date on this post and subscribe to comments

Pega
August 23, 2019 - 5:36pm

There are at least a couple of features you are looking for that do not exist in the OOTB report scheduling:

Last time I checked, scheduled reports cannot be sent to non-users. Scheduled guardrail reports can, but these are done through a different interface.

There is no provision with the scheduled reports to vary a single scheduled report on a per user basis. These are effectively different reports. The only way to do this is to define separate reports for each group of users.

I have a feeling that what you are trying to do may be much easier in BIX.

Pega
October 3, 2019 - 3:00pm

There is another way of varying the criteria of a report per user, and that is to use properties instead of literal values in the filter criteria of the report. You could set the property vales per user, and that would allow you to use a single report definition.