Abstract: Among other things, records are maintained for machine-executable intelligent assistance agents. The record for an assistance agent includes information about (1) a user to which the agent belongs, (2) a domain or facet of activity of the user, (3) a goal of the assistance agent within the domain or facet of activity, and (4) a principle of conduct of the assistance agent. Each assistance agent is executed to provide assistance only to the user to which the assistance agent belongs, only in the domain or facet, and only in accordance with the goal and the principle of conduct.

Abstract: Among other things, data is received representing a case for which an output premise is to be generated. The received data is processed to generate the output premise for the case. The processing includes both analytical processing and statistical processing. The analytical processing in the statistical processing are managed so that the output premise depends on results of the analytical processing that have been affected by the statistical processing, or on results of the statistical processing that have been affected by the analytical processing, or on both.

Abstract: Among other things, data is received representing a case for which an output premise is to be generated. The received data is processed to generate the output premise for the case. The processing includes both analytical processing and statistical processing. The analytical processing in the statistical processing are managed so that the output premise depends on results of the analytical processing that have been affected by the statistical processing, or on results of the statistical processing that have been affected by the analytical processing, or on both.

Abstract: An application portal selectively provides a user selective access to data. A data access layer is included in the portal and includes a map associating the user with a permission and further associating a combination of the user and the permission with a data entity, whereby it may be determined whether the user is permitted to access data identified with the data entity. A data stage included in the portal selectively undergoes a synchronization with a remote data store, the synchronization providing data access information that is used to update the map.

Abstract: A system may include a data store storing global data mapped from local data maintained by a plurality of heterogeneous data subsystems. The system may further include a life cycle coordinator including a global data life cycle model defining at least one life cycle for the global data, said life cycle coordinator being configured to receive a data update message defined in accordance with the global data life cycle model and representative of an update of the local data of one of the heterogeneous data subsystems, the data update message including a life cycle status identifier of a data record associated with the update, translate the data update message to at least one global data operation, the translation being based at least in part on the life cycle status identifier, and apply the update to the global data by performing the at least one global data operation.

Abstract: In one of many possible embodiments, an exemplary system includes a data integration subsystem including at least one base hierarchical data structure representative of a first set of one or more data relationships. The system further includes a customization subsystem configured to receive one or more commands from an external source. The commands represent a second set of one or more data relationships, the second set of data relationships being externally defined. The customization subsystem is further configured to generate, based on the commands, a custom hierarchical data structure representative of the second set of data relationships, the second hierarchical data structure being generated on top of at least a subset of the base hierarchical data structure.

Abstract: An integration portal provides a user with access to application entities of a plurality of remote applications. An authorization layer included in the integration portal includes a permission map indicating an association between the user and at least one of the application entities of the plurality of remote applications that the user is permitted to access. The authorization layer in the integration portal is synchronized with an authorization layer included in an application portal that provides the user with access to a subset of the remote applications, whereby the permission map is updated with information about at least one of the application entities that the user is permitted to access through the integration portal. Corresponding systems and methods are also disclosed.

Abstract: Exemplary scalable, rule-based data synchronization systems and methods are disclosed. An exemplary method includes at least one computing device executing a database trigger process in response to a database trigger event, the database trigger process including writing a general data message to a general message repository. The method further includes the at least one computing device executing an independent process including monitoring the general message repository, detecting the general data message in the general message repository, and processing, in response to the detecting of the general data message in the general message repository, the general data message in accordance with a predefined set of rules. Corresponding systems and methods are also disclosed.

Abstract: A system may include a data store storing global data mapped from local data maintained by a plurality of heterogeneous data subsystems.

Abstract: An exemplary system includes a plurality of heterogeneous data subsystems maintaining local data and a coordinator subsystem configured to maintain global data mapped from the local data. The coordinator subsystem includes a global data life cycle model defining at least one life cycle for the global data. The coordinator subsystem is configured to use the global data life cycle model to coordinate a data update between the global data and the local data. In certain implementations, the coordinator subsystem and the heterogeneous data subsystems are configured to communicate using at least one data update message representative of the data update, the data update message being defined in accordance with the global data life cycle model. In certain implementations, the data update message includes a life cycle status identifier associated with the data update.

