Honestly, I felt that Queue Reports VBO is doing so many operations using code stages like excel formulas, excel templates, pivot tables, etc etc. making it a more complex solution just for the reporting. Also, it is a Queue Reporting right so we do not need any data inside the queue, I'm not sure why we are looking inside the data of a queue and why the nested collection is required here.
So instead of going with that VBO, I have seen people prefer "Get Report Data Action from Default WorkQueue VBO itself which will be a more simple, easy, and more efficient solution. (Considering that WQ data is gonna be huge in most cases)
Also, this is the reason why I was checking if we can replicate the same Control Room-"Export Current View as Report" option in some utility itself to get the CSV exports easily. As we already have this option in Control Room so there must be some SQL query or something running in the backend. This will also streamline the format of reports when generated manually OR generated by automation. -
Thread Reference My thought is to keep it very simple and straightforward and then later we can add more new functions to enrich the Reporting Utility in Blue prism.
These are just my thoughts on this from the design and general requirement perspective. Please share your thoughts as well so that we all can bring a great reporting feature to BP.
------------------------------
If I was of assistance, please vote for it to be the "Best Answer".
Thanks & Regards,
Tejaskumar Darji
Sr. Consultant-Technical Lead
------------------------------