Asynchronous Dashboard Query Prompting via JSON Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Dashboards are not fully compatible with web technologies optimized for mobile devices, particularly in executing queries originating from prompts, leading to compatibility issues and limitations in rendering dashboard documents across various platforms.
Innovation Solution
A client-server architecture converts dashboard files into a JavaScript-friendly JSON format, enabling asynchronous query prompting and rendering, allowing dashboard documents to be viewed in any modern browser or device using HTML5 and standard web technologies, eliminating the need for intermediate publishing steps and reducing dependency on specific software applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If dashboards are designed using traditional software applications, then dashboard functionality and data visualization capabilities are maintained, but compatibility with mobile web technologies and standard browsers is lost
Solution Approach 1:
The patent transforms the dashboard document format from proprietary binary formats to JSON (JavaScript Object Notation), a text-based format natively supported by web browsers. This parameter change in data representation enables dashboards to be rendered in standard browsers and mobile devices while maintaining execution reliability through structured data validation and asynchronous query processing mechanisms.
Solution Approach 2:
The patent introduces an intermediary conversion process that translates dashboard documents into a web-compatible format. The JSON representation acts as an intermediary between the original dashboard structure and the web rendering engine, enabling compatibility with HTML5 and JavaScript while preserving the original dashboard's data sources, visualizations, and prompt functionalities.
2Adaptability or versatility
If dashboard documents are converted to web-friendly formats, then compatibility with mobile devices and browsers is improved, but the ability to execute queries from prompts is compromised
Solution Approach 1:
The patent implements dynamic query execution through asynchronous JavaScript code that responds to user interactions with dashboard prompts. When a user provides input through a prompt, the system dynamically generates and executes the appropriate query against the data source, then updates the dashboard visualization with the results. This dynamic approach maintains ease of operation while ensuring cross-platform compatibility through web technologies.
Solution Approach 2:
The patent establishes a feedback loop where prompt inputs trigger query execution, which in turn generates results that update the dashboard display. This feedback mechanism ensures that query execution capability is preserved in the web-friendly format by continuously responding to user actions with real-time data updates, maintaining the interactive nature of dashboards across all platforms.
3Adaptability or versatility
If intermediate publishing steps are used to convert dashboards, then compatibility is achieved, but system complexity and deployment time increase
Solution Approach 1:
The patent extracts the essential dashboard components (data sources, visualizations, prompts, and layout) from the proprietary format and represents them directly in JSON structure. This extraction eliminates the need for intermediate publishing steps by directly translating the dashboard document into a web-compatible format that can be immediately rendered by browsers, reducing system complexity while maintaining platform compatibility.
Data Source
AI summary
A client receives data from a server that includes a dashboard generated at the server by converting each of a spreadsheet file and a dashboard structure file into a text-based, language-independent data interchange format. In addition, the dashboard includes at least one component dependent on at least one prompt. Thereafter, the at least one prompt is asynchronously rendered in a graphical user interface at the client. Data is later received that includes answers to one or more prompts. At least one query is subsequently executed based on the received answers. After results of the executed at least one query is received, the component having a corresponding received answer is rendered in the dashboard. Related apparatus, systems, techniques and articles are also described.