Entity validations with changing a value in a microflow

3
Why do entity validations go off when changing a value in a microflow whitout committing? This is very annoying. The microflow stops running. Seems like this is introduced with 2.5(.1.1)
asked
2 answers
3

Since 2.5 validations are triggered on change instead of commit. Validations means: no object may exist in memory or database which doesn't comply to the validations.

This also makes sure security is checked on change instead of commit. In other words: you cannot pass the security.

answered
2

A work around which I use often now:

Perform validations manually in a before commit, using the 'Validation Feedback' activity. The user won't notice the difference.

answered