The disclosure generally describes computer-implemented methods, software, and systems, including a method for presenting information. A command is identified from an application, the command associated with a configuration model. The identified command is matched to a step defined within the configuration model, each step in the configuration model associated with a request to a particular backend system, wherein each request is associated with at least one representation, the representation defining a visualization associated with the results returned in response to the request. The requested step is added to an analysis path, the analysis path storing a series of ordered steps performed during execution of the application. The request associated with the added step is executed including sending the request to the particular backend system for execution, and the analysis path is updated. A representation object is generated in response to executing the request.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method comprising: identifying a command from an application, the command associated with a configuration model; matching the identified command to a step defined within the configuration model, each step in the configuration model associated with a request to a particular backend system, wherein each request is associated with at least one representation, the representation defining a visualization associated with the results returned in response to the request; adding the requested step to an analysis path, the analysis path storing a series of ordered steps performed during execution of the application; executing the request associated with the added step including sending the request to the particular backend system for execution, and updating the analysis path; and generating a representation object in response to executing the request.
The system identifies a command from an application, where the command is linked to a configuration model. It matches the command to a specific step within the configuration model. Each step in the model is associated with a request to a backend system, and each request has a representation that defines how the results are visualized. The system adds this step to an "analysis path," which tracks the sequence of steps taken in the application. Then, it executes the request, sending it to the backend system, updates the analysis path to reflect the execution. Finally, it generates a representation object to display the results.
2. The method of claim 1 , further comprising, prior to identifying an initial command from the application, creating an empty analysis path and setting an initial context.
Before anything else happens, when the application starts, the system creates an empty "analysis path" to store the steps taken during analysis and sets up the initial context or state needed for the analysis. After creating the empty analysis path and setting the initial context, the system identifies a command from an application, where the command is linked to a configuration model. It matches the command to a specific step within the configuration model. Each step in the model is associated with a request to a backend system, and each request has a representation that defines how the results are visualized. The system adds this step to an "analysis path," which tracks the sequence of steps taken in the application. Then, it executes the request, sending it to the backend system, updates the analysis path to reflect the execution. Finally, it generates a representation object to display the results.
3. The method of claim 1 , wherein prior to executing the request associated with the added step, executing requests associated with each of the preceding steps in the analysis path.
Before the system executes the latest step added to the "analysis path," it first executes any requests associated with the preceding steps in the path. After executing requests associated with each of the preceding steps in the analysis path, the system identifies a command from an application, where the command is linked to a configuration model. It matches the command to a specific step within the configuration model. Each step in the model is associated with a request to a backend system, and each request has a representation that defines how the results are visualized. The system adds this step to an "analysis path," which tracks the sequence of steps taken in the application. Then, it executes the request, sending it to the backend system, updates the analysis path to reflect the execution. Finally, it generates a representation object to display the results.
4. The method of claim 3 , wherein executing each of the preceding steps in the analysis comprises executing the preceding steps in order from the first step in the path to the added step.
When the system executes the preceding steps in the "analysis path," it processes them in the order they appear in the path, starting from the first step and moving sequentially to the step immediately before the newly added step. After executing each of the preceding steps in order from the first step in the path to the added step, before the system executes the latest step added to the "analysis path," it first executes any requests associated with the preceding steps in the path. After executing requests associated with each of the preceding steps in the analysis path, the system identifies a command from an application, where the command is linked to a configuration model. It matches the command to a specific step within the configuration model. Each step in the model is associated with a request to a backend system, and each request has a representation that defines how the results are visualized. The system adds this step to an "analysis path," which tracks the sequence of steps taken in the application. Then, it executes the request, sending it to the backend system, updates the analysis path to reflect the execution. Finally, it generates a representation object to display the results.
5. The method of claim 1 , wherein one or more steps in the analysis path include one or more filters determined by the representation object, and wherein the method further comprises, prior to executing the request, retrieving a filter from the representation.
If any of the steps in the "analysis path" include filters (criteria for refining data), determined by the representation object, the system retrieves these filters from the representation object before executing the request. After retrieving a filter from the representation, the system identifies a command from an application, where the command is linked to a configuration model. It matches the command to a specific step within the configuration model. Each step in the model is associated with a request to a backend system, and each request has a representation that defines how the results are visualized. The system adds this step to an "analysis path," which tracks the sequence of steps taken in the application. Then, it executes the request, sending it to the backend system, updates the analysis path to reflect the execution. Finally, it generates a representation object to display the results.
6. The method of claim 1 , wherein added steps are executed using filters associated with preceding steps in the analysis path.
The system executes newly added steps in the "analysis path" using filters that were associated with the steps that came before it in the path. Added steps are executed using filters associated with preceding steps in the analysis path, and the system identifies a command from an application, where the command is linked to a configuration model. It matches the command to a specific step within the configuration model. Each step in the model is associated with a request to a backend system, and each request has a representation that defines how the results are visualized. The system adds this step to an "analysis path," which tracks the sequence of steps taken in the application. Then, it executes the request, sending it to the backend system, updates the analysis path to reflect the execution. Finally, it generates a representation object to display the results.
7. The method of claim 1 , further comprising: receiving a request to move a particular step to a new location in the analysis path; updating the order of the analytical path based on the request to move the particular step; and re-executing the requests associated with each step in order beginning with the first step in the analysis path.
If a user requests to move a step to a different position in the "analysis path," the system updates the order of the steps in the path to reflect the change. It then re-executes all the requests associated with each step in the path, starting from the very first step and proceeding in the updated order. After re-executing the requests associated with each step in order beginning with the first step in the analysis path, the system identifies a command from an application, where the command is linked to a configuration model. It matches the command to a specific step within the configuration model. Each step in the model is associated with a request to a backend system, and each request has a representation that defines how the results are visualized. The system adds this step to an "analysis path," which tracks the sequence of steps taken in the application. Then, it executes the request, sending it to the backend system, updates the analysis path to reflect the execution. Finally, it generates a representation object to display the results.
8. The method of claim 1 , wherein the configuration model defines a plurality of step prototypes, each step prototype defining a binding between a request and at least one representation.
The "configuration model" contains pre-defined "step prototypes." Each prototype specifies the connection (binding) between a request to a backend system and the representation (visualization) that should be used to display the results of that request. The configuration model defines a plurality of step prototypes, each step prototype defining a binding between a request and at least one representation. The system identifies a command from an application, where the command is linked to a configuration model. It matches the command to a specific step within the configuration model. Each step in the model is associated with a request to a backend system, and each request has a representation that defines how the results are visualized. The system adds this step to an "analysis path," which tracks the sequence of steps taken in the application. Then, it executes the request, sending it to the backend system, updates the analysis path to reflect the execution. Finally, it generates a representation object to display the results.
9. A system comprising: memory storing: at least one configuration model defining a plurality of steps, each step associated with at least one backend request to a backend system and each step further associated with at least one representation corresponding to each backend request, the representation defining a visualization associated with the backend request; and a runtime data model comprising a runtime object defining an analysis path associated with at least one step from the configuration model and the execution of an application; an application for: receiving information associated with representations corresponding to steps in the configuration model; displaying representations and information for the configuration model in a user interface; receiving user inputs through the user interface relative to the representations and user selections associated with the configuration model; and sending user requests, each user request associated with a step from a particular configuration; and an analytical processor for: receiving user requests identifying a command from an application, the command associated with the configuration model, the command associated with adding, moving, removing or updating a particular step; matching the identified command to a step defined within the configuration model; adding the requested step in an analysis path, the analysis path storing a series of ordered steps performed during execution of the application, and updating the analysis path; providing the backend request associated with the requested step to the particular backend system for execution; generating a representation object in response to executing the backend request, the representation object for use in updating the visualization; and sending the representation object to the application.
The system includes memory storing a configuration model. The configuration model defines steps, each associated with a backend request and a visualization (representation). A runtime data model stores an analysis path with steps from the configuration model based on application execution. An application displays the representations, receives user input, and sends user requests associated with configuration model steps. An analytical processor receives these requests, matches them to configuration model steps (add, move, remove, update), updates the analysis path, sends backend requests to the backend system, generates representation objects for visualization updates, and sends the representation objects to the application.
10. The system of claim 9 , wherein the analytical processor, prior to providing the backend request associated with the added step to the particular backend system for execution, executes requests associated with each of the preceding steps in the analysis path.
Before the analytical processor sends a request associated with a newly added step to the backend system, it executes the requests associated with all the preceding steps already present in the analysis path. The analytical processor, prior to providing the backend request associated with the added step to the particular backend system for execution, executes requests associated with each of the preceding steps in the analysis path. The system includes memory storing a configuration model. The configuration model defines steps, each associated with a backend request and a visualization (representation). A runtime data model stores an analysis path with steps from the configuration model based on application execution. An application displays the representations, receives user input, and sends user requests associated with configuration model steps. An analytical processor receives these requests, matches them to configuration model steps (add, move, remove, update), updates the analysis path, sends backend requests to the backend system, generates representation objects for visualization updates, and sends the representation objects to the application.
11. The system of claim 9 , wherein one or more steps in the analysis path include one or more filters.
One or more of the steps within the analysis path may include filters, which are criteria used to refine the data being processed or displayed. One or more steps in the analysis path include one or more filters. The system includes memory storing a configuration model. The configuration model defines steps, each associated with a backend request and a visualization (representation). A runtime data model stores an analysis path with steps from the configuration model based on application execution. An application displays the representations, receives user input, and sends user requests associated with configuration model steps. An analytical processor receives these requests, matches them to configuration model steps (add, move, remove, update), updates the analysis path, sends backend requests to the backend system, generates representation objects for visualization updates, and sends the representation objects to the application.
12. The system of claim 9 , wherein steps are executed using filters associated with preceding steps in the analysis path.
When executing steps in the analysis path, the system uses filters associated with the steps that precede the current step. Steps are executed using filters associated with preceding steps in the analysis path. The system includes memory storing a configuration model. The configuration model defines steps, each associated with a backend request and a visualization (representation). A runtime data model stores an analysis path with steps from the configuration model based on application execution. An application displays the representations, receives user input, and sends user requests associated with configuration model steps. An analytical processor receives these requests, matches them to configuration model steps (add, move, remove, update), updates the analysis path, sends backend requests to the backend system, generates representation objects for visualization updates, and sends the representation objects to the application.
13. The system of claim 9 , the analytical processor further performing: receiving a request to move or remove a particular step in the analysis path; updating the order of the analytical path based on the request; and re-executing the requests associated with each step in order beginning with the first step in the analysis path.
The analytical processor can also handle requests to move or remove steps in the analysis path. When such a request is received, the processor updates the order of steps in the path and re-executes all the requests, starting from the first step, to ensure that the data and visualizations are consistent with the new path configuration. The analytical processor further performing: receiving a request to move or remove a particular step in the analysis path; updating the order of the analytical path based on the request; and re-executing the requests associated with each step in order beginning with the first step in the analysis path. The system includes memory storing a configuration model. The configuration model defines steps, each associated with a backend request and a visualization (representation). A runtime data model stores an analysis path with steps from the configuration model based on application execution. An application displays the representations, receives user input, and sends user requests associated with configuration model steps. An analytical processor receives these requests, matches them to configuration model steps (add, move, remove, update), updates the analysis path, sends backend requests to the backend system, generates representation objects for visualization updates, and sends the representation objects to the application.
14. The system of claim 9 , wherein the configuration model defines a plurality of step prototypes, each step prototype defining a binding between a request and at least one representation, the binding defining required filter properties, and the representation, when requested, converts any user interface selection into a filter expressed over the required filter properties.
The configuration model has step prototypes linking a request to a representation, defining required filter properties. The representation turns UI selections into filters based on those properties. The configuration model defines a plurality of step prototypes, each step prototype defining a binding between a request and at least one representation, the binding defining required filter properties, and the representation, when requested, converts any user interface selection into a filter expressed over the required filter properties. The system includes memory storing a configuration model. The configuration model defines steps, each associated with a backend request and a visualization (representation). A runtime data model stores an analysis path with steps from the configuration model based on application execution. An application displays the representations, receives user input, and sends user requests associated with configuration model steps. An analytical processor receives these requests, matches them to configuration model steps (add, move, remove, update), updates the analysis path, sends backend requests to the backend system, generates representation objects for visualization updates, and sends the representation objects to the application.
15. A computer-readable media, the computer-readable media comprising computer-readable instructions embodied on tangible, non-transitory media, the instructions operable when executed by at least one computer to: identify a command from an application, the command associated with a configuration model; match the identified command to a step defined within the configuration model, each step in the configuration model associated with a request to a particular backend system, wherein each request is associated with at least one representation, the representation defining a visualization associated with the results returned in response to the request; add the requested step to an analysis path, the analysis path storing a series of ordered steps performed during execution of the application; execute the request associated with the added step including sending the request to the particular backend system for execution; and generate a representation object in response to executing the request.
A computer-readable medium stores instructions. When executed, they identify a command from an application associated with a configuration model. The command is matched to a step in the model, which links to a backend request and visualization. The step is added to an analysis path tracking application steps. The backend request for the step is executed. Finally, a visualization object is generated to display the results.
16. The computer-readable media of claim 15 , wherein the instructions further include instructions for, prior to executing the request associated with the added step, executing requests associated with each of the preceding steps in the analysis path.
The computer-readable medium's instructions also include steps to execute requests for each preceding step in the analysis path before the current step's request is executed. The instructions further include instructions for, prior to executing the request associated with the added step, executing requests associated with each of the preceding steps in the analysis path. A computer-readable medium stores instructions. When executed, they identify a command from an application associated with a configuration model. The command is matched to a step in the model, which links to a backend request and visualization. The step is added to an analysis path tracking application steps. The backend request for the step is executed. Finally, a visualization object is generated to display the results.
17. The computer-readable media of claim 15 , wherein one or more steps in the analysis path include one or more filters.
One or more steps in the analysis path may include one or more filters for refining the data. One or more steps in the analysis path include one or more filters. A computer-readable medium stores instructions. When executed, they identify a command from an application associated with a configuration model. The command is matched to a step in the model, which links to a backend request and visualization. The step is added to an analysis path tracking application steps. The backend request for the step is executed. Finally, a visualization object is generated to display the results.
18. The computer-readable media of claim 15 , wherein added steps are executed using filters associated with preceding steps in the analysis path.
When executing added steps in the analysis path, the steps are executed using filters associated with preceding steps in the path to refine the data based on earlier steps. Added steps are executed using filters associated with preceding steps in the analysis path. A computer-readable medium stores instructions. When executed, they identify a command from an application associated with a configuration model. The command is matched to a step in the model, which links to a backend request and visualization. The step is added to an analysis path tracking application steps. The backend request for the step is executed. Finally, a visualization object is generated to display the results.
19. The computer-readable media of claim 15 , the wherein the instructions further include instructions for: receiving a request to move a particular step to a new location in the analysis path; updating the order of the analytical path based on the request to move the particular step; and re-executing the requests associated with each step in order beginning with the first step in the analysis path.
The computer-readable medium's instructions include steps for receiving a request to move a step in the analysis path, updating the path's order accordingly, and re-executing all requests from the start of the path. The wherein the instructions further include instructions for: receiving a request to move a particular step to a new location in the analysis path; updating the order of the analytical path based on the request to move the particular step; and re-executing the requests associated with each step in order beginning with the first step in the analysis path. A computer-readable medium stores instructions. When executed, they identify a command from an application associated with a configuration model. The command is matched to a step in the model, which links to a backend request and visualization. The step is added to an analysis path tracking application steps. The backend request for the step is executed. Finally, a visualization object is generated to display the results.
20. The computer-readable media of claim 15 , wherein the configuration model defines a plurality of step prototypes, each step prototype defining a binding between a request and at least one representation.
The configuration model defines multiple step prototypes, each defining a binding between a request and at least one representation (visualization). The configuration model defines a plurality of step prototypes, each step prototype defining a binding between a request and at least one representation. A computer-readable medium stores instructions. When executed, they identify a command from an application associated with a configuration model. The command is matched to a step in the model, which links to a backend request and visualization. The step is added to an analysis path tracking application steps. The backend request for the step is executed. Finally, a visualization object is generated to display the results.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
January 21, 2015
August 1, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.