Microsoft Technology Licensing, LLC

Hyperproof Inc.

Andrew Robert Miller

Michael J McCormack

Scott Timothy Gardner

Vijay Mital

Clinton Dee Covington

Jason A Bould

Sumit Chauhan

Robert Coggins

David Robert Shutt

Gregory Scott Lindhorst

Christopher Warren Bryant

Timothy E Getsch

Suraj T Poozhiyil

Steven Miles Greenberg

Alexander Sasha Stojanovic

Neil Warren Black

Erik Rucker

Pavel R Karimov

David L Kaplan

David Jon Conger

Alexander M Tkatch

Greg S Lindhorst

Jay L Massena

Stephen I Lesser

Robert Scott Cooper

Ryan Christopher McMinn

Marshall Scot Bjerke

Robert Tobkes

Bryan David Cooke

Jonathan Wayne Phillips

Abhishek Agarwal

David John Brennan

Abhijit Gore

Konrad Tupaj

Zachary P Woodall

Vitore Selca

Kelly Michael Krout

Kulothungan Rajasekaran

Cyrus R Balsara

Theresa Naramore

Roger Wolff

Jonathan McPherson

Craig Howard Unger

Robert Moodie Heddle

Amarinder Singh Grewal

Daniel Hough

Adithya Nittor Vishwanath

Michael J Eatough

David M Vierzba

Andrew M Warden

Jianlan Song

Manjeet Bothra

Ramani Jagadeba

Jonathan M Sigler

Peter D Mullen

Tim Getsch

Alexander Vorobiev

Geoffrey L Griffith

Paul D Bishop

Robert E Coggins

Kunal Garg

Ankit Malpani

Edward Martinez

Andrew McRae Warden

A program model that includes requirements and control objects associated with requirements, workflows, proof assets. Workflow tasks associated with the workflows may generate requests to collect each proof asset associated with the control objects. Workflow tasks may validate each collected proof asset based on the plurality of control objects associated with each collected proof asset. Workflow tasks may determine completed control objects based on the validated proof assets. Workflow tasks may employ an amount of the completed control objects that is equivalent to the amount of the control objects associated with the program model to provide a report indicating that the requirements associated with the program model may be satisfied. Workflow tasks may employ detection of modifications to the validated proof assets to determine a portion of the workflow tasks based on the modified proof assets such that the portion of the workflow tasks may be re-executed.

Managing proof assets for validating program compliance

A tenant comprising one or more users receives services from a cloud computing system ('CCS'). The CCS determines when a tenant is not using any services, and if so, the CCS initiates a tenant suspension process. The tenant suspension process involves suspending various asynchronous computing processes for the tenant, which execute otherwise execute even if no users of the tenant are currently accessing the CCS. After a period of non-use of the CCS, the tenant is suspended. The tenant is returned to an active state automatically when a user of the tenant logs-on to receive services.

Managing capacity in a data center by suspending tenants

A data reporting framework that works across on-premise and hosted Customer Relationship Management (CRM) platforms enabling definition and execution of secure custom reports is provided. A fetch query language of a CRM platform is used along with reporting service tools and constructs to enable users to upload and execute custom fetch based reports with support for expressions, code, formatting, and drill through. Users are also enabled to build simple reports from within CRM and, if needed, enhance those reports using reporting service tools and re-upload in CRM. Furthermore, custom reports may be executed in a sandboxed environment to provide full security in a multi-tenant, hosted CRM system.

Data reporting framework across on-premise and hosted CRM services

Embodiments are provided for creating and reusing custom data types in a database. A selection of a field or group of fields may be received from a database table in the database by a database software application executing on a computer system. Each selected field may include a set of field properties. The application may further receive a user input to initiate saving the selected field or group of fields as a custom data type. In response to receiving the input, the application may be configured to generate a dialog for receiving custom data type information for the selected field or group of fields and save the selected field or group of fields as a custom data type. The custom data type may then be reused by the application in the database.

Database data type creation and reuse

Technologies are described herein for generating a platform-independent data application. In one method, a definition of a data schema is received for defining data types. A definition of a user interface is also received for access data stored in the data types. Further, a definition of business logic is received for enforcing validation rules and actions associated with the data types. The definitions of the data schema, the user interface, and the business logic are each received in a platform-independent format and used to generate the platform-independent data application.

Platform-independent data application description language

