Service Pack 3 of version 7.1, includes bug fixes and improvements to enhance the user experience and GIS capability of the application, as well as general bug fixes.

Supported Third Party Applications and Versions

Supported Platforms and Third Party Applications for Version 7.1 SP3

New Features and Enhancements

  • N/A

Dropped/Replaced Features

  • N/A

Bug Fixes and Other Improvements

  • Added: Map Filter as a parameter that can used when creating or updating Jasper Map Reports
  • Added: The ability to export a map as an image file (png format)
  • Added: Validation in the naming of maps, layers and folders to prevent entry of unsupported special characters:  / # % ; . ? \
  • Added: When a layer is added to a map, the layer is turned on by default
  • Fixed: Issue where the display order of feature offsets is reversed, now a positive offset value offsets a feature to the right and a negative value offsets the feature to the left
  • Fixed: Issue where the display order of a layers legend is displayed in reverse order on the map, now the display order of the legend is as specified in the layer panel
  • Fixed: Issue where an 'Others' category in the Range styling tab could not be excluded from a set of range definitions, now the 'Others' category cFixedan be excluded or included
  • Fixed: Issue where in certain instances, an error message is displayed when a user selects to show a jasper report in an html format
  • Fixed: Issue where the year value is not displayed in the event comparison reports, in the Roads & Highways interface
  • Added: A reason field (reason for a given invalid record) to the Invalid Reports generated from the Roads & Highways interface
  • Fixed: Issue where the google maps usage was not properly reported to Google, when utilizing an enterprise license for Google Maps
  • Fixed: Issue where in certain instances, a refresh of the interface was required to insert a similar record using the insert like functionality, after inserting and saving a record

Known Issues, Limitations & Restrictions

  • The new GIS Interface is currently designed for datasets with SRID of 4326, so customer schemas with a different SRID would need to be re-projected to 4326 in order for map layers to be created from the dataset.
  • Inserting a location or inventory item from a map is not functional when using Firefox as your web browser. To work around this limitation, use the other supported web browsers: IE 11, Chrome or Safari
  • When select to print a map as an image (png file) whilst using a Firefox as your web browser, the file is downloaded as map.png.pdf. You would have to manually edit out '.pdf' from the file name after the download to be able to open/utilize the file
  • While working on the GIS Interface and performing tasks that does not generate a request to the server (such as styling a map), your user session may expire as a result. The configured session expiration warnings will be displayed when this occurs or your session may timeout and a session expiration notification displayed, if a warning is not configured
  • Map filter value does not get pre-populated in the Jasper report print template, even though the parameter is specified for display in the template
  • Map filter value cannot be defined or edited for a map with a specified area of interest. To work around the definition limitation, the map filter should be defined before the AOI is set
  • When labels are enabled and defined for a map/layer, the selection is not retained with the resulting map when the map is saved
  • An area of interest filter and the crop setting are lost for a map when the screen is refreshed or across more than one user session
  • A map's layer style settings become null and uneditable, when an applied filter is partially applicable or not applicable to the defined styling attribute values for the map
  • For certain schemas, when a map is bound to a grid view and a record is selected from the grid for display on the map, the map is not updated with the records location or information
  • This release was not tested with a customer schema that has polygon based GEOMs in their data set
  • The loading and display of maps and associated styles in IE 11 is not as performant as Chrome, Firefox and Safari
  • In the GIS Interface, when you select to print a displayed map and then select a print template, the displayed map zooms out rather than staying at the previously set zoom level and map extent