Abstract: Systems and methods are disclosed that assign and/or enforce usage rights for a software application. Further, the systems and methods assign and/or enforce usage rights for a software application with one or more users by decoupling the identity of the person who purchases the application from the actual users of the application. Additionally, the systems and methods provide for centralized built-in user assignment with support for multiple applications.

Abstract: A first database and a second database have different schemas. An activity in a workflow accesses a data item in a list by invoking a method in an interface of a list object. The list comprises a collection of data items. Each data item in the list comprises an item key field specifying an item key. No two data items in the data item collection have item key fields specifying a shared item key. In addition, each data item in the list comprises a set of additional fields. Each field in the set of additional fields has a value derived from the first database or each field in the set of additional fields has a value derived from the second database. In this way, the activity can be implemented without knowledge of the different schemas of the first database and the second database.

Abstract: A computing device includes instructions that, when executed by a processing unit, cause the processing unit to: create a business data catalog module that accesses and manipulates data residing on an internal data store and an external data store, wherein the business data catalog module receives a request for data, determines whether the data resides in the internal data store or the external data store, and access the data residing on the external data store, and create a external data provisioning module that provisions data accessed from the external data store, wherein the external data provisioning module maps external data from the external data store for presentation on a client computing device. A user can access and manipulate the data from the external data store in a same manner as accessing and manipulating data from the internal data store.

Abstract: A first database and a second database have different schemas. An activity in a workflow accesses a data item in a list by invoking a method in an interface of a list object. The list comprises a collection of data items. Each data item in the list comprises an item key field specifying an item key. No two data items in the data item collection have item key fields specifying a shared item key. In addition, each data item in the list comprises a set of additional fields. Each field in the set of additional fields has a value derived from the first database or each field in the set of additional fields has a value derived from the second database. In this way, the activity can be implemented without knowledge of the different schemas of the first database and the second database.

Abstract: A computing device includes instructions that, when executed by a processing unit, cause the processing unit to: create a business data catalog module that accesses and manipulates data residing on an internal data store and an external data store, wherein the business data catalog module receives a request for data, determines whether the data resides in the internal data store or the external data store, and access the data residing on the external data store, and create a external data provisioning module that provisions data accessed from the external data store, wherein the external data provisioning module maps external data from the external data store for presentation on a client computing device. A user can access and manipulate the data from the external data store in a same manner as accessing and manipulating data from the internal data store.

Abstract: Technologies are described herein for declaratively defining forms and views and for rendering the declaratively defined forms and views. A declarative and rendering technology agnostic form definition is defined and stored that defines a layout for a form. A transformation definition file is also stored that defines a transformation from the declarative form definition to renderer-specific code. A transformation is performed using the transformation definition file, the declarative form definition, and form data provided by an application to generate renderer-specific markup for the form. The desired form will be displayed when a rendering client is utilized to render the renderer-specific markup. A view may also be declaratively defined, transformed, and rendered similarly.

Abstract: Methods, systems, and computer-readable media implementing various aspects of data retrieval, transformation, data interrelationship inference, and aggregate data view generation are disclosed. The aggregate data view may incorporate data sources from geographically disparate servers, and in different data formats. The aggregate data view may further be converted into HTML and published on the web.

Abstract: Methods, systems, and computer-readable media implementing various aspects of data retrieval, transformation, data interrelationship inference, and aggregate data view generation are disclosed. The aggregate data view may incorporate data sources from geographically disparate servers, and in different data formats. The aggregate data view may further be converted into HTML and published on the web.