User interface portlet data cascade actuator apparatuses, methods and systems
The User Interface Portlet Data Cascade Actuator Apparatuses, Methods and Systems (“UIPDCA”) transforms database data sets, user interface widget data selections inputs via UIPDCA components into cascading UI subsequent views data selections and channel outputs. In one embodiment, the UIPDCA may include a data cascade user interface view apparatus. The UIPDCA's processor issues instructions from a UI view component to generate and broadcast a first event message that specifies a data source parameter associated with a user selection and the channel associated with the UI view component. The UIPDCA's processor issues instructions from a subsequent UI view component to update UI widget elements based on result of executing a query modified using parameters specified in the first event message, and to generate and broadcast a second event message that specifies a data source parameter associated with a default selection and the channel associated with the subsequent UI view component.
1. A data cascade user interface view apparatus, comprising:
a memory;
a component collection in the memory, including:
a user interface (UI) view component, and
a subsequent UI view component;
a processor disposed in communication with the memory, and configured to issue a plurality of processing instructions from the component collection stored in the memory,
wherein the processor issues instructions from the UI view component, stored in the memory, to:
obtain, via at least one processor, a user selection of a UI widget element from the UI view component;
determine, via at least one processor, a first data source parameter associated with the user selection;
determine, via at least one processor, a channel associated with the UI view component;
generate, via at least one processor, a first event message that specifies the first data source parameter and the channel associated with the UI view component; and
broadcast, via at least one processor, the first event message;
wherein the processor issues instructions from the subsequent UI view component, stored in the memory, to:
obtain, via at least one processor, the first event message;
determine, via at least one processor, a channel associated with the subsequent UI view component;
determine, via at least one processor, that the subsequent UI view component should process the first event message based at least on determining that the channel specified in the first event message and the channel associated with the subsequent UI view component match;
retrieve, via at least one processor, a query associated with the subsequent UI view component;
modify, via at least one processor, the query using the data source parameter specified in the first event message;
provide, via at least one processor, the modified query to a database;
obtain, via at least one processor, result data associated with executing the provided query;
update, via at least one processor, UI widget elements of the subsequent UI view component using the obtained result data;
determine, via at least one processor, a default selection of a UI widget element from the subsequent UI view component associated with the update;
determine, via at least one processor, a second data source parameter associated with the default selection;
generate, via at least one processor, a second event message that specifies the second data source parameter and the channel associated with the subsequent UI view component; and
broadcast, via at least one processor, the second event message.
2. The apparatus of claim 1 , wherein the user selection is a selection of a row in a grid.
3. The apparatus of claim 1 , wherein the first data source parameter is one or more of: identifier of a database table, identifier of a dataset, a row selection filter.
4. The apparatus of claim 1 , wherein the UI view component is the master of the subsequent UI view component.
5. The apparatus of claim 4 , wherein the determination that the subsequent UI view component should process the first event message is also based on the first event message originating from the master of the subsequent UI view component.
6. The apparatus of claim 4 ,
wherein the first event message further specifies a query modifier parameter associated with a filter of the UI view component; and
wherein the processor issues instructions from the subsequent UI view component, stored in the memory, to:
modify, via at least one processor, the query using the query modifier parameter specified in the first event message.
7. The apparatus of claim 1 , wherein the subsequent UI view component is a masterless receiver.
8. The apparatus of claim 7 , further comprising:
the processor issues instructions from the subsequent UI view component, stored in the memory, to:
determine, via at least one processor, one or more event data fields that should be specified in an event message in order for the subsequent UI view component to handle the event message; and
wherein the determination that the subsequent UI view component should process the first event message is also based on the first event message specifying the determined one or more event data fields.
9. The apparatus of claim 7 , further comprising:
the processor issues instructions from the subsequent UI view component, stored in the memory, to:
determine, via at least one processor, the UI view component type of the subsequent UI view component;
wherein the first event message further specifies a UI view component type of UI view components that can handle the first event message; and
wherein the determination that the subsequent UI view component should process the first event message is also based on determining that the UI view component type specified in the first event message and the UI view component type of the subsequent UI view component match.
10. The apparatus of claim 7 , further comprising:
the processor issues instructions from the subsequent UI view component, stored in the memory, to:
determine, via at least one processor, a transformation function associated with the subsequent UI view component; and
modify, via at least one processor, the query using the transformation function.
11. The apparatus of claim 10 , wherein the transformation function modifies the query by transforming the query into a plurality of different queries.
12. The apparatus of claim 1 , further comprising:
the processor issues instructions from the subsequent UI view component, stored in the memory, to:
determine, via at least one processor, a query modifier parameter associated with a filter of the subsequent UI view component; and
modify, via at least one processor, the query using the query modifier parameter.
13. The apparatus of claim 1 , wherein the UI view component is associated with a UI view component data structure that specifies (a) a visualization associated with the UI view component, (b) a channel associated with the UI view component, (c) a query associated with the UI view component, (d) a data source parameter associated with the UI view component, (e) a query modifier parameter associated with the UI view component, (f) a transformation function associated with the UI view component, and (g) a local filter associated with the UI view component.
14. The apparatus of claim 1 , wherein the UI view component is a root emitter incapable of acting as a receiver.
15. The apparatus of claim 1 , wherein the subsequent UI view component is one of a plurality of UI view components that update their respective UI widget elements based on the first event message.
16. A processor-readable data cascade user interface view non-transient physical medium storing processor-executable components, the components, comprising:
a component collection stored in the medium, including:
a user interface (UI) view component, and
a subsequent UI view component;
wherein the UI view component, stored in the medium, includes processor-issuable instructions to:
obtain, via at least one processor, a user selection of a UI widget element from the UI view component;
determine, via at least one processor, a first data source parameter associated with the user selection;
determine, via at least one processor, a channel associated with the UI view component;
generate, via at least one processor, a first event message that specifies the first data source parameter and the channel associated with the UI view component; and
broadcast, via at least one processor, the first event message;
wherein the subsequent UI view component, stored in the medium, includes processor-issuable instructions to:
obtain, via at least one processor, the first event message;
determine, via at least one processor, a channel associated with the subsequent UI view component;
determine, via at least one processor, that the subsequent UI view component should process the first event message based at least on determining that the channel specified in the first event message and the channel associated with the subsequent UI view component match;
retrieve, via at least one processor, a query associated with the subsequent UI view component;
modify, via at least one processor, the query using the data source parameter specified in the first event message;
provide, via at least one processor, the modified query to a database;
obtain, via at least one processor, result data associated with executing the provided query;
update, via at least one processor, UI widget elements of the subsequent UI view component using the obtained result data;
determine, via at least one processor, a default selection of a UI widget element from the subsequent UI view component associated with the update;
determine, via at least one processor, a second data source parameter associated with the default selection;
generate, via at least one processor, a second event message that specifies the second data source parameter and the channel associated with the subsequent UI view component; and
broadcast, via at least one processor, the second event message.
17. A processor-implemented data cascade user interface view system, comprising:
a user interface (UI) view component means, to:
obtain, via at least one processor, a user selection of a UI widget element from the UI view component;
determine, via at least one processor, a first data source parameter associated with the user selection;
determine, via at least one processor, a channel associated with the UI view component;
generate, via at least one processor, a first event message that specifies the first data source parameter and the channel associated with the UI view component; and
broadcast, via at least one processor, the first event message;
a subsequent UI view component means, to:
obtain, via at least one processor, the first event message;
determine, via at least one processor, a channel associated with the subsequent UI view component;
determine, via at least one processor, that the subsequent UI view component should process the first event message based at least on determining that the channel specified in the first event message and the channel associated with the subsequent UI view component match;
retrieve, via at least one processor, a query associated with the subsequent UI view component;
modify, via at least one processor, the query using the data source parameter specified in the first event message;
provide, via at least one processor, the modified query to a database;
obtain, via at least one processor, result data associated with executing the provided query;
update, via at least one processor, UI widget elements of the subsequent UI view component using the obtained result data;
determine, via at least one processor, a default selection of a UI widget element from the subsequent UI view component associated with the update;
determine, via at least one processor, a second data source parameter associated with the default selection;
generate, via at least one processor, a second event message that specifies the second data source parameter and the channel associated with the subsequent UI view component; and
broadcast, via at least one processor, the second event message.
18. A processor-implemented data cascade user interface view method, comprising:
executing processor-implemented user interface (UI) view component instructions to:
obtain, via at least one processor, a user selection of a UI widget element from the UI view component;
determine, via at least one processor, a first data source parameter associated with the user selection;
determine, via at least one processor, a channel associated with the UI view component;
generate, via at least one processor, a first event message that specifies the first data source parameter and the channel associated with the UI view component; and
broadcast, via at least one processor, the first event message;
executing processor-implemented subsequent UI view component instructions to:
obtain, via at least one processor, the first event message;
determine, via at least one processor, a channel associated with the subsequent UI view component;
determine, via at least one processor, that the subsequent UI view component should process the first event message based at least on determining that the channel specified in the first event message and the channel associated with the subsequent UI view component match;
retrieve, via at least one processor, a query associated with the subsequent UI view component;
modify, via at least one processor, the query using the data source parameter specified in the first event message;
provide, via at least one processor, the modified query to a database;
obtain, via at least one processor, result data associated with executing the provided query;
update, via at least one processor, UI widget elements of the subsequent UI view component using the obtained result data;
determine, via at least one processor, a default selection of a UI widget element from the subsequent UI view component associated with the update;
determine, via at least one processor, a second data source parameter associated with the default selection;
generate, via at least one processor, a second event message that specifies the second data source parameter and the channel associated with the subsequent UI view component; and
broadcast, via at least one processor, the second event message.