A plurality of database application components available in a first components store is received. A plurality of pointers is created with each of the plurality of pointers referencing a selected object, such as the plurality of database application components or an existing pointer to one of the plurality of database application components. The plurality of pointers is collected into a reference group defining a plurality of selected objects included in a database application. In some examples, the database application components include a header, a footer, a control, a fragment, a table, a query, a report, a relation, a form, a conditional formatting statement, a programming component, a validation statement and a module.

Database application assembly and preparation

A user interface (UI) includes floating action buttons. Respective hot zones are established for associated respective UI elements. When a focus is targeting (e.g., located at) a given hot zone, one or more floating action buttons that are associated therewith are presented as part of the UI. Activation of a particular action button of the one or more floating action buttons causes an action corresponding to the particular action button to be implemented. In an example implementation, the actions available through the one or more floating action buttons may be context-sensitive such that the actions thereof are tailored to the type of item corresponding to the UI element (e.g., an icon, a graphical element, a text portion, a screen area, etc.).

Floating action buttons

The present invention extends to methods, systems, and computer program products for allowing a computer system user to extend the functionality of a data-centric software application. The method includes instantiating the data-centric software application, where the data-centric application has portions of business logic categorized and associated with items of data-centric application functionality defined in a schema. The method includes receiving customization input to customize at least one of the portions of business logic. The method includes formulating a representative model corresponding to at least one of the portions of customized business logic. The method includes applying the representative model to the schema to generate a customized schema that extends the business logic of the data-centric software application. The method includes instantiating the data-centric software application in accordance with the customized schema to customize the functionality of the business logic in the data-centric software application.

User-customized extensions for software applications

Technologies are presented herein for self-describing re-usable software components. Metadata is generated and published with a re-usable software component that identifies the capabilities of the software component, identifies other software components that the re-usable software component may be integrated with, and identifies mechanisms for integrating the re-usable software component with other software components. The metadata can then be used to discover re-usable software components and to integrate the re-usable software components with other software components.

Self-describing re-usable software components

Computer software applications may be separated into components and distilled into functional and identifying attributes, which may then be used to regenerate the computer software application on a different system. A component of a computer software program is received. From the component, one or more functional attributes describing the operation of the component on a first operating platform are distilled from which the component can be generated to operate on one or more operating platforms. Attributes identifying the component are identified. The functional attributes and the identifying attributes of the component are stored in a distillation store. From the distillation store, using information about a selected operating platform on which the computer software program is to be executed, components of the computer software program may be generated to execute on the selected operating platform.

Application dehydration, synchronization, and rehydration

A database server application program is provided that is configured to provide a programmable interface into a database application by way of database services uniform resource locators (URLs). A database services URL utilized by the database application can be updated programmatically by program code executing within or under control of the database server application program. A macro action for use in conjunction with a database server application that provides functionality for displaying a database object, such as a form or report, in-place in a Web browser is also disclosed.

Database application navigation

Tools and techniques are described for formats for database template files shared between client and server environments. Systems provided by these tools may include client subsystems that include client-side database management applications that instantiate tables within a database, and instantiate client-specific database template files corresponding respectively to the tables. These database management applications may also instantiate server-specific database template files that correspond to the client-specific template files, and may enable servers to access the server-specific template file. These systems may also include server subsystems that further include server-side database management services that access the server-specific template files, and instantiate server-side template files based thereon. In turn, the database management services may create database applications from the server-side template files.

Formats for database template files shared between client and server environments

Embodiments are provided to define relationships for merging template or database part tables with one or more database tables in a computer system. A database application may utilize a schema to receive metadata associated with a target database part table in one or more markup language elements. The database application may then receive metadata associated with a source database table to be joined with the target table in the schema elements. The database application may then receive join type metadata in the schema elements. The join type metadata may specify whether fields from the source table are to be merged into the target table or whether fields from the target table are to be merged into the source table. In response to receiving the target table metadata and the source table metadata, the database application may then merge the target and source tables utilizing the join type metadata.

Database part table junctioning

The present invention extends to methods, systems, and computer program products of user-interface architecture for manipulating business models. Embodiments of the invention facilitate efficient generation and extension of business related software applications, including commingled data-centric applications that represent both data elements and business logic in metadata. Modules of the user-interface architecture permit users to enter commands through common metaphors and wizards that abstract underlying (and more complex) modeling commands and data formats from users. The user-interface architecture can automatically search for existing models to provide and extend business related functionality.

User-interface architecture for manipulating business models

Growing community of inventors

Issaquah, WA, United States of America

Andrew Robert Miller