Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A client application provides a user interface for defining a form that includes a navigation control. The navigation control includes two or more selectable tabs that are each associated with a target, such as another form or a report. When one of the selectable tabs on the navigation control is selected using an appropriate user input device, the target associated with the selected tab is displayed in the form. The client application also provides functionality for publishing a form including navigation controls to a server application, thereby making the form and the navigation control accessible through a Web interface.

Abstract: 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.

Abstract: 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.

Abstract: The present invention extends to methods, systems, and computer program products for processing data-centric business models. An execution engine accesses a commingled data-centric application model that includes a data model for a data store and a business logic model for interacting with data entities contained in the data store. The execution engine receives an event related to the data store and identifies an involved data entity corresponding to the received event. The execution engine identifies a business logic rule indicated as affecting the involved data entity. The execution engine establishes a context for evaluating the identified business logic rule. The execution engine evaluates the conditions of the business logic rule in accordance with the established context. The execution engine executes any appropriate actions indicated in the business logic rule as a result of the conditions of the business logic rule being satisfied.

Abstract: 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.

Abstract: 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.

Abstract: The present invention extends to methods, systems, and computer program products for processing data-centric business models. An execution engine accesses a commingled data-centric application model that includes a data model for a data store and a business logic model for interacting with data entities contained in the data store. The execution engine receives an event related to the data store and identifies an involved data entity corresponding to the received event. The execution engine identifies a business logic rule indicated as affecting the involved data entity. The execution engine establishes a context for evaluating the identified business logic rule. The execution engine evaluates the conditions of the business logic rule in accordance with the established context. The execution engine executes any appropriate actions indicated in the business logic rule as a result of the conditions of the business logic rule being satisfied.