In a previous post, How to embed JRS Charts in RPE Documents, I described the procedure of including JRS charts in RPE documents.
The process is straightforward with one notable exception, providing the credentials for the image. RPE 2.0 and older do not support defining credentials for images so the workaround was to set the template credentials in the document specification.
With RPE 2.0.1 this is resolved as it is now possible to specify credentials for images and included files using the data source inheritance mechanism already used for Dynamic Data Sources.
This is applicable when accessing image and files from any data source but the most immediate use is for accessing JRS images.
Inherited Data Source for Image
Taking an example the JRS example in the aforementioned post you need to set the Inherited Data Configuration property for all JRS charts to be the JRS data source you use to pull the textual data. You can safely remove the credentials set for template in the document specification.
If you only use the chart you need to add a data source so that the user can provide the credentials.
This is how JRS, Insight and RPE fit together to provide reporting capabilities for CLM and more. The JRS and RPE combination offers excellent design usability and runtime performance for any report that involves traceability/data aggregation.
(click to enlarge)
If you have ever had to generate a document that contains Requirements, the Test Cases that validate them and the related work items you’ve most likely ended up using (at least) 3 different data sources and you’ve had to use Java Script to switch between APIs.
Aside from a complex design, the performance of the report wasn’t that great as RPE had to crawl over all the data sources to fetch the required data.
Continue reading “Creating traceability documents with RPE and JRS”
If you have used the JRS 6.0 milestones such as M11 you have probably observed the “Export to Rational Publishing Engine” option in the Export menu.
Export to Rational Publishing Engine allows to:
- make the report data available in XML format for RPE to produce a typical document
- make the report’s graphic representation available as an image to be used in RPE and elsewhere
This adds to RPE the much needed charting capabilities which until now were achieved using external tools like the Google Charts APIs.
Assuming you already have the JRS report ready the steps to embed it’s graphical representation in an RPE document are the following:
Continue reading “How to embed JRS Charts in RPE Documents”
I’m building an internal report that uses JRS to access data aggregated from multiple CLM projects and tools and I’m thrilled by how simple and effective the process compared to accessing the individual point products’ Reportable REST APIs. All the data in one place and you have a visual query builder to select, filter and sort the data that you need. The process is server side so RPE receives only the data it needs in the exact order it needs it.
All it’s left for you to do is to use the data and render it nicely in the document format of your choice. I am documenting the process and I will post my results here.
Selecting the artifact types and the traceability links in the JRS Query Builder
Authored by Rosa Naranjo and Sudhakar Frederick, this workshop is intended to provide insight into the Jazz Reporting Service (JRS) introduced in CLM v5.0 and updated recently in v5.0.2
More here: https://www.ibm.com/developerworks/community/blogs/nfrsblog/entry/Jazz_Reporting_Service_JRS_Workshop?lang=en
As mentioned in previous posts, JRS is a great solution for simplifying and speeding up document generation with RPE so I highly recommend exploring its potential