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 126.96.36.199 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”
IBM Rational has a Youtube channel hosting demos and tutorials for Rational tools: IBM Rational User Education – YouTube
RPE is also covered and below are listed some recent related videos:
My colleague Nithya Rajagopalan has prepared a video of setting up and using the RPE Remote Services for scheduled document generation.
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
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?”
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 188.8.131.52 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”
With RPE there is usually more than one way to achieve a goal and tables make no exception. However not all methods are equal and some designs are better/faster/more maintainable than others.
This article documents the guidelines the RPE team recommends for designing RPE tables, with a focus on the Word and PDF outputs.
Continue reading “Best practices for table design in RPE”