Transaction Load Reduction for Process Instance Completion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The high transaction load associated with process instance completion in business process management systems, particularly due to the need for frequent finalization actions on numerous status variables, leads to significant performance penalties and increased turnaround time.

Innovation Solution

The system identifies the type of end event for a process instance, determines the presence of additional tokens, and performs termination actions by joining finalization actions into a single completion transaction, reducing the number of transactions required for process instance termination.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate transactions are performed for each finalization action on process instance variables, then data consistency and proper cleanup are ensured, but transaction load increases significantly and turnaround time increases

Engineering Contradiction:
Improvedata consistencyVSAvoidturnaround time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent combines multiple separate finalization transactions into a single transaction by joining them together. When an end event is triggered and no additional tokens are found, the system merges all finalization actions for process instance variables into one completion transaction, thereby reducing transaction load and turnaround time while maintaining data consistency through the atomicity of the merged transaction.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If frequent process terminations are performed to avoid memory leaks and maintain system health, then system reliability is improved, but performance penalties increase due to high transaction load

Engineering Contradiction:
Improvesystem healthVSAvoidperformance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple finalization transactions into a single transaction, reducing the overall transaction load associated with process terminations. This allows the system to maintain frequent process terminations for memory leak prevention and system health while minimizing the performance penalty through reduced transaction overhead.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The merged completion transaction serves multiple functions simultaneously: it performs finalization actions on process instance variables, cleans up status variables, notifies business process management components, and terminates the process instance. This multi-functionality reduces the number of separate transactions needed while maintaining system reliability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If multiple finalization transactions are executed for each process instance variable, then complete cleanup is ensured, but resource contentions increase and system overhead increases

Engineering Contradiction:
Improvecleanup completenessVSAvoidsystem overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent joins multiple finalization transactions into a single merged transaction that handles all process instance variable cleanups atomically. This ensures complete cleanup while reducing resource contentions and system overhead by eliminating the need for multiple separate transaction executions.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8863131B2Transaction load reduction for process completion
Publication Date: 2014.10.14 SAP SE
  • US8863131B2 patent drawing
  • US8863131B2 patent drawing
  • US8863131B2 patent drawing

AI summary

The present disclosure involves systems, software, and computer implemented methods for reducing transaction load for process instance completion. One process includes identifying an end event triggered by an initial token of a process instance, determining a type of the end event, performing a search for additional tokens associated with the process instance that are distinct from the initial token, and performing a termination action based on the type of end event and a number of additional tokens identified in the search. The end event type may be non-terminating or terminating, and the end event type can determine the termination action to be performed. If the end event is non-terminating, then the termination action includes joining each finalization action for each process instance variable to a completion transaction if no additional tokens are found and executing the completion transaction to terminate the process instance.