View more results: All Community | Partner Community
  • Blog Post: Working with 'Create Follow-Up Task' and 'Create Follow-Up Appointments' using Server Side code

    The image above shows the New Task screen. Both the New Task and New Appointment screens allow a user to Create Follow-up Communications. A customer might have a business requirement to know whether the communication a user is currently entering is actually a followup of another communication. That...
  • Blog Post: The Values() collection

    This article has been edited and corrected. The code in this article has been changed to follow the coding convention that was introduced in Sage CRM 6.2 The Values() collection can be used in all serverside scripts to examine the passed in Values from a form. Create Scripts Validate Scripts...
  • Blog Post: Write to the CRM logs in a server-side script

    If you are developing a server-side script such as a Create Script, Validate Script or Table Level Script, it is often useful to write debugging information to a log. Jeff has blogged about a technique for doing this using the Scripting.FileSystemObject. I'd like to share with you a very simple...
  • Blog Post: How can I get the SID in Serverside scripting?

    The SID is the session ID value. The SID may be wanted if you are building a string that represents a hyperlink that will be returned to the browser. The SID after all only is needed for a new web request, we do not actually need it within server side scripts normally as there we are already in the context...
  • Blog Post: CurrentUser object in Serverside Code

    The CurrentUser object can be used in all serverside code including Create Scripts, Validation scripts, Table Level scripts and Workflow javascript conditions. It provides information about the current user session. You can list the properties of the CurrentUser object by using this snippet of code in...
  • Blog Post: More about the Values and FormValues collections

    This article was updated on 22nd May 2009 to follow the coding convention introduced in Sage CRM 6.2. The Values() and FormValues() collections are serverside objects that are analogous to the ASP Request.Form() and Request.QueryString() collections. In an ASP page we can see the submitted values...
  • Blog Post: Creating Global Code for OnCreate and Validate scripts (Internal COM API)

    There have been several articles written about using the scriptcommonfunction registry key to set a global function library for tablelevel scripts, but this option is not available for the other internal scripts. So if we can't use the function library of the tablelevel scripts to create globally...
  • Blog Post: Objects Available in the Internal COM API

    The diagram below contains the objects, methods and properties that are the main ones used in the internal COM API of Sage CRM. These objects can be used in field level scripts; Create and Validate and also in TableLevel scripts and Workflow JScript conditions. The are sometimes...
  • Blog Post: Reporting on Customizations

    One of the chief advantages of Sage CRM is that it is meta data based. The definitions of screens, lists and business rules like workflow are all stored in the database. If you change the definition in the database then it immediately changes the system with out need to recompile or otherwise 'deploy'...
  • Blog Post: A Universal "Go Back" button in Workflow

    This article has been edited (1st November 2009) to correct links and make the code follow the convention introduced in Sage CRM 6.2 The requirement to allow the user to fall back to an earlier point in the workflow is usually handled by looping. We can see from the diagram below how a workflow...