Browse By Tags

  • Blog Post: Distinguishing Between Primary Workflow Rules in Create Scripts

    In Sage CRM it is possible to have multiple workflows created for an Entity. For example we may have one Opportunity workflow that is used by a one team for a particular type of sales opportunity and another workflow that is used for a different type of sales process. The different workflows may...
  • Blog Post: Populating Default Date Field Values

    This article has been updated. Create Script example Date/Time fields can can have their values set by using the DefaultType property. If DefaultType set to 6 then the field displays the Current Date/Time DefaultType = 6; If DefaultType set to 14 then the field displays the Current Date/Time plus...
  • Blog Post: Company and Person Workflow Progress with Tracking tab in CRM

    Many thanks must go to a colleague in the UK professional services team for this article. Introduction Customers often request the ability to track Company or Person changes in much the same way that CRM offers with Opportunity and Case entities. As standard, CRM does not offer a CompanyProgress...
  • 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: A Universal "Go Back" button in Workflow

    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 can allow a user to drop back and repeat or cycle through certain workflow states again and again. But what if we need to have a workflow...