The Design Manager team has published an excellent tutorial on how to generate documents from IBM Rational Software Architect Design Manager using Rational Publishing Engine. See here.
RQM 3.0.1 Reportable API used for document generation with RPE is, excepting a few areas, backwards compatible meaning the templates you’ve created for 2.x should work with 3.0.1
For the areas where RQM 3.0.1 is not backwards compatible see Notable Changes in RQM Schema
Another interesting link is RQM API Fields This new API will allow you to build more elegant and efficient RPE templates for RQm document generation.
Update 2012.02.10: a better solution is now available . See Passing arguments to Word macros (2)
Passing arguments to Word macros is very desirable and often necessary. Having parametrized macro allows the macro to be reused in your organisation. Unfortunately there is no direct way to provide arguments to macros when invoking the macros from outside Office, like RPE does.
Continue reading “Passing arguments to Word macros”
When using Type Cast-ing in Rational Publishing Engine a few rules must be followed:
- use Type Cast when and where supported by the data source
- use a correct query structure
Use Type Cast when and where supported
RPE will allow you to CAST any type to any other type without checking if there is a relationship between those types to make the CAST valid. Defining invalid casts won’t break the template or cause run time errors but those queries will not return any results.
Continue reading “Using RPE 1.1.2 Type Cast”
From RPE’s homepage on imb.com one can access the RPE support page. The “Choose your page” menu ( located on the left side of the page for the US version of the site) you can access the technotes and techdocs for RPE. These documents contain information about known RPE issues and quite often workarounds for these problems.
The latest technotes added in the troubleshooting section are:
UPDATE: the example template is available here.
One of the most exciting features of RPE 1.1.2 is the ability to use variables in native filters. Prior to 1.1.2 native filters were hardcoded in the template limiting the applicability of this extremely useful feature.
Best practice: native filters should be used over scripted filters is to be preferred whenever available as it results in the minimum amount of data returned by the provider, reducing the data RPE has to process ( and discard).
Continue reading “What is new in RPE 1.1.2 – Variables in native filters”