Record watcher switches change request state to: New after approval rather than valid state: Scheduled for Change Model driven changesDescriptionA user on a change form sees record watcher setting the state value to "New" rather then the valid state of: "Scheduled", caused by an update of the record in another session, often resulting in the change process being broken by the user then saving the change request with the incorrect state.Steps to Reproduce 1. Create a change request (using Emergency change model) state is in "New" and provide assignment group as "CAB Approval", assigned to "Bernard Laboy" 2. Move the state to authorized via REST API below: curl "https:///api/sn_chg_rest/v1/change/emergency/{sys_id}" \ --request PATCH \ --header "Accept:application/json" \ --header "Content-Type:application/json" \ --data "{\"state\":\"authorize\"}" \ --user 'luke.wilson':'luke.wilson' Note: --user: luke.wilson is one of the CAB approvers.Change depending on the approvers you have 3. Approve the Change request via Change Management Approvals PATCH API below: curl "https:///api/sn_chg_rest/v1/change/{sys_id}/approvals" \ --request PATCH \ --header "Accept:application/json" \ --header "Content-Type:application/json" \ --data "{\"state\":\"approved\"}" \ --user 'luke.wilson':'luke.wilson' WorkaroundImport the attached Script Include: ChangeModelAJAXProcessor that provides the fixed "getModel" function. Verify that the fix is correct by looking at script include: ChangeModelAJAXProcessor and check line: 76 is as below } else if (!typeCompatibility)Related Problem: PRB1551289