Salesforce Com, Inc.

Salesforce, Inc.

James Bock Wunderlich

Jeffrey Michael Bartolotta

Michael Dwayne Miller

Dileep Burki

Josh Kaplan

Vamshidhar Rao Gandham

Mark Wilding

Avrom Irwin Roy-Faderman

George Murnock

Gregory Darrell Fee

Samuel William Bailey

Peter S Wisnovsky

Nathan Edward Lipke

Nicholas Chun Yuan Chen

Forrest Junod

Michael Goldberg Boilen

Leo Duy Tran

Thomas Pollinger

Reid A Elliott

Miguel Canizares

Elizabeth Balsam

Michael Christopher Olson

Mike Boilen

Techniques are disclosed relating to installing and operating applications in a server-based application workspace. A computer system, while operating the server-based application workspace, may store subscription information indicating a user that is a developer for a particular application package, and one or more users that are subscribers for the particular application package. The computer system may further store lock data for the particular application package that indicates user permissions to edit at least one application component for the particular application package. Based on the lock data, the computer system may permit the developer to edit the at least one application component of the particular application package, and deny requests from the one or more users to edit the at least one application component.

Restricting access and edit permissions of metadata

Techniques are disclosed relating to database techniques for storing metadata for web applications. In some embodiments, a server computer system may operate a platform for executing one or more application modules that utilize one or more application components to implement an application. The server computer system may generate a first set of values indicative of versions of a first set of application modules specified by an application package stored on the server computer system for implementing the application. The server computer system may determine a second set of values indicative of versions of a second set of application modules specified by an updated application package for an upgrade of the application. The server computer system disables application components associated with application modules specified in the first, but not the second, set of values.

Version management automation and consistent application builds for different target systems

Techniques and structures to provide smart packaging in a database environment. A package and a set of customizations corresponding to the package are detected. The package with the set of customizations are bundled to form an additive package such that the additive package provides for the set of customizations to remain bonded with the package throughout one or more processes including testing, deploying, and/or updating of the package.

Additive packaging through smart wrapping of packages and customizations in an on-demand environment

A system may include an application server and one or more tenants served by the application server. The application server may host a virtual machine with multiple isolated sub-environments. Each tenant of the application server may request to run a program in a tenant-specific sub-environment of the virtual machine. The sub-environments may be configured so the execution of one tenant's code does not affect execution of another tenant's code or the hosting virtual machine, for example, by considering the resources used to execute the code. The application server may implement techniques to securely execute 'untrusted' code, programmed using one or more different programming languages, in the sub-environments by enforcing resource restrictions and restricting the sub-environments from accessing the host's local file system. In this way, one tenant's code does not negatively impact execution of another tenant's code by using too many resources of the virtual machine.

Usage checks for code running within a secure sub-environment of a virtual machine

Techniques and architectures for creating scratch organizations in a multitenant environment. A scratch organization defined by metadata corresponding to a subject organization is generated. The metadata defines at least a set of privileges for the subject organization to be replicated in the scratch organization. Test data is loaded from a test source that is not the subject organization. Changes to the subject organization are not applied to the scratch organization after creation of the scratch organization and changes to the scratch organization are not applied to the subject organization. One or more test operations are performed on the scratch organization using the loaded test data. The scratch organization is destroyed after the one or more test operations have been performed.

Declarative signup for ephemeral organization structures in a multitenant environment

Apparatuses and techniques to utilize a scratch organization as a unit of virtualization. Potential hosts for a scratch organization are evaluated. The potential hosts include at least the first group of hardware processing devices and a second group of the plurality of hardware processing devices to provide remote client computing environments. A target host is selected from the potential hosts. The scratch organization to be hosted by the target host is generated. Data is loaded from a test source that is not the subject organization into the scratch organization. One or more test operations are performed on the scratch organization using the loaded data with the target host. The scratch organization is destroyed on the selected host after the one or more test operations have been performed.

Virtualization of ephemeral organization structures in a multitenant environment

Techniques and mechanisms for providing a functionality which is selectable to undo one or more changes to metadata in a computing environment. In an embodiment, one or more source objects, stored by a version control system (VCS), represent one or more previous metadata changes. In response to a detection of the one or more metadata changes, an element of a user interface is configured to be selectable for undoing the one or more metadata changes. In another embodiment, a subsequent selection of the element invokes a retrieval of the one or more source objects from the VCS. Based on the retrieval of the one or more source objects from the VCS, a compilation is performed to generate a program which is executed to undo the one or more metadata changes.

Techniques and architectures for providing functionality to undo a metadata change

Techniques and architectures for scratch organizations in a multitenant environment. A first scratch organization is generated based on a designated set of metadata defining at least a set of privileges for the first scratch organization. Test data is loaded into the first scratch organization from a source external to the first scratch organization. A designated test sequence is performed on the first scratch organization using test data. The test operations are defined by structures external to the first scratch organization and utilize the test data to generate test results. The first scratch organization is destroyed after extracting the test results. A second scratch organization is generated based on the designated set of metadata cause the second scratch organization to have the set of privileges.

Creation and utilization of ephemeral organization structures in a multitenant environment

Techniques are disclosed relating to database techniques for storing metadata for web applications. In some embodiments, manageable state information indicates whether certain entities (e.g., developers or subscribers) are allowed to edit particular fields (e.g., upon installing a version of an application package or when updating a package to a new version). In some embodiments, the manageable state information is stored separately from the corresponding metadata, which may avoid a need to query the metadata to determine manageable state and may allow validation of manageable state rules upon insertion of metadata into a new organization. In some embodiments, a short-lived build organization may facilitate validation of updates to web application packages.

Maintaining manageability state information distinct from managed metadata

Techniques and architectures for maintaining metadata version controls. A change to metadata within a computing environment is detected. Metadata subject to the change is decompiled into a source object that is in a format compatible with a version control system (VCS). The source object is stored in the VCS with relationship information to indicate a relationship to another source object, if the relationship is determined.

Techniques and architectures for maintaining metadata version controls

The technology disclosed describes systems and methods for implementing global profiling to track resource usage and performance for multiple threads across multiple servers for a cloud-based system. This disclosed technology provides global profiling to track resource usage across any part of a transaction as it passes between layers of a computing stack regardless of the language being executed, on logically different virtual machines across multiple servers. After data collection stops, the disclosed technology combines the results into a configurable profile view that accurately represents the order of execution of applications and methods, as though they ran on one machine. The disclosed technology builds multiple formats of the data files for different display visualizations.

Growing community of inventors

Burlingame, CA, United States of America

James Bock Wunderlich