Understanding type of the model from DM

While building a cross product template from DNG to Design manager, the derived by attribute links to model diagram from Design Manager. How do you know whether it is a use case diagram or sequence diagram or something else?

If you make a GET request to DM model OSLC  / permanent URL (https://server:9443/dm/models/_Eea40KY8EeWtTLergOJe7g~OLDID__6018453__1) with Accept header as application/rdf+xml, you get OSLC representation of the resource. Looking at RDF/Description/type@resource attribute mentions whether the model is a use case or sequence diagram or etc. Continue reading “Understanding type of the model from DM”

OOTB Templates and Snippets in RPE 2.1

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.

Continue reading “OOTB Templates and Snippets in RPE 2.1”

Share variable across templates

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”

OSLC API and POX Profile simplifies CLM traceability

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.

Use OSLC / Permanent link for configuring the data source URL without having to modify the URL manually or through JavaScript. This simplifies the data source configuration to a great extent as the Permanent / OSLC links are available to the user from the product UI.

Watch video, created by Dragos, on requirement (DNG) to use case design (DM) traceability document generation using Permanent / OSLC links from DNG and DM without having to go through building Rest URL. Continue reading “OSLC API and POX Profile simplifies CLM traceability”

Create Template and Generate Document for JRS report

With continuation to Drag and drop template design in RPE 2.1, generate complex, high performance traceability documents in RPE using Jazz Report Server (JRS) report URL.

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.

jrs-drag-drop

Watch short video on generating document using JRS report URL in RPE Studio.

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”