Which action is not a typical capability in FME Workbench?

Which action is not a typical capability in FME Workbench?

• A. Download a workspace
• B. Publish a workspace
• C. Schedule a workspace
• D. Republish a workspace

Answer: (C)

In FME, Workbench is the desktop tool used for designing, testing, and refining a workspace, while automation and scheduling are handled by FME Server. Scheduling a workspace is a server-side function that sets up when and how often a workspace runs, often with data sources and destinations configured for automated jobs. Because of that, scheduling isn’t a typical capability inside Workbench itself. You can download a workspace into Workbench, publish it to FME Server so it can be run automatically, or republish a newer version to the server, but actually scheduling the execution is done on the server, not in Workbench.

In FME, Workbench is the desktop tool used for designing, testing, and refining a workspace, while automation and scheduling are handled by FME Server. Scheduling a workspace is a server-side function that sets up when and how often a workspace runs, often with data sources and destinations configured for automated jobs. Because of that, scheduling isn’t a typical capability inside Workbench itself. You can download a workspace into Workbench, publish it to FME Server so it can be run automatically, or republish a newer version to the server, but actually scheduling the execution is done on the server, not in Workbench.