Page Comparison

...

• ArcGIS REST Map Engine legend update
  • The ArcGIS REST Map Engine now supports aliases when displaying the legend in a BIRT report
• ArcGIS REST Map Engine update
  • You can now specify a referer property in the map engine config have that value sent as a referer header to ArcGIS when making requests from the Weave server
• Support dump update
  • A support dump now includes the style.css file is one exists
• Optimization of spatial filter
  • Some spatial filters generated inefficient SQL clauses when filtering on a list of values, in certain cases this has be changed to use an IN clause which should be quicker
• Optimization of user attribute spatial filters
  • A filter applied to a spatial mapping that used user attributes would generate inefficient SQL when there were lots of values for the user attribute, this has been changed to use an IN clause
• Grid panel update
  • Now if a column is hidden in a grid panel the column will not be included in the data is exported to a different format
• Cascading form parameter enhancement
  • Cascade parameters now support adding a label and having the fields grouped within that label
• Removed obsolete warning
  • A warning about REST map engines has been removed because it's no longer applicable and was causing confusion
• Layer access logging enhancement
  • Individual layer accesses are recorded to log layer access counts
• Handling of groups in ArcGIS updated
  • You can now specify if Weave honors or ignores groups from ArcGIS. Setting ignoregroups to false (true is the default) for a AGS map engine will instruct Weave to include a layer entry for the group when it loads the information from ArcGIS, allowing you to turn on and off groups directly. If you having issues with AGS map toc models not doing the right thing try changing this value for the map engine.
• Selection transfer API update
  • The selection transfer config no longer requires a userid column in the table it works with
• BIRT report CRS update
  • It's now possible to set the CRS that a map component should use directly in a BIRT report UI. Previously this had to be added manually.
• New spatial validation API
  • A new API to check spatial object has been added, this will be used down the track to check config entries to ensure that tables, columns, etc that are referenced in a config file are valid when the config is processed, rather than waiting until the items is used.\
• Improved formatting of numeric values
  • Some database columns were including additional trailing zeros when displayed in a grid panel, this update should tidy up these values
• Improved internal search API
  • The API used to perform a search has been enhanced to support additional ways to provide the values for a multi-valued input field
• Updater enhancement
  • When running the updater on a Weave instance that uses Subversion for revision control the updater will add and remove changed files for you
• Kerberos authentication enhancement
  • There's now the ability to remove the realm from user names when a user is authenticated via a Kerberos server
• REST API update
  • The REST API is more relaxed about the JSON it accepts, no longer requiring attribute names to be quoted
• Security code update
  • Some old security related code has been removed to tidy up the security handling
• Security handler update
  • Security handler now have more control over the information they expose to the rest of the system, making it easier to customize the user experience based on the underlying security provider
• WMS server update
  • The Weave WMS server now handles non-integral DPI values
• Third party module update
  • There are now proper .msi installers for any Weave integration components that need to be installed on client PC's
• Excel export enhancement
  • URL's in Excel files are now clickable links
• Security update
  • A major update to the security code to tidy up and enhance the supported security options

...