@Premalatha Nagaraj

In Constellation 24.1.x the pxClearMessage function only clears the message on the server page, but the Constellation UI keeps its own error state and does not “see” that change, so the message stays on screen even if you call pxClearMessage in a form-refresh data transform. This behavior is tied to a known Constellation issue where validation errors were not clearing correctly after the field was updated, and Pega fixed it in the 24.1.3 patch by changing how the updated field is revalidated and its error state refreshed in the Redux store. Because of that, the recommended approach is: don’t try to manually clear the message with pxClearMessage; instead, keep the validation on the field (required / validate rule / edit validate) and let Constellation re-run validation and remove the error when the value is corrected. Make sure your on-change action on the checkbox is configured to refresh the whole view or assignment (not just run the data transform), so the client pulls the updated error state from the server. If you are still on a base 24.1.3/24.1.4 build without the latest patch, raise an SR and move to the most recent 24.1.x patch level where this behavior is corrected. As a short-term workaround on older builds, avoid property-set-message for this scenario, or move the logic so that validation only runs on submit instead of on every on-change, which stops the “stuck” error from appearing in the first place.