Release notes 4.13.0

Load choice parameters dynamically via map.apps stores

Published parameters of the type choice can now be changed dynamically without republishing the workspace. Choice values can be loaded from a map.apps store configured via the agssearch bundle. This allows fetching values from different data sources like Feature Services, GeoJSON, CSV, etc.

Configuration in map.apps ETL for the published parameter called "City". The attribute "city_name" from the store is used as a display value, "city_id" is used as the actual parameter value:

app.json

"etlToolSettings": {
    "dynamicChoiceParameter": [
        {
            "parameterName": "City",
            "source": "store",
            "storeId": "demostore",
            "valueAttribute": "city_id",
            "displayAttribute": "city_name",
            "limit": 100,
            "sort": "asc",
            "filter": {"state": "NRW"}
        }
    ]
}

The properties "displayAttribute", "limit", "sort" and "filter" are optionally. Filter can be any query using the ComplexQuery syntax.

Related configuration keys and reference pages:

etlToolSettings.dynamicChoiceParameter: Dynamic choice parameters
fmeServerConfig and etlTool: Configuration reference overview
Full configuration example: app.json

The used agssearch configuration:

app.json

"agssearch": {
    "AGSStore": [
        {
            "id": "cities",
            "url": "https://services.arcgis.com/<id>/ArcGIS/rest/services/<layer>/FeatureServer/0",
            "title": "Cities"
        }
    ]
}

Configurable "Number of processes features" in result dialog

The information about number of processed features can now be toggled off for each etl tool if necessary:

app.json

{
    "etlToolSettings": {
        "showProcessedFeatureCount": false
    }
}

ETL Proxy 2.3

This version has introduced security improvements by filtering the FME REST API output. The output is filtered to only allow content that is necessary for map.apps ETL.

When using the "map" mode for user management, the FME REST API v4 is now used. This is necessary for FME Flow 2026 and newer.

Update notes

If you skip several versions during the update, please also follow all update notes of the intervening versions.

4.13.0

ETL Proxy 2.3

This release includeds ETL Proxy with version 2.3. This version requires map.apps ETL 4.13 or higher.

Changelog

4.13.0

Load choice parameters dynamically via map.apps stores.
Fix auto-grow for multiline parameters if window resizes.
Information about number of processed features can now be toggled of
Fix number parameter for new FME versions
Fix published parameter mandatory flag for new FME versions
Fix location updates when automatically opening popups (conflict with zoom to result)

ETL Proxy 2.3

Enhanced security by filtering FME REST API requests to exclude unnecessary information
Switch user map mode to FME REST API v4