Abstract: Methods, devices and systems for providing a user interface in an on-demand software service environment are described. Some implementations involve receiving a component request from a first client device, locating class-level definition source code for a component definition corresponding to the component request, identifying the component definition within the source code, determining a language of the component definition and selecting a parser according to the language of the component definition. Such implementations may also involve parsing the source code to create the component definition and transmitting an intermediate representation of the requested component to the client device. The intermediate representation may allow the client device to create an instance of the requested component.

Abstract: Methods and systems are provided that aid users in customizing notification graphical user interface (GUI) components. In some aspects, the customization interface is driven from the notification interface or window. Users may then manage the position and appearance of a notification window or GUI component from the notification itself. In addition, the user can manage the position of a notification and direction of subsequent notifications from an originating notification.

Abstract: Methods, devices and systems for providing a user interface in an on-demand software service environment are described. Some implementations involve receiving an indication of a component definition to instantiate. The component definition may be a portion of a component definition data structure. Such implementations may also involve instantiating the provided component, instantiating all remaining attributes of the component definition data structure to produce a component instance data structure and transmitting an intermediate representation of the indicated component to a client device. The intermediate representation may comprise a version of the component instance data structure. The intermediate representation may allow the client device to create an instance of the component in memory.

Abstract: A method of accessing feeds based on metrics is provided. Feeds, each associated with an object stored in a database system, are provided to users of the database system. Inferential user interaction data captures implicit user behavior of users of the database system, wherein the data is generated in relation to a feed. Feed metrics are determined based on the user interaction data, wherein a feed metric is based upon statistics comprising user consumption, user responsiveness, content proliferation, and feed life. Finally, an action is executed in relation to at least one feed based on the feed metrics, wherein the action comprises discontinuing the feed, characterizing a feed, determining that a feed can be monetized, determining that a feed should be cached, or determining that intervention in a feed is advisable.

Abstract: In accordance with embodiments disclosed herein, there are provided systems, devices, and methods for testing methods in a multi-tenant database environment, including, for example, hosting a plurality of customer codebases within a host organization, where each of the plurality of customer codebases includes a plurality of operational statements and one or more test methods. Such a method further includes generating a first test result set by executing the one or more test methods associated with each of the plurality of customer codebases against a production release codebase of the host organization; generating a second test result set by executing the one or more test methods associated with each of the plurality of customer codebases against a pre-release codebase of the host organization; and identifying errors associated with the pre-release codebase based on a comparison of the first test result set and the second test result set.

Abstract: Example embodiments include a system and method for managing and viewing dependencies between Scrum teams working on a software release. In one embodiment, all dependency information for a release is stored in database objects on the cloud and dependencies are viewed on a user system coupled to the cloud. User interfaces for viewing, editing and creating dependencies are built on the cloud for display and interaction on the user system.

Abstract: Methods, devices and systems for providing a user interface in an on-demand software service environment are described. Some implementations involve receiving a component request from a first client device and building or retrieving component definitions corresponding to the component request. The implementations may also involve instantiating the component definitions and obtaining data and metadata for the component instances. Such implementations may also involve serializing the component definitions, component instances, the data and the metadata, and returning a response to the first client device. The response may include serialized instantiated component definitions, serialized data for the instantiated component definitions and serialized metadata for the instantiated component definitions.

Abstract: Systems and methods for sharing document annotations. A document is displayed on a graphical user interface and first annotation information for the document is created by a first user, the annotation information including first annotations and positioning information for positioning a first overlay window relative to the document. The first overlay window with the first annotations is displayed over the document wherein the document is visible through the first overlay window. The annotation information is sharable with other users, whereby a different user is able to display the overlay with annotations made by the first user over the document on a different system, and the annotations do not modify the underlying document.

Abstract: A system and method for providing features in a database system. In one embodiment, a method includes receiving, from a user, a request for a feature, where the feature is a functionality of the database system. The method further includes upgrading the database system, where the upgrading includes one or more provisioning steps that are based on the request from the user.

Abstract: Methods and systems for efficient API integrated login in a multi-tenant database environment and for decreasing latency delays during an API login request authentication including receiving a plurality of API login requests at a load balancer of a datacenter, where each of the plurality of API login requests specify a user identifier (userID) and/or an organizational identifier (orgID), fanning the plurality of API login requests across a plurality of redundant instances executing within the datacenter, assigning each API login request to one of the plurality of redundant instances for authentication, and for each of the respective plurality of API login requests, performing a recursive query algorithm at the assigned redundant instance, at one or more recursive redundant instances within the datacenter, and at a remote recursive redundant instance executing in a second datacenter, as necessary, until the login request is authenticated or determined to be invalid.

