More traceability – following links from RQM

Continuing the series of articles on producing traceability documents from IBM CLM I will describe today how to follow links from RQM.

If you examine the RQM schema for testcase for example you will notice entries for workitems and requirements.

qm_schema
Click on the image to enlarge it.

With these properties it should be fairly straightforward to build a template that retrieves CM and RM data associated with the QM artefacts.

However if you run your report on a test case feed URL like https://giediprime:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/JKE Banking (Quality Management)/testcase?abbreviate=false there is no requirement or work item data in the document. And if you examine the XML returned by RQM for this request you will see that information is not present there either.

So what is the problem? The answer is in the Rational Quality Manager Reportable REST API Documentation.  For efficiency reasons RQM does not return the link information by default. If you want to create traceability documents you’ll have to explicitly ask for the link information using the calmlinks argument in the request URL.

qm_calm_links
Which means that the right URL to use in the RPE docspec will look like this https://giediprime:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/JKE Banking (Quality Management)/testcase?abbreviate=false&calmlinks=true

Note that the URLs to RTC and DNG are OSLC links and you will need to convert them to Reportable REST API URLs before fetching RM and CCM data.

Examples showing how to follow links from individual testcase or from a test case feed are available in the RPE DevWorks – Cross Domains Templates Wiki.

Advertisements

CLM 6.0

More details here, https://jazz.net/blog/index.php/2015/06/26/collaborative-lifecycle-mangagement-6-0-in-a-nutshell/ and here:

For document generation, CLM 6.0 ships with RRDG 1.3 iFix 003 which is significant as it allows to use all the latest in template design.

Generate PowerPoint ready documents with RPE

RPE does not generate PowerPoint natively. However Word can export a document in PowerPoint and PowerPoint can load Word documents as presentations. This means that you can get the CLM/DOORS 9/Rhapsody data in PowerPoint format via Microsoft Word with RPE.

output_powerpoint
A PowerPoint presentation from a Word document

Continue reading “Generate PowerPoint ready documents with RPE”

How to embed JRS Charts in RPE Documents

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:

  1. make the report data available in XML format for RPE to produce a typical document
  2. 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.

JRS_Chart_RPE

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”

Using the JRS Query Builder for selecting the document data

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.

query_builder
Selecting the artifact types and the traceability links in the JRS Query Builder

High level comparison between RPE Launcher and the 2.0 Web UI

With the introduction of RPE Web Services 2.0 ( new Web UI) a valid question is how does the new UI compare in terms of capabilities to classic Launcher.

A comparison of the most significant capabilities of the two is listed below including my recommendation for when RPE Launcher is better to use.

NOTE: In terms of supported data sources and output formats the two are identical. 

Capability
Launcher
Web Services
2.0
Generate document yes yes
Publish Wizard yes yes
Schedule document yes(1) yes
Built-in asset store yes(1) yes
Built-in document store no yes
Design and configure report yes yes
Report review no yes
Portable reports yes no
Rename data sources
and variables
no yes
Hide/Fixate data sources
and variables
no yes
Use templates, reports and
style-sheets from any location
 yes no
Authentication no yes
Dashboard Integration no yes
DOORS 9 Plug-in yes no
Dynamically referenced
templates in reports
yes no
64 bit support yes yes
Continue reading “High level comparison between RPE Launcher and the 2.0 Web UI”

Jazz Reporting Services workshop

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