The example built for New in 1.2.1 – Dynamic Master Pages has been extended to show how to restart the page numbers selectively. In a somewhat related effort in the same context I’ve documented a way to calculate the total number of pages in a Word document. The entire discussion and the examples are available here.
Posted in Design Manager, IBM, Rational, Rational Publishing Engine, Rational Quality Manager, Rational Requirements Composer, Reporting, RRDG, Tips&Tricks
Tagged clm, cross product, Rational Publishing Engine, rrdg, traceability
RPE Master Pages are the means through which template designers control the layout of the document for the Word and PDF output. There is one aspect with design of the master pages that makes them harder to use, their properties are static.
This limitation can be overcome by using multiple master pages and toggling the use of one or the other though a variable, essentially allowing a dynamic master page usage in the template. The fundamental problem with this approach is that it requires duplication of the master pages.
RPE 1.2.1 removes this limitation and allows master pages to be fully dynamic. The outline of the typical process to use dynamic master pages is provided below. Continue reading
As I’ve seen numerous questions on producing documents with RPE from RRC I’m compiling a list of RRC related document generation topics here. Please leave comments with resources that I have missed.
Modules are a relatively new but very interesting feature of Requirements Composer and DOORS Next Generation. Geoffrey Rosenthal has set up an example of using RPE for producing documents from such modules. These templates should not be treated like a gold standard but rather that they outline an approach for doing this.
The templates, document specification and sample outputs are available here: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Rational%20Publishing%20Engine/page/CLM%20Templates
NOTE: you need RRC 4.0.5 and RPE 1.2.1 with the latest hotfixes applied.
For more information on reporting from RRC see https://jazz.net/wiki/bin/view/Main/RRCReportingWiki and for information geared specifically towards RPE/RRDG check https://jazz.net/wiki/bin/view/Main/RRCCreatingModuleRRDGReportsfromtheAPI
More information is available on a number of RRC work items on Jazz.net:
Posted in Reporting, Rational, IBM, Rational Requirements Composer, RRDG, Rational DOORS, Troubleshooting, Tips&Tricks
Tagged rpe, document specification, dng, modules, rrc
RPE Region elements are helpful when you want to update/add information to a certain area in the output, not necessarily in the normal document flow. The RPE Infocenter further defines regions as:
Static elements that are used to display the text from another element in the template. When you generate the output, the content of that element displays where the region element is used in the template.
The key property of the regions is that they are static, meaning that you can only define them at design time. This is enforced by the fact that you can only use simple values for their name.
There are however many interesting scenarios where regions would need to be dynamic (created at runtime) and while you cannot achieve this using regions there is a way of doing this for the Word and PDF outputs thanks to how regions are implemented in RPE.