Accessing the docgen configuration information in JavaScript

RPE 1.2.1 introduced three new Internal Variables:

  • _sessionInfo
  • _sessionLogger
  • _sessionUtils

The _sessionLogger gives you access to the RPE Log system so that any debug/troubleshooting messages will reach the log file as well.

The _sessionUtils exposes utility functions for JavaScript. At the time of writing this ( RPE 1.2.1.1) _sessionUtils only exposes the tidyXHTML function.

Out of the 3 the most interesting is the _sessionInfo variable which gives access to the document generation configuration properties and more.

Continue reading “Accessing the docgen configuration information in JavaScript”

Advertisements

RPE with DOORS 9.6 64 bit

When RPE  Launcher/Studio load and run DOORS templates one of the first actions performed is to read the path of the DOORS executable on the current machine. That action is required to populate this value when creating a new docspec or to validate that the value stored in the document specification is correct.

RPE finds this information by reading registry values, specifically HKLM\SOFTWARE\Telelogic\DOORS\9.x\InstallationDirectory and  HKLM\SOFTWARE\Telelogic\DOORS\9.x\Config\Data. This works well for all DOORS 32 bit versions but not for the 64 bit ones. This failure is perceived as a slowness of RPE to load docspecs: RPE 1.2.1.1 Launcher slow loading Specifications

NOTE: the document generation is not affected by this problem, this behavior is limited exclusively to loading and configuring a docspec.

Continue reading “RPE with DOORS 9.6 64 bit”

Sorting on children properties

RPE supports sorting on properties of the current query and not its children. With RPE’s 1.2.1 introduction of Special Attributes it is now possible to sort even on properties of child queries. Andy Lapping does a great job explaining how to do this here: http://merlinscave.info/Merlins_Cave/Tips_n_Tricks/Entries/2014/1/17_RPE_-_Sorting_reported_elements_by_tag.html

How to move queries?

While designing templates it is sometimes needed to move a query. There are many reasons to do that and a concrete example would be to refactor templates as described in Best practices for table design

RPE Document Studio enables to move queries in a non destructive way as long as the new query location does not invalidate any of the queries in the template.

Continue reading “How to move queries?”

Speeding up the loading and configuration process of DOORS templates

When you use RPE templates that use DOORS as a data source, RPE tries to identify the location of the DOORS installation as well as the default database to connect to.

RPE finds these values by querying the registry. Depending on the DOORS version used and the bitness of your OS this process can take a good few seconds.  This happens every time you load an RPE template or when you use the DOORS Configuration Dialog.

With RPE 1.2.0.1 and newer you can completely circumvent this process and gain significant time with every  document generation if you “tell” RPE these values instead of having it search them every time.

Continue reading “Speeding up the loading and configuration process of DOORS templates”