Salesforce Com, Inc.

Salesforce, Inc.

Alex Gitelman

Twisha Mehta

Michael Tang

Stefan Eberl

Abraham Adam

Daphne Kao

Harish Bellamane

Venkatachalam Muthukrishnan

Ruisheng Shi

Donovan Schneider

Alex Field

Simon Y Wong

Ravishankar Arivazhagan

Stephen Petschulat

Puneet Gupta

Eric Nash

Pradeep Mantha

Lingtao Zhang

Jan Michael Timmerman

Santanu Sinha

Farid Nabavi

Torrey Teats

Methods, systems, and devices supporting dynamic process orchestration are described. An orchestration server may receive a request defining a data modification process from a user device. The orchestration server may generate an execution file based on the request, and the execution file may include a set of tasks for performing the data modification process and an order for performing the set of tasks. The orchestration server may execute, for the execution file, a first set of tasks according to the order for performing the set of tasks and, in some cases, may update the execution file based on executing the first subset of tasks. For example, updating the execution file may involve modifying a second subset of tasks of the set of tasks. The orchestration server may execute, for the updated execution file, the modified second subset of tasks according to the order for performing the set of tasks.

Orchestration for data pipeline execution plans

The technology disclosed relates to creating and frequently updating multiple online analytic processing (OLAP) analytic databases from an online transaction processing (OLTP) transaction updatable system that includes transaction commit, rollback, and field level security capabilities. It also relates to transparently decoupling extraction from rebuilding of frequently updated OLAP analytic databases from the OLTP transaction updatable system.

Pseudo-synchronous processing by an analytic query and build cluster

Streamlined creation and updating of olap analytic databases

Disclosed herein are systems and methods for implementing change value indication and historical value comparison at a user interface including means for storing records in a database, wherein updates to the records are recorded into a historical trending data object to maintain historical values for the records when the records are updated in the database; receiving input from a user device specifying data to be displayed at the user device; receiving historical filter input from the user device; querying the records stored in the database for the data to be displayed; querying the historical trending data object for the historical values of the data to be displayed; comparing the data to be displayed with the historical values of the data to be displayed to determine one or more changed values corresponding to the data to be displayed; and displaying a change value indication GUI to the user device displaying at least the data to be displayed and a changed value indication based on the one or more changed values determined via the comparing. Other related embodiments are further disclosed.

Systems, methods, and apparatuses for implementing change value indication and historical value comparison

System and methods for implementing dataflow life cycles are described and include forming, by a first server computing system, a dataflow life cycle by associating a dataflow with a customized code; associating, by the first server computing system, the customized code of the dataflow life cycle with context information, the customized code including one or more of pre-processing customized code and post-processing customized code; scheduling, by the first server computing system, the dataflow of the dataflow life cycle to be executed by a second server computing system when the customized code includes the pre-processing customized code and when the pre-processing customized code is successfully executed by the first server computing system; and executing, by the first server computing system, the post-processing customized code when the customized code includes the post-processing customized code and when the dataflow of the dataflow life cycle is successfully executed by the second server computing system.

Dataflow life cycles

Methods, systems, and devices for data processing within a distributed data system are described. In a multi-tenant distributed data system, a provider may supply executable code for processing data using declarative processing instructions received from a tenant. For example, a tenant may provide tenant-specific processing instructions for a requested set of data. The processing instructions may indicate input information (e.g., a data structure, tenant-specific fields, etc.), transformation information (e.g., from a set of pre-defined transformations), and output information. The provider-supplied code may use the tenant-specific processing instructions to process and generate the requested set of data, where the code may be executed by multiple nodes within the system. As such, the code executed by multiple nodes may utilize the input information, transformation information, and output information from the tenant-specific processing instructions to generate the requested data and provide the data to the tenant.

Distributed data processing in multi-tenant environments

