Customer relationship management system and method

• US 8,489,543 B2
• Filed: 08/01/2008
• Issued: 07/16/2013
• Est. Priority Date: 08/12/2005
• Status: Active Grant

• Current Assignee: Sugarcrm Incorporated
• Original Assignee: Sugarcrm Incorporated
• Inventors: Taylor, Jacob, Roberts, John, Oram, Clinton, Dreisch, Andrew, Gupta, Ajay, Itani, Majed, Ostrow, Julian, Parsons, Joseph
• Primary Examiner(s): Lewis, Cheryl
• Assistant Examiner(s): Hoffler, Raheem
• Application Number:
  US12/185,001
• Publication Number:
  US 20090070755A1
• Time in Patent Office: 1,810 Days
• Field of Search: None
• US Class Current: 707/601
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A software-based customer relationship management system and method.

Claims

1. An upgrade method for an open source software application on a system, the method comprising:

receiving, at a system with an installation of an existing open source software application, an upgrade package to upgrade the existing open source software application;

identifying, by the system with the installation of an existing open source software application, for each file in the upgrade package, if the file does not match a prior version of the file in the existing open source software application in order to indicate a file in the existing open source software application that has been customized by the user of the existing open source software application;

automatically upgrading, on the system with the installation of an existing open source software application, the files in the upgrade package that are not identified as being customized; and

selectively, based on one of user instructions and default logic, upgrading the files on the system with the installation of an existing open source software application identified as being customized so that the customizations of the user of the existing open source software application are not lost during the upgrade process.

2. The method of claim 1, wherein identifying the customized file further comprises computing a checksum for each file in the upgrade package and comparing the computed checksum against known checksum values for the file from a previously installed version of the software application.

3. The method of claim 2, wherein computing the checksum further comprises computing an MD5 checksum.

4. The method of claim 2, wherein computing the checksum further comprises computing an MD5 checksum that is independent of line feeds, source code control system tags, and/or changes to whitespace in the source code.

5. The method of claim 2 further comprising storing the upgrade package in a staging folder.

6. The method of claim 1 further comprising ensuring, before the files are upgraded, that the system capable of being upgraded to the upgrade for the existing open source software application.

7. The method of claim 2, wherein identifying the customized file further comprises identifying, for each file in the upgrade package, the file as not being customized if the checksum for the file is equal to the known checksum values for the file from a previously installed version of the software application.