Browse By Tags

  • Blog Post: Building a Workflow Map Diagram that Shows Progress through Workflow

    Workflows in Sage CRM can become long and a user may wish they had a version of the diagram that is available when the workflow is constructed. You can see from this image below that an extra button has been added to the Opportunity screen. In this example application, when the 'Workflow Map'...
  • Blog Post: Calling CRM Actions

    The CRM.URL() method is used to allow you to build correctly formatted URLs that reach back into the application. Most commonly this is used to interact with ASP pages and with Sage CRM .NET application extensions. For example to build a button that calls an ASP page the code would look like: var...
  • Blog Post: Some thoughts on Sage CRM, FOP, PDF and Reports

    Sage CRM uses Apache FOP (Formatting Objects Processor) to generate its reports in PDF format. See http://xmlgraphics.apache.org/fop/ FOP is an example of a print formatter that uses XSL formatting objects (XSL-FO) and is in theory not tied to outputting in a particular format, although its usage...
  • Blog Post: How did I get Here?

    In this post I would like to consider how you can establish whether a page has just been called via a hyperlink (from the tab) or it has been called because "Save" action button has been pressed. Pages can be called either by direct hyperlinking to them or by clicking a "button"....
  • Blog Post: Listing System Actions

    System Actions are not formally part of the official API and there is no list of them in the documentation although there are plenty of articles that make use of them. The article "Calling CRM Actions" is a good introduction to how the inbuilt System Actions can be referenced in custom pages...
  • Blog Post: Oh botherations! Shoot, drat and darn!

    It just goes to show that this blog describes tips that could just as well be described as 'traps'. Like most of you I try and use tricks that sometimes inhabit the grey zone between what is possible and what shouldn't be done. The interface has several features that allow us ride on existing...
  • Blog Post: Changing Context when jumping between pages using the COM ASP API

    I have created a very simple page that contains a couple of buttons. The starting page is an ASP page in the context of the Opportunity. These buttons will allow me to jump to different places in the application. The first "company" button jump is built using var strCompanyButton = CRM...
  • Blog Post: How to Build Buttons that call the Email Editor using the COM ASP API

    This has article has been corrected and the code reformatted 17th October 2011. I have written before about building buttons that call the inbuilt system actions. The action code for the internal email editor is 1500. We can set up a new SendEmail button on a custom page that will either display...
  • Blog Post: The Forward and Back buttons (Page History) in code

    Creating your own forward and backwards buttons You can create buttons that make use of the internal system actions that control the forward and backward behaviour. var strForwardButton = CRM.Button("Forward","forward.gif",CRM.URL(522)); var strBackButton = CRM.Button("Back"...