Hello Community,
I wanted to share a quick fix for a blocking issue I discovered in Problem Management within the Service Operations Workspace (SOW) after upgrading to the Yokohama release (specifically glide-yokohama-12-18-2024__patch7-hotfix2b-10-21-2025).
If you are facing issues where re-analyzing a problem leaves the form in a broken state, preventing you from applying a fix, this article is for you.
The Issue
When a Problem record is moved back to the Root Cause Analysis state (using the "Re-analyze" button) and you subsequently attempt to resolve it by clicking "Fix", the system throws a mandatory field error.
The Error:
"The following fields contain errors: Resolution code"
The Bug: While the error persists, the 'Resolution code' field is not visible on the form, making it impossible for the user to select a value and save the record.
Here is a screenshot of the error behavior: (Insert your uploaded image: image_1b20c1.png here)
Root Cause
The issue appears to be a UI synchronization glitch in the Workspace client script. When the state changes via the "Re-analyze" action, the form view does not properly refresh to update the field policies (mandatory/visibility states) for the new flow.
The Solution
To resolve this, we need to modify the Declarative Action responsible for the "Re-analyze" logic to force a form reload. This ensures the UI renders the correct fields for the current state.
Here is the step-by-step fix:
Step 1: Navigate to Declarative Actions
Open the application navigator.
Navigate to Now Experience Framework > Declarative Actions > Form Actions.
Step 2: Locate the Action
In the "Form Actions" list, search for the Action name: sow_problem_reanalyze.
Open the record.
Step 3: Update the Client Script
In the Action Assignment form, locate the Client Script section.
We need to introduce a reload logic (g_form.reload()) to ensure the form refreshes correctly when the action is triggered.
Updated Logic: You can modify the script to ensure the form reloads, clearing the "ghost" validation error.
Result
After applying this script update, clicking "Re-analyze" will properly refresh the form. When you subsequently move to "Fix," the Resolution Code field will behave correctly, allowing the record to be saved without errors.
Hope this helps anyone facing similar issues in the Yokohama release! Let me know in the comments if this worked for you.
