You can use a predefined schema which is generic and valid for all Rational DOORS formal modules. Use this predefined schema when you are working with the entire view or with predefined attributes of the view and you do not need to extract user-defined attributes. When user-defined attributes are required, use the Schema Discovery wizard in Document Studio to create a new Rational DOORS schema.
Query | Results | Attributes |
---|---|---|
Module | A single entity, the module specified in the data source configuration. | Name - the module's name |
Module.Attribute | The list of module-level attributes for the module. | Name – the attribute's name |
Module.Discussion | The list of discussions for the module. | - |
Module.Discussion.Attribute | The list of attributes for a discussion. | - |
Module.Discussion.Comment | The list of comments for a discussion. | - |
Module.View | A single result, the view defined for each Rational DOORS data source in the document specification. | Name - the name of the view |
Module.View.Column | The list of column names for the selected view. Note: This
query provides a list without you having to iterate the Module Objects.
The result does not contain column data.
|
Name – the name of the column |
Module.Object | The list of all objects of the specified version of the modules as filtered and sorted by the selected view. | Object Identifier |
Module.Object.Attribute | The list of attributes for the object if this query is in the context of a module.object query. Otherwise, the list of all attributes for all objects in the module. | Name: the attribute's name |
Module.Object.Column | The list of columns in the selected View for the current Object. | Name: the column's name |
Module.Object.Table | A single result (the Rational DOORS table) if the object is a table header. No |
None |
Module.Object.Table.Row | The table's rows. | None |
Module.Object.Table.Row.object | A collection of objects; the current rows' cells. Same attribute list available as for the module.object query. | Object Identifier |
Module.Object.External Link | A collection of external links for the object. | URL: the URL of the external linked entity and other attributes as defined in Rational DOORS |
Module.Object.Link | A list of Rational DOORS links for the object. | - |
Module.Object.Link.Attribute | The attribute list for the link. | - |
Module.Object.Link.Linked Object | The list of linked objects. | - |
Images are extracted from a Rational DOORS module with the attribute's value. You cannot query for the images only.
You can extract OLEs from a Rational DOORS data source. OLEs are always rendered as images in HTML, PDF, and XSL-FO output, because those formats do not support OLEs. For Word output, the OLEs as static images flag, in the metadata section of the document specification controls how OLEs are rendered.
If OLEs as static images is set to TRUE, OLEs are included in the output document as static images.
If OLEs as static images is set to FALSE, a ref folder is generated in the same location as the Word output document.
Action | Result |
---|---|
Select the entire document content and use the Update fields function in Word. | The OLEs are displayed in the document. The document is not self-contained. |
Use the updateFields macro provided by Rational Publishing Engine. | The OLEs are displayed in the document. The document is not self-contained. |
Use the insertOLEs macro provided by Rational Publishing Engine. | The OLEs are displayed in the document. The document is self-contained. |
Use the rpe or insertOLEs macros provided by Rational Publishing Engine. | The OLEs are displayed in the document. The document is self-contained. |
Rational DOORS tables are not extracted automatically; you must explicitly query for them. Although manually adding queries requires extra effort, this manual approach provides fine-grained control over the table format. The table is created only for Rational DOORS objects that start a table.
An example of a query that extracts a table.
Container DOORS 1 $1 Module.Object Paragraph Text Module.Object.Object.Text Table DOORS 1 $2 Module.Object.Table Row DOORS 1 $3 Module.Object.Table.Row Cell DOORS 1 $4 Module.Object.Table.Row.Object Text Module.Object.Table.Row.Object.Object Text
The Module.Object.External Link query retrieves information related to Rational DOORS links. The information consists of the URL of the external entity and a set of other attributes defined for the external link.
Use queries to retrieve information related to Rational DOORS inner links. The inner links create a link between related information. For example, a user requirement to the design features. You can query on object links or linked objects.
To follow Rational DOORS links recursively, set Recursive Level property to a nonzero value in the Properties view. This follows the links from the initial object and from all its linked objects and up to the specified recursive level.
You can define native filters on link queries. Using these filters reduces the number of links to be processed and thus reduces the time to generate the document.
The syntax for filtering all the in links or out links is:
Link direction in|outThe syntax for filtering all the links through a link module is:
Link module link module nameWhere link module name is the full path name of the link module. The filter is case-sensitive.
The following example filters all links from a Link Module 1:
Link module /Demo/Car/Link Module 1The syntax for filtering all links to or from a specified module is:
Link analize module target module name
Where target module name is the full path name of the target module.
The following example filters all links between the analize module and system requirement module:
Link analize module /Demo/Car/System RequirementsFor example, in the native filter tab, type the filter as:
Link direction out.
Link analize module /Demo/Car/System Requirements.
A Rational DOORS data source in Rational Publishing Engine is defined by the module, baseline, view. You cannot query the module's baseline list or the module's list of views Rational DOORS Data Source is defined by the module, baseline, view. Extracting data from more than one module, or baseline, or view can be done one of following ways: