With RPE 2.1, a number of new out of the box snippets and templates are shipped for various resources like DNG modules, QM test plan, test cases, RTC work items, Design Manager models, etc. This would allow quick start on document generation without worrying about finding the schema, building the initial template.
Check out RPE_HOME\templates and RPE_HOME\snippets directory for snippets and templates for products like DNG, RQM, RTC, DM, DOORS, etc.
There might be a scenario where you want to share a variable value across templates within a document specification. This is not supported directly using RPE template variable. However this could be achieved using Java system variable.
Note: Once the Java system variable is set, the variable value is available during future document generation until RPE Launcher / Studio is restarted. Hence, make sure to reset such variable value at the beginning of the template to avoid unnecessary results.
During concurrent document generation, if same variable name is used, it could result in inconsistent value. Hence, create a very unique variable name for using across document specifications. You could log (using _sessionLogger) the variable value before using them for printing. Continue reading “Share variable across templates”
Further to OSLC + POXProfile post, RPE 2.1 with CLM 6.0.2 simplifies the data source configuration; especially while configuring dynamic data source for traceability reports.
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.