Extracting data by using native filters
Before you begin
Review the Reportable Rest v1 document for more information about defining Reportable REST v1 services requirements.
About this task
Native filters are supported by Reportable REST data sources, which enable the filtering, sorting, and selective support of properties. The native filter requests a set of data from the data source, and then filters and refines the data for output from a Rational Publishing Engine template. You are not required to create filters in the product the data came from unless you would like to test the filters for accuracy, but you can create filters exclusively for use in Rational Publishing Engine templates from within Rational Publishing Engine.
In previous releases of Rational Publishing Engine, you could only define filters that were static. You had to know what the filters were when you designed the template and they could not be changed at run time.
Procedure
Data sources that support the Reportable Rest v1 syntax
Design Management
IBM Rational ClearCase
IBM Rational ClearQuest
IBM Rational DOORS Next Generation
IBM Rational Quality Manager
IBM Rational RequisitePro
Example
fields=Project/Requirements/PRRequirement[Stability = 'High']/(Stability|FullTag|Priority|Status)
IBM Rational Rhapsody
IBM Rational Team Concert
Example
[projectArea/name="JKESample"]/*
https://server:port/ccm/rpt/repository/workitem?fields=workitem/workItem[projectArea/name="JKESample"]/(@href|summary)
Requirements Management application
Data sources that support the Reportable Rest v2 syntax
About this task
- Requests are made to a data source only when required. For example, you can use conditions to have an element display in the output only when it contains data. The condition on a container element might be variable == "true". If this condition is not met and no data meets the variable condition, no requests are made to the data source.
- You can calculate native filters before making the request. The native filter is calculated at the point where the query is encountered and uses the variable values at that point. So you can perform calculations in the template, which impacts the native filters.
IBM Rational ClearQuest
Example
cq:Product{cq:Product="${productName}")
cq:Product{cq:Product="Rational Publishing Engine")
Data sources that support the proprietary API syntax
IBM Rational DOORS
Example
Attribute 'Object Text' contains 'Documentation' (case sensitive)
- Open a Rational DOORS Module, and then click .
- Create the filter syntax:
- Select the Attributes tab.
- For Attribute, select Object Text.
- For Condition, select Contains.
- For Value, enter a specific value to filter on. For example, to filter only those objects that contain the word Documentation in the Object Text attribute, enter: Documentation
- Click Add. In the Advanced options section, the rule syntax is created.
- Click Description and copy the full description. You now have the Rational DOORS filter, which is a DXL script.
- Select the template element that contains the query that is to be filtered.
- In the Properties tab, expand Data.
- In the Filter field, click the ellipsis. The Filter Editor window opens.
- In the Native Filter tab, paste the Rational DOORS filter (DXL script) and click OK.

