RPE Studio 2.1 could now access assets from RPE 2.1 Document Builder (Web Services). The templates, snippets and stylesheets from 2.1 web services are available in Studio 2.1. The “Load From Library” in Open Template dialog lists templates and snippets, which could be view, modified and saved back to the web app.
RPE template is generated on the fly and available for modification and document generation for the JRS report. The document specification is configured with Rest URL of the selected JRS report along with credentials for accessing the data source, allowing to single click document generation.
Watch short video on generating document using JRS report URL in RPE Studio.
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.
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.
I’ve received this from Nancy Rundlet and I’d like to share it here. I’m glad to see that at least one of the sessions will cover document generation with RPE.
We are very pleased to announce the DOORS and DOORS Next Generation Enlightenment Series for April through June 2016.
Each month, the DOORS Next Generation webinars will be held on the 1st Thursday, and DOORS 9.x will be on the 3rd Thursday at 11:00 AM ET (8:00 AM PT). Details with abstracts and registration links for each of the webinars are in the attached Word Document or you can register by clicking on the registration link below.
In the last week it so happened that I spent a lot of time working with RQM. I’ve created a number of templates in the process and I want to share the most interesting three here.
The templates were created and tested using CLM 5.0.2 and are available on the RPE Developer Works Wiki here.
How to print basic test plan information
Prints basic information about the test plan and its test cases. The test cases are retrieved using the efficient QM native filtering which allows RPE to gets all the test cases associated with the test plan in a single request.
Note that the test plan data source has metadata information that allows the end user to select the test plan from a list rather than typing it.
How do dynamically get state labels for test plans, test cases etc
Prints the test plans and for each their state. The state labels are read from RQM instead of being inferred from the state identifier.
How to print the requirements from a requirement collection associated with a test plan
Prints basic information about a test plan and its linked requirements. The requirements are read from from the requirements collection associated with the testplan.
When starting with DNG and document generation or when deploying new reports on the server the RRDG log is an invaluable resource for troubleshooting problems on the RRDG server. As expected the log provides detailed information on errors and additional information including performance data.
All the DNG logs can be access at https://server:9443/rm/logs. The log for document generation is rrdg.log which is located towards the end of the list.
By default the RRDG log is set on WARN level which means only warnings and errors will be logged. This is the recommended setting for most production servers but if you need to troubleshoot document generation you should increase the level and set it to INFO.