Domain-Agnostic Graphical Flow Interface for Back-End Data Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional graphical user interface (GUI) design requires dual implementation of user interface frameworks, leading to inefficiencies in managing and displaying back-end graphical flow models, as changes and improvements need to be made in both back-end and front-end implementations, causing maintenance and scalability issues.

Innovation Solution

A system that manages the visual presentation of a back-end graphical flow model on a domain-agnostic graphical flow interface, where the back-end server handles all logic and updates, transmitting action and update messages to the client device to dynamically update the visual presentation, using renderer objects that comply with standards like React and HTML, allowing for a single implementation that is portable across different front-end applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If dual implementation of user interface framework is used (both back-end and front-end), then functionality can be implemented, but code complexity and maintenance difficulty increase

Engineering Contradiction:

ImprovefunctionalityVSAvoidcode complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the visual presentation logic from the front-end and consolidates it into the back-end graphical flow model. The back-end now contains both the business logic and the visual presentation definitions, eliminating the need for separate front-end implementation. This extraction resolves the contradiction by reducing code complexity while maintaining functionality through centralized model management.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The back-end graphical flow model is designed to serve multiple functions: it stores business logic, defines visual presentation, and generates both backend code and frontend code. This multi-functionality eliminates the need for separate dual implementations, reducing code complexity while maintaining adaptability across different platforms and frameworks.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If dual implementation is used, then complete functionality is achieved, but efficiency in managing and displaying models decreases

Engineering Contradiction:

ImprovefunctionalityVSAvoidmanagement efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges the back-end logic and front-end visual presentation into a unified graphical flow model stored in the back-end. This consolidation eliminates the need to manage separate implementations, improving management efficiency while maintaining complete functionality through the integrated model that encompasses both business logic and presentation definitions.

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If changes are made in both back-end and front-end implementations, then functionality is maintained, but maintenance difficulty increases

Engineering Contradiction:

ImprovefunctionalityVSAvoidmaintenance difficulty

Core Design Contradiction:

ReliabilityVSEase of repair

Solution Approach 1:

The patent extracts visual presentation definitions from the front-end implementation and stores them within the back-end graphical flow model. This extraction means that all changes to visual presentation can now be made in a single location (the back-end model) rather than requiring coordinated changes in both back-end and front-end code, significantly reducing maintenance difficulty while maintaining functionality.

Inventive Principle:

Principle #2Taking out (Extraction)

4Adaptability or versatility

If proprietary logic is exposed in front-end implementation, then functionality is achieved, but security decreases

Engineering Contradiction:

ImprovefunctionalityVSAvoidsecurity

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts and consolidates all logic definitions into the back-end graphical flow model, keeping proprietary logic secure on the server side. The front-end becomes a thin client that only displays and interacts with the model without containing any proprietary logic, thus maintaining functionality while improving security by protecting sensitive business logic from exposure.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS20250004620A1Back-end data management system for visual presentation of a back-end graphical flow model on a domain agnostic graphical flow interface

Publication Date: 2025.01.02 ATLASSIAN US INC

AI summary

Methods and apparatus for managing the visual presentation of a back-end graphical flow model on a domain agnostic graphical flow interface are provided. An example method receives, from a back-end server, a back-end graphical flow node of a back-end graphical flow model additionally having one or more back-end graphical flow edges. An example method also presents at a graphical flow interface, a displayed node visual object representing the back-end graphical flow node. The method is configured to detect a user interaction with the displayed node visual object and transmit to the back-end server, a back-end graphical flow action message based at least in part on the user interaction. A back-end graphical flow update message comprising one or more back-end graphical flow update properties is received from the back-end server, causing an update to the visual presentation of the displayed node visual object.