Solution

When performing upgrade preparatory tasks, you need to refer to the above list and verify whether there are any tailorings to these ScriptLibrary records. For those tailored ScriptLibraries, you must back up the codes before the upgrade. After upgrade, you can compare the tailored backups with the corresponding new 9.64 out-of-the-box ScriptLibraries and merge the conflicts manually.

Follow these steps to merge the tailored ScriptLibraries in a production environment. In these steps, the SmartEmailManager ScriptLibrary is used as an example.

1. In the development environment, copy the codes in the SmartEmailManager ScriptLibrary and save them in a text file.
2. In the test environment, copy the codes in the new out-of-the-box SmartEmailManager ScriptLibrary and save them in another text file.
3. Use a 3rd-party compare tool (for example, Beyond Compare) to compare the two files and merge the conflicts manually.
4. In the test environment, open the database and then execute the following SQL script to rename the current SmartEmailManager ScriptLibrary.
    

   UPDATE SCRIPTLIBM1 SET NAME='SmartEmailManager_NEWOOB' WHERE NAME='SmartEmailManager'

5. Add a new ScriptLibrary named "SmartEmailManager" and then copy the merged codes to this ScriptLibrary.