Dynamic Workflow Engine for Multi-Tenant Database Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business processes in companies are often manual, leading to inconsistent execution, lost opportunities, and higher operating costs due to their inflexibility and inability to adapt quickly to changes in the marketplace.
Innovation Solution
A visual process manager is provided for a multi-tenant database system that allows users to design, simulate, and deploy dynamic workflows without restarting or rebooting the system, using a drag-and-drop designer, process simulator, and real-time process engine to ensure consistent execution and adaptability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual business processes are used, then flexibility and adaptability to market changes are improved, but execution consistency and operational efficiency deteriorate
Solution Approach 1:
The patent implements dynamic workflows that can be modified and updated in real-time without system restart. The workflow definitions are stored in a database and can be changed by users through a visual designer, allowing the process to adapt to market changes while maintaining consistent execution through automated enforcement of the defined workflow logic.
Solution Approach 2:
The patent replaces manual mechanical processes with an automated computer-based workflow system. The visual process manager and process engine automatically execute and enforce workflow definitions, eliminating human error and inconsistency while maintaining the ability to adapt through digital modifications rather than physical process changes.
2Adaptability or versatility
If dynamic workflow modification capability is added, then adaptability and responsiveness are improved, but system complexity and deployment difficulty increase
Solution Approach 1:
The patent introduces a visual process manager as an intermediary layer between users and the workflow execution system. This manager provides a simplified drag-and-drop interface for defining and modifying workflows, hiding the underlying complexity from users while enabling powerful dynamic workflow capabilities through the process engine.
Solution Approach 2:
The patent creates a universal workflow management system that handles multiple functions including workflow definition, simulation, deployment, and execution through a single integrated platform. The process engine can execute various types of workflows using a common framework, reducing overall system complexity despite the broad capabilities.
3Productivity
If workflow changes are implemented without system restart, then operational continuity and productivity are improved, but system stability and reliability may worsen
Solution Approach 1:
The patent implements a simulation capability that allows users to test workflow changes in a virtual environment before deploying them to production. This preliminary action ensures that workflow modifications are validated for correctness before being activated, maintaining system stability while enabling continuous operation without restart.
Solution Approach 2:
The patent implements dynamic workflow loading where workflow definitions are stored in a database and loaded into memory during execution. This allows the system to modify workflows dynamically without restart by simply updating the database records and reloading the affected workflow definitions into the process engine's memory.
Data Source
AI summary
Techniques and systems for modifying a virtual machine functionality. Archive files each including at least a class files are received. The archive files are stored within the virtual machine. The virtual machine runs on a host system and neither the virtual machine nor the host system are restarted in response to the receiving or storing of the archive files. Files of the host system are scanned to find class files that are not included in a class path for the virtual machine. The class files are copied to a class path for the virtual machine. Neither the virtual machine nor the host system are restarted in response to the copying of the class files. The classes corresponding to the class files are registered in the virtual machine in response to the copying of the class files to the class path. Neither the virtual machine nor the host system are restarted in response to the registration of the classes.