Abstract: An integration portal provides a user with access to application entities of a plurality of remote applications. An authorization layer included in the integration portal includes a permission map indicating an association between the user and at least one of the application entities of the plurality of remote applications that the user is permitted to access. The authorization layer in the integration portal is synchronized with an authorization layer included in an application portal that provides the user with access to a subset of the remote applications, whereby the permission map is updated with information about at least one of the application entities that the user is permitted to access through the integration portal. Corresponding systems and methods are also disclosed.

Abstract: An exemplary system includes an application portal providing access to items of a plurality of remote applications, wherein at least one of the items is related to more than one of the remote applications, and an authorization layer that is included in the portal and that includes a permission map indicating an association between a user and at least one of the items of the plurality of remote applications that the user is permitted to access. In certain embodiments, the items include an application program interface (API). In certain embodiments, the authorization layer is synchronized with the remote applications, whereby the permission map is updated concerning information about at least one of the items that the user is permitted to access. Corresponding methods and systems are also disclosed.

Abstract: Data cache systems are provided that can be implemented on a backend server side, are session independent, support caching of large amounts of data while passing only the required amount of requested data through a network, and support pagination of data in an efficient manner. A backend data cache system may include a special database schema for caching data in a database server, a middleware program for providing application program interfaces to application programs making cache requests, and a cache maintenance program for maintaining cached data sets stored within the database server. Each cache request can be stored as a type of temporary table that is assigned a unique identifier, which can be used during different sessions and/or by different application programs to access cached data sets.

Abstract: An exemplary system includes a plurality of heterogeneous data subsystems maintaining local data and a coordinator subsystem configured to maintain global data mapped from the local data, the global data including a plurality of global data relationship views. One of the heterogeneous data subsystems is configured to initiate a data conversion of at least one local data record included in the local data from an origin data schema to a target data schema and to provide at least one data update message representative of the data conversion to the coordinator subsystem. The coordinator subsystem is configured to receive the data update message and asynchronously propagate the data conversion through to at least a subset of the global relationship views in the global data.

Abstract: An exemplary system includes a plurality of heterogeneous data subsystems maintaining local data and a coordinator subsystem configured to maintain global data mapped from the local data. The coordinator subsystem includes a global data life cycle model defining at least one life cycle for the global data. The coordinator subsystem is configured to use the global data life cycle model to coordinate a data update between the global data and the local data. In certain implementations, the coordinator subsystem and the heterogeneous data subsystems are configured to communicate using at least one data update message representative of the data update, the data update message being defined in accordance with the global data life cycle model. In certain implementations, the data update message includes a life cycle status identifier associated with the data update.

Abstract: An exemplary system includes a plurality of heterogeneous data subsystems maintaining local data and a coordinator subsystem configured to maintain global data mapped from the local data, the global data including a plurality of global data relationship views. One of the heterogeneous data subsystems is configured to initiate a data conversion of at least one local data record included in the local data from an origin data schema to a target data schema and to provide at least one data update message representative of the data conversion to the coordinator subsystem. The coordinator subsystem is configured to receive the data update message and asynchronously propagate the data conversion through to at least a subset of the global relationship views in the global data.

Abstract: An application portal selectively provides a user access to items of a plurality of remote applications. At least one of the items is related to more than one of the remote applications. An authorization layer is included in the portal and includes a map indicating that the user is permitted to access at least one of the items.

Abstract: An application portal selectively provides a user selective access to data. A data access layer is included in the portal and includes a map associating the user with a permission and further associating a combination of the user and the permission with a data entity, whereby it may be determined whether the user is permitted to access data identified with the data entity. A data stage included in the portal selectively undergoes a synchronization with a remote data store, the synchronization providing data access information that is used to update the map.