The removal of the framesets in Sage CRM 7.2 has an impact in the follow areas
- onChange and Custom Content scripts.
- ASP extensions
- .NET extensions
There is a new folder in the WWWRoot, called js, and files added there will be deployed to the client. These can either be in the CRM or custom folders.
Some of these system generated object and functions that were created in the eware_mid frame in Sage CRM v7.1 and referenced by your code should still be fine. Examples of these objects are
CurrentUser and GetKeys(). These continue to exist in the page in which the code runs.
But in Sage CRM v7.1 there also used to be objects that were created in other frames. Examples of these are
- Arrays (userslist, usersdislist, targetlistslist)
Code that references these objects will need to be changed and tested.
You will need to check the meta data for the screens and lists that contain client side customizations. The following SQL statements can be run in the database to find those screens with defined custom content and onChange scripts.
select * from Custom_ScreenObjects where Cobj_CustomContent is not null
select * from Custom_Screens where SeaP_OnChangeScript is not null;