View more results: All Community | Partner Community
  • 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: 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...