Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Hello all,Today again, I dropped a filter in an automation I was building, and immediately missed the ability to filter on a regular expression. I actually never have to search for an exact case sensitive string, but always need some flexibility.I searched the Idea's section to vote up any idea posted already for this, but did not find any. So here it is... Add regular expressions to the automations filter..ps. If I recall correctly, Don promised something like that on one of the first presentations of the whole Automations concept.
I've heard that the Filter Action for Automations in recent FME Server versions has changed to be integrated, as opposed to simply being the FilterMessage.fmw workspace published to the Tools repository. I'm using FME Server 2019.1.3.1 and I found it useful to update the Tester in the FilterMessage.fmw workspace to "Contains Regex" (as opposed to "Contains") so that I could add more complex queries (i.e. multiple strings searches) in my Filter Action in the Automation. I don't have hands on experience with newer FME Server versions, but I'm thinking this might be something to consider for the integrated Filter Action.Thanks!
The current Automation filter does not allow for regular expressions. Having the ability to perform the filtering of the data within the automation, instead of triggering a workspace would be nice. Currently the filtering is done within the workspace, but I think it would be a better idea to do this within the automation itself, rather than calling a workspace.
I think it would be nice to be able to open the settings of multiple transformers at the same time. Currently this is limited to only be able to open the settings of one transformer at a time. I know there is a workaround to this by turning the summary annotation on so that you can view the settings, but it would be nice to be able to open two separate transformers and view/edit them.
In large Workbenches it is sometimes necessary to edit the same parameter on multiple Reader/Writer/Transformer to change it to the same value e.g.: I have 36 SQL Server Spatial Writers in one Workbench and want to change from "Drop and Create" to "Truncate" mode. Now I have to click trough all of them and apply the change.It would be nice to mark all Reader/Writer/Transformer that I want to change, click "Properties" and apply the change only once and all marked Reader/Writer/Transformer are changed.
Hi together, I was looking for a way to create a custom header/footer template using our corporate colors/icons/favicon for FME Server based workspace apps. The idea is that whenever any of our FME admins wants to create a new workspace app on the server, he/she would work with a customized header/footer from the get go - without reapplying the color hex to the header, inserting some text to the footer etc. Such a functionality would save time and is less error prone.
It would be great if one is able to make FME Server App Layout templates that can be reused throughout different workspace apps. I.e. whenever one builds a new workspace app, in the 'Customize' section one can select a layout out of a list of previously configured templates.
When Counts or Caching are on, please make the numbers easier to read.
It would be great to show feature counts on the output ports, instead of on the connection lines. A couple of reasons:Feature counts will still be available when nothing is connected to the output portWhen connection lines overlap/intersect, the numbers won't overlap each other, making it hard to read. (When two numbers overlap, it could look like a different number)
Storing a parameter like $(HOST) in Embed Connection Parameters could be a great thing to add. Very versatile in combination with the FeatureWriter and dynamic configurations.
***Note from Migration:*** Original Title was: Database Connections - make connection parameters available as published parameters Make it possible to make the connection parameters such as host or database name available as published parameters so that they can be used in other readers, writers, or transformers, such as SystemCaller.More details in this Forum discussion: Database connections retrieve parameters programmatically
It would be useful to have an option to create a parameter that only accepts input that's of a specified length or matches a regular expression or similar
Add a new type of published parameter : text with regular expression (or add it as an option in the actual text type).The idea is to be able to control the input by a regular expression.Imagine the possibilities : check if the input is a valid email, a valid ID, etc...
Hi,Wouldn't it be great to have a parameter to define the initial window size of the geometry picker parameter?Yes you can adjust the size of the window once it is open, but it would be great to be able to define it yourself.Cheers,Itay
It would be great to have the option to limit the input extent size in the GeometryPicker itself! We oftentimes develop tooling for which it is a necessity to limit the area size, for various reasons (e.g. to prevent an engine being used by one tool for too long or to prevent putting a heavy load on an open data service). Currently, in order to achieve this, the supplied input in the GeometryPicker is checked in the workspace itself. If it’s too large, this will be communicated to the user through a log message. In my opinion, it would be a lot more intuitive to have this feedback in the GeometryPicker itself. E.g. whenever the user draws a polygon that exceeds the allowed size, the polygon will turn red.PS. I’ve only experienced this with polygonal input, but maybe other FME users would like the same functionality for limiting input length of line geometries as well?
FME Desktop 2022: A transformer to add a comma separator (thousands separator) and specify the number of decimal places, It would be great to have a transformer to add a comma separator (thousands separator) and specify the number of decimal places so that they appear in the table
How about a new transformer (or added capability to an existing transformer) that would format a number with the thousands separator. Right now you have to use Python or use several transformers - see https://knowledge.safe.com/questions/37508/format-number-with-commas.html?childToView=37546#answer-37546 for a discussion on this subject.
A nice feature is creating attributes on ports of a transformer, rather than always adding another transformerWhen this has been used, please add the output in the "Show Summary Annotation" so that other users/clients can understand the workspace better.
I would like to see information on created port attributes included in the summery annotation of a transformer. Port Attributes is easy to miss, and I think it is a good practice to document them.I suggest a similar table that appears in the summery annotation of the AttributeCreator. In case an attribute with same name is set on several ports, let the Attribute Value column be populated with key-value pairs, where key is port name, and value is new attribute vale.
Would be nice if there was some kind of progress indicator in the translation log for the SherbendGeneralizer. The transformer can take a really long time to run especially if the dataset you are trying to generalize is very large and you have no indication on how far along the process actually is.
Add ability to display progress indicator on connection, relative to a prior connection (manually linked).For long running workspaces we should have the ability to "link" different connections so they can display a percentage of the passed through features relative to the previous "linked" connection
When the Translation log isn't whizzing by at 100mph, it can provide useful information, but I think it can be made better. My ideas - feel free to add your own are:1) Pause and resume button - I know you can pause the translation, but...2) Have collapsible/expandable sections - watching 2,000 sets of CSV Reader Directives flash by isn't much fun3) Progress bar when a particular action is being tardy
When creating an automation we use a lot of SDE connection, we cannot use the Database Connections in FME server so we need to pass the User Password to each workspace in the automation. When attempting to add the password as a Global Variable the password is visible to anyone with access.It would be nice to either have a Database Connection type of SDE or to have a Encoded global variable in Automations
The User can select a queue on Run Workspace, when the admin creates queue admins can add a description of the queue. But there is no way in the server for the user to see the queue description. Usecase: We have 3 queues, Small, Medium, and Large, each queue has a specific size of the engine associated which is described in the description field. e.g. small = t3.large 2 CPU 8GB Ram. This information is crucial for user consumption when the user is starting the job on a specific queue to understand what size of the engine the user is going to use when they run the job and if is it the right size of the engine for the job they are going to run or not.
The FME Server job queues in the Engines & Licensing -> Configure page have a Description field where you can explain what the job queue is for. However, in the Schedule->Advanced->Job Queue page the descriptions do not show; only the job queue name shows. This makes it difficult for a user who does not have access to the Configure page to understand what the queue is for.It would be great to have a popup appear on mouseover of each job queue description on each page in FME Server that shows the job queues select box.
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.
