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:
- Interactive Guides – new designers will be walked through the design process
- 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
- Simplified CLM traceability – with the POX profile you no longer need to manipulate URLs to transform between OSLC and REST API.
- 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
- 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.
I want to welcome the entire RPE team on http://rpeactual.com as authors. Nithya, Kumar, Prasad, Sunil and Akash – welcome and thank you.
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.
Publishing Engine is supported with a number of IBM products as described in the RPE System Requirements. What this means is that we’ve tested the integration and we will support users running into issues with those products.
However RPE is designed to work with any product that meets the following 3 rules:
- the product’s API provides data in XML format
- it’s preferable that the API is Web based but that is not mandatory as long as you can automate the process of obtaining the XML.
- an XML schema exists for the data
- the XSD can be provided by the API or it can be manually created
- RPE can handle the authentication* used to protect the API.
- RPE currently supports Basic authentication, Form based authentication and the Jazz flavour of OAuth
There are further details like rich text, binary file attachments and more but if the above conditions are met RPE should be able to at least produce documents with raw data from your product.
So when you don’t see your product on the support page my advice is to give it a try and if you run into any issues raise them on the RPE DevWorks forum.
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)
The IBM User Education team has released 6 new videos on template design and document generation. Thanks Heidi.
Part 1 of 6: Laying out a simple template with static text (14:49)
Part 2 of 6: Adding a Rational Doors Next Generation schema (11:36)
Part 3 of 6: Connecting to a data source and generating a document (10:23)
Part 4 of 6: Formatting your document (10:42)
Part 5 of 6: Adding headers and footers (11:20)
Part 6 of 6: Troubleshooting and debugging (8:40)