Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
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)
When Counts or Caching are on, please make the numbers easier to read.
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...
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?
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
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.
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.
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.
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.
A possible way to improve working with FME Workspaces and informing the end-users about changes.Documenting the workspaces with Bookmarks and Annotations is the first step in creating a well documented workspace. But what if you want a better way to work, and save all the minor changes you do every day? And find back to a previous version? Also if you share the same workspace with more colleagues either through Github or through a shared drive? Can we benefit more by working a bit more similar by looking to our coders even if we are non-code people? YES!We also want to inform all the end users of our workspaces / FME Server workspaces / Gallery apps of any changes we have made with the workspace. NOT with a separate word-document we have prepared and they have to look at. NOT by sending an e-mail and say: Hey, we have added a new format. But within the actual workspace itself.A suggestion to Safe Software to consider would be like this?1. Start FME Workbench2. Select Workspace you want to work with3. Get pop-up:a. What are you doing today? Enter short description: For instance (Check errors when writing to Shape)4. Open workbench and you have a new textfield floating on the top left cornver of the canvas5. When you have “found and fixed” what you should (should only take 5min – 1 hour is) hit SAVE button and a new pop-up. Prefilled with the text already enteretd:6. This will now be saved in the workspace “History- which few people use?”. And you now have a good track history of the changes. 7. When published on FME Server the last change (and older) can be showcased on the Run Workspace:And also on the FME Server Apps side.
I like to display a description of what a workspace does in annotation. The workspace parameters already have a place to input a description (e.g. Overview property in 2017.1), but that is not nearly as visible as annotation. It would be helpful if annotation could be created that is dynamically linked to workspace parameters, such that if I update the text in the annotation the corresponding workspace parameter is updated, and vice versa.
In some Workspaces there are critical comments which should popup when opening the workbench-File.E.g. "Don't upgrade Linejoiner in this Workspace"
***Note from Migration:*** Original Title was: Option to force workspace description to popup when closing a workspace (after changes) Would love to see an option that allows you to force a popup of the workspace parameter descriptions when closing a workspace/workbench. Option would be saved in the workspace and only for the ones you need too and when there are (meaningful) content changes made within this workspace.This would help in keeping track of the Overview, help and most importantly the History.
It would be nice to have a summary annotation like functionality for the workspace history parameter
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.
