View more results: All Community | Partner Community
  • Blog Post: Sage CRM 7.2: Script Libraries: Defining Namespace References

    In a previous article " Script Libraries: Reusing Client Side Code Between Screens " I discussed how Sage CRM 7.2 will automatically add any javascript file that you add to the custom folder into the header of every page produced by the system. It is a good idea when adding script libraries...
  • Blog Post: Sage CRM 7.2: Binding Client Side Script to the onLoad event using crm.ready()

    Sage CRM 7.2 has a Client Side method crm.ready() which is used to execute scripts once the page is loaded. In earlier versions of Sage CRM we could use 'Plain Old Javascript' to associate custom code to the moment the page was loaded. In Internet Explorer the way to do this was: window...
  • Blog Post: Sage CRM 7.2: Script Libraries: Reusing Client Side Code Between Screens

    It has always been possible in Sage CRM to share client side code between screens. In Sage CRM v7.1sp2 and earlier we could do this by using a shared external script library. For example if we wanted a set of business rules to be available in both the PersonBoxLong screen and the PersonBoxDedupe screen...
  • Blog Post: Sage CRM 7.2: Controlling the RecentList using Client Side Code

    I have previously written about how the RecentList can be controlled in Client Side script using a technique suitable for Sage CRM v7.1 and earlier. You can find this article here: Clearing the Recent List using Custom Clientside Code (for Sage CRM v7.1 and earlier) The removal of frames in Sage CRM...
  • Blog Post: Sage CRM 7.2: Making sure upgraded ASP pages work correctly.

    This article has been prompted by a customer who was left scratching their head when an ASP page that had been working in old install of Sage CRM didn't seem to be 'quite right' in Sage CRM 7.2. The upgraded page seemed to being missing some features when they looked at it after they had...
  • Blog Post: Sage CRM 7.2: The Evolution of Client Side Code

    Sage CRM supports multiple browsers, Chrome, Firefox, Safari and right from the earliest versions it has supported Internet Explorer. Multi-browser support was added in Sage CRM v7.1sp2. Much of the support for different browsers within the code included in the system screens was made easier by the use...
  • Blog Post: Sage CRM 7.2: Creating and Using ASP pages

    I have noted in previous articles that Sage CRM 7.2 has eliminated the use of Frames within its general screen architecture. Why Remove the Framesets? The Impact of Frameset Removal on CTI integrations The Impact of Frameset Removal on Code in Upgraded Systems ASP pages however are...
  • Blog Post: Sage CRM 7.2: Using the Clientside API to control Tabs

    Consider the following business rule. "A customer has a requirement that the Case Tab in the company screen should only display when the Company has an agreed service level agreement and the user accessing the screen is in the 'Customer Service' team." This is a business rule...
  • Blog Post: Sage CRM 7.2: Detecting Screen Mode in the Client Side API

    Sage CRM Screens can exist in different ‘Modes’. The basic two modes that we have to worry about in Client Side code are View and Edit. We can use the fact that in Sage CRM 7.2 and earlier <INPUT> HTML tags are named and have an ID with same name as the physical field in the database...