Release Notes 4.16

Live configuration is no longer being developed and will be removed in an upcoming release. Instead, use the app-editor to configure apps. You can already hide the live configuration for your users by setting the configuration option manager.config.editor.showLiveConfigButton to false.

App and app template synchronization has been deprecated since version 4.8 and will be removed in version 4.15. Use domain-bundles instead.

The allowedWorkflows:["create"] configuration option in the editing bundle will be removed soon. Use allowedWorkflows:["create-features"] instead.

The omnisearch bundle is no longer developed. Use the search-ui bundle instead.

The resultcenter and selection-resultcenter bundles are no longer developed. Use the result-ui bundle instead.

Support for module.exports in JavaScript files will be removed soon. Use the ECMAScript keywords export or export default instead.

To simplify a future migration from AMD to another module system, JavaScript files should be written as ECMAScript modules only, if possible, and then transpiled.

Support for cancel in return values of store queries (QueryResult) will be removed soon. The goal is to simplify the store-api.Store interface. Please use a AbortController , described in Usage of an AsyncStore to cancel pending queries.

const aborter = new AbortController();
store.query({name: "Test"}, { signal: aborter.signal })
    .then((resultItems)=>{
     ...
    }, (e)=>{
      if (e.name === "AbortError"){
          // aborted
      }
})
// trigger abort
aborter.abort();

The class ct/mapping/store/MapServerLayerStore is replaced by a new class LayerStore in the agssearch bundle. The LayerStore class is stored with an ArcGIS FeatureLayer instance and is therefore consistent with the map content. The agssearch bundle now creates LayerStore instances by default in the AGSStoreFactory class and the AutoStoreRegistration and AGSStore configuration options. The old behavior can be restored during the transition phase with the legacyImplementation option.

The use of data-template-window and data-template-window-events in template files will not be supported in the future. Instead, make window definitions in manifest.json files.

The following classes will be removed in one of the next releases: