When the clusterFeatureLayer is turned off in the toc and turned on again in a different map section or a different scale the icons don't appear unless the user moves the map section or changes the scale again.

If the visibility of the sublayers of a cluster feature is set to false they still appear as activated in the toc

Definition queries do not work with cluster feature layers

Its not possible to print Cluster Features by using the agsprinting Bundle

There is no legend available when using clusterFeatureLayer

The info popup summarizing a cluster merely contains a "," as of now.

Reproduction:

• Open either sample app 1 or local clusterfeaturelayer project
• Click on cluster

This issue also persists in the map.apps 4.13.0-SNAPSHOT version

Clicking on a cluster to dissolve it and zoom into the map queries underlying features (such as an area-layer) and results in opening a popup-window when queryable features are hit.

When users create own content viewer definitions for the clusterFeatureLayer, these are not taken into account. Instead, a default featureinfo window gets opened.

The visible property has no influence on the ClusterFeatureLayer.

Sample:
"visible": false, has no effect

In der aktuellen Version 3.4.1 wird für Objekte, die vom spiderfying betroffen sind, kein popup angezeigt. Dieser Effekt lässt sich auch in der sample-App nachvollziehen.

Clusterfeaturelayer ignores scale dependent visibility settings on the underlying Feature-Service. As well the clusterlayer is not affected by using the sublayer-properties "minScale" or "maxScale".

Using a clusterfeaturelayer based on a FeatureService results in a wrong presentation on mobile/tablet layout. Just a few features/clusters are displayed while the others just disappear.

Die Version 3.3.1 verursacht in unseren Themenkarten einen Fehler. Der Start der Themenkarte bricht ab.

Wir setzen folgende Versionen ein:
map.apps: 4,11,1
firefox: 91.5.0esr

In der Konsole wird folgender Fehler gelistet:
https://...../mapapps/resources/jsregistry/root/esri/4.18.1/rest/support/Query.js -> Fehler: 404 Not Found