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

• US 9,348,576 B2
• Filed: 12/02/2013
• Issued: 05/24/2016
• Est. Priority Date: 10/03/2006
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Hofhansl, Lars, Hansma, Scott, Jensen-Horne, Nathan, Tamm, Steven, Weissman, Craig
• Primary Examiner(s): Dao, Thuy
• Application Number:
  US14/094,738
• Publication Number:
  US 20140173582A1
• Time in Patent Office: 904 Days
• US Class Current: 1/1
• 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:

storing an uploaded application package at a directory that is accessible by a plurality of subscribers, the application package being created by a developer and including a set of metadata components;

wherein application packages subject to a name conflict are enhanced with explicit namespace declarations;

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

receiving, from the developer, a new version of the uploaded application package at the directory;

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

storing the new version, wherein the stored new version includes a) any new metadata component or components relative to a prior version, b) any changes to a metadata component of a prior version;

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

responsive to receiving from the first subscriber a selection of the new version, installing the new version to the first subscriber.

2. The method of claim 1, wherein the selection of the new version is received from the first subscriber, and wherein installing the new version includes installing the new metadata component or components and/or any changes to a metadata component of the prior version.

3. The method of claim 1, wherein the selection of the new version is received from a second subscriber, and wherein installing the new version includes installing the metadata components of the prior version of the application package and the new metadata component or components and/or any changes to a metadata component of the prior version.

4. The method of claim 1, wherein the set of metadata components includes 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 metadata component in a uploaded package is a component that cannot be modified, not applying any changes attempted to be made to that metadata component by a subscriber or the developer.

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

7. The method of claim 1, wherein the application package is marked as managed, further including restricting modification of the application package metadata objects, fields, code, or formulas based on package management restrictions.

8. The method of claim 1, wherein the application package contains code and metadata used to identify resource requirements for the installation of the application package, before installing the application package to the first subscriber, 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 code including instructions to:

include in application packages subject to a name conflict an enhancement including explicit namespace declarations;

store an uploaded application package at a directory that is accessible by a plurality of subscribers, the application package being created by a developer and including a set of metadata components;

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

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

responsive to receiving from the developer a new version of the uploaded application package, store the new version to the directory, wherein the stored new version includes a) any new metadata component or components relative to a prior version and b) any changes to a metadata component of a prior version;

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

responsive to receiving from a subscriber a selection of the new version, install the new version to that subscriber.

10. The non-transitory computer-readable medium of claim 9, wherein the selection of the new version is received from the first subscriber, and wherein the instructions to install the new version includes instructions to install the new metadata component or components and/or any changes to a metadata component of the prior version.

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 the metadata components of the prior version of the application package and the new metadata component or components and/or any changes to a metadata component of the prior version.

12. The non-transitory computer-readable medium of claim 9, wherein the set of metadata components includes 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 code further includes instructions to not apply any changes attempted to be made to a metadata component by a subscriber or the developer if the developer had indicated that that metadata component in the uploaded package is a component that cannot be modified.

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

15. The non-transitory computer-readable medium of claim 9, wherein the application package is marked as managed, further including restricting modification of the application package metadata objects, fields, code, or formulas based on package management restrictions.

16. The non-transitory computer-readable medium of claim 9, wherein the application package contains code and metadata used to identify resource requirements for the installation of the application package, before installing the application package to the first subscriber, verifying 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;

include in application packages subject to a name conflict an enhancement including explicit namespace declarations;

store an uploaded application package to a directory portion of the database that is accessible by a plurality of subscribers, the application package including a set of metadata components created and uploaded to the directory by a developer;

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

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

responsive to receiving from the developer a new version of the uploaded application package, store the new version to the directory, wherein the stored new version includes a) any new metadata component or components relative to a prior version and b) any changes to a metadata component of a prior version;

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

responsive to receiving from a subscriber a selection of the new version, install the new version to that subscriber.

18. The system of claim 17, wherein if the selection of the new version is received from the first subscriber, installation of the new version includes an install of the new metadata component or components and/or any changes to a metadata component of the prior version, and wherein if the selection of the new version is received from a second subscriber, installation of the new version includes an install of the metadata components of the prior version of the application package and the new metadata component or components and/or any changes to a metadata component of the prior version.

19. The system of claim 17, wherein the application package is marked as managed, further including restricting modification of the application package metadata objects, fields, code, or formulas based on package management restrictions.

20. The system of claim 17, wherein the application package contains code and metadata used to identify resource requirements for the installation of the application package, before installing the application package to the first subscriber, verifying that the resource requirements are met.