There is no shortage of reporting options within WorkView. So I wanted to gather some opinions and possible best practices on when to use what reporting/data delivery mechanisms for users.
Environment: On-Prem environment with 24.1.7; primarily web client (want to avoid Unity if possible)
Claim system users process hundreds of objects a day, and these claims can be in various states/statuses. Currently, business groups use filters to retrieve objects in different statuses. However, the web client has proven a bit of a challenge from time to time. Mainly, by default, filters are maxed out at 1000 items by default. It is worth noting too that most of the reports we generate are data grid type data dumps and less of a dashboard. These grids often return all attributes, which can be 30+ columns. While it is common for filters to contain thousands of items at a time, it is uncommon for someone to request "all items" in a query. We often force parameters in filters (User Prompts), but that would not stop someone from setting a Date Range for 5 years and quickly exceeding the 1000 limit.
- WorkView Filters - Filters are base for all other areas, so these look like they will be built regardless
- PROS: Data is all in a centralized place for users as they live and work within the WorkView context;
- CONS: Max limit concerns
- If we increase the WVMaxResults in Web Server web.config from 1000 to x, is there a max number (x) that OnBase supports? Is there guidance around performance hits?
- WorkView Filters - Reportable View
- PROS: Easy data provider in Reporting Dashboards that can be promoted from env to env
- CONS: Still need to create the dashboard one column a time, effectively duplicating effort of building the filter
- Reporting Dashboards - we can create a Module Association from the filter, which then can be used to create a Data Provider in Reporting Dashboards.
- PROS: Allows us to get past the 1000 limit
- CONS: Still need to create the dashboard one column a time, effectively duplicating effort of building the filter
- SQL Data Provider
- PROS: Allows us to fully customize the output in SQL
- CONS: Has to be rebuilt in each environment as attribute numbers will change env to env; Still need to create the dashboard one column a time, effectively duplicating effort of building the filter
- API
- We are early in the stages of investigating API calls for work-items in filters. This would potentially be used if a user wants a data dump and not necessarily looking for a dashboard.
- ???
So, for large data sets, how does your organization report out WorkView items sitting in a variety of different filters? Do you utilize different ones for different types of data returns? And how do you streamline the UX if reports are in different spots (filters vs dashboards)?