Abstract: Categorizing data in an on-demand database environment is provided. The categorized data is accessed to provide results based on statistical likelihood that records provide a desired result of a query. The categorization of the data includes organizing queries based on semantic terms, with categorization based on a multidimensional categorization of data in the database environment. The generating of results includes accessing relationship metadata both for individual records and for categories. Relationships along the same category, or among categories can provide records that may answer the query. The relationships and statistics are updated based on usage of the results data. Records and relationships identified as being used to solve the query, or being a desired solution to the query, can be weighted more heavily, thus increasing the likelihood of providing the most relevant data for subsequent queries.

Abstract: A system and method for providing a timeline control in a multi-tenant database system. In one embodiment, a method includes determining a plurality of entitlement processes and milestones that are to be enforced, where each entitlement process includes one or more actions, and where each action is associated with a corresponding milestone. The method further includes displaying a timeline control window that shows one or more milestones for an entitlement process, and updating the timeline control window as the status of the entitlement process changes.

Abstract: Methods and systems are described for determining candidates for a custom index in a multi-tenant database environment. In one embodiment, a method includes, capturing a query that is directed to a multi-tenant database, determining whether the captured query is a candidate for an additional filter, determining operators used by the captured query if the query is a candidate, determining data types of the database used by the captured query if the query is a candidate, determining whether there is a current filter for the operator and data types used by the captured query if the query is a candidate, selecting the captured query based on the determined operators, data types, and the determined current filters, and generating a custom index for the selected query.

Abstract: Systems and methods are described for communicating between a client machine and a server. A security token message may be transmitted from the server to the client machine. The security token message may include a first security token. The first security token may include a communication interaction identifier that identifies a communication interaction between the client machine and the server and an action request identifier that identifies an action request message capable of being sent from the client machine to the server to request that an action be performed on the server. An action request message including a second security token and transmitted in association with the communication interaction may be received at the server. When it is determined that the first security token matches the second security token, the requested action may be performed.

Abstract: A method for software performance analysis and debugging in a multi-tenant database network system is provided. In at least one embodiment, sampling is achieved using configuration files of each server cluster. Knowledge of the host names of each server in the cluster enables a profiler to target a single server for each sample, thereby facilitating a round-robin sample across a clustered server environment such that a CPU's load and processing cost associated to sampling is fairly and uniformly distributed across all servers in the cluster. As a result, in at least one embodiment of the analysis and debugging tool each sample is a complete stack trace dump of each thread running on the application server at that moment in time.

Abstract: A compositional recommender framework using modular recommendation functions is described. Each modular recommendation function can use a discrete technology, such as using clustering, a database lookup, or other means. A first recommendation function can recommend to a user items, such as books to check out, automobiles to purchase, people to date, etc. Another modular recommendation function can be daisy chained with the first to recommend items that are similar or related to the first recommended items, such as users who have also checked out the same recommended book, trailers that can be towed by the recommended automobiles, or vacations booked by people that were recommended as people to date. The modular recommendation functions can be used to build customized recommendation engines for different industries.

Abstract: Disclosed herein are techniques for testing a page. In some implementations, an intermediate representation of a page is created. The page may be defined by a page description implemented in a markup language. The page description may refer to data accessible via a data model. The intermediate representation may include at least a portion of the data accessible via the data model. The intermediate representation may be capable of being rendered to create a rendered page. The rendered page may be capable of being displayed on a display device. A determination may be made as to whether a test value for a portion of the intermediate representation matches an expected value for the portion of the intermediate representation. When the test value does not match the expected value, an indication of an error may be stored.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for query optimization in a database system. These mechanisms and methods for query optimization in a database system can enable embodiments to optimize OR expression filters referencing different logical tables. The ability of embodiments to optimize OR expression filters referencing different logical tables can enable optimization that is dynamic and specific to the particular tenant for whom the query is run and improve the performance and efficiency of the database system in response to query requests.

Abstract: A system and method for providing administrative capabilities in a multi-tenant database system. In one embodiment, a method includes providing a portal for a database system to a user, providing administrative capabilities through the portal, and enabling the user to manage objects in the database system using the administrative capabilities.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for validating queries. These mechanisms and methods for validating queries can enable embodiments to provide more reliable and faster execution of queries both in development and in production. In an embodiment and by way of example, a method for validating queries is provided. The method embodiment includes capturing a query that is directed to a multi-tenant database. A plan is determined by which the query will be applied to the database. The plan is statically analyzed for performance. Then a performance measure is applied to the query.