Hotfixes for 4.5.10-4.5.11

UI Design

• When using the AMAP provider in the Maps element, an issue was resolved where individual Markers and the Icons or Images assigned to them were not displayed at the corresponding locations based on the lat and long values bound to the DataSource; instead, the cluster view only functioned when the map was zoomed out.
• In the Maps element (Google Maps and AMAP), a bug has been fixed that caused the selected icon (selectedIcon) to open upon the first click on a Marker, while the details pane opened only upon the second click.
• When the AMAP configuration is selected, an error has been fixed that prevented address information obtained from coordinates selected via Maps—particularly for locations outside of China—from being correctly transferred to the LocationSearch element using Set Value, and that caused the address not to update during successive location selections.
• In the Location Search element (Google Maps and AMAP), location information can now be managed separately via the Latitude, Longitude, and Address fields instead of the Value field.
• When switching from the Shell application to another application via a Micro App, the issue where, if the Starting Screen field in the Micro App was left blank, the role-based Starting Screen settings in the target application were ignored and the user was redirected to the default screen regardless of their role has been resolved.
• A bug has been fixed in the Maps element that prevented external values from being set for the circleRadiusInKm parameter, which in turn prevented the circle from being drawn based on the specified radius and only the points within the circle from being displayed.
• A bug has been fixed in the Maps element where, when AutoCenter was disabled, the center of the circle drawn using circleRadiusInKm would not move to the location the user clicked on the map.
• A bug has been fixed in the Map element where, when clicking a single Pin from the DataSource, not only was the Pin data displayed, but the “position” action—as if clicking an empty area of the map—was also triggered, resulting in an unnecessary backend request.

System Actions

• When managing roles using the Add User To Role and Remove User From Role actions for multiple users within a For Each loop, the bug that caused the operation—which worked without issues in the preview environment—to fail in the production environment has been fixed.