View more results: All Community | Partner Community
  • Blog Post: Workflow and Web Services

    The CRM Webservices API allows the change of the data in the record or set of records being manipulated but it can't invoke the workflow behaviour to change the workflow state. You can have a Web Services call change the stage and the status fields and any other data field you want but the workflowstate...
  • Blog Post: Using a TableLevel script to Update Submitted Values

    This article has been updated 22nd May 2009 to ensure the code follows the convention introduced in Sage CRM 6.2. Imagine you have a requirement to a ensure that a particular opportunity field contains certain data as an Opportunity record is inserted. In addition this information should be partially...
  • Blog Post: Taking a Snapshot of Currency Exchange Values

    Sage CRM offers Multi Currency features. This allows, for example, a Sales user in the UK to quote in Sterling for their British Customers and to Quote in Euros for their German customers. The Sales Manager in Ireland can then see both quotes expressed in Euros or a financial controller in the US could...
  • Blog Post: Modify field on another table in a workflow action

    When choosing a field for the Display Field For Amendment action, you can select fields from the view that are not on the table the rule is based on. For example you can select the comp_primaryuserid if you use the vSummaryOpportunity view to base your rule on. However this will not work by design: You...
  • Blog Post: Conditionally send e-mail on entity creation

    It is common to have CRM send out an e-mail on the creation of a new entity. For example you may have an e-mail sent to the assigned user on a new Opportunity notifying them that a the Opportunity has been created and that it is assigned to them. This is achieved by putting a Send E-mail action on the...
  • 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...