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”
While extracting Object heading from DOORS using RPE, RPE will try to retain DOORS heading formatting and styles and the heading is put in a new line. For example, add Object ID or Heading Number before Object Heading in a RPE template as below:
Though you expect the RPE document to show Heading Number and Object Heading in same line, they will be shown in separate lines. Continue reading “Printing DOORS Object Heading without line break”
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”
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.
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”
RPE 2.1 introduces a new feature of importing a MS Word template to build a RPE template. Prototype the document in a Microsoft Word template, which a new user is mostly familiar with, and then import it in RPE Studio to create a RPE template out of it.
Watch the video on how to import word template RPE 2.1.0 – Import Word Template
Continue reading “New in RPE 2.1 – RPE Template by importing a Word Template”
With RPE 2.1 web services, a template can be marked as a snippet when a template is tagged with snippet-XXX. XXX will act as a snippet group name when used from RPE Studio.
When RPE Studio is configured to use 2.1 web services, the Open Template dialog lists the snippets under it’s own group and the palette view again shows the snippets under the snippets group.
Continue reading “Snippets in RPE 2.1 Web Services”