Abstract: Disclosed herein are method, system and device embodiments for responding to a customer via a dynamic multi-channel publisher. An embodiment operates by providing a window in a graphical user interface (GUI) that provides access to a list of channels related to a customer, receiving a selection of a first channel from the list of channels in response to a request from the customer using a second channel from the list of channels, and updating the window with one or more message types and one or more action types corresponding to the first channel to respond to the request. The list of channels corresponds to multiple applications available to communicate with the customer, and the first channel is different from the second channel.

Abstract: Disclosed are examples of systems, apparatuses, methods and computer program products for maintaining flows to manage tasks assigned to a user of a database system. Further disclosed are examples of systems, apparatuses, methods and computer program products for sharing execution logic, including but not limited to running instances of flows, across different users of a database system.

Abstract: Systems and methods for an elastic cost-to-serve system including a first module to orchestrate an elastic server set; a second module to orchestrate a load test and to apply one or more use-case scenarios for each orchestrated server set; a third module to generate a cost metrics model of the orchestrated server set for predictive cost modeling; a fourth module coupled to the third module to collect a plurality of performance metrics across the server resources and associated client devices; a fifth module to post-process the collected performance metrics across a load testing duration and to provide analytics of the server set performance; and a sixth module coupled to analyze the performance metrics adapting available resources and to apply a heuristic of the cost metrics model to predict a model of cost optimization of the server set.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for storing documents that are being tracked in an on-demand service. These mechanisms and methods for storing documents in an on-demand service can enable embodiments to provide the sharing of documents and the storing of the documents in association with a tag. The ability of embodiments to provide the sharing of documents and the storing can enable an efficient searching for a shared document. In an embodiment, the shared document is categorized upon being stored.

Abstract: A request may be received to relocate source data within a distributed database system arranged in a hierarchy composed of a plurality of levels. The plurality of levels may include a local level that includes a plurality of pods, which may be end points in the hierarchy. The data may be stored at a source pod. The request may identify a designated level in the hierarchy at which to relocate the source data. A target pod within the distributed database system may be selected. The source pod and the target pod may be located remotely from one another. The data may be replicated to the target pod via a local change bus in communication with the source pod. The local change bus may capture changes made to data stored in the source pod and transmit the captured changes to the target pod via the hierarchy.

Abstract: Disclosed herein are system, method, and computer program product embodiments for generating and operating workbooks. One embodiment operates by causing display of a workbook having: a first page including a preview of a first object generated by a first online tool; and a second page including a preview of a second object generated by a second online tool. The first page and the second page are displayed simultaneously within the workbook. Then, a command to execute a function against the first object is received, via the workbook, from a user. A request to execute the function is transmitted to the first online tool, where execution of the function generates a revised first object. The embodiment also operates by receiving a revised first page comprising a preview of the revised first object from the first online tool, and replacing the first page in the workbook with the revised first page.

Abstract: A method and system to manage application package installation in a multi-tenant system is provided. The method includes accessing metadata of an application package for distribution in the multi-tenant system, selecting a component of the application package with a permission guard in the metadata, evaluating permission guard logic to determine wither a target tenant in the multi-tenant system can install the component, and compiling and installing the component in response to the permission guard logic indicating the tenant of the multi-tenant system has met conditions to utilize the component.

Abstract: Methods, systems, and devices for data retention handling are described. In some data storage systems, data objects are stored in a non-relational database schema. The system may support configurable data retention policies for different tenants, users, or applications. For example, a data store may receive retention requests, where the retention requests may specify deletion or exportation actions to perform on records contained within data objects. The data store may determine retention rules based on these retention requests, and may periodically or aperiodically evaluate the rules to determine active actions to perform. To improve the efficiency of the system, the data store may aggregate the active actions (e.g., according to the dataset to perform the actions on), and may generate work items corresponding to the aggregate actions. A work processor may retrieve these work items and may efficiently perform the data retention actions on datasets stored in the data object store.

