Amazon Technologies, Inc.

Salesforce Com, Inc.

Keas, Inc.

Adam Bosworth

Joseph Rozenfeld

Ian Scott Eslick

Tatyana Mamut

Anupam Srivastava

Syed Kamran Masood

Andrew Layman

Stu Statman

Stephan Richter

George Kassabgi

Rajesh Goli

Eric Hauser

Mohammad Asif Ali Khan

Matthew John Fleckenstein

At a data management service, a child template associated with a parent group of one or more cells of a first data sheet is stored. In response to detecting that a parent cell has been added to the parent group, a particular child data sheet is instantiated automatically in accordance with the template. In response to a change to a value in a first cell of the child data sheet, a corresponding value of a cell of the first data sheet is modified.

Network-accessible data management service with web-of-sheets data model

A descriptor of a dynamically materialized view is stored. The descriptor includes a query to select a subset of cells from a data sheet, and a result of executing the query. In response to an update directed to the data sheet, the result stored in the descriptor is modified based on re-executing the query, and a notification is transmitted to an execution platform at which an application whose output depends on the dynamically materialized view runs.

Dynamically materialized views for sheets based data

In response to a determination that a first logical table is to be created in a data sheet, a respective row identifier is generated and stored for individual rows of the first logical table. To indicate a relationship between a particular cell of another logical table and a particular row of the first logical table, the row identifier of the particular row is stored. After a modification of a value stored in the particular row, the row identifier is used to determine an updated value to be displayed in the particular cell of the other logical table.

Dynamically updated data sheets using row links

Representations of a set of cards are displayed via an application authoring interface. A given card represents one or more screen layouts of an application, and contents of a particular card are based on contents of a data sheet materialized in accordance with a data model which enables automatic instantiation of child data sheets associated with a parent cell within a parent data sheet. In response to detecting an edit operation directed at a particular card, an updated representation of the particular card is displayed at the first application authoring interface, and a screen layout corresponding to the updated representation is rendered at a particular mobile computing device.

Application authoring using web-of-sheets data model

The technology disclosed offers a declarative framework that implements a machine for multi-step progression of interaction with an entity. The declarative framework is usable over and over for a broad range of applications because it provides a simple rule-based authoring tool that can be used for specifying different elements and components of a complex state machine, including state definitions, state transition triggers, state transition conditions and state transition actions. Once defined, the state machine is automatically generated and implemented based on the declarative input provided by a non-technical user.

Simplified entity lifecycle management

The disclosed declarative framework implements a machine for multi-step progression of interaction with an entity. The framework is usable for a broad range of applications&#x2014;providing a simple rule-based authoring tool for specifying elements and components of a complex state machine, including state definitions, state transition triggers, state transition conditions and state transition actions. Case-status states, a first filtering condition, and a count parameter that specifies a limit on a number of times within a time period in excess of which additional events with characteristics that match will be ignored or discarded are usable to determine whether to ignore or process an incoming event&#x2014;throttling the rate at which certain actions occur. A workflow engine gets loaded with instructions derived from the states and event filtering conditions, for handling incoming machine-generated events. Once defined, the state machine is automatically generated and implemented based on the declarative input provided.

Throttling events in entity lifecycle management

A method for processing risk factors for a user is disclosed. The method may include receiving protocol data for creating a risk factor engine by an application stored and executed at a computing device. The risk factor engine may be stored in memory and executable by a processor to process a first set of stored user health data for a user. The protocol data may include a rule and one or more health attribute values. The rule and the one or more health attribute values may each include a computer programming expression editable by an administrator. The method may further include determining a user health score through execution of the risk factor engine by the processor and based on the user health data.

Risk factor engine that determines a user health score using a food consumption trend, and predicted user weights

Risk factor engine that determines a user health score

Risk factor data can be processed by a risk factor coaching engine to determine health risk for a user. The risk factor coaching engine may be executed within a health coaching protocol to perform actions that provide a user with information, recommendations and alerts via other coaching engines, and appointments with health care professionals. The risk factor coaching engine may also predict attribute values for a user based on a time period and goals for user health data upon which the predicted attribute value is based.

Growing community of inventors

San Francisco, CA, United States of America

Adam Bosworth