Hi All,
It was brought to my attention that there were a couple of errors in the following blog entry, so I wanted to take the opportunity to highlight the corrections and apologize for it.
Colleen's name
In the post, I have her listed as Colleen Rinehart (which is her maiden name). Her name is Colleen Murray. My apologies Colleen, my only defense is that I still call the part of app designer for editing records Record Editor.
Discontinuation of Subreport Support in Crystal
I'm not sure how I misheard this one, but the official source has chimed in (Colleen herself). Therefore, Support for Subreports in Crystal will NOT be dropped in future releases
Here's some background behind subreports and Crystal.
Prior to PeopleTools 8.48, there was limited subreport support in Crystal (due to a limitation in the ODBC driver that fetched data from PeopleSoft Queries... it was single threaded, meaning only one query can be run per Crystal Report). In PeopleTools 8.48, the initial work to support Crystal Enterprise provided a new mechanism for Crystal to connect to Queries (using the Analytic server under the covers) that allowed multithreaded access to the connection, thus enabling multiple queries to be fetched from simultaneously (thus allowing full subreport support in that release). It's good to hear that customers who leveraged that functionality can continue to do so (and that it's not being affected in upcoming PeopleSoft releases).
We're pleased to announce the release of our new Report Retention Manager product. After we posted the following blog entry, we had several PeopleSoft customers ask us about providing a product that allows them to more easily manage the retention of all their reports, provide a review step prior to distributing reports widely, and tracking signatures of report results.
Why worry about this?
Good question. As delivered, PeopleSoft provides only one option for setting report expiration settings. However, each report is not created equal in terms of value and usage. Therefore, organizations often incur additional cost in terms of processing load of running and re-running expired reports, storage capacity for storing all reports for a long period of time, and usability in either wading through long lists of drills and ad-hoc reports to find the ones they're interested in. This also doesn't consider the fact that you're not easily identifying and keeping your most important regulatory or control documents (unless you're doing it manually).
The Report Retention Manager automates this and allows you to manage it in the ways that make most sense for your organization.
More about the Product
Without covering everything that's already in the product page, this product takes a little different approach than what was covered in the blog. Instead of hooking the PSRF_REPORT_CREATE application message, we decided to leverage application engine. This is because we are supporting much more robust rules, we want to process higher volumes of reports, and we don't want to be dependent on organizations setting up Integration Broker properly. The product allows you to look at the reports that you've already run to help you make the settings. It also has components that allow end-users to participate in setting retention, reviewing and releasing results, and approving their reports.
Interested in learning more?
We've recorded a demo on the product page, but are also willing to do live demos and even let you try it out with a trial version. Feel free to contact us at Info@GreySparling.com.
RSS
Email
