Resolving Field Message Persistence for Multi Line Text Fields Using g_form.showFieldMsg()Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Error messages displayed using g_form.showFieldMsg() do not consistently clear from Multi Line Text fields after the validation condition has been resolved. When client-side validation scripts (such as onSubmit scripts) use g_form.showFieldMsg() to display errors—for example, to prevent submission if invalid characters like commas are present—the behavior works as expected for standard text fields. However, for Multi Line Text fields, the error message may persist in the UI even after the invalid input is corrected, resulting in a confusing user experience. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Users may observe one or more of the following behaviors when interacting with a form that includes Multi Line Text fields: 1. Validation error messages persist after correcting the input in a Multi Line Text field (e.g., removing a disallowed character like a comma). 2. The error message triggered via g_form.showFieldMsg() does not disappear even after the field is updated to meet validation criteria. 3. Form submission is blocked due to the lingering error message, despite the field appearing valid to the user. 4. Inconsistent behavior across UI types: Error message clears as expected in Classic UI but persists in Workspace or Service Portal environments. 5. Field-specific error messages behave correctly on other field types (e.g., single-line text fields), suggesting the issue is isolated to Multi Line Text fields. 6. Developers using g_form.hideFieldMsg() may find that messages do not clear without additional logic, such as adding an onChange script or delay. These symptoms can lead to confusion for both end users and developers, as the interface may appear unresponsive or buggy when validation appears to be resolved but the system does not reflect the change. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Any version where Configurable Workspace, Service Portal, or Next Experience UI is used with Multi Line Text fields. Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } 1. g_form.showFieldMsg() Limitations Does not support multi-line messages or automatic formatting with line breaks (e.g., \n or <br>). Dynamic updates are inconsistent for Multi Line Text fields—message removal does not always trigger on input change. 2. Workspace vs. Classic UI Behavior of showFieldMsg() may differ in: Configurable Workspace Service Portal Classic UI Workspaces sometimes do not auto-clear error messages on field change, especially for multi-line fields. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Solution Options Script Fix (onChange + onSubmit) Ensure messages are explicitly cleared in both onChange and onSubmit scripts. onChange Script (UI Type: All, Field: Multi Line Text field) function onChange(control, oldValue, newValue, isLoading) { if (isLoading) return; if (newValue.includes(',')) { g_form.showFieldMsg('street', 'Field "Street" cannot contain commas', 'error'); } else { g_form.hideFieldMsg('street', true); // true ensures all messages are cleared } } onSubmit Script function onSubmit() { var street = g_form.getValue('street'); if (street.includes(',')) { g_form.showFieldMsg('street', 'Field "Street" cannot contain commas', 'error'); return false; // Prevent submission } return true; } Additional Tips & Workarounds Use g_form.hideFieldMsg() explicitly in both onSubmit and onChange to clear messages. Add a delay using setTimeout() before showing or hiding the message to let the UI process changes: setTimeout(function() { g_form.hideFieldMsg('street', true); }, 300); Use g_form.addInfoMessage() for general form-wide messages if the field-specific behavior is problematic. Test across UI types, especially if working within Configurable Workspace or Service Portal.