View more results: All Community | Partner Community
  • Blog Post: Defining Namespace References

    In a previous article " Script Libraries: Reusing Client Side Code Between Screens " I discussed how Sage CRM 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: Binding Client Side Script to the onLoad event using crm.ready()

    Sage CRM has a Client Side method crm.ready() which is used to execute scripts once the page is loaded. We do not have to worry whether the browser is Chrome or Internet Explorer. The crm.ready() method will take the browser version into account and add the function we pass to it in the correct way...
  • Blog Post: 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 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 then we could...
  • Blog Post: Controlling the RecentList using Client Side Code

    The GoRecent function is held in Sage CRM in an external file which is included in every page. Sage CRM Code Example <script> function doCode() { SageCRM.webMenu.GoRecent('C'); } </script>
  • Blog Post: 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: 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 <INPUT> HTML tags are named and have an ID with same name as the physical field in the database. e.g. <input...
  • Blog Post: Hiding Panels in System Screens in Sage CRM

    Screens like the Opportunity Summary, Case Summary and Company Summary page are divided into different panels. Much of the page layout in the current version is controlled by HTML Tables. CSS styles are used to format the display of the tables and their TD tags. In these summary pages the different...
  • Blog Post: Using an External Script file to add event code to a field.

    A customer had the requirement to place some rules on the company name field to discourage users from entering characters that were not allowed in business names. Which special characters may be used in a business name will differ between countries. I am most familiar with the UK rules having set...
  • Blog Post: The Client Side API in Sage CRM: A round up of articles.

    There is now a number of articles that show the use of the Client Side API and I hope this is a useful reference blog that brings everything together. Introduction to the API The Client Side API Using Chrome to help write Client Side Scripts Binding to Events Binding Client Side...