The installation guide now contains instructions on how to activate user queries.
In release 2.2, the cannedQueries
parameter
of the GET Report Information and
GET Catalog Information APIs is now namedQueries
.
Release 2.1 includes a small upgrade to the Pull Reports REST API,
sort
parameter. If the exported <report>
's
defaultSort
attribute is specified, a sort
parameter with an empty value (e.g. sort=
)
negates the defaultSort
and returns the results unsorted.
This upgrade fixes defect in the Ad Hoc Report Creator in which removing the
final sorted column of a <report>
with a defaultSort
could still
return the results sorted by the default value.
Release 2.1 upgrades the following Export Report REST API
map
format
JavaScript dependencies.
Leaflet upgraded to 1.7
Leaflet Markercluster to 1.5
JQuery to 3.6
If your configuration
decorates the map
format result and depends on these dependencies, please verify your decoration
is compatible with the upgrade.
Release 2.1 upgrades the following Report Creator JavaScript dependencies.
angular-translate upgraded to 2.19
The Pull Reports™ Maven repository
is now available at https://repo2.pullreports.com
and no longer requires authentication to download
the Pull Reports™ JAR.
For example, a 1.7 Gradle repository configuration like this:
repositories { ... maven { url "s3://repo.pullreports.com/maven2" credentials(AwsCredentials) { accessKey 'YourAccessKey' secretKey 'YourSecretKey' } } }
Should be changed to this in 2.0:
repositories { ... maven { url "https://repo2.pullreports.com/maven2" } }
primaryKeyColumns
The geojson
,
map
, and kml
export formats
now require the report's base table to specify
the primaryKeyColumns
attribute. Each format now returns distinct results
based on the primary key columns.
When upgrading from 1.6 to 1.7, it is necessary to specify the primaryKeyColumns
attribute on the base table of each report with <geojson>
or <kml>
configuration
or the corresponding export formats will not activate.
The geojson
,
map
, and kml
export formats
now return features only if the feature geometry is non-null.
This effects the export results when the limit
and offset
parameters are specified.
For example, in Pull Reports™ 1.6, specifying offset=0
and limit=10
for a REST API request in which the first 10 rows of data contained 8 records
with geometry and 2 with null geometry would return a result set of 8 features because the two records
with null geometry would be within the limit.
In Pull Reports™ 1.7, the same request will contain the first 10 records with non-null features exactly
as if the request explicitly filtered to non-null geometries.
1.6 | 1.7 |
---|---|
com.pullreports.model.config.ColumnConfiguration.ColumnConfigurationBuilder | com.pullreports.model.config.ColumnConfiguration.Builder |
com.pullreports.model.config.TableConfiguration.TableConfigurationBuilder | com.pullreports.model.config.TableConfiguration.Builder |
com.pullreports.model.config.ReportConfiguration.ReportConfigurationBuilder | com.pullreports.model.config.ReportConfiguration.Builder |
com.pullreports.model.config.ExportConfiguration.ExportConfigurationBuilder | com.pullreports.model.config.ExportConfiguration.Builder |
com.pullreports.model.config.CannedQueryConfiguration.CannedQueryConfigurationBuilder | com.pullreports.model.config.CannedQueryConfiguration.Builder |
com.pullreports.model.config.JoinColumnsRelationshipConfiguration.JoinColumnsRelationshipConfigurationBuilder | com.pullreports.model.config.JoinColumnsRelationshipConfiguration.Builder |
com.pullreports.model.config.JoinTableRelationshipConfiguration.JoinTableRelationshipConfigurationBuilder | com.pullreports.model.config.JoinTableRelationshipConfiguration.Builder |
1.6 | 1.7 |
---|---|
com.pullreports.export.request.ColumnsTerm | com.pullreports.model.config.ColumnsTerm |
com.pullreports.export.request.SortTerm | com.pullreports.export.request.Sort |
com.pullreports.export.request.SortTermTemplate | com.pullreports.model.config.SortTerm |
1.6 | 1.7 |
---|---|
com.pullreports.model.config.CannedQueryConfiguration.CannedQueryConfigurationBuilder#setSortTermTemplates | com.pullreports.model.config.CannedQueryConfiguration.Builder#setSortTerms |
com.pullreports.model.CannedQuery#getSortTerms | com.pullreports.model.CannedQuery#getSorts |
1.6 | 1.7 |
---|---|
com.pullreports.model.config.PreFilter(ColumnId,Operator,List<Object>) | com.pullreports.model.config.PreFilter(ColumnId,Operator,List<FilterValue>) |
1.6 | 1.7 |
---|---|
com.pullreports.export.request.SortTerm#fromString(String) | com.pullreports.export.request.parsers.SortParameterPreParser#parseSingle(String) |
1.6 | 1.7 |
---|---|
com.pullreports.export.request.ColumnsTerm#fromString(String) | com.pullreports.export.request.parsers.ColumnsParameterPreParser#parse(String) |
The meta.sort
and meta.subqueries
properties
of the REST API json
format are now the
empty Array instead of undefined if they have no value.
The following Java dependencies are upgraded.
org.codehaus.groovy:groovy-all
to 2.5.14
Activate the new jsontree
and
htmltree
export formats by specifying
the new primaryKeyColumns
attribute for all report
tables which have at least one relationship descendant of cardinality many
.
Tree formats are disabled until activated.
creator.url
configuration propertyActivate the new "Creator" navigation link from HTML export formats back to the Report Creator by specifying the creator.url configuration property.
Release 1.6 contains a new pullreports-catalog-1.6.1.xsd
schema file.
Change the xmlns
attribute in each Pull Reports™ XML Catalog file to the new value.
<catalog xmlns="http://www.pullreports.com/catalog-1.6.1"...>
In release 1.6, <column>
and <relationship>
id
values within the same <table>
or <table_ref>
must now be unique.
This rule is required by the new jsontree
export format
which returns column and relationship ids as properties of the JSON Object representation of the table.
The following Java dependencies are upgraded.
org.codehaus.groovy:groovy-all
to 2.4.19
Version 1.5 has no breaking changes nor dependencies upgrades.
Release 1.4 contains a new pullreports-catalog-1.6.0.xsd
schema file.
Change the xmlns
attribute in each Pull Reports™ XML Catalog file to the new value.
<catalog xmlns="http://www.pullreports.com/catalog-1.6.0"...>
Release 1.4 simplifies and improves the JavaScript initialization of the Report Creator. However, these improvements mean that Pull Reports™ 1.3 JavaScript initialization code will not work in 1.4. See the Report Creator Installation for instructions on how to correctly initialize the Pull Reports™ 1.4 creator.
catalogId
and reportId
initialization propertiesRelease 1.4 removes the catalogId
and reportId
Report Creator initialization properties. In order to open the creator to a
specific <report>
, see the section called “Linking to a Component”
or use the new adHocCreatorParams
initialization property.
Release 1.4 upgrades the following Report Creator JavaScript dependencies.
JQuery upgraded to 3.3
The following Java dependencies are upgraded.
org.codehaus.groovy:groovy-all
to 2.4.16
Release 1.3 contains a new pullreports-catalog-1.5.0.xsd
schema file.
Change the xmlns
attribute in each Pull Reports™ XML Catalog file to the new value.
<catalog xmlns="http://www.pullreports.com/catalog-1.5.0"...>
Release 1.3 removes the GET Global Label Value List REST API endpoint because it was redundant with the GET Label Value List endpoint. This removal is unlikely to effect REST API users since the common use of the GET Global Label Value List REST API endpoint was within the Pull Reports™ Report Creator.
<subquery>
provider attributeThe <subquery>
factory
attribute is renamed
to provider
. Additionally, the referenced class must implement
SubqueryProvider.
<export_config>
defaultSort does not permit table pathThe <export_config>
element's defaultSort
attribute no longer permits the base table path within the sort term list.
Only @
prefixed column ids are valid.
Replace a defaultSort
value defined like this:
<export_config defaultSort="/tablePath@columnId"/>
With the @
prefixed column id:
<export_config defaultSort="@columnId"/>
<label_value_query_default>
elementThe <label_value_query>
element now requires a SQL query
within the element body. Use the new <label_value_query_default>
element
to configure a <column>
's label value list
to contain the distinct set of values within the column.
Replace a <label_value_query>
defined like this:
<column id="foo" name="bar" displayName="fooBar"> <label_value_list> <label_value_query/> </label_value_list> </column>
With a <label_value_query_default>
like this:
<column id="foo" name="bar" displayName="fooBar"> <label_value_list> <label_value_query_default/> </label_value_list> </column>
The GET Report Information API's
column.labelValueList
property is now a
boolean instead of a string or a boolean.
This change relates to the removal of the GET Global Label Value List REST API endpoint and is unlikely to effect users.
<relationship>
cardinality default valueThe <relationship>
element's cardinality
attribute now has a default value of many
.
<relationship>
s configured like this:
<relationship cardinality="many">...</relationship>
may now be configured like this:
<relationship>...</relationship>
The following Java dependencies are upgraded.
org.codehaus.groovy:groovy-all
to 2.4.15