Issue

When a user inputs data into an attribute field with a custom validation microflow, and then cuts or deletes the information before saving, the custom validation microflow does not get triggered.

Environment

Mendix application

Cause

This is the expected runtime behavior.

The runtime input validation behaves differently based on the scenario.

Scenario 1

The user does not enter any value into the required field. In this case, runtime does not perform validation for that field, as there is no change sent from the client for that field. This in turn causes runtime to move forward with executing the microflow.

Scenario 2

When a user inputs a value and then cuts or deletes it, the client sends a change for that attribute. Subsequently, the runtime performs validation, generates an error if necessary, and sends it back to the client before the microflow is executed.

The runtime also performs a complete validation before committing NEW objects. So, this prevents committing invalid objects.

Solution/Workaround

There is no solution or workaround for the described issue since this is the correct and expected runtime behavior.

Additional information

Not applicable