Visual Workflow Integration with Logical Data Objects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for integrating web-based applications with back-end databases and logic require custom programming, which is cumbersome, error-prone, and demands extensive debugging, necessitating a more efficient approach to connect workflows with logical data objects (LDOs) without requiring knowledge of text-based programming languages.
Innovation Solution
The implementation of visual programming tools allows for the development of interactive workflow specifications that can be linked to LDOs, enabling read and write access to data without needing to know the underlying data structures or programming languages, using graphical user interfaces to define and execute workflows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If custom programming is used to connect web-based applications with back-end databases and logic, then integration functionality is achieved, but the process becomes cumbersome, error-prone, and requires extensive debugging
Solution Approach 1:
The patent introduces visual programming tools and workflow specification languages as intermediaries between the application developer and the back-end database system. These tools provide a standardized interface that eliminates the need for custom programming while maintaining reliable integration. The visual workflow specifications act as mediators that automatically generate the necessary integration code, reducing errors and debugging requirements.
Solution Approach 2:
The patent replaces manual text-based programming mechanics with visual programming interfaces. Instead of writing and debugging text code, developers use graphical elements and drag-and-drop operations to define workflows. This substitution eliminates syntax errors and logical errors associated with manual coding while maintaining the same integration functionality.
2Ease of operation
If text-based programming languages are required for workflow integration, then precise control over data access is achieved, but the barrier to entry increases and requires specialized knowledge
Solution Approach 1:
The patent substitutes text-based programming mechanics with visual programming interfaces. Developers interact with graphical elements, drag-and-drop components, and visual workflow definitions instead of writing code. This substitution makes workflow integration accessible to users without programming expertise while maintaining precise control over data access through the visual specification language.
Solution Approach 2:
The patent uses templates and pre-defined workflow patterns that can be copied and adapted. Instead of creating custom programming solutions from scratch, users can replicate proven workflow templates and modify them visually. This copying mechanism reduces the knowledge barrier while maintaining precise control over data access operations.
3Productivity
If visual programming tools are used to create workflow specifications, then development speed increases and programming expertise is not required, but the underlying data structure knowledge must be hidden
Solution Approach 1:
The patent introduces a visual workflow specification language as an intermediary layer between the user and the underlying data structures. This intermediary abstracts away complex data structure details while maintaining the ability to precisely control data access. The visual specifications automatically map to the underlying database operations without requiring users to understand the data structure implementation details.
Solution Approach 2:
The patent segments the workflow development process into distinct visual components that can be assembled independently. Each visual element represents a specific operation or data access pattern, allowing developers to focus on high-level workflow logic without being overwhelmed by underlying data structure complexity. This segmentation enables rapid development while hiding implementation details.
Data Source
AI summary
Methods and apparatus are disclosed for integrating a workflow with logical data objects (LDOs), which expose their own external access methods and hide underlying data items. An interactive workflow specification can be authored by visual programming, and the workflow can be performed at a workstation via a graphical user interface. The visually-programmed specification can be automatically converted to markup language statements invoking ABAP calls to the LDOs' access methods. Underlying organization of LDO data can be transparent to reads and writes of the LDO data during workflow performance. Other aspects are described, including configuration of the authoring interface, launching the workflow, and text analytics.