π‘Introduction
I'd like to propose a browser-based workspace authoring environment for FME Flow that provides much of the functionality currently available in FME Form (Workbench).
FME Flow already provides a powerful server-side execution environment, workspace management, web connections, scheduling, and automation. However, developing and maintaining workspaces still requires a locally installed copy of FME Form. This creates an unnecessary separation between the development environment and the execution environment.
What if we could develop FME workspaces directly in the browser, with FME Flow handling the processing?
π‘Proposed functionality
An optional browser-based Workbench integrated directly into FME Flow could provide:
Visual workspace authoring: Create and edit workspaces using the familiar drag-and-drop interface, transformer library, and connection model of FME Workbench.
Server-side execution: Run workspaces using FME Flow engines rather than relying on local processing resources.
Centralized connections and credentials: Access web connections, database connections, and other resources already configured in FME Flow without having to recreate, publish, or synchronize them between environments.
Integrated testing and debugging: Execute workspaces, inspect feature counts, review logs, and troubleshoot transformers directly in the browser.
Integrated version control: Connect workspaces to Git repositories and support collaborative development.
No local installation required: Allow developers to access and maintain workspaces from any computer with a browser, without installing FME Form.
π‘Why would this be valuable?
Currently, there is a disconnect between FME Form and FME Flow. Developers create workspaces locally, configure connections and credentials, publish them to Flow, and then troubleshoot differences between the two environments.
This can introduce several challenges:
Connections and credentials may need to be configured separately in Form and Flow.
Workspaces may behave differently depending on local drivers, libraries, software versions, or environment configuration.
Developers need access to a workstation with FME Form installed to make even relatively minor changes.
Publishing and maintaining workspaces introduces additional steps and potential configuration errors.
Collaboration can be more difficult when developers have different local environments.
A browser-based authoring environment could eliminate much of this friction by making the development and execution environments effectively the same.
π‘This wouldn't need to replace FME Form
I recognize that FME Form provides capabilities that may depend on local files, installed drivers, specialized integrations, and local development resources. There will always be use cases where a desktop application makes sense.
I'm proposing an additional development option, not the removal of the existing one.
For many ETL workflows, particularly those built around databases, web services, enterprise GIS, and other server-accessible resources, a browser-based authoring environment would be more than sufficient.
π‘The bigger picture
FME Flow has already evolved beyond simply being a place to execute scheduled workspaces. It is an increasingly important platform for managing enterprise data integration and automation.
Bringing workspace authoring into that same environment would be a natural next step.
It would make FME more accessible to distributed development teams, reduce workstation dependencies, simplify credential management, and provide a more consistent development-to-production workflow.
I'd be interested to hear whether others have encountered similar challenges and whether this is something Safe Software has considered for the future.

