Out of the box "Resolve" button is not working as expected on custom recordsIssue ProblemThe out-of-the-box (OOTB) "Resolve" button is not posting the inputs from the pop-up to the record in Service Operation Workspace. Steps to reproduce 1. Customer created a custom entry list for custom table x_jpmc_gsd_tsd which extends incident table2. Go to Service Operation Workspace3. Go to List > Click on the entry created on step #14. Open any record in "In Progress" state5. Click on the OOTB action assignment called "Resolve"6. A popup is opened, fill the fields and click resolve7. See the fields are updated but not on the backend as refreshing the UI not updates are done Note: If you the same steps to an incident record, that works fine ReleaseGenericCauseRoot CauseThe issue was caused by a custom modification to the Save OOTB UI Action (sys_ui_action_f4deef100b701300099a83eb37673a4d), which added a condition to exclude the x_jpmc_gsd_tsd table (current.sys_class_name != 'x_jpmc_gsd_tsd'). This modification prevented the "Resolve" button from functioning correctly for records in the x_jpmc_gsd_tsd table.ResolutionSteps to ResolveRemove the condition for the Save OOTB UI Action that excludes the x_jpmc_gsd_tsd table by reverting it to the OOTB version, ensuring the condition is set to !current.isNewRecord() && current.canWrite().