With RPE 2.1.1, an RPE administrator can pause, resume, or cancel the jobs that are running for an unexpectedly long time, or allow a high priority job to go through early in the queue by cancelling some of the low priority jobs.
Find more details on jazz dot net blog https://jazz.net/blog/index.php/2017/01/20/monitoring-and-controlling-document-generation-jobs-in-document-builder/
Out-of-the-box sample assets have been available in the Rational Publishing Engine (RPE) Desktop installation of RPE Document Studio and RPE Launcher for many versions. These sample assets are now included within RPE Document Builder 2.1.1.
Find details at https://jazz.net/blog/index.php/2017/01/19/sample-assets-in-rational-publishing-engine-document-builder/
With Rational Publishing Engine (RPE) 2.1.1, we can render mathematical equations in Word and PDF documents. RPE expects input to be MathML format to be able it to render them. See examples of mathematical equations in MathML format at MathJax. Microsoft Word DOCX format has built-in support for math equations (through MathML) with an equations editor to create and modify equations.
- Syntax coloring: For any programming language, syntax coloring is a must.
- Line marking: The line containing the cursor has a line marking.
Rational Publishing Engine (RPE) 1.3 and above was already capable of configuration-aware document generation. With Collaborative Lifecycle Management (CLM) 6.0.3, we can use configurations of separate components in the project area to achieve re-usability. Rational DOORS Next Generation (RDNG) and Rational Quality Manager (RQM) offer the reusable solution. With RPE 1.3 (yes, 1.3) and above, we can generate documents by selecting the configuration of a component through RPE Launcher (desktop application) and also from RPE Document Builder (Web application) while configuring the template data source.
Find more details at https://jazz.net/blog/index.php/2017/01/16/generate-documents-from-fine-grained-components/
As you might of RPE being available on jazz dot net, we’ve started blogging RPE related topics more on jazz dot net blog. You could search the blog with tags like rpe, document generation, studio, etc.
https://jazz.net/blog/?s=rpe would search jazz dot net blog with tag “rpe”.
If you notice “Data Source Configuration conflict detected” error in problems view upon opening a template in RPE studio, you should fix it immediately to avoid undesired results. The document generation might go through successfully for some case. However, for some cases the document generation could fail as well.
The data source configuration conflict happens when you use a schema normally and then use the same schema to configure the DSC element as in the below screen capture.
How to fix the conflict
Duplicate the conflicting schema either by using “Duplicate Schema” option from the outline. If the duplicate option is not available, go through the normal Add Schema operation to add the schema with a different name again.
Once the schema is duplicated as _resources (or any unique name), use this schema to configure the DSC element and make sure to configure rest of the properties like URL, inherited data source, etc for the DSC element as earlier.
After you fix the issue, re-opening the same template should NOT result in “Data Source Configuration conflict detected” in the problems view.