Abstract: According to some embodiments, a source application part may be established having a source data object with a set of source attribute identifiers and associated source attribute values. A target application part may also be established having a target data object with a set of target attribute identifiers. An object reuse platform may then receive, from a user via a graphical interface, an indication that the source data object relates to the target data object. The object reuse platform may then calculate, for each source attribute identifier, a probability that the source attribute identifier is associated with one of the target attribute identifiers.

Abstract: According to some embodiments, a logical set operator platform may recognize that a user has selected, via a graphical user interface, a sub-set of items from an item set associated with a source application. The logical set operator platform may then receive an indication from the user that a selected logical set operation is to be applied to the item set and to the selected sub-set of items, wherein the selected logical set operation is not implemented by the source application. The selected logical set operation may be applied to create a resulting item set based on the selected sub-set of items, and it then may be arranged for an indication of the resulting item set to be provided to a receiving application.

Abstract: A communication port may exchange information with a user via a graphical user interface, and an application data store may contain information about executable applications, including input data and output data associated with each executable application. A merging platform may recognize that a user has selected, via the graphical user interface, a first executable application in the application data store. The merging platform may also recognize that the user has selected a second executable application in the application data store and receive an indication from the user that an application merging application is to be triggered. Responsive to this triggering, the merging application may merge behaviors of the first executable application and the second executable application, including functionality of the input and output data of each executable application, to create a merged application. The merging platform may then arrange to facilitate execution of the merged application.

Abstract: According to some embodiments, a source application part may be established having a source data object with a set of source attribute identifiers and associated source attribute values. A target application part may also be established having a target data object with a set of target attribute identifiers. An object reuse platform may then receive, from a user via a graphical interface, an indication that the source data object relates to the target data object. The object reuse platform may then calculate, for each source attribute identifier, a probability that the source attribute identifier is associated with one of the target attribute identifiers.

Abstract: At design time, a Use Logic Entity (ULE) and ULE Configuration Element (UCE) is defined for a particular Context. At run time, the defined ULE and UCE are placed into the particular Context. The defined ULE and UCE are rendered within a user interface associated with the particular Context. A user interface manipulation event associated with either the ULE or the UCE is received, and the user interface is dynamically configured based upon at least the received user interface manipulation event.

Abstract: At design-time, a user interface element of a user interface application is defined for use with a Behavior. The Behavior is defined for the defined user interface element. A user interface class is defined for the defined Behavior and registered with the user interface application. A trigger event is defined within the defined user interface class to activate when a particular event is detected by the Behavior.

Abstract: According to some embodiments, a source application part may be established having a source data object with a set of source attribute identifiers and associated source attribute values. A target application part may also be established having a target data object with a set of target attribute identifiers. An object reuse platform may then receive, from a user via a graphical interface, an indication that the source data object relates to the target data object. The object reuse platform may then calculate, for each source attribute identifier, a probability that the source attribute identifier is associated with one of the target attribute identifiers.

Abstract: A method, user interface, and computer-readable medium to receive a representation of a first query item, the first query item belonging to a data set and having at least one attribute; receive a representation of a second query item, the second query item being defined as relating to at least one particular attribute of another query item; associate the second query item with the first query item; automatically retrieve, in response to the second query item being associated with the first query item, a value for the at least one particular attribute of the second query item from the first query item; and save a record of the retrieved value.

Abstract: A communication port may exchange information with a user via a graphical user interface, and an application data store may contain information about executable applications, including input data and output data associated with each executable application. A merging platform may recognize that a user has selected, via the graphical user interface, a first executable application in the application data store. The merging platform may also recognize that the user has selected a second executable application in the application data store and receive an indication from the user that an application merging application is to be triggered. Responsive to this triggering, the merging application may merge behaviors of the first executable application and the second executable application, including functionality of the input and output data of each executable application, to create a merged application. The merging platform may then arrange to facilitate execution of the merged application.

Abstract: According to some embodiments, a logical set operator platform may recognize that a user has selected, via a graphical user interface, a sub-set of items from an item set associated with a source application. The logical set operator platform may then receive an indication from the user that a selected logical set operation is to be applied to the item set and to the selected sub-set of items, wherein the selected logical set operation is not implemented by the source application. The selected logical set operation may be applied to create a resulting item set based on the selected sub-set of items, and it then may be arranged for an indication of the resulting item set to be provided to a receiving application.

Abstract: According to some embodiments, a source application part may be established having a source data object with a set of source attribute identifiers and associated source attribute values. A target application part may also be established having a target data object with a set of target attribute identifiers. An object reuse platform may then receive, from a user via a graphical interface, an indication that the source data object relates to the target data object. The object reuse platform may then calculate, for each source attribute identifier, a probability that the source attribute identifier is associated with one of the target attribute identifiers.

Abstract: A method, user interface, and computer-readable medium to receive a representation of a first query item, the first query item belonging to a data set and having at least one attribute; receive a representation of a second query item, the second query item being defined as relating to at least one particular attribute of another query item; associate the second query item with the first query item; automatically retrieve, in response to the second query item being associated with the first query item, a value for the at least one particular attribute of the second query item from the first query item; and save a record of the retrieved value.