Release Notes 4.6
What’s New
This release contains important updates of the base technology "ArcGIS API for JavaScript" to the current version 4.10. In addition, the UI library Vuetify used in map.apps has been updated to a newer version. Both updates bring important improvements and new possibilities (for example completely new UI components in Vuetify, new interfaces in the Esri API). To update these basic technologies, a few adjustments to existing map.apps installations and to custom developments are unavoidable. If you have any further questions, contact con terra support.
This release also includes the possibility to measure distances and areas in 2D maps in map.apps Line 4. In addition, the coordinate tool has been extended by common formats. The available formats can now be configured.
Update Notes
Update of the ArcGIS API for JavaScript to version 4.10 (from 4.8)
The ArcGIS API for JavaScript used by map.apps as technical basis is updated to version 4.10 with this release. With this release, changes in the handling of Cross-Origin Requests and Cross-Origin Resource Sharing (CORS), which were implemented by Esri in version 4.9 of the API, become effective. A detailed description of these changes is given in the article CORS and the ArcGIS API for JavaScript: Changes coming in 4.9 .
Most important changes are:
-
It is now assumed that all requested servers support the CORS mechanism. Previously, a list of supporting servers was maintained or a check if a server supports CORS was made.
-
If CORS is not supported, a proxy is required. The URL of the server can be entered in the parameter proxy.use.rules in this case. The previous workaround over JSONP or JSONP support is removed.
These changes also affect map.apps and some configuration options.
The following settings are no longer effective for apps from version 4.6.0 (however, they still apply to line 3 apps running under a map.apps 4.6 installation).
Adjustments to these options, which are usually made in an application.properties file in the data directory of the map.apps installation, can be removed accordingly.
proxy.cors.enabled=true
proxy.cors.detection=true
proxy.cors.enabledServers=servicesbeta.esri.com,server.organization.com
proxy.use.always=trueThe first three options are omitted as CORS support is now assumed by default.
If the option proxy.use.always was used in previous versions, all servers for which the proxy always has to be used have to be configured with proxy.use.rules.
For apps version 4.6.0 and higher only the following option applies, which corresponds to the former
option proxy.cors.enabledServers with the flag |true:
# List of URLs for backend services for which the transfer of security-critical information with CORS is activated (for example cookies and authorization headers)
proxy.cors.trustedServers=servicesbeta.esri.com,server.organization.comVuetify Update to 1.3.8 (from 1.0.17)
map.apps 4.6 contains an updated version of the vue based UI Library Vuetify. For a complete overview of changes, check the Vuetify release notes from 1.0.18 to 1.3.8 .
The following changes might affect custom developed bundles, themes or style overwritings (for example in app.css).
Changes
-
all vuetify component style classes are now prefixed consistently with v- so you have to add .v- to custom CSS selectors targeting vuetify components. For example the selector
.ctAppRoot .my-custom-bundle .list__tile{}must be changed to.ctAppRoot .my-custom-bundle .v-list__tile{} -
The components
<v-textfield textarea/>, <v-text-field autocomplete/>and<v-select combobox/>have changed to independent components and are replaced by<v-textarea/>, <v-autocomplete/>and<v-combobox/>. A search and replace operation can be used because the properties stay the same. -
The components <v-radio/> and <v-checkbox/> without a color attribute defined gets the "accent" color assigned as fallback. All map.apps UIs have already success color assigned (for example
<v-checkbox color="success"/>). For custom bundles this has to be done too.
Measurement in 2D
In Line 4 apps, measurement is now possible in 2D maps in addition to the existing 3D measurement functions.
The previous bundle measurement now loads the bundles measurement-2d and measurement-3d.
If an app is only intended for operation in 2D or 3D, one of the bundles measurement-2d and measurement-3d can be loaded instead.
Updated default apps
The templates for the so-called default apps have been updated.
If you have not made any customizations, remove the existing templates (files: default-app-*.zip) from the working directory.
The path to this directory is defined using the parameter data.directory.location in the file %TOMCAT%\webapps\mapapps\WEB-INF\classes\custom-application.properties.
At the first start, the new templates are copied there.