Domain Scripting Framework for Enterprise Workflow Adaptability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional enterprise applications require costly and time-consuming recompilation and redeployment to make changes to their workflow or services, and they lack efficient fault management, leading to frustration and potential system errors.
Innovation Solution
A domain scripting language architecture is implemented, where scripts on a database are updated by a runtime engine to change the workflow without recompiling, and a 'savepoint' feature creates snapshots for reliable fault management, allowing for quick changes and error recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a conventional workflow layer is used in enterprise applications, then the application provides structured business flow orchestration, but any changes to workflow or services require costly recompilation and redeployment
Solution Approach 1:
The patent segments the workflow layer from the core application by introducing a separate runtime engine that executes workflows independently. Workflows are stored as scripts in a database, allowing them to be modified without recompiling the application core. This segmentation enables workflow changes to be made by simply updating database scripts rather than recompiling the entire application.
Solution Approach 2:
The patent implements dynamic workflow modification by allowing workflows to be changed at runtime through database script updates. The runtime engine dynamically loads and executes updated workflows without requiring application restart or recompilation. This dynamic approach transforms static, compiled workflows into flexible, runtime-adjustable processes.
2Productivity
If the workflow layer is compiled into the application, then the application has good performance, but fault management becomes complex and time-consuming
Solution Approach 1:
The patent extracts the workflow execution logic from the compiled application by implementing a separate runtime engine. This extraction allows the core application to maintain optimized compiled performance while workflow faults can be managed independently through database script updates and runtime engine adjustments, simplifying fault management.
Solution Approach 2:
The patent enables fault management through parameter changes in the workflow scripts stored in the database. By modifying script parameters and logic at runtime rather than recompiling, faults can be addressed through simple parameter adjustments and script updates, making fault management easier and faster.
3Adaptability or versatility
If changes are made to the workflow layer after deployment, then the application adapts to new requirements, but the application must be disabled and recompiled
Solution Approach 1:
The patent implements preliminary action by pre-storing workflow scripts in the database before they are needed. When changes are required, the updated scripts are prepared and uploaded to the database in advance, allowing the runtime engine to execute the new workflows immediately without interrupting the application or requiring compilation.
Solution Approach 2:
The patent uses copying by storing workflow definitions as scripts in the database, creating a copyable representation of workflows that can be modified and uploaded without affecting the running application. This copying mechanism allows workflow changes to be made by replacing database scripts rather than recompiling the application, maintaining system availability.
Data Source
AI summary
Systems and methods are disclosed herein to a computer-implemented method of executing an enterprise application comprising: receiving, by a computer, an external request for a service provided by a runtime engine of the enterprise application; selecting, by a computer, a script from a plurality of scripts saved on a database based on the external request; referencing, by the computer, one or more tags stored in a tag library saved on the database that are called by the script, wherein the tags in the tag library define commands of the plurality of scripts and call one or more granular services of the enterprise application; loading, by a computer, the selected script and the tags referenced by the selected script; and executing, by a computer, instructions of the script to provide the service requested by the external request, wherein the selected script is updated in the database after executing instructions of the script.