In previous versions (up to 16.1.2), if attribute validations were configured in Studio, no validation alerts were displayed in Clarity Home until the instance was actually edited and saved. The current behavior starting from 16.1.3 appears to trigger validations prematurely, resulting in unexpected error messages and potential confusion for end users.
Steps to Reproduce:
Expected Behavior: Validation errors should only appear after the user edits and attempts to save the instance, consistent with behavior in Clarity version 16.1.2.
Actual Behavior: Validation errors are displayed as soon as the instance is opened, even before any edit action.
Clarity 16.1.3, 16.2.x, 16.3.x
This behavior is an intended design change introduced with the Microservice Broker to notify users about outdated data and ensure accurate, high-quality data capture.
Users needs to correct the data while editing the instance.