An Slashdot article titled “Is reporting relevant?” caught my attention yesterday. My interest dropped rapidly after I started reading since it was not about “document generation” type of reporting, even though it does mention documents. The article also provoked James Moody to react on his blog: http://james.moody.name/simplethings/2014/09/25/is-reporting-still-relevant/
The original article and the discussion around it show just how overloaded the term “reporting” is. James explains this very well so I want to focus on the “document” part. The term “document” is less overloaded compared to “report” but it is far from unequivocal.
In some cases “document” accurately describe the nature and intention ( to document a certain state at a moment in time) of user with regards to the data as in the case of requirements documents, compliance document etc.
In other cases the “document” describes only the packaging form (Word, PDF, Excel) as in the case of traffic reports, trend reports etc. Here the data would be more naturally presented and better used in a dynamic environment where the report’s parameters can be changed and connections can be explored ( drill down).
My point here is not if reporting is still relevant or not but to remark the importance of properly identifying the “report/document” type and choosing the right tool for the job. The scenarios above overlap and most “reporting” tools support the overlap to various degrees but for the best results it is important to identify and use the right reporting tool.
The RPE Introduction for Beginners presentation I have mentioned here has been reorganized and is provided on devWorks with additional information and product links: Introduction to IBM Rational Publishing Engine for beginners
Massimo Caprinali has put together a guide on printing RQM grid sections with RPE. The guide and required scripts are available on the RPE devWorks Wiki.
The GEBS Reporting webinars series focused on Document Generation and RPE continues on Thu, September the 23rd with Episode 4 – Introducing Reporting Central . For more details and registration please visit http://eepurl.com/0Mut9
If you have installed MS Internet Explorer 11 security update KB2977629 you may experience RPE Launcher/Studio crashing after you close the results dialog. You may notice this also after using the Welcome Screen or the Data preview features.
This impacts products built on Eclipse 3.7-4.2.2. See http://www-01.ibm.com/support/docview.wss?uid=swg21684445
At this time the only way to resolve this problem while keeping all the RPE functionality is to uninstall the KB2977629 security update.
We keep getting the following message from you, the RPE users: the RPE documentation/enablement is not sufficient.
This is a constant message and one of the reasons for starting this blog and other initiatives the RPE UA and development team are undertaking, such as preparing videos for the new features in our next RPE releases.
There are many things to write about RPE and the new/less known features of RPE are the obvious targets for the next articles. However what the development team might think is less known is not necessarily what end user does so for a more relevant content we need your direct feedback: for what features of RPE would you like to see more enablement material?
Your requests will have as result one or more of the following: posts on this blog, enhancements in the official RPE documentation, requests to the other Rational teams.
I’m looking forward for your answers here as comments so we can discuss them and see what would be of greater interest.
One more week left of my summer vacation. I will be back on Sep 08 with fresh RPE articles.
PS: this message would have made a lot more sense last week. :)