The download links for this content is now generated automatically to allow for the rapid release of these updates without having to come back and manually update this page.
...
- JavaScript minimisation fix
- Fixed an issue where a regular expression at the end of a line of Javascript JavaScript would cause minimisation to generate incorrect code
- Redline fix
- Loading a redline would not offer a warning that the contents were about to be replaced if it was configured to do so
- Transparency slider fix
- The new transparency slider wouldn't work when used with a non-expandable group
- A couple of small fixes for the Google panels
- Checking if the StreetView panel has started correctly and stopped limiting of new Google layers types
- MapTip date/time fixes
- Handling of dates and times in map tips has been fixed
- Measure polyline fix
- If minKm was used the conversion wasn't always done correcty correctly in the measure polyline tool
- Grid highlight fix
- Setting an
xandycoordinate in a data definition to have the grid row highlight a different point on the map when a row was clicked wouldn't work unless acrswas also included. See Client Views Data for more info.
- Setting an
- ToC filter fix
- Setting collapseOnClear to false would cause ToC entries that should be hidden to be shown after the ToC filter was cleared
- SwitchView action fix
- The SwitchView action only worked on tab and card layouts, now it should work on accordion layouts also
- ToC load fix
- Fixed an issue with exclusive groups when loading a ToC model (from a bookmark for example)
- Entity combo fix
- Fixed issue when entity combo had been narrowed down to set of entities but the default entity wasn't one of them
- URL link fix
- Sometimes clicking on a link would display a warning about not being able to open the link while it did actually open the link (if this still happens set openWithScript to true)
- Radio button fix
- Some forms wouldn't package up radio button values correctly when sending them to the server
- GeoJSON encoding fix
- Generated GeoJSON wasn't including the "properties" attribute if there weren't any properties, but according to the spec it should always be included
- JSON encoding fix
- The logic for encoding objects into JSON has changed slightly to produce more consistent results
- Non-spatial editing fix
- Invalid input forms were still allowed to be submitted
- Non-spatial editing fix
- Fixed handling of text fields with "MAX" size.
- Index building fix
- Sometimes after building an index it wasn't replacing the index content with the newly generated content
- Legend genarator fix
- Legend images for layers with multiple geometry type is handled better
- ArcGIS REST API fixes
- Various fixes for working with ArcGIS REST map engines
- ArcGIS SOAP API fixes
- Some improvements when working with projections on ArcGIS SOAP map engines
- Fixed BIRT maps
- The reported scale would be wrong if the DPI was not the default for a map component
- Fixed BIRT scale rounding issue
- Fixed some rounding issues resulting in scales like 2500.00000000000001
- Spatial edit fix
- Fixed an issue when the filter that was generated to select the record to update
- Spatial edit fix
- Dates are now stored using GTMGMT
- Spatial edit fix
- Tidied up handling of default values when submitting an update
- Search API fix
- The search API was using the target entity instead of the source entity when performing an entity intersection search
- Zip'n'ship fix
- Fixed issue when exporting records with more than one geometry column
- Zip'n'ship MIF fix
- Fixed issue generating MIF file with mixed geometry
- IE POST fix
- Fix for zero length POST issue is also applied to PUT requests
- Fixed "Jersey not ready" error
- This issue would sometimes stop the server from starting up properly removing access to a number of functions including the admin UI
- ToC expand/collapse fix
- Expanding a ToC model, using the expand button, would result in non-expandable groups being expanded
- OpenLayers scale rounding issue
- When OpenLayers calculates scales based on a list of provided resolutions JavaScript rounding issues would sometimes result in scales like 2500.00000000000001 which would cause issues elsewhere