Release Notes 4.3.1
What’s New
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:
"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"
}
}
}
}
]
}
Have a look at all possible app.json configurations: app.json Configuration
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.
Update Notes
4.3.1
Log4J Security Patch
There haven’t been any changes to the map.apps bundles. However, the FME Server Proxy Servlet has been updated and should therefore be updated. You can ignore this relase, if you are not using the Proxy Servlet. For more information visit: https://developernetwork.conterra.de/de/blog/con-terra-technologies-und-log4shell-sicherheitsl%C3%BCcke-cve-2021-44228
Changelog
4.4.1
Changed tool property to set a fixed zoom level if only one feature is drawn (from zoomFactorForIndividualFeatures to scaleForIndividualFeatures) |
4.4.0
Added tool property to set a fixed zoom level if only one feature is drawn (fmeParameterOpts.mapappsParameters.zoomFactorForIndividualFeatures) |
Added tool property to open the first popup of a feature (fmeParameterOpts.mapappsParameters.openPopupForFirstFeature) |
Labeling information can be provided in the FME JSON response to display map labels. |
4.3.0:
Reorganized i18n. It is now easier to overwrite more strings directly in the tool configuration. |
Localization for FME published parameters is now possible via the i18n tool configuration. |
File uploads are now also available for published parameters |
Removed deprecated imports (dojo, ct) |
Removed validation of hidden published parameters |
Replaced select input elements with autocomplete (published parameter and live configuration) |
UI changes |
Switched data download link to button |
Hide steps in wizard if only one page is used by the tool |
Terms of use CSS fix |
Condensed layer checkboxes for map features selection |
Switched drawing library (2d/draw to SketchViewModel) to allow drawing in 3D |
4.2.0:
Internal restructuring of some modules |
Changed implementation of the map features input method to allow for better CRS support |
New map.apps ETL Realtime implementation |
4.1.7:
Fix missing mail adresses in result view |
FME Terminator messages are now used in the result if a workspaces fails. |
4.1.5:
Fixed spelling: mapapp_etl_point → mapapps_etl_point |
More i18n text elements with html support |
Loading animation while gathering FME parameter information |
Live configuration: duplicate tool function |
Tooltips for result table after analyze workspace is used |
Custom iframe content via FME |
4.1.3:
Esri JS Api Bugfix (drawing geometries) |
Removed JavaScriptCaller from demo workspaces |
Improved parameter form validation |
Convert epsg codes to coordinate system names in the analyze result |
4.1.0:
File analyzing workflow: Workspace and map.apps Bundle to analyze files before starting the actual FME Workspace |
Default representation in map.apps is now a FeatureLayer. Therefore, FME Workspaces use a different output template. The previous FME Workspaces still work for backwards compatibility. |
Custom error messages can now be defined in the FME Workspaces for DataStreaming processes. |
Fix: Show error message if a process executes successfully without providing output features. |
Feature selection can now be configured to hide specific layers |
New output method: Download from Result Center |
New selection methods for the input type: "Extent". You can now also use points and lines. |
Maximum selection area can now be calculated for all CRS. |
Maximum number of drawn features can now be configured. |
New geometry published parameter (FME 2020) can be used |
4.0.15:
Counter after layer name is only increased if the title already exists |
Layer name is used as popup title |
4.0.10:
Layers are put in group layers |
Group layers and layer names can be configured from the FME Workspace |
i18n and widgetRole can be set in the Live Configuration |
4.0.9:
Every upload is handled with a new session |
GraphicsLayer for extents does not show up in the TOC |
Fixed zoom to layer for new Esri JS Api |
Fixed handling of allowed file extensions in upload dialog |
4.0.4:
Fixed async mode handling for failed workspaces |
Calculate area for drawn extent is only used for WebMercator and WGS84 |
4.0.3
Removed opt_requesteremail from URL to prevent duplicate emails |
Improved error handling for conenction errors |
4.0.2:
Added more configurable text elements in widget |
Introduced layouting mechanism for widget roles |
4.0.0:
Migration of map.apps ETL to map.apps 4.x (Line 4) |
Combination of individual bundles (db_export, db_import, file_upload, file_download, web_connect) into one bundle (mapapps_etl) |
Completely new live configuration |
Bundles can be configured multiple times per app |
Bundle functionality can be combined based on the use case |
Workspace services and published parameters will be validated when selecting a workspace in the live configuration |
New GUI for all Dialogs |
FME Server connection possible without map.apps proxy |
All unknown published parameter types default to text parameters |
Published parameters for extent and source file can’t be chosen freely anymore. Instead, the default parameters mapapps_etl_extent, mapapps_etl_files have to be used. |
Handling published parameters has been inverted. You do not have to enable all parameters that should be visible to the user. Only parameters that should not be visible have to be hidden. This makes changing workspaces much easier, since new FME parameters are automatically visible in map.apps ETL. |