After New York Upgrade - On-Call Schedule has error "Expected argument of type object, but instead had type undefined"DescriptionYou have upgraded your Development instance to NY patch 1 - Hot Fix 1. You have reverted all the customizations related to the on-call back to OOB, so we can be aligned with the ServiceNow code base and also utilize all the features and advancement that have been made on the new On-Call as part of NY release. We have encountered below error as we begin the testing after reversion. ERROR: Expected argument of type object, but instead had type undefined Steps to reproduce:1. Navigate to the On-Call schedule application2. Click on Create /Edit Schedule3. Pick a group, fill the fields and click next4. You'll receive the error message and you can't make any further steps. CauseIssue has been caused by heavily customized file belowOnCallRotation https://vfcdev.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=00de3ea6c0a81701018849faa834ee9c This file is not at the upgrade version but rather has been merged with your customizations. ResolutionI will suggest you revert the following file back to the upgrade version OnCallRotation https://xxxxx.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=00de3ea6c0a81701018849faa834ee9c Reverting this file fixes the issue.