The technology disclosed relates to assigning field level security to fields extracted from primary sources on a batch basis and compiled into analytical, read-only databases, for ultra-fast, ad-hoc data exploration and faceted navigation on integrated, heterogeneous data sets. The method includes assigning field level security to the extracted fields by combining user selectable inheritance of field level security from source fields that yield the extracted fields, with pinning of inheritance of field level security for the extracted fields to reference fields in the database sources wherein the reference fields are distinct from the extracted fields. The disclosed method also includes receiving additional fields as unsecured data sets, and assigning field level security to the additional fields, received by combining user selectable explicit specification of field level security for the received fields with pinning of inheritance of field level security for the received fields to reference fields in the database sources.

Fine grain security for analytic data sets

In accordance with disclosed embodiments, there are provided systems, methods, and apparatuses for implementing concurrent dataflow execution with write conflict protection within a cloud based computing environment. For instance, an exemplary system having at least a processor and a memory therein includes means for: creating a dataflow definition for a first dataflow type, wherein the dataflow definition includes at least one or more datasets to be accessed by the dataflow and a plurality of functional operations to be performed on the one or more datasets when the dataflow is executed; generating and storing a dataflow version identifying all datasets accessed by the dataflow based on the dataflow definition created; receiving multiple requests for the first dataflow type; enqueuing the multiple requests into a message queue pending execution; selecting, from the message queue, a first runnable dataflow having been earliest enqueued of the first dataflow type for execution based on (i) the first dataflow type being allowable within system limits and based further on (ii) verification that the selected first runnable dataflow is not already executing and based further on (iii) verification there is no write conflict for any dataset accessed by the selected first runnable dataflow. Other related embodiments are disclosed.

Systems, methods, and apparatuses for implementing concurrent dataflow execution with write conflict protection within a cloud based computing environment

The technology disclosed relates to creating and frequently updating multiple online analytic processing (OLAF) analytic databases from an online transaction processing (OLTP) transaction updatable system that includes transaction commit, rollback, and field level security capabilities. It also relates to transparently decoupling extraction from rebuilding of frequently updated OLAP analytic databases from the OLTP transaction updatable system.

Systems and methods are provided for user interface date selectors for historical reports. A user interface outputs a date selector including a calculated dates option, wherein the calculated dates option is based on a date frequency applied to a date range. The user interface receives a selection via the date selector. Dates associated with the selection are identified. The user interface outputs the dates as a preview of a historical report, wherein the dates are output in a chronological order.

User interface date selectors for historical reports

Streamlined creation and updating of OLAP analytic databases

Systems and methods are provided for alternative change processes for changes to data objects. A change to a data object is recorded, wherein the change is submitted to a first change process. The first change process is disabled. A second change process is asynchronously executed to process the change to the data object.

Systems and methods for alternative change processes for changes to data objects

A method for automatically updating a filter logic expression representing a Boolean filter comprising a plurality of search conditions is disclosed. The method includes receiving a first indication to remove a first search condition from a condition list comprising search conditions. Each search condition is associated with an identifier and the first search condition is associated with a first identifier, and the search conditions are listed in sequential order according to the associated identifier. In response to receiving the first indication, a second search condition associated with a second identifier that sequentially follows the first identifier is identified, and the second search condition is reassociated with a third identifier that immediately precedes the second identifier. A filter logic expression comprising a plurality of identifiers and operators and representing a Boolean filter is then modified by automatically replacing any reference to the second identifier with the third identifier.

Method and system for updating a filter logic expression representing a boolean filter

Systems and methods are provided for data object change history. A first data object and a second data object are retrieved, wherein the first data object includes an identifier, a field name, a first value, and a first date, and wherein the second data object includes the identifier, the field name, a second value, and a second date. A history object is stored, wherein the history object comprises the identifier, the field name, the first value, the first date, and the second date. The history object is output in response to a query which specifies the identifier, the field name, and a query date within a range of the first date and the second date.

Growing community of inventors

Berkeley, CA, United States of America

Alex Gitelman