Filter tasks can be added to FME Server 2019 Automations, as demonstrated during the FME World Tour.
The example shown during the WT was filtering incoming Shape file datasets after a Directory Watch trigger had fired so that the subsequent workspace would only process files with a .shp extension. However, when the Automation logs are viewed, it indicates that a filter.fmw workspace is being run to apply the filter. Does this filter workspace tie up an available Engine license? If so, could it cause contention on a system with only 1 available Engine?