Changes in reports in the version 1.6

Build 1501 on 14/Nov/2017  This topic last edited on: 5/Aug/2014, at 14:13

Enabled the GNQuery in GN4 reports: now the report can use a XPath expression to query the objects data. Added to the ReportOptions object the XQuery attribute where to specify the XPath string used to perform the query in GN4 database.

For example:

<ReportOptions 

xmlns="http://www.teradp.com/schemas/GN4/1/ReportOptions.xsd"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

NavOptions="None"

XQuery="gn4:page[gn4:editionRef/nav:refObject/gn4:edition/@date &gt; $fromDate and gn4:editionRef/nav:refObject/gn4:edition/@date &lt; $toDate]">

. . .

The 'XQuery' attribute replaces the old 'Conditions' element (where the SearchConditions were configured): that is, if the 'XQuery' attribute is set then the 'Conditions' element is ignored.

However, the 'Conditions' element is yet supported for backward compatibility.

So, the ReportOptions, used to generate the reports in GN4 clients, can now specify the database query using:

XPath (new 'XQuery' attribute) or SearchConditions (old 'Conditions' element).

SearchObjectUI ('SearchObjectUI' element, used to display search control in Report main tab). If the 'SearchObjectUI' element is set, then the XQuery attribute and the Conditions element are ignored in client reports.