Transaction Mapping Filter for Decoupled Workflow Specification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction processing systems require code changes to add or modify links between workflows and transactions, making it impractical for continuously running business applications, such as web applications, to handle various results of transaction execution.
Innovation Solution
A transaction mapping filter that detects requests and responses to specify workflows based on transaction results, allowing designers to define mappings in an XML document, which are then used to initiate corresponding workflows without interfering with the application's core logic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If business application code is modified to add or modify workflow links, then workflow specification flexibility is improved, but application reliability deteriorates due to continuous code changes in running systems
Solution Approach 1:
The system segments workflow specification from application code by introducing a separate workflow configuration file (XML format) that stores workflow definitions independently. This allows workflow links to be modified without changing the application code, thus maintaining application stability while improving workflow flexibility.
Solution Approach 2:
The patent introduces an intermediary component (workflow engine) that reads workflow definitions from external configuration files and translates them into executable workflow instructions. This intermediary layer decouples workflow specification from application code, enabling flexible workflow changes without affecting the running application.
2Reliability
If workflow links are hard-coded in business applications, then application reliability is maintained, but workflow adaptability deteriorates requiring code changes for modifications
Solution Approach 1:
The system transforms static hard-coded workflow links into dynamic configurations by loading workflow definitions from external XML files at runtime. This allows workflow specifications to be changed dynamically without recompiling or restarting the application, achieving both reliability and adaptability.
Solution Approach 2:
The patent changes the parameter storage location from fixed code to external configuration files. Workflow parameters (links, conditions, actions) are stored as modifiable data in XML files rather than being compiled into the application, enabling flexible changes while maintaining application stability.
3Adaptability or versatility
If code changes are made to specify new workflows, then workflow functionality is improved, but ease of operation deteriorates due to development and deployment complexity
Solution Approach 1:
The system uses XML configuration files as a copyable template for workflow definitions. Designers can create, modify, and deploy workflow specifications by copying and editing XML files without involving code compilation or deployment processes, significantly improving ease of operation.
Data Source
AI summary
Enabling a designer to specify workflows to process various results of execution of transactions. A user specifies the specific workflow to be executed on the corresponding result of a transaction. A transaction mapping filter then detects the occurrence of each result and initiates execution of the corresponding workflow. As the transaction mapping filter can be implemented decoupled from the application software/code, a user can flexibly change the links of workflows to results of transactions, as desired in the specific situation.