Further Configurations

The following chapter describes additional configurations necessary for different use cases. Have a look at all possible configurations in the app.json.

i18n for Published Parameters

You can now overwrite Published Parameters prompts for each tool via the tool configurations i18n settings. This means you can use different prompts for different languages:

app.json

"mapapps_etl": {

      "MapappsETLTools": [
       {
          "fmeServerConfig": {...},
          "fmeTool": {...},
          "fmeParameterOpts": {...}
          "id": "mapapps_tool_id",

           // optional: specify i18n values for each tool individually if necessary.
          "i18n": {
            "en": {
                // optional: localize/overwrite prompt of Published Parameters. The key is the parameter name in FME
                "fme_published_parameter": {
                    "opt_requesteremail": "Enter Mail Address"
                }
            },
            "de": {
                // optional: localize/overwrite prompt of Published Parameters. The key is the parameter name in FME
                "fme_published_parameter": {
                    "opt_requesteremail": "E-Mail Adresse eingeben"
                }
            }
          }
        }
    ]
}

File uploads via Published Parameters

Previously, there was only one file upload available via the input configuration that required a Published Parameter mapapps_etl_files. It’s now also possible to create more file uploads that are shown in the Published Parameter step as parameters. This feature can be used if users should provide (optional) additional files, or if users want to provide multiple files that have to be distinguishable for the FME workspace.

Labeling information

You can now provide labeling information for layers created by map.apps ETL via the FME workspace to map.apps. Include the necessary configuration in the JSON output of the workspace as described in Workspace Templates.

See .\fme_templates\building_blocks\esriJson_CustomTransformer.fmw for a custom transformer to include the labeling information.

Automatically open popups

Popups can automatically be opened after features drawn via map.apps ETL. Apply the configuration using the parameters automaticallyOpenPopup and numberOfAllowedPopupsForMultipleFeatures to each tool individually:

app.json

"mapapps_etl": {
      "MapappsETLTools": [{
          "fmeServerConfig": {...},
          "fmeTool": {...},
          "fmeParameterOpts": {
                "mapappsParameters": {
                    // optional: opens a popup for the first feature
                    "automaticallyOpenPopup": true,
                    // optional: if more than one feature is available, specify how many popups should be loaded (defaults to 1).
                    "numberOfAllowedPopupsForMultipleFeatures": 5
                }
            }
      }]
}

Configurable zoom level for individual features

You can configure the zoom level of a map after a feature is drawn in the tool configuration. This is only possible if only a single feature is drawn.

app.json

"mapapps_etl": {
      "MapappsETLTools": [{
          "fmeServerConfig": {...},
          "fmeTool": {...},
          "fmeParameterOpts": {
                "mapappsParameters": {
                    // optional: set a map scale. Only applies, if only one feature is supposed to be displayed on the map. A value of 10000 means a map scale of 1:10000
                    "scaleForIndividualFeatures": 10000,
                }
            }
      }]
}

Accept terms of use before starting an ETL tool

ETL tools can be configured to only start, if the terms of use are accepted. The following text elements can be overridden using the i18n configuration: termsOfUse, termsOfUseInfoText

app.json

"mapapps_etl": {
      "MapappsETLTools": [{
          "fmeServerConfig": {...},
          "fmeTool": {...},
          "fmeParameterOpts": {
                "acceptTermsOfUse": true
            }
      }]
}