I have noticed that coming from a version with the old script editor causes issues with the scripts. In my experience, you need to first build the scripts. You may get some errors as I have seen some semicolons left off of the end of scripts. The error window should take you directly to those lines though. Once you have all of the scripts built, then you can run the solution to see which automations have scripts that are "corrupted". When you attempt to open these, you may see the option to replace the script method with one in the script. It may take a little trial and error to get all of the scripts corrected.
Thank you for your reply. But if there are any issue with the scripts like missing semincolon or namespace issues, the script will not build in Openspan 7 also right? But in Openspan 7, it is working perfectly fine till today. Kindly advice. Even if i resolve the script issue, it keeps recurring everytime for different scripts.
A few changes in the components have left a requirement to manually resolve some missing syntax in the script components. Most commonly, it is only semi-colons and some missing 'using' references. There is a series of steps that we recommend going through when upgrading a Solution.
Delete obj and bin folders from the solution projects
Open the Solution in Studio
Clean and Build the Solution
Double-click each error, in Error List window, to open the error in the designer view. Then resolve any syntax error in the script.
It is important not to open the automations containing the script methods because the component will fail to resolve and then disappear from your automation. This would force you to re-add them.