Unable to set a value in another field when using an onChange client script on an HTML variable type, based on a user-entered value in the form.Issue Unable to set a value in another field when using an onChange client script on an HTML variable type, based on a user-entered value in the form.ReleaseAllCauseHTML variable are for user input with advanced formatting, including images, for a catalog item. HTML variables are designed for display purposes only and do not store values. Consequently, they cannot be used as triggers for UI Policies, Client Scripts, or other dynamic behaviors that rely on variable value changes. Why HTML Variables Can't Trigger Logic-No Stored Value: HTML variables are meant to render static HTML content, such as instructions or formatting, and are not intended to capture user input. Therefore, they lack a stored value that can be monitored for changes. -Not Recognized by g_form: Since they don't have a value, HTML variables aren't accessible via g_form.getValue() in client-side scripting. This means they can't be evaluated in conditions that depend on variable values. -No Change Events: Without a value to change, there's no event to trigger scripts or policies. UI Policies and Client Scripts rely on detecting changes in variable values, which isn't possible with HTML variables. ResolutionIf you need a text field as a trigger to write something in HTML variable, you can use "Single Line Text" type variable as a text field with a trigger to write something in HTML variable.