Abstract: Methods, systems, and devices supporting data archiving are described. A device (e.g., an application server) may identify a set of archiving jobs for a first database (e.g., a relational database), where each archiving job indicates a set of data records for archiving. The device may receive a data record of the set of data records from the first database, where the data record is filtered by an abstraction layer (e.g., removing some information from the data record such that the filtered data record corresponds to a user's view of the data record). For example, the filtered data record may include a subset of the total information for the stored data record. The device may transform this received, filtered data record from a first format to a second format supported by a second database. The device may then send the transformed data record to the second database for storage.

Abstract: Methods, systems, and devices supporting data storage are described. A database system may store order information for an organization. This order information may span multiple steps of an order lifecycle, including order creation, order changes, order fulfillment, etc. To efficiently store order information for low-latency querying and data consistency, the database system may implement order summaries. For example, a database server may receive a new order data object associated with an order identifier and may create a corresponding order summary data object. If the database system receives any additional data objects associated with the same order identifier, the database server may update the order summary data object based on the additional data objects. If the database system receives a query for information related to the order, the system may retrieve queried values directly from the order summary data object, rather than aggregating data on-the-fly across multiple underlying data objects.

Abstract: Methods, systems, and devices for validation at an application server are described. The application server may validate a user device utilizing a public-private key pair, and may refrain from establishing a database connection until the user device is validated. For example, the application server may transmit a private key and a public key identifier to the user device. When the application server receives a session establishment message that is based on a private key and that contains the public key identifier, the application server may determine the public key of the public-private key pair based on the identifier. The application server may validate that the session establishment message is received from the user device based on the private key and the determined public key. Based on this validation procedure, the application server may establish a database connection with a database, granting the validated user device access to requested data.

Abstract: A method of training a predictive model to predict a likely field value for one or more user selected fields within an application. The method comprises providing a user interface for user selection of the one or more user selected fields within the application; analyzing a pre-existing, user provided data set of objects; training, based on the analysis, the predictive model; determining, for each user selected field based on the analysis, a confidence function for the predictive model that identifies the percentage of cases predicted correctly at different applied confidence levels, the percentage of cases predicted incorrectly at different applied confidence levels, and the percentage of cases in which the prediction model could not provide a prediction at different applied confidence levels; and providing a user interface for user review of the confidence functions for user selection of confidence threshold levels to be used with the predictive model.

Abstract: Methods and systems are provided for implementing session synchronization to synchronize applications at different user systems (e.g., mobile device, laptop, desktop, tablet) of a particular user. This platform level solution can maintain session information received any number of different user systems of the particular user and share this collective session information with each of the other user systems as session-synchronization information that can be used, at any user system of that user, to ensure that when that user switches from using one user system to another user system that applications at the “new” user system being switched to are synchronized with any other applications that were most recently in use at all of the other user systems of that user.

Abstract: A messaging system is provided that includes a first message server, a second message server and a distributed database system that stores a blockchain. The first message server receives a message from a first user system, and records at least one selected component of the message into a block of the blockchain stored in the distributed database system. When the second message server receives the message from the first message server, the second message server can determine whether a component from the message matches the selected component that is stored in the block of the blockchain.

Abstract: Methods, systems, and devices supporting data storage are described. A database system may implement lazy optimistic concurrency control (LOCC). LOCC may support an efficient use of database connections for a data archiving process. The data archiving process may involve a first worker thread at an application server copying data records from a primary database and writing the data records to a secondary database. A second worker thread may operate concurrent to the first worker thread to monitor the primary database for changes (e.g., using a shared database connection), as the primary database may not lock the copied data records during the archiving process. Data records that are altered in the primary database during the archiving process may be logged for error handling by an administrator. The data records that are copied from the primary database and not altered during the archiving process may be deleted from the primary database.

Abstract: Methods, systems, and devices for data attribution using frequent pattern analysis are described. In some cases, data stored at a multi-tenant database server may be analyzed to understand various interactions and patterns between data attributes associated with multiple users. The multi-tenant database server may effectively cluster and/or perform calculations on attributes of the data to understand user patterns. In some examples, the multi-tenant database server may determine a change (e.g., a probability change) in the user patterns by removing one or more attributes from the data set and re-performing the analysis. By re-performing the analysis, the multi-tenant database server may attribute a value to individual pieces and combinations of the data in order to indicate the effect that each piece of data has on the analysis.