Version 5.6.10

Version No5.6.10
Release Date

 

About this Release

Patch release with minor enhancements and fixes

Modules affected

Data Share, iShare GIS, iShare Maps, Studio, Web Services

Pre-requisites

This release of iShare requires the following to be installed:

  • Windows Server 2012 R2, 2012, 2008 R2 or 2008
  • Internet Information Services (IIS) Versions 8.5, 8.0, 7.5 or 7.0
  • Microsoft .NET Framework V3.5 Service Pack 1 (installed and enabled)

iShare and its modules are installed using the iShare Installer. Any 3rd Party software required by iShare may be installed using the Astun 3rd Party Installer. The AstunPGInstaller will install any Astun scripts on your Data Share database depending upon the selected Install Options.

Studio

  • Stopped the Add Datasource dialogs appearing with a black dialog header in newer versions of Windows.
  • The Map Source BaseMaps lists now scroll vertically and also expand and contract horizontally depending on the available space.
  • Added a 32 character limit to the OGC Layer Name.
  • The Virtual Layer Name in the tree in Studio is now updated correctly when the Display Name is changed in the Layer editor.
  • Studio (& Studio ETL) now checks when starting up to make sure it can write to all of it's configuration files.
  • Studio ETL no longer crashes when loading if the iShareMaps.xml file is missing.
  • The Layer Group name in the tree view is now updated when the text field is updated.

Data Share

  • Check added to ensure valid SQL entered in DataSource

iShare Maps

  • Fix for issue in Classic Layers where Info-clicks would fail due to an XML processing error.
  • The perma-link button now works correctly on mobile devices.

iShare GIS

  • The Map Categories panel will update to correctly show Layers which previously failed to load, then subsequently loaded.
  • Ensure that FeatureServer configuration is rewritten on Web Service startup in addition to whenever related files, such as MapSources, are updated.
  • Fix problem with Layers being written into featureserver.cfg file more than once when the FeatureServer Layer name contained - (dash) characters.
  • Info-clicks should no longer fail due to unescaped characters in the returned JSON.

Web Services

  • The Metadata Abstract, Keyword list and Group title fields are now written correctly into the map file.