Salesforce Com, Inc.

Microsoft Technology Licensing, LLC

Salesforce, Inc.

Michael Allan Friedman

Marla Hay

Yvonne Zhou

Shivan Kaul Sahib

Yu Chen

Vikas Taneja

Arjun Kumar Sirohi

Jiong Qiu

Jeremy Lynn Reed

Vidushi Sharma

Kim Lichong

Charles Patrick Mann

Kwan-Leung Chan

Brendan McKeon

Paul James Reid

Rajmohan Rajagopalan

Shane Brady

Andrey Lukyanov

Patricia Mary Wagoner

Heather S Burns

Robert Sinclair

James Nunn

Rage Hawley

Bryan Atwood

Methods and apparatus for updating a denormalized database object after updating, deleting, or inserting a record in a source database object are described. A first operation on a source database object that involves a record of the source database object being updated, deleted, or inserted is performed. A first part of a corresponding second operation involving a respective record of the denormalized database object being updated, deleted, or inserted is performed. A query result that references an aggregate field of a set of records in the denormalized database object is altered. The altering includes an aggregation operation using values in the query result being performed and altering that part of the query result that includes the aggregate field of the set of records. A second part is optionally performed to complete the corresponding second operation and update the denormalized database object.

Updating of a denormalized database object after updating, deleting, or inserting a record in a source database object

Methods and systems for using consent policies to determine whether to proceed with actions relative to persons based on a hierarchy of consent values for that person are described. Responsive to a query, records are retrieved which pertain to a person's consent for another entity to perform an action relative to the person in view of data privacy laws. A consent policy is selected. The selected consent policy includes rules that are configurable to reflect a manner to comply with data privacy laws. The selected consent policy is applied to the records. Applying the selected consent policy comprises applying rules to find a result for a second level of the hierarchy of consent values, determining a result for a first level of the hierarchy of consent values, and applying rules to determine whether to proceed with the action relative to the person.

Determining consent for an action using a consent policy reflecting an interpretation of applicable data privacy laws

Predictive execution of query flows in an application aware database environment. A repository of previously received and registered database queries along with at least corresponding metadata having information about database query flows generating the database queries is maintained. Application metadata corresponding to a subsequent database query is received. The repository is checked to determine if the application metadata matches one of the previously received and registered database query flows. One or more queries corresponding to the query flow from the repository is/are retrieved if a match is determined. Execution of the retrieved one or more database queries is started prior to receiving the query from outside the repository.

Techniques and architectures for providing and operating an application-aware database environment with predictive execution of queries and query flows

An indication of an action is received through and application program interface (API) provided by one or more hardware processing devices. The action corresponds to communication with a specified party. Multiple disparate tables stored in at least one database of a of a database environment associated with the one or more hardware processing devices are searched for records having the field property corresponding to the specified party. The field property from the corresponding multiple disparate tables are evaluated. A unified field property is determined based on the evaluation of the field property from the corresponding multiple disparate tables. The unified field property is returned through the API.

Techniques and architectures for managing privacy information and permissions across disparate database tables

At least one database table of denormalized values corresponding to selected values of field properties in records across multiple disparate tables of the database environment is maintained. A structured query is received through a structured query language application program interface (API). The structured query to request a listing of records across the multiple disparate tables of the database environment. The database table is searched for indications corresponding to records across the multiple disparate tables of the database environment corresponding to the selected values indicating communication with a specified party. A listing of records from across the multiple disparate tables that satisfy the selected values is returned through the structured query language API.

Techniques and architectures for managing privacy information and permissions queries across disparate database tables

Application-aware database environments. A repository of previously received and registered database queries is maintained that includes at least corresponding metadata having information about an application generating the database queries. A subsequent database query and application metadata corresponding to the subsequent database query can be received. The repository to determine if the subsequent database query and application metadata match one of the previously received database queries and application metadata. A matching previously received database query is retrieved from the repository if a match is determined. The retrieved database query is executed.

Techniques and architectures for providing and operating an application-aware database environment

Integrated fuzzing techniques are described. A fuzzing system may employ a container configured as a separate component that can host different target pages to implement fuzzing for an application. A hosted target file is loaded as a subcomponent of the container and parsed to recognize functionality of the application invoked by the file. In at least some embodiments, this involves building a document object model (DOM) for a browser page and determining DOM interfaces of a browser to call based on the page DOM. The container then operates to systematically invoke the recognized functionality to cause and detect failures. Additionally, the container may operate to perform iterative fuzzing with multiple test files in an automation mode. Log files may be created to describe the testing and enable both self-contained replaying of failures and coverage analysis for multiple test runs.

Integrated fuzzing

A secret (e.g. a password, key, certificate) is automatically generated by a system. For example, at the time of deployment of a computing machine, a password may be generated and securely stored by the system with other secrets. The password may be used by the system to perform various operations (e.g. configuring the machine, . . . ). When a secret is requested by a user to access a resource, a secret is provided to the user. Once the secret has been utilized by the user, the secret is reset and replaced with a newly generated secret. All/portion of the secrets may also be automatically regenerated. For example, when a breach occurs and/or is suspected, each of the secrets may be replaced with newly generated secrets and securely stored. Auditing and reporting may also be provided (e.g. each request/access to a secret is logged).

Scalable and automated secret management

A method and system providing a client with user interface information are described. The method and system implement a set of application program interfaces for providing user interface information to a client through an accessibility system. The accessibility system includes a mechanism for transferring user interface information from a provider side to the client side and a logical tree for selectively revealing user interface information. The application program interface system includes client side application program interfaces for assisting the client in obtaining user interface information. The client side application program interfaces include an automation class, a logical element class, a raw element class, control pattern classes, and an input class. The provider side application program interfaces include a provider automation class, a provider automation interface, a raw element interface, and control pattern provider interfaces.

User interface automation framework classes and interfaces

Growing community of inventors

Bellevue, WA, United States of America

Michael Allan Friedman