Overview

Version 7.3.3 includes enhancements and bug fixes to the AgileAssets asset management application platform.

Supported Third Party Applications and Versions

Supported Platforms/Third Party Applications

New Features and Enhancements

Work Manager

• Support for spatial assets or assets not on an LRS network
• Support for version compatibility check and restriction between the mobile app and a corresponding web app
• Support for configuring the number of decimal places allowed for entry on day cards
• Support for editing comments on a work order before and after syncing with the web app

Maintenance Manager

• Support for assets with multiple location segments
• Support for the definition of a pay period type to be used with Work Manager for back dating work orders
• Configurable option 'AccomplishmentsByLocation', to create or not create accomplishment day cards for a work order, with the 'Make Day Cards' and 'Completely Remake Day Cards' actions

Dropped/Replaced Features

• Support for ESRI ArcGIS Enterprise (Server) and Roads & Highways 10.4.1 is deprecated

Other Improvements and Bug Fixes

• Added: Support for ESRI Roads & Highways 10.6.1
• Fixed: Issue in Work Manager, where existing day cards for equipment or labor needed to be manually deselected, when adding new day cards for a crew on a day with same resources
• Fixed: Issue in Maintenance Manager, where an error is displayed for a record year with more than 11 records in the Baseline/Dynamic Plan screen
• Fixed: Issue in Maintenance Manager, where location editing of a selected segment is initiated when attempt to add a location to a work order
• Fixed: Issue in GIS Explorer, where a layer remains turned on, when added to a group with visibility turned off
• Fixed: Issue in GIS Explorer, where a layer added to a group and saved as a map, does not remain in the group when the map is reopened
• Fixed: Issue in GIS Explorer, where features matching a map filter defined with an IN operator for an integer parameter, are not displayed on the map
• Fixed: Issue in GIS Explorer with IE 11, where a data window bound with a map does not display the corresponding map locations of features in the data window

 Known Issues, Limitations, and Restrictions

• The new GIS Explorer like all web mapping applications requires datasets in the geographic coordinate system (EPSG:4326), so customer schemas with data stored in a different coordinate system would need to be transformed in order for map layers to be created from the dataset. See the section on re-projecting geometries in the Implementation Guide
• Inserting a location or inventory item from a map is not functional when using Firefox as your web browser. To work around this limitation, use the other supported web browsers: IE 11, Chrome or Safari
• When you select to print a map as an image (png file) whilst using Firefox as your web browser, the file is downloaded as map.png.pdf. You would have to manually edit out the '.pdf' extension from the file name, after the file has been downloaded, to be able to open/use the file
• When you define a map print template of size 34x44 or larger, an error is returned since the size of the generated map image always times before a PDF for printing is generated
• While working on the GIS Interface and performing tasks that does not generate a request to the server (such as styling a map), your user session may expire as a result. The configured session expiration warnings will be displayed when this occurs or your session may timeout and a session expiration notification displayed, if a warning is not configured
• Map filter value does not get pre-populated in the Jasper report print template, even though the parameter is specified for display in the template
• Map filter value cannot be defined or edited for a map with a specified area of interest. To work around the definition limitation, the map filter should be defined before the AOI is set
• A map's layer style settings become null and un-editable, when an applied filter is partially applicable or not applicable to the defined styling attribute values for the map
• On a map bound to a data window, some items when selected on the map aren't highlighted in the data window because they aren't present there (In a data window, items can be Access Regulated), but on the map all inventory items are displayed
• The loading and display of maps and associated styles in IE 11 is not as performant as Chrome, Firefox and Safari
• In the Roads & Highways interface, routes with curves are not handled properly by the ESRI FDGB API. A workaround is to have the agency densify the routes to turn the curves into line strings
• The HTML5 based copy/paste functionality has limitations on the number of rows that can be copied to a browsers clipboard
  • IE 11 - 4000 rows
  • Edge - 4000 rows
  • Chrome - 400 rows
  • Firefox - 1000 rows
  • IE or Edge on a Surface Tablet - 15 rows
• When you select to copy rows from a data window, data from hidden columns on the window are also copied to the clipboard
• The spinner indicating that a layer is loading in the GIS Explorer, continues to spin after selecting to remove a previous loading layer by using either the new map or remove layer option
• When zoomed in at the 0.6km/0.4m level before selecting to print a map, the basemap is not rendered on the resulting printed map
• Hebrew and other languages with special characters are not rendered properly on the properties panel of GIS Explorer
• GIS Explorer does not display the contents of the screen for a right to left language setting
• The owner of a GIS catalog folder no longer has access to the catalog, when the folder is shared by a GIS admin with administrative units that the owner of the folder does not belong to
• A map built from an image service is not rendered in the printed document (PDF or PNG) when select to print the map
• An image layer is not displayed on the map when change the basemap from the 'None' option to any other basemap option
• A map comprised of layers from multiple sources including an image service, does not display the layers in the correct z-order when the layers are re-ordered
• For some monitor resolutions, opening the messages dialog while the GIS Explorer window is open results in the messages dialog to be partially hidden
• In FDC, when enter an incorrect password twice and then enter the correct password afterwards, a message indicating an incorrect reCAPTCHA answer is displayed
• When the same editable layer is added to GIS Explorer so there are more than one active, the features on the layer cannot be dragged for an edit
• The undo/redo of edits retains the actions performed even the associated layer has been removed
• When add a new editable layer to a map with in-progress edits, the undo and redo options are temporarily disabled. Performing an edit re-enables undo/redo and previous edits can be undone or redone
• When a user a user enters an incorrect username or password in the Work Manager mobile app, an incorrect message 'Unable to connect to server' is displayed
• In Microsoft Edge, some admin units in the Admin Units drop-down on the inspection teams creation dialog, appear as actionable links
• Setting some columns as fixed in a data window is not functional in IE 11
• Setting of columns as fixed in a data window is not supported in right to left language displays, such as for Hebrew or Arabic, i.e. only the left most columns can be fixed
• GIS Explorer does not display a basemap nor the basemap selection dialog, when using Microsoft Edge web browser. However, basemaps function as expected with IE 11, Chrome and Firefox web browsers

• The supplied CORS filter for Tomcat will not work on Tomcat version 8.5.2. The Tomcat documentation (https://tomcat.apache.org/tomcat-8.5-doc/config/filter.html) implies the below extra setting will address the issue:

  <init-param>

   <param-name>cors.support.credentials</param-name>

  <param-value>true</param-value>

  </init-param>

• There is an issue in ESRI ArcGIS Enterprise 10.6.1, that prevents the publishing of services for Oracle tables or views with a geometry column owner of MDSYS. When the ESRI issue is addressed, we will test and ensure that the functionality has been restored