Description

At the moment, when a user creates a workflow, a couple of things are validated - like the presence of a mandatory name.

However, the existing validation needs to be improved to include things like:

• name uniqueness
• condition expressions validation: at the very least the providers referenced in the condition expressions (both on and if expressions) should be validated for existence
• steps validations: the step provider should have a chance to validate the step configuration and send an error message if, for example, a required config is missing

Value Proposition

The value of better workflows validation is to enhance the user experience. At the moment, some workflow definitions will be accepted on creation time, only to fail and be auto-disabled when they are used to process an event. An example is if the workflow has a typo in a condition that makes it not match any of the condition providers. This workflow, although successfully created, will fail when evaluating the condition for a resource and will then be auto-disabled.

A better UX is to show the user what is wrong at creation time, allowing them to adjust the workflow definition at that point.

Goals

See description.

Non-Goals

See description.

Discussion

No response

Notes

No response