Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
When using the datetime user parameter in FME Form/Flow, the viewer where the user chooses the date ranges from Sunday-Sunday. As a swedish user, our calendar system is in line with ISO 8601 standard and starts with Monday-Monday. Being accustomed to this format, it is possible for a user to choose wrong date in a Sunday-Sunday formatted calendar. I would like a functionality for the datetime user parameter to switch between a Sunday-Sunday and Monday-Monday calendar.
When using ExcelStyler early on in your flow (I use it to highlight invalid values in Excel fles right after the data has been read from my database) or any transformer that creates <attributename>.something “sub-attributes” (not sure what the actual name would be), you currently must make sure to manually rename all of those alongside the main attribute whenever you rename them through an AttributeManager or AttributeRenamed, otherwise they will not be observed by downstream writers and transformers. If the Styler is added in the later stages of building the flow, that means going through all downstream AttributeManagers one by one to make sure the newly added sub-attributes follow the main one.It would be conveinient if those could all be renamed together automatically whenever the main attribute is renamed.
Our team uses a GitLab repository to have a single recorded source for some of our FME Workbench workspaces that get deployed to our FME Flow server. Whenever we save the files locally and make a new commit, the diff tools comparing the git revisions can become noisy with extra line changes that weren’t actually changes made to the file by the user in FME Workbench. This is because data series in the XML contents of the .fmw file are input randomly and may input in a different order upon additional saves. Child nodes in arrays under elements like <DATA_TYPES>, <GEOM_TYPES>, <CONNECTIONS>, and <BOOKMARKS> will fully rearrange their order in an inconsistent manner. This can happen if one entry is removed/added in the list and the workspace file is saved. This adds a lot of “diff” lines where changes didn’t occur when comparing two versions of the same .fmw file in any external git comparison tool. An example of a rearranging of the child nodes under <CONNECTIONS> causing extra diff lines Please add functionality to sort these series of nodes/values alphabetically by a name attribute so that they are saved to the .fmw file in a consistent manner that doesn’t change between saves.
When processing by group there is the option to wait for all features to be receive before splitting up the groups and there is an option to process when group changes.Both options are great, however, in the “Process when group changes” method the process doesn’t actually start until the group value changes. This makes working with live data streams difficult sometimes when processing in group - especially trying to capture the last feature, or group of features. In some cases it’s possible to know the size of the group(s) - for example in some cases the size is just 1. If the site of the group was given then once that size was reached then it could head off to be processed before the next group arrives. see this question for use case: This method would also allow for processing of groups of a defined size where the content isn’t so important. At present one must create an artificial group ID to support this workflow.
Hi, team!I am in need of a Palantir Foundry Reader/ Writer.Palantir Foundry is a technology that is rapidly growing in multiple industries. It is an all-in-one solution environment--similar to MicroSoft Fabric. I have a use case to integrate FME with Foundry but unfortunately, we don’t have an Ontology Writer. The ontology is a semantic layer for data hosted in Palantir.
With the rising importance of columnar format databases it would be great if FME would support ADBC connections:https://arrow.apache.org/docs/format/ADBC.htmlThis would give FME high performance access to the large (and growing) number of columnar databases commonly used in data analytics.
These days, a lot of people use the WhatsApp mobile phone app. Kindly send the user a WhatsApp message as well. in order for the user to determine the success or failure of his FME workflow. For example, we now have an emailer transformer.
To strengthen the integration between FME Form and FME Flow, it would be beneficial to improve access to FME Flow's shared resources directly from FME Form.Currently, we know that it is possible to access files stored in Shared Resources via a reader in "Select Files from the Web" mode, but it would be much more convenient if this capability were natively built into FME Form.Proposed EnhancementsDirect Navigation in FME Flow Resources (from FME Form) Enable browsing Shared Resources or Network Resources directly from FME Form, without having to copy-paste paths or manually modify macros. Deployment parameters & Automatic Resolution of Macros and UNC Paths Currently, if an FME Flow Network Resource (ex: $(SDEconnection)) points to a network drive, users must manually specify the UNC path in FME Form because the macro does not resolve automatically. It would also be useful if Deployment Parameters could include connections to FME Flow resources (Shared Resources, Network Resources). Pre-population of FME Flow User Parameters in FME Form When connected to an FME Flow instance, global parameters like FME_FLOW_WEB_URL could be automatically populated in FME Form. Access Alignment with FME Flow User Permissions Access to files and resources from FME Form should respect the permissions defined in FME Flow, ensuring users only access the resources they are authorized to use.
It would be nice if there was a link between initiator and schema. let say you read a folder containing XXX amount of datafiles and you are only interested in the ones that contain a specific schema. the you could read the folder, only read schema, test for the schema you want then merge that schema with the link to initiator. schema has the primary key, and initiator has the foregin key, with a 1:many relation.
Similar to how the InlineQuerier and FeatureWriter work, have the ability for custom transformers to support the “Connect Input” functionality where new input ports are madeSpecifically thought around Marks creation of the DataLogicControllerhttps://www.linkedin.com/pulse/whats-up-wednesday-26th-june-2024-routing-features-logic-mark-ireland-r84oc/
Highlight all selected features in the data inspector - There is a method to Save Selected features from within the data inspector, however, sometimes it's not clear what is selected. In the table view the selected features are highlighted, however, in the Map view only the feature which is seen in the Feature Informantin window is highlighted. It would be really nice is all selected features were automatically styled in such a way so see what is selected.
It would be nice to get the Transformer version history as a default option in the context menu. If you update a Transformer in FME 2016 you get to see the changes between the different versions that are used but you have to go via the update option and you aren’t able to see all changes. So in case you just want to see what changes occurred to a transformer, you have to find an old version of it to see the changes.
Please make the restoration of FME Server Version Control after upgrade more intuitive. This could be done by:1) Prompting to fetch from remote immediately after a restore, or2) Silently fetching from remote after a restore.Currently the back/restore tool will restore FME Server Version Control settings, but you have to fetch from remote before making any commits in FME Server to avoid remote ref and local ref errors (ie a sync to remote is needed before making changes in FME Server).
Is the LineExtender mis-named? I have a set of lines starting from the centre of a buffer polygon and ending at the edge of the polygon. I want to extend the line from the start point to the other side of the polygon. So LineExtender seems to be the perfect choice.However, if I use the Beginning port, I just get a line going from the centre of the buffer the other way. If I use the End port, I get a line outside the buffer, starting from the end point of the original line. I expected the Beginning and End ports to output the original feature with the original line extended in one direction. But only the Stretched port outputs the original line actually extended, but it's in both directions which is not what I want.I can work round this by aggregating the original line with the output from the Beginning port (and using Group By in the Aggregator), or using the LineCombiner (again with Group By), but that seems like a long way round when LineExtender should be able to extend the line in one direction.Original line:LineExtender Beginning port:LineExtender End port:LineExtender Stretched port:What I want - LineExtender beginning port + original line + Aggregator:
***Note from Migration:*** Original Title was: Apply Style Changes to More than One Annotation, Connection or Bookmark at a Time The ability to style connectors, annotations and book marks by assigning background colours or styles is very useful in visually organizing a workspace. But right now changes can only be applied to single item at a time, even if multiple items are selected. The ability to apply a colour, font or even a style to all the selected connectors, annotations or bookmarks would make it easier to provide a consistent look to a workspace.
I would like the canvas UI to tell me if a transformer being used is a Blocking Transformer (or has blocking/feature holding tendencies), Red always blocking, or Pink when transformers have GroupBy tendencies which can be or have been enabled (change Pink to Red when in blocking mode). The visual queue will tell me where I may have to control my flow of feature and runtime orders; or when I am about to create a loop which will trigger a linked transformer. Added benefit it will visually tell me of aggregation points of data, and likely memory intensive operations, in my script.
We already have the ability to set up and modify default connection styles and set unique styles for individual connections when they are enabled but, particularly in complex workspaces, it can be hard to identify connections that have been turned off. It would be a huge help in some cases to be able to set our disabled connections to be a different color so they stand out the same way that we can with active connections.
I would like to costumize the content of the six tiles for the FME Flow Home page for my own use. I’d like to add tiles with “recent failed jobs”, “Queued jobs”, “running jobs” and maybe other filteres in the tiles of the home.I am aware that this UI is worked on in a FME Flow release that is comming soon, but the preview that I’ve seen recently didn’t seem to include the posibility to costumize the FME Flow home page.
Presently Data Download result links while temporarily available are accessible without authentication. Propose honoring user authentication for accessing the result links or generating a longer token based URL that would be hard to brute force generate. Per this thread, https://community.safe.com/s/question/0D54Q00008Kq1hiSAB/security-of-fme-server-results-download-link
It would be nice if there was some sort of toggle option when running with feature caching as to whether a custom transformer produced a single output cache (like a collapsed bookmark) or if every transformer within it had a cache (current behaviour).I can see the latter being useful when actual developing the custom transformer, but in most cases I don't care about the interim portions of the custom transformer, when developing a workspace that uses one.I could put a bookmark around each custom transformer and collapse it, but that becomes tedious when there are several (dozens) of custom transformers.
When it is about to move or copy a workspace to another repository (from test repo to live/scheduled, making it available to other teams, etc) the way to do is to download and publish to the other repository taking care of the data upload and service settings.It would be much more convenient if a workspace could be copied in the web interface with uploaded data, services and notification settings.
Default styles in Data Inspector, e.g. default opacity, line thickness, point symbol, color, etc.
It would be nice if there was the possibility of setting up a notification that a security token for an FME Server account has expired (or is about to).
Make it possible in the jobs page on FME Server to open a job in a new window - to make it possible to easily open multiple jobs.
If a user is assigned the fmeadmin role, whilst they have permission to access and create items, they cannot view items (repositories/schedules etc) created by other users unless explicitly set under those user/role permissions. Currently the only way to expose everything to the admin is to assign the fmesuperuser role.Instead I would like to be able to provide full permissions on a per item basis, for example if I have multiple administrators, I may not want them all to have fmesuperuser privileges but I would like to give full permissions to certain components. E.g. As an Admin I can see all scheduled jobs in the Job History no matter the user that owns them, so I would like to see all Schedules on the Schedules page as soon as they created by other admins without having to go in and modify my own security settings to get full access to these.
In-depth courses for all FME skill levels.
Explore our extensive collection of how-to guides and tutorials.
Log an issue with us. Our support team is ready to help.
