System, method and computer program product for creating an application within a system

• US 9,195,438 B2
• Filed: 10/09/2013
• Issued: 11/24/2015
• Est. Priority Date: 12/19/2012
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Toens, Simon, Li, Eugene, Wang, Sheng, Torman, Adam, Smith, Andrew, Kwong, Herman
• Primary Examiner(s): Mitchell, Jason
• Assistant Examiner(s): APONTE, FRANCISCO JAVIER
• Application Number:
  US14/050,299
• Publication Number:
  US 20140173553A1
• Time in Patent Office: 776 Days
• Field of Search: 717100-178
• US Class Current: 1/1
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 9/44584 Portable applications, i.e. making applications self-contained, e.g. U3 standard

Abstract

In accordance with embodiments, there are provided mechanisms and methods for creating an application within a system. These mechanisms and methods for creating an application within a system can enable improved application diversity and productivity, enhanced customer experience, increased user flexibility, etc.

Claims

1. A computer program product embodied on a non-transitory computer readable medium, the computer program product including computer code adapted to be executed by a computer to perform a method comprising:

receiving, at a system, a request to create an application having one or more components;

creating the application within the system, based on the request, the created application including a module having the one or more components of the application;

defining, within the system, a unique namespace for the created application and dictating the unique namespace within the module;

defining, within the system, a permission level for the unique namespace;

limiting, through the system, access to components of the created application by applications outside of the unique namespace, in accordance with the permission level defined for the unique namespace;

preventing, through the system, access by the components of the created application to metadata outside of the unique namespace when the permission level defined for the unique namespace dictates that the access by the components of the created application to the metadata outside of the unique namespace is disallowed;

wherein the system implements a module directory to distinguish between an application component type within the system and an application module within the system having a same name.

2. The computer program product of claim 1, wherein the system includes a multi-tenant on-demand database system.

3. The computer program product of claim 1, wherein the request is received from a user associated with an organization registered within the system.

4. The computer program product of claim 1, wherein the request includes code used for creating the application.

5. The computer program product of claim 1, wherein the request is created utilizing an interface of the system.

6. The computer program product of claim 1, wherein the application includes a standalone application.

7. The computer program product of claim 1, wherein the application is created within and associated with an organization of the system and is isolated from all other applications within the system, such that data accessed by the application cannot be accessed by any other applications within the system.

8. The computer program product of claim 1, wherein the application includes a manifest that includes one or more details of the application, including an identifier of the application.

9. The computer program product of claim 1, wherein the module includes a container containing metadata, where such metadata is named, organized, and called utilizing the unique namespace for the application.

10. The computer program product of claim 9, wherein the metadata includes configuration information that dictates how the application is used.

11. The computer program product of claim 9, wherein the metadata includes one or more schemas or programmatic elements associated with the application.

12. The computer program product of claim 1, wherein the permission level includes one of:

allowing the components of the created application to be accessed by the applications outside of the unique namespace, disallowing the components of the created application to be accessed by the applications outside of the unique namespace.

13. A method, comprising:

receiving, at a system, a request to create an application having one or more components;

creating the application within the system, based on the request, the created application including a module having the one or more components of the application;

defining, within the system, a unique namespace for the created application and dictating the unique namespace within the module;

defining, within the system, a permission level for the unique namespace;

limiting, through the system, access to components of the created application by applications outside of the unique namespace, in accordance with the permission level defined for the unique namespace;

preventing, through the system, access by the components of the created application to metadata outside of the unique namespace when the permission level defined for the unique namespace dictates that the access by the components of the created application to the metadata outside of the unique namespace is disallowed;

wherein the system implements a module directory to distinguish between an application component type within the system and an application module within the system having a same name.

14. An apparatus, comprising:

a processor of a system for;

receiving, at the system, a request to create an application having one or more components;

creating the application within the system, based on the request, the created application including a module having the one or more components of the application;

defining, within the system, a unique namespace for the created application and dictating the unique namespace within the module;

defining, within the system, a permission level for the unique namespace;

limiting, through the system, access to components of the created application by applications outside of the unique namespace, in accordance with the permission level defined for the unique namespace;

preventing, through the system, access by the components of the created application to metadata outside of the unique namespace when the permission level defined for the unique namespace dictates that the access by the components of the created application to the metadata outside of the unique namespace is disallowed;

wherein the system implements a module directory to distinguish between an application component type within the system and an application module within the system having a same name.