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…
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…
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 HTML tags are named and have an ID with same name as the physical field in the…
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…
The GoRecent function is held in Sage CRM in an external file which is included in every page.
Sage CRM Code Example
function doCode()
{
SageCRM.webMenu.GoRecent('C');
}
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…
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…
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…