@Pavanir6  

pyDefault is meant to set defaults when the case page is first created or when a view runs a pre-processing data transform; it does not auto-run in the middle of a case when a single field changes. What likely happened in the video is that either the view had a pre-processing DT and a refresh re-applied it, or the author wired an on-change action but didn’t call it out. To make this work, open the Eligibility Type field in the Constellation view and add a Change action: first Post value, then Run data transform (create one like SetEligibilityMessage), and if needed Refresh current view. In that DT, set EligibilityInfoAccept or EligibilityInfoReject based on the current .EligibilityType using simple when conditions or a decision table. If you want it to recompute automatically without explicit actions, model a derived property with a declare expression (for example .EligibilityMessage = function of .EligibilityType) and bind that to a text/paragraph control. Keep pyDefault for initialization only; don’t overload it for mid-case logic. Save, clear preview cache if needed, and retest the change flow.