Declarative Transaction Control for Process Flow Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing process flow design tools in cloud computing environments face issues with database transactions, where executing invocable actions within pending transactions can lead to extended database connections, impacting other processes and requiring unnecessary steps or delays.
Innovation Solution
A system that provides a graphical user interface for users to configure database transaction control options, allowing them to commit or not commit pending transactions before executing process flow elements, based on metadata associated with the elements, to manage transaction flow efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If invocable actions are executed within pending database transactions, then transactional integrity is maintained, but database connection times are extended and process flow efficiency deteriorates
Solution Approach 1:
The system dynamically adjusts transaction commit behavior based on the type of process flow element being executed. Different elements (e.g., database operations vs. external service calls) have different transaction control settings, allowing the system to adapt transaction management to specific execution contexts and optimize both integrity and efficiency.
Solution Approach 2:
The patent changes the parameter of transaction commit timing based on element metadata. By reading metadata associated with each process flow element, the system determines whether to commit pending transactions before execution, during execution, or after execution, thereby optimizing performance while maintaining data integrity where required.
2Productivity
If database transactions are committed before executing process flow elements, then connection times are reduced and efficiency improves, but transactional integrity may be compromised
Solution Approach 1:
The system changes the transaction commit parameter dynamically based on element-specific metadata. For elements requiring strict transactional integrity (e.g., database write operations), the system configures commit behavior to occur at appropriate transaction boundaries, while for elements less sensitive to transaction state (e.g., read operations or external calls), different commit timing is applied.
Solution Approach 2:
Different transaction control qualities are applied to different process flow elements based on their specific requirements. Each element can have its own transaction control configuration, allowing localized optimization where strict integrity is needed for some elements while allowing more flexible timing for others.
3Reliability
If manual configuration steps are added to manage transaction commits, then transaction control is achieved, but process flow complexity increases
Solution Approach 1:
The system performs automatic transaction control management by reading metadata associated with each process flow element and autonomously determining the appropriate commit timing. This eliminates the need for manual configuration of transaction commits, as the system self-configures based on element characteristics, reducing complexity while maintaining reliable transaction control.
Solution Approach 2:
Metadata describing the transaction control requirements of each element is prepared in advance. This preliminary information allows the system to automatically make informed decisions about transaction commit timing during execution, eliminating the need for complex runtime analysis or manual configuration while ensuring proper transaction management.
Data Source
AI summary
Disclosed are some implementations of systems, apparatus, methods and computer program products for facilitating the implementation of declarative transaction control. A database transaction control configuration associated with an element of a process flow can be obtained via a graphical user interface (GUI) and stored in association the element. The database transaction control configuration indicates whether a pending database transaction is to be committed to a database prior to executing a set of computer-readable instructions corresponding to the element. During execution of the process flow, the database transaction control configuration is accessed and it is determined whether a currently pending database transaction is to be committed to a database prior to executing a set of computer-readable instructions corresponding to the element. The currently pending database transaction is committed to a database prior to executing the set of computer-readable instructions according to a result of the determination.