How can a workspace stored in Resources be executed?

How can a workspace stored in Resources be executed?

• A. Browse the resources, select the workspace, and click Run
• B. Use Manage > Workspaces to run it
• C. Call it with the FMEFlowJobSubmitter transformer in FME Form
• D. It cannot be run

Answer: (A)

Running a workspace stored in Resources is done by using the Resources browser: browse to the workspace, select it, and click Run. This action launches a server-side job that executes the stored workspace with its configured data sources and parameters. It’s the straightforward way to execute any pre-published workflow without loading it into a separate session or manually initiating it from a different tool. Why this works best: the Resources area is specifically designed as a repository for workspaces that you can run directly from the UI. This makes execution quick and repeatable, leveraging the server’s scheduling, job tracking, and parameter handling. Why the other options aren’t the right method here: managing workspaces via a general Manage path is more about organization and editing rather than launching an execution from Resources. The FMEFlowJobSubmitter transformer is a component used inside a workspace to trigger Flow submissions, not a method to run a workspace stored in Resources itself. And saying it cannot be run is incorrect because the Run action is the intended method to execute stored workspaces.

Running a workspace stored in Resources is done by using the Resources browser: browse to the workspace, select it, and click Run. This action launches a server-side job that executes the stored workspace with its configured data sources and parameters. It’s the straightforward way to execute any pre-published workflow without loading it into a separate session or manually initiating it from a different tool.

Why this works best: the Resources area is specifically designed as a repository for workspaces that you can run directly from the UI. This makes execution quick and repeatable, leveraging the server’s scheduling, job tracking, and parameter handling.

Why the other options aren’t the right method here: managing workspaces via a general Manage path is more about organization and editing rather than launching an execution from Resources. The FMEFlowJobSubmitter transformer is a component used inside a workspace to trigger Flow submissions, not a method to run a workspace stored in Resources itself. And saying it cannot be run is incorrect because the Run action is the intended method to execute stored workspaces.