In the FME Server 2019 beta, you can add triggers, actions, etc, but while you can add all these, there is no warning if you save them without altering anything. That is you can add a process to call a workspace caller, but never call a workspace in it. So it may be easy to overlook a piece of the puzzle.
It would great if on save the automation was checked to see if the details are filled in, in all the automation and warned if not (e.g. type = trigger or type=sender means they are blank, while workspace types would have empty WORKSPACE). You could choose to save, but be aware that bits are missing.
Like the best practice workspace for desktop, a handy check.
FME Server 2019.1 Beta (Build 19556 or Newer)
safe.com/betaWe have improved the validation on the nodes or objects in an FME Server Automations workflow. The "indicator" will now appear when required parameters have not been filled out.
As development progresses, we will look to address the error messages as well. For example, when I try to enable this Automation without configuring the Schedule Trigger I receive the error message below, and I cannot Start the Automation.
----
Please note that this is a beta feature and its functionality and appearance are subject to change as the product continues to evolve before the official release.
Should this feature or its implementation not address your concerns, related to this Idea posting, please let us know by leaving a comment.
As with all beta features and beta versions of our software, they are not considered production-safe and should be incorporated into your workflows with consideration and testing.
FME Server 2019.1 was released July 11th, 2019 and included some improvements for FME Server Automations to indicate when Triggers or Actions have incomplete configurations. For most scenarios, there will be a visual indicator on the Automation node itself, and we are catching other errors when you attempt to Start the FME Server Automation.
Image. Example: An error or alert is presented when attempting to save an FME Server Automation where a "Run a workspace" Action did not specify an FME Workspace.