CartoVista Viewer 5.6.4 (HTML)

IMPROVEMENTS

  1. Improved user experience on desktop touch screen.
  2. Map initial extent is now entirely visible at map loading when a tile layer is included in the map (scale now rounds up to higher tile zoom level).
  3. Zooming in or out using two fingers pinch and infoPanTool does not trigger an info event anymore.
  4. Two fingers pinch now zooms to the center of the line between the two fingers.
  5. Two finger tap now zooms out only.

BUG FIXES

  1. Fixed problems when loading resources from filesystem (e.g. mobile app).
  2. Fixed issue with data cell not on the proper row in the data view when data was published in two different data table and features ids were not in the same order.
  3. Fixed problem in print layout when map contained two tile layers.
  4. Fixed problem in print layout with broken image url. If image fails to load, it removes html component associated to it.

TECHNICAL NOTES (SDK)

  1. Constants for multi checkbox filters now exposed on MapSettings.js.

CartoVista Publisher 5.6.4

IMPROVEMENTS

  1. Changed CloudVista url to https.
  2. WMS Layer now uses the wms layer style for rendering the map.
  3. Allow right-click and copy in the WMS tab.

BUG FIXES

  1. FGDB File Geodatabase locate now works.
  2. Theme set category (folder) can now be renamed.
  3. License dialog now works correctly in evaluation mode.
  4. Deactivating a license and activating a new license now works properly.
  5. Collection of server layers under the portal node is now exactly the same as the list in the web interface.
  6. Fixed issue with File GeoDatabase (FGDB).
  7. Two new Viewer Configuration options added to set the maximum number of values for multi checkbox filters.
  8. Fixed problem with file extension under data table properties.
  9. Data column added on a server layer now usable in the publisher.

CartoVIsta Server 5.6.4 (HTML)

BUG FIXES

  1. Count report is now correct on all files.
  2. Custom logo now displayed on login page in Firefox, IE, and Edge.
  3. Update server layer now correctly empties the db vector cache.
  4. Warning message now displayed when user tries to update server layer by one with different column name(s).