New in RPE 2.1 – Drag and Drop Template Design

With RPE 2.1, you could drag and drop the web resource URL from the application your are working, like DNG, RQM, RTC, Design Manager (6.0.2 and above only), JRS, onto RPE Studio editor and get a RPE template for the web resource.

drag_n_drop-dng
DNG Module – text requirement
drag_n_drop-resource-confirmation
RPE Studio – resource confirmation

Continue reading “New in RPE 2.1 – Drag and Drop Template Design”

Advertisements

RPE 2.1 – “Multumesc”

I’m happy to announce RPE 2.1, codename Multumesc, has been made generally available today. With this release we continued on the path we started in RPE 2.0 around simplifying the user experience with RPE. While with 2.0 and 2.0.1 we focused on administrators and end users with 2.1 our focus are template designers:

  1. Interactive Guides – new designers will be walked through the design process
  2. Drag&Drop for quick template design– drop your resource URL from the Browser in document studio and RPE will create a starting template for you
  3. Simplified CLM traceability – with the POX profile you no longer need to manipulate URLs to transform between OSLC and REST API.
  4. Word Import – use Word documents as the starting point of your template. RPE will convert the structure and a subset of the formatting into an RPE template
  5. Java Script Reuse – you can now define code modules inside a template and reuse the functions defined there everywhere else in the template.

This and much more is described in https://www.ibm.com/support/knowledgecenter/SS6RHZ_2.1.0/com.ibm.rational.pe.overview.doc/topics/c_whats_new_21.html and will be further discussed here.

The team even put together videos to show some of the new features https://www.youtube.com/playlist?list=PLZGO0qYNSD4UtXl3xXGsL1hhumg0s8m9i

Kudos to the RPE team and to all of you that helped us define and refine these features.

Quickly finding a query in the data source schema

When designing a template you often need to explore a query’s context and all its available attributes. You might need that in order to add another attribute to the output or to work with sibling queries.

Prior to RPE 2.0 your only option is to manually expand one node of the schema at a time until you reached your query. With RPE 2.0.1 you have a far simpler option: right click on the element holding your query and select “Go to schema” from the “Search” sub menu.

gotoschema

RPE will focus the appropriate data source schema in the Schema View and ensure the query is expanded and visible in the schema tree.

gotoschema_result

 

Printing history information for QM data

qm_history_feed
Test Plan history fragment

IBM Quality Manager provides an API for accessing the history of individual resources as well as the history  of archived/deleted resources. You can read about the supported resources types and more on https://jazz.net/wiki/bin/view/Main/RqmApi#historyUrl

Continue reading “Printing history information for QM data”

RPE team at Interconnect 2016

The RPE team will be represented at Interconnect 2016 by the RPE Product Manager Jared Pulham, the RPE Dev Lead Nithya Rajagopalan and myself. We will be joining the Inner Circle’s QM, CM and RM tracks on Sunday, present sessions and roam the Solution Expo the remainder of the week.

With the Session Preview Tool you can get a sneak peak at the sessions dedicated to Publishing Engine, Reporting and any other topics of interest.

We are looking forward to seeing you there. Please contact any of us via email if you’d like to meet with us and chat about your reporting experience.

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.