User Interface Defined Document System for Multi-Tenant Database Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for connecting user interfaces to backend database systems require extensive computer programming and are inefficient for multi-tenant databases, where each form or document type necessitates its own schema, leading to complex database management and limited flexibility in storing nested or chained documents.
Innovation Solution
A method that allows users to create customizable user interfaces and documents without coding or database management, using front-end design to generate unique schemas for each document, enabling the storage and analysis of complex data structures using map-reduce techniques, and allowing documents to contain sub-documents with dynamic schema generation and updating.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users define user interfaces in code using various programming languages and bind controls to backend code, then the user interface can be connected to the database system, but computer programming is required at multiple steps which increases complexity and reduces ease of use
Solution Approach 1:
The system allows users to define and configure user interfaces through visual designers and configuration files without requiring programming knowledge. The framework automatically handles the binding between interface elements and database operations, enabling non-programmers to create customized interfaces that connect to backend systems independently.
Solution Approach 2:
The patent introduces an intermediary framework layer that sits between the user interface definition and the database connection. This framework automatically generates the necessary binding code and configuration, mediating between the simple user interface definition and the complex database interaction requirements, thereby eliminating the need for users to write binding code manually.
2Ease of manufacture
If Object Relational Mapping tools are used to automatically generate databases from code, then database management is simplified, but each form requires its own view model that must be compiled and results in separate database schemas for each form type which complicates multi-tenant database management
Solution Approach 1:
The patent implements a universal configuration system where a single database schema can support multiple tenant organizations with different custom forms and fields. Instead of creating separate schemas for each form type, the system uses a unified schema with configurable fields that can be dynamically customized per tenant through configuration files and visual designers, allowing one schema to serve multiple purposes across different tenants.
Solution Approach 2:
The system employs dynamic configuration where the database schema remains static but the interpretation and usage of fields are dynamically adjusted per tenant through configuration files and runtime settings. This allows the same database structure to adapt to different organizational requirements without requiring separate schemas or compilation steps for each form type.
3Adaptability or versatility
If multiple extra columns are added to each database table to store end-user-definable information, then user-defined information can be stored, but the user is limited to the number of columns allowed per table and can only store simple values without nested documents
Solution Approach 1:
The patent implements a nested configuration structure where configuration files can contain nested elements representing hierarchical data structures. Users can define nested documents and chained documents within the configuration files, allowing complex data structures to be represented without requiring additional database columns. The system parses these nested configurations and stores them as structured data that can represent hierarchical relationships.
Solution Approach 2:
Instead of adding more columns horizontally to store user-defined information, the patent introduces a vertical dimension through nested configuration files and hierarchical data structures. This allows unlimited user-defined information to be stored by nesting configuration elements within existing structures, transforming the limitation from a horizontal column constraint to a vertical nesting capability that bypasses database column limits.
4Adaptability or versatility
If a key-value pair table is used to provide extra configurable information, then simple key-value pairs can be stored without compilation, but the table grows very large with billions of rows and lacks inherent structure making aggregation and reporting difficult
Solution Approach 1:
The patent applies local quality by organizing configuration data into structured sections and elements within configuration files, where each section serves a specific purpose (e.g., form definitions, field definitions, tenant-specific configurations). This local structuring allows efficient querying and aggregation by enabling the system to target specific sections rather than scanning entire unstructured key-value tables, thereby improving reporting efficiency while maintaining configuration flexibility.
Data Source
AI summary
The preferred embodiment of the invention encompasses a method used to (a) create computer applications, or (b) create database-backed forms/documents for a customizable user interface within an existing computer program, that (c) can then be stored, queried and analyzed using map-reduce techniques; using nothing but the front-end user-interface design performed on the device and without the use of any computer coding or database management or setup of any kind. The preferred embodiment invention permits both simple documents (also known as forms), documents-within-documents, and business processes that link documents together, to be defined and converted into a working application on a smart phone, tablet or computer system by end users without the use of code or database management by the end user.