Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 11 Next »

2.4.11

Pending Release

Enhancements

  • Bookmark and redline manager updates.
    • The dialog boxes for managing the redline and bookmarks have had a tidy up so they more consistent and standard.
  • Redline toolbar has some more tooltips.
    • Some of the drop down menus didn't have any tooltips.
  • Meta tags for client.
    • It's not possible to specify "meta" tags in the client config to have them included in the client html page.
  • Ability to create polygons with holes
    • The redline and editing bundles can now create holes in polygons, using the Alt key when drawing.
  • Client Feedback component available.
    • A new feedback component that allows the user to email information to the administrator is now included.
  • More logging in the Dynamic map engine.
    • The dynamic map engine will now log when there's a failover to a different map engine.
  • host name available as variable in logging.properties file
    • You can reference ${hostname} and ${canonicalhostname} in logging.properties to user the local servers name in logging properties.
  • DMS can use different column as key
    • Previously the document management system could only link via the entity key column value, now a different column can be specified as the source of the identifiers to link.
  • Details panel can be sorted.
    • The configuration of the details panel now allows the results to be sorted.
  • New Redline buffer tool.
    • A new tool for the creating redline buffers has been added.
  • Default entity can be set in spatial identify drill-down.
    • The drill-down spatial identify tools allows for the default entity to be set directly in the tools configuration, either by setting the 'defaultEntity' property or by setting 'isDefault' on one of the sub-entity tags (if they're included).
  • Preloading of map engine metadata.
    • ArcGIS Server, ArcIMS and WMS map engines will now pre-load their metadata from the server as soon as they're created rather than waiting for the first time they're accessed. This can be disabled by setting a 'preload' property to 'false' in the map engine configuration.
  • Icons can be set for entities.
    • Setting an iconCls property for an entity in the defaults section of a client config will replace the default icons in the entity selector combo box and the spatial identify drill-down tool.
  • Sorting of entities.
    • Entities listed in the entity selector combo box will be listed in the order of any <entity> sub-tags. Previously the sub-entities would only filter the list, now they order it also.
  • Enhanced zoom to entity interoperability action.
    • The action now allows for the highlighting of the entities boundary when zoomed to.
  • Implemented an entity list panel.
    • As an alternative to the entity selector combo box.
  • Allow browser locale to be set in url.
    • A url parameter 'locale' can be set to overwrite the browsers specified locate.
  • Added support for LegendURL in WMS.
    • For WMS services that don't support GetLegendGraphic it's now possible to fall back to the layer Legend URL if set.
  • Full support for Neighbour Notification in with Authority integration.
    • Previously the Neighbour Notification support was limited in the types of notification it supports, not it supports more.

Fixes (from 2.4.10.0)

  • Error when updating index.
    • The index builder will complain that it can't update a read-only index.
  • Error when performing an index search.
    • Some characters, []{}(), were causing the index search to fail if the user used one of those characters in the search term.
  • Filtering of numeric fields failing.
    • Filtering numeric field in a data view would generate an exception on the server.
  • 'none' setting on redline fill not working.
    • The fill was being set to white rather than transparent.
  • Redline lines are not selectable when they don't have a stroke style.
    • If you set the stoke for a line to 'none' and unselect it you won't be able to reselect it.
  • Redline fills properties are lost when reselecting a polygon with no fill.
    • If you set the fill for a polygon to 'none' and reselect it after unselecting it then if you turn off the 'none' setting it doesn't restore the previous fill colour or opacity.
  • Dynamic map engine bundle not working.
    • Some client resources required for the dynamic map engine bundle weren't being included in the final .jar file.
  • Scale drop down list not working.
    • The scale selector combo box control was not correctly changing the map scale.
  • TocAction not working when referencing a toc model.
    • The TocAction, which provides a toolbar menu allowing users to toggle map layers, wasn't working when referencing a separate toc model, embedded toc models were working ok.
  • Client side WMS map engines not working.
    • An initialization function for client side WMS map engines was not set properly.
  • Spatial data upload function wasn't working.
    • The list of available colours to display the uploaded file in was not loading.
  • Some fixes for the edit bundle.
    • Key values were being treated as column names rather than column values in some circumstances.
    • Blank id's were not being treated the same as null id's when performing a create operation.
    • Writing geometry collections with only a single geometry were failing on spatial engines that don't support geometry collection even when they could be converted to a single geometry.
  • System datasource not being shutdown correctly.
    • This update ensures that the system datasource is created and destroyed in a more stable manner.
  • Fixed handling of multi-word synonyms in indexes.
    • If a synonym contained more than one word there would not be a match if the source text contained text other than the synonym.
  • Problem with details panel.
    • If the details panel was initially hidden sometimes it would fail when first exposed.
  • Overview map not showing parent extent.
    • The extent of the parent map was not being saved properly so an overview map would not highlight the parent extent.
  • ArcGIS Tiles map server generates incorrect URL.
    • If there are more than 9 levels in the AGS map cache the URL for those levels beyond 9 were incorrect.
  • ArcGIS map engine was assuming incorrect base url.
    • The ArcGIS map engine was assuming that AGS URL's always started with "/arcgis", which isn't the case.
  • Invalid SQL generated when collecting data.
    • The SQL generated for SQL Server would be invalid if the key was included as a parameter with the same name as the column.
  • Resetting input fields in report form wouldn't always clear values.
    • If you used the reset button the fields would appear to be cleared but the values would still be sent to the server.
  • Details panel not allowing multiple instances.
    • You could not add more than one details panel to a client.
  • Check boxes and radio button parameters in BIRT report weren't working.
    • If you hada check boxes or radio buttons as report parameters the client would not display them properly.
  • Generating data with a joined selection table wasn't working.
    • When a joined selection table was used the table wasn't being populated, so the data generation was failing.
  • Spatial identify tool not honouring the default entity.
    • When initially displayed the spatial identify tool should be using the default entity setting to determine which entity to display first.
  • NTLM security filtering not always working.
    • The algorithm used to determine ip range matches had a problem so would sometimes not filter incoming requests properly, e.g. 10.0.11.20 was being treated the same as 10.0.1.120.
  • Toogle toolbar fixes.
    • The toggle toolbar client control would not work if it wasn't embedded within a view.
  • Grid tool fixes.
    • The pan and zoom tools for the grid panel didn't work correctly when used in the spatial drill down view.
  • Fixed CSS tags in geocoding bundle.
    • Some CSS tags in the geocoding bundle were effecting other non-geocode controls.
  • No labels