Methods and systems for upgrading and installing application packages to an application platform

• US 9,870,218 B2
• Filed: 04/18/2016
• Issued: 01/16/2018
• Est. Priority Date: 10/03/2006
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Hofhansl, Lars, Jensen-Horne, Nathan, Hansma, Scott, Tamm, Steven, Weissman, Craig
• Primary Examiner(s): Dao, Thuy
• Application Number:
  US15/132,128
• Publication Number:
  US 20160231994A1
• Time in Patent Office: 638 Days
• CPC Class Codes: G06F 21/563 by source code analysis
• CPC Class Codes: G06F 2221/033 Test or assess software
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• 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

Abstract

Systems and methods for installing and upgrading application packages to an application platform. Application packages may be uploaded to a directory by developing users (developers) for installation by subscribing users (subscribers). Alternatively, a developer may send identification information to a subscribing user to allow that user to access and install that application package created by the developer. Application packages may also be upgraded. If a developer changes the original source package, a subscriber can choose to pull into their organization the change(s) made by the publisher while preserving any data rows the subscriber had created since first importing the package.

Claims

1. A method for upgrading application packages installed to an application platform and managed by an on-demand database service, comprising:

responsive to receiving from a first subscriber a selection of an application package that includes metadata components, installing the application package to the first subscriber on an application platform of the on-demand database service;

receiving, from a developer, a new version of the installed application package, the new version of the installed application package including (i) any new metadata component or components relative to a prior version of the new version of the installed application package and (ii) any changes to a metadata component of the prior version of the new version of the installed application package;

enforcing restrictions on modification of software entities in the new version of the installed application package, wherein the restrictions prevent the developer from making invalid changes to custom field types and application programming interface (API) names of the installed application package;

informing the first subscriber of the new version of the installed application package; and

responsive to receiving from the first subscriber a selection of the new version of the installed application package, installing the new version of the installed application package on the application platform.

2. The method of claim 1, wherein the installing of the new version includes installing the new metadata component or components and/or the changes to a metadata component of the prior version of the new version of the installed application package.

3. The method of claim 1,

wherein the selection of the new version is received from a second subscriber, and

wherein the installing of the new version includes installing metadata components of the prior version of the new version of the installed application package and the new metadata component or components and/or the changes to the metadata component of the prior version of the new version of the installed application package.

4. The method of claim 1, wherein the metadata components of the installed application package include one or more of a standard object, a custom objects, a custom field, code or a formula.

5. The method of claim 1, wherein if the developer indicated that a specific metadata component in the installed application package is a component that cannot be modified, not applying any changes attempted to be made to the specific metadata component by a subscriber or the developer.

6. The method of claim 1, wherein if the developer indicated that a specific metadata component in the installed application package is modifiable, allowing a subscriber to modify the specific metadata component in the installed application package.

7. The method of claim 1,

wherein the installed application package is marked as managed, and

wherein the method further includes restricting modification of metadata objects, fields, code, or formulas of the installed application package based on package management restrictions.

8. The method of claim 1,

wherein the new version of the installed application package contains code and metadata used to identify resource requirements for installing the new version of the installed application package, and

wherein the method further comprises, before installing the new version of the installed application package, verifying that the resource requirements are met.

9. A non-transitory computer-readable medium storing computer code for controlling one or more processor components to manage installation and upgrading of application packages to an application platform in an on-demand database service, the computer code including instructions to:

responsive to receiving from a first subscriber a selection of an application package that includes metadata components, install the application package to the first subscriber on an application platform of the on-demand database service;

receive, from a developer, a new version of the installed application package, the new version of the installed application package including (i) any new metadata component or components relative to a prior version of the new version of the installed application package and (ii) any changes to a metadata component of the prior version of the new version of the installed application package;

enforce restrictions on modification of software entities in the new version of the installed application package, wherein restrictions prevent the developer from making invalid changes to custom field types and application programming interface (API) names of the installed application package;

inform the first subscriber of the new version of the installed application package; and

responsive to receiving from the first subscriber a selection of the new version of the installed application package, install the new version of the installed application package on the application platform.

10. The non-transitory computer-readable medium of claim 9, wherein the instructions to install the new version includes instructions to install the new metadata component or components and/or the changes to a metadata component of the prior version of the new version of the installed application package.

11. The non-transitory computer-readable medium of claim 9,

wherein the selection of the new version is received from a second subscriber, and

wherein the instructions to install the new version includes instructions to install metadata components of the prior version of the new version of the installed application package and the new metadata component or components and/or the changes to a metadata component of the prior version of the new version of the installed application package.

12. The non-transitory computer-readable medium of claim 9, wherein the metadata components of the installed application package include one or more of a standard object, a custom objects, a custom field, code or a formula.

13. The non-transitory computer-readable medium of claim 9, wherein the computer code further includes instructions to not apply any changes attempted to be made to a specific metadata component by a subscriber or the developer if the developer had indicated that that the specific metadata component in the installed application package is a component that cannot be modified.

14. The non-transitory computer-readable medium of claim 9, wherein the computer code further includes instructions to allow a subscriber to modify a specific metadata component in the installed application package if the developer had indicated in the installed application package that the specific metadata component is a component that is modifiable.

15. The non-transitory computer-readable medium of claim 9,

wherein the installed application package is marked as managed, and

wherein the computer code further includes instructions to restrict modification of metadata objects, fields, code, or formulas of the installed application package based on package management restrictions.

16. The non-transitory computer-readable medium of claim 9,

wherein the new version of the installed application package contains code and metadata used to identify resource requirements for installing the new version of the installed application package, and

wherein the computer code further includes instructions to, before installing the new version of the installed application package, verify that the resource requirements are met.

17. A system for managing installation and upgrades of application packages installed to an application platform in an on-demand database service, the system comprising:

a database system for storing metadata components; and

one or more processors configured to;

responsive to receiving from a first subscriber a selection of an application package that includes metadata components, install the application package to the first subscriber on an application platform of the on-demand database service;

receive, from a developer, a new version of the installed application package, the new version of the installed application package including (i) any new metadata component or components relative to a prior version of the new version of the installed application package and (ii) any changes to a metadata component of the prior version of the new version of the installed application package;

enforce restrictions on modification of software entities in the new version of the installed application package, wherein restrictions prevent the developer from making invalid changes to custom field types and application programming interface (API) names of the installed application package;

inform the first subscriber of the new version of the installed application package; and

responsive to receiving from the first subscriber a selection of the new version of the installed application package, install the new version of the installed application package on the application platform.

18. The system of claim 17,

wherein if the selection of the new version is received from the first subscriber, the installation of the new version includes an install of the new metadata component or components and/or the changes to a metadata component of the prior version of the new version of the installed application package, and

wherein if the selection of the new version is received from a second subscriber, the installation of the new version includes installing metadata components of the prior version of the new version of the installed application package and the new metadata component or components and/or the changes to the metadata component of the prior version of the new version of the installed application package.

19. The system of claim 17,

wherein the installed application package is marked as managed, and

wherein the one or more processors are further configured to restrict modification of metadata objects, fields, code, or formulas of the installed application package based on package management restrictions.

20. The system of claim 17,

wherein the new version of the installed application package contains code and metadata used to identify resource requirements for the installation of the new version of the installed application package, and

wherein the one or more processors are further configured to, before installing the new version of the installed application package, verify that the resource requirements are met.