feat(forms): support for dynamic control change

[dtsanevmw]

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• If applicable, have a visual design approval

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

With dynamic controls which are not available initially but when they appear available combined with a value, we don't track that and status validation is not triggered and it stays in NONE state.

Issue Number: CDE-1464

What is the new behavior?

Now we trigger validation if there is a change inside the control and validations works.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[github-actions]

👋 @dtsanevmw,

• 🙏 The Clarity team thanks you for opening a pull request
• 🎉 The build for this PR has succeeded
• 🔍 The PR is now ready for review
• 🍿 In the meantime, view a preview of this PR
• 🖐 You can always follow up here. If you're a VMware employee, you can also reach us on our internal #clarity-support Slack channel

Thank you,

🤖 Clarity Release Bot

[wghglory]

Hello @dtsanevmw,

Could you please provide an estimated timeframe for the resolution of this issue? Our product heavily relies on it, and having an idea of when it will be fixed would greatly assist our planning. Thank you for your prompt attention to this matter.

[github-actions]

Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary.