In FME Flow, Automations can be triggered by various FME Flow System Events, such as the creation or modification of repository items. This provides a powerful and flexible way to build event-driven workflows and governance mechanisms.
However, currently these system events are primarily focused on repository-based entities. There is no equivalent event available for entities that exist outside of repositories.
For example, the creation (or modification/deletion) of an FME Flow App does not trigger a corresponding FME Flow System Event. As a result, it is not possible to directly react to such changes using Automations.
This limitation makes it difficult to:
-
Implement governance or auditing processes for FME Flow Apps
-
Automatically enforce naming conventions or security policies
-
Trigger notifications when new public apps are created
-
Maintain synchronization with external systems
-
Track lifecycle events of non-repository entities
