Skip to main content

Open ideas have been reviewed by our Product Management and are open for commenting and voting.

Filter by idea status

Filter by product area

1111 Ideas

davisblack
Contributor
davisblackContributor

FME Flow User Role Security EnhancementsOpen

The following improvements to Role Based Security would be useful:1.Increased Granularity for Job Viewing and Job Management PermissionsI need the ability to allow users to see specific other user’s jobs and logs rather than all jobs and logs. We use different service accounts for different enterprise projects and currently I am having to share all jobs/logs with users so they can monitor their processes. Since not all groups need to see each other’s jobs this is not the best solution. (Thank you Safe for new search options in 2019 as they slightly help with this issue.)Likewise, in the current Role system being able to view all jobs requires job management permissions which let users cancel jobs in the queue or terminate running jobs. This puts me in a difficult position regarding how we implement SOX compliance. It is preferred users be locked out from managing running production processes. If the ability to view all logs but not manage jobs was made available that would be a move in a positive direction. If the option to say kill queued jobs but not running jobs was an option that may also be useful.2. Additional Options on Database ConnectionsHaving a Read option alongside the Full Control option for database connections would be excellent. I am seeing issues when I grant users access to connections without giving them full control over a connection. Since we have many processes using the same named database connection it is not ideal to grant users management access since one incorrect change by any user with access could disrupt jobs for all users using the connection. Something similar to how the Notification items are broken out would be amazing.3. Automatic Content Sharing with Administrator AccountsIt would be helpful if FME Server automatically shared user created content with members of the Super User role. If this could be an option for the FME Admin role that would also be appreciated. I have a plethora of users creating content and when they ask for help it is cumbersome to have to share their content with myself and my fellow Admins before I can help troubleshoot.

j.botterill
Evangelist
j.botterillEvangelist

Geometry Picker Support for ArcGIS Esri content basemaps + feature services in FME Flow Apps – background mapsOpen

Asking for an improvement to FME Flow Apps, to better support ArcGIS Enterprise or ArcGIS Online content. Currently web mapping tile services are supported, while these are useful for basic public mapping scenarios, it can be limiting for enterprise users, like ESRI customers who rely on managed GIS content, authoritative operational layers, and internal esri basemap standards. Workflow for Geometry Picker….In FME Form under user parameters there is an input called “Spatial Geometry” type.Define & Select spatial Geometry user parameterWhen this parameter type is published to FME Flow and a ‘Workspace App’ is created, under the ‘Parameter Defaults’ there is an option for Map Configuration, as outlined in this helpful article Using the Geometry Parameter – FME Support Center.proposed UI improvement to Map Configuration in Flow apps - add ArcGIS map services Why add ESRI map support to Flow Apps?Many organisations already manage authoritative spatial context through Esri platforms. When a Flow App requires a user to draw or select an area of interest, the user often needs to see operational reference layers such as boundaries, tenements, assets, work areas, inspection zones, environmental constraints, or approved operational footprints.Without access to these layers in the Geometry Picker, users may need to manually cross-reference another GIS application, which can reduce confidence, increase error risk, and make the Flow App feel disconnected from established enterprise GIS workflows. Desired spatial geometry parameter functionality:Support existing Esri webservice/connections already configured and authenticated in Flow to come into the Flow spatial geometry parameter Allow Flow App authors to configure Esri REST 1. map and 2. feature services as selectable or reference layers in the Geometry Picker. Respect secured services where authentication is already configured in FME Flow, including (arcgis) web connections or stored/encrypted web service credentialsThe old htmlreportgenerator supports the consumption of “feature layer URLs”, even multiple layers if they are comma separated. HTML report generator support Esri leaflet - feature service URLs shared openly I posted on this in the past, and the community wanted the transformer to see more support added as well. HTMLreportgenerator ESRI leaflet - feature layer URL more info needed | CommunityOne issue I anticipate might be challenging 😥, is that the latest ARCGISFEATURESERVICE safe.esri.agol package only supports content that is my content or shared to groups. The above functionality all assumes the esri REST map/feature services are shared to groups. But through the use of web connections to arcgis content, supporting group shared or originisational shared content like basemap services could be explored?the latest ArcGIS feature service reader > its parameters to item sourceThe Background Maps available in FME Form, would be very complimentary if added to FME Flow and Workspace Apps!Much of the functionality could be used in a similar manner 😎in FME form we have ‘background map’ support… how about this in Flow apps? You might find other ideas similar to this onehttps://community.safe.com/ideas/geometry-picker-basemap-using-arcgis-webmap-29298  https://community.safe.com/ideas/set-a-default-map-for-geometry-picker-in-fme-flow-app-29958  https://community.safe.com/ideas/flow-apps-customize-geometry-parameter-search-37946

gisbradokla
Enthusiast
gisbradoklaEnthusiast

directory and pathnames Reader skip invalid pathsOpen

I am revising/ simplifying the idea   it would be nice if to start with the path reader would allow exclusion of write protected (received an error and failed), hidden, system, invalid folders/files. secondly I currently use a tester to exclude many folders that I am not interested in scanning. But this requires a read to get the features through the tester. It would be optimal to tell the path reader to use a list or sheet of folder names to exclude from the read. I know this sounds perf expensive but when scanning several hundred thousand folders the payoff is NOT to read them all before exclusion.   leaving this confusing original section below:I have a question in community forum for a flow issue that cropped up. I previously had a ticket with my own IT with an issue that falls into this same category and now a third iteration.in each instance the reader fails and does not continue. whether in form or flow.instance:we receive a zip file that has been incorrectly named. When it is unzipped the folder name ends with a period. (eg. my folder-0name.it doesn’t\matter if there is a\period in the folder it only matters if the folder name ends with period.) this causes the reader to fail and cancel running in both flow and form. I have not identified why the second instance occurs but it is odd that if i am using a reader and it fails with ‘Media is write protected’. see this question here. I understand the 3rd instance is an error on our network. but still can’t the reader detect that it can’t really (with only symlink references) read this and just circumvent the folder? (the error is - PATH Reader: Error reading path '\\Tx-mio-mis01\fw-shared2\SURVEY\CHus\HM_PKG_9_LOWLINES\0_GIS\FOOTAGE_TABLE.xlsx' with error message: 'directory_entry::status: The symbolic link cannot be followed because its type is disabled. Response from my IT dept… From: Helpdesk <helpdesk@topo.sur>Date: Wed, 19 Aug 2026 16:13:56 (UTC -05:00) These are not corrupted. They are a new form of archiving that we have begun implementing. Are they giving you troubles? create specific exclusions. for instance maybe with regex. (e.g. _ARCHIVE) do not read