Integrated Workflow Rules Engine for Dynamic Business Logic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional workflow software products and rules engines are delivered as separate technologies with limited integration, resulting in a disconnected experience for users, where rules cannot be directly modeled against different aspects of a workflow, and there is a lack of equal access to runtime services.

Innovation Solution

An integrated workflow services system that includes a host process hosting a workflow foundation runtime engine and a rules engine, allowing rules to be directly modeled against workflow activities and fields, with equal access to runtime services, and providing a unified debugging and dynamic update mechanism.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If workflow software products and rules engines are delivered as separate technologies, then each technology can be developed and maintained independently, but users experience a disconnected experience and cannot directly model rules against workflow aspects

Engineering Contradiction:
ImproveAbility to model rules against workflow aspectsVSAvoidSystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges workflow software and rules engine into a single integrated system. The rules engine is embedded within the workflow engine, allowing rules to be directly modeled against workflow aspects such as activities, fields, and parameters. This unification eliminates the disconnected experience users faced with separate technologies while enabling direct rule modeling against workflow elements.

Inventive Principle:
Principle #5Merging (Combining)

2Ease of operation

If workflow and rules engine are integrated, then users can directly model rules against workflow aspects, but the system requires equal access to runtime services which increases complexity

Engineering Contradiction:
ImproveRule modeling capabilityVSAvoidRuntime service access structure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The integrated system implements a universal runtime service access structure where both workflow activities and rules engine share common access to runtime services through a unified interface. This allows the rules engine to access workflow runtime services (such as workflow instance information, activity context, and field data) using the same mechanisms as workflow activities, simplifying the overall architecture despite the enhanced rule modeling capabilities.

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

3Ease of operation

If rules are defined directly against workflow, then a connected experience is provided, but the system requires unified debugging and dynamic update mechanisms which affect reliability

Engineering Contradiction:
ImproveAuthoring experienceVSAvoidSystem stability during updates
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system implements dynamic update mechanisms that allow rules to be modified, added, or removed during workflow execution without requiring system suspension or recompilation. The integrated architecture enables real-time rule updates while maintaining system stability through coordinated management of workflow and rule states, ensuring that changes are applied safely without compromising overall system reliability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7509655B2Integration of workflow and rules
Publication Date: 2009.03.24 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7509655B2 patent drawing
  • US7509655B2 patent drawing
  • US7509655B2 patent drawing

AI summary

Various technologies for integrating workflow services are described. In accordance with one described embodiment, an integrated workflow services system includes a host process, such as a Windows® application program. The host process hosts a workflow foundation runtime engine for executing workflows and a workflow foundation library. A workflow executable by the workflow foundation runtime engine may include an activity (e.g., a policy activity) that defines a ruleset that includes a number of rules (e.g., business rules). At least one rule of the ruleset is defined directly against the workflow. Furthermore, the activity has access to a rules engine capable of evaluating rules in the ruleset.