# Improving Responsiveness of Data Validation Rules

**URL:** <https://community.tulip.co/t/improving-responsiveness-of-data-validation-rules/12086>\
**Category:** Product Suggestions\
**Tags:** data-entry, feature-request, validation\
**Created:** [July 31, 2024, 2:14am UTC](https://community.tulip.co/t/improving-responsiveness-of-data-validation-rules/12086 "2024-07-31T02:14:19Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Beth](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/beth/32/5987_2.png) [@Beth](https://community.tulip.co/u/Beth)\
**Post date:** [February 14, 2025, 4:37pm UTC](https://community.tulip.co/t/improving-responsiveness-of-data-validation-rules/12086/5 "2025-02-14T16:37:52Z")

</div>

@k.ober @thorsten.langner @ta-aoki - in [Platform Release 306 - February 2025](https://community.tulip.co/t/platform-release-306-february-2025/13827) there is a new when “input is exited” condition option for triggers of text, multiline, and number input widgets - wanted to check in here if this helps with some of the data validation pain points discussed here?

---

_[View the full topic](https://community.tulip.co/t/improving-responsiveness-of-data-validation-rules/12086)._