Changing records associated with a software application

• US 8,566,283 B2
• Filed: 08/31/2010
• Issued: 10/22/2013
• Est. Priority Date: 08/31/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Williams, Alexis, Mastrogiovanni, Analia, Hatton, James
• Primary Examiner(s): ALAM, SHAHID AL
• Application Number:
  US12/873,243
• Publication Number:
  US 20120054250A1
• Time in Patent Office: 1,148 Days
• Field of Search: 707/638, 707/640, 717/124
• US Class Current: 707/640
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27

Abstract

A system and method for changing records associated with a software application. In one embodiment, a method includes receiving a change command to change a record type for a record that is associated with code that is submitted for integration into a software application; receiving a selection of a new record type; populating a new record format with information that is associated with the code; and receiving a save command to save the record.

Claims

1. A method comprising:

receiving, by a database system implementing a cloud platform, information associated with code submitted for integration into a software application implemented on the cloud platform, wherein the code is for new functionality that is added to the software application, the database system entering the information associated with the code into a record;

receiving, by the database system, a change command to change a record type for the record that is associated with the code;

receiving a selection of a new record type;

populating, by the database system, a new record format corresponding to the new record type with the information associated with the code that is common to the new record format to change from an old record type associating the code with a bug fix to the new record type associating the code with a user story; and

receiving a save command to save the record.

2. The method of claim 1, wherein the record type is changed from an old record type having an old record format to the new record type having the new record format, and wherein the new record format is populated with information that is common to information that is associated with the old record format and the new record format.

3. The method of claim 1, further comprising:

receiving additional information associated with the code; and

populating the new record format with the received additional information.

4. The method of claim 1, wherein the selection of the new record type is received via a page dedicated to receiving selections of new record types.

5. The method of claim 1, wherein the information associated with the code includes one or more of a description of the code, a purpose of the code, a URL of the code, a user who wrote the code, and a reviewer of the code.

6. The method of claim 1, further comprising generating, by the database system, a stamp included in the record, wherein the stamp is associated with a particular release of the software application.

7. The method of claim 1, wherein the code provides a change to the software application.

8. A non-transitory computer-readable storage medium having one or more instructions thereon for changing records associated with a software application implemented on a cloud platform of a database system, the instructions when executed by a processor causing the processor to:

enter information associated with code submitted for integration into the software application into a record, wherein the code is for new functionality that is added to the software application;

receive a change command to change a record type for the record that is associated with the code;

receive a selection of a new record type;

populate a new record format corresponding to the new record type with the information associated with the code that is common to the new record format to change from an old record type associating the code with a bug fix to the new record type associating the code with a user story; and

receive a save command to save the record.

9. The computer-readable storage medium of claim 8, wherein the record type is changed from an old record type having an old record format to the new record type having the new record format, and wherein the new record format is populated with information that is associated with the old record format and the new record format.

10. The computer-readable storage medium of claim 8, wherein the instructions further cause the processor to:

receive additional information associated with the code; and

populate the new record format with the received additional information.

11. The computer-readable storage medium of claim 8, wherein the selection of the new record type is received via a page dedicated to receiving selections of new record types.

12. An apparatus for changing records associated with a software application implemented on a cloud platform of a database system, the apparatus being configured to:

enter information associated with code submitted for integration into the software application into a record, wherein the code is for new functionality that is added to the software application;

receive a change command to change a record type for the record that is associated with the code;

receive a selection of a new record type;

populate a new record format corresponding to the new record type with the information associated with the code that is common to the new record format to change from an old record type associating the code with a bug fix to the new record type associating the code with a user story; and

receive a save command to save the record.

13. The apparatus of claim 12, wherein the record type is changed from an old record type having an old record format to the new record type having the new record format, and wherein the new record format is populated with information that is common to information that is associated with the old record format and the new record format.

14. The apparatus of claim 12, wherein the instructions further cause the processor to:

receive additional information associated with the code; and

populate the new record format with the received additional information.

15. A method comprising:

receiving, by a database system implementing a cloud platform, information associated with code submitted for integration into a software application implemented on the cloud platform, wherein the code is for a fix to a bug;

receiving, by the database system, a change command to change a record type for the record that is associated with the code;

receiving a selection of a new record type;

populating, by the database system, a new record format corresponding to the new record type with the information associated with the code that is common to the new record format to change from an old record type associating the code with a user story to the new record type associating the code with a bug fix; and

receiving a save command to save the record.

16. A non-transitory computer-readable storage medium having one or more instructions thereon for changing records associated with a software application implemented on a cloud platform of a database system, the instructions when executed by a processor causing the processor to:

enter information associated with code submitted for integration into the software application into a record, wherein the code is for a fix to a bug;

receive a change command to change a record type for the record that is associated with the code;

receive a selection of a new record type;

populate a new record format corresponding to the new record type with the information associated with the code that is common to the new record format to change from an old record type associating the code with a user story to the new record type associating the code with a bug fix; and

receive a save command to save the record.

17. An apparatus for changing records associated with a software application implemented on a cloud platform of a database system, the apparatus being configured to:

enter information associated with code submitted for integration into the software application into a record, wherein the code is for a fix to a bug;

receive a change command to change a record type for the record that is associated with the code;

receive a selection of a new record type;

populate a new record format corresponding to the new record type with the information associated with the code that is common to the new record format to change from an old record type associating the code with a user story to the new record type associating the code with a bug fix; and

receive a save command to save the record.