Workflow Re-evaluation for Dynamic Task Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In dynamic business processes like e-procurement, traditional workflows struggle to handle unexpected changes efficiently, often requiring complete re-initiation of processes, which is time-consuming and resource-intensive, and lack flexibility in exception handling.

Innovation Solution

Implementing a workflow re-evaluation mechanism that identifies and re-executes only necessary tasks based on predefined re-evaluation rules, allowing for granular control at various levels, including task and workflow fragments, and integrating exception handling dynamically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete process re-initiation is performed when unexpected changes occur, then process correctness is ensured, but time consumption and resource usage increase significantly

Engineering Contradiction:
Improveprocess correctnessVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The workflow is divided into individual tasks that can be independently evaluated. When a change occurs, only the affected tasks are identified and re-executed, rather than re-executing the entire workflow. This segmentation allows for selective re-execution based on change impact analysis.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically determines which tasks need re-execution based on the type of change detected. The re-evaluation mechanism adapts the re-execution scope according to the specific change scenario, making the process flexible rather than rigidly re-executing all tasks or none.

Inventive Principle:
Principle #15Dynamics

2Reliability

If complete process re-initiation is performed when unexpected changes occur, then process correctness is ensured, but resource consumption increases significantly

Engineering Contradiction:
Improveprocess correctnessVSAvoidresource usage
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The workflow is divided into individual tasks that can be independently evaluated. When a change occurs, only the affected tasks are identified and re-executed, rather than re-executing the entire workflow. This segmentation allows for selective re-execution based on change impact analysis.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the execution state parameter of individual tasks based on change impact analysis. Tasks are marked for re-execution, skipping, or cancellation based on their relationship to the detected change, optimizing resource utilization.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If traditional workflow approaches are used, then process simplicity is maintained, but flexibility in handling unexpected changes is reduced

Engineering Contradiction:
Improveprocess simplicityVSAvoidflexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary evaluation of task dependencies and change impacts before executing the workflow. By pre-analyzing which tasks are affected by changes, the system can quickly determine the appropriate re-execution scope without complex runtime decisions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where change detection triggers re-evaluation of task execution requirements. The outcome of change impact analysis feeds back into the workflow execution decision, creating a closed-loop system that adapts to changes while maintaining structural simplicity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8429668B2Workflow task re-evaluation
Publication Date: 2013.04.23 SAP SE
  • US8429668B2 patent drawing
  • US8429668B2 patent drawing
  • US8429668B2 patent drawing

AI summary

An occurrence of a workflow re-evaluation event during execution of tasks in a workflow is identified. In response to the workflow re-evaluation event, it is determined for each task previously executed in the workflow whether such task needs to be executed again. Those tasks in the workflow for which it was determined that the corresponding task needs to be executed again are executed again, while the tasks in the workflow that were previously executed and for which it was not determined that the corresponding task needs to be executed again are skipped. Related apparatus, systems, techniques and articles are also described.