Create more flexible automations with additional triggers and conditions

Reacting to many requests to extend the automations and serve more use cases, we'll gradually introduce additional triggers and conditions. The extended capabilities will include responding to changes to the values in string, integer, double, and lifecycle fields.

In addition to the already existing trigger when a fact sheet's lifecycle status changes (e.g., from active to phase out), you can now start an automation if the specific date of a lifecycle field has been changed. This enables scenarios such as creating an approval to-do for the application owner to review the impact on downstream initiatives and IT components if someone postpones an end-of-life date.

Next, we’ll add the lifecycle state as a condition so you can react to it for any fact sheet inside an automation (e.g., if an application reaches its end of life, add a specific tag).