Rule Handling Component for Business Process Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computer systems lack the ability for non-technical users, such as business analysts or system administrators, to easily customize and modify business process rules within complex computer applications without accessing or modifying the underlying software code, especially when dealing with numerous rules and complex data structures.

Innovation Solution

A rule handling component that allows users to define and assign business process rules at specific points in a transaction process, using data structures for rule collections, rule data, and rule conditions, enabling the execution of customized processes without requiring programming knowledge, and integrating with generic components to process transaction data in a manner applicable to various business enterprises.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users modify computer programs to customize application behavior, then customization capability is improved, but programming knowledge and complexity are required

Engineering Contradiction:
Improvecustomization capabilityVSAvoidprogramming knowledge requirement
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary layer consisting of declarative rule data structures that mediate between users and the application program. Users define customization rules using simple data structures (rule conditions, rule actions, rule parameters) rather than modifying program code directly. This intermediary rule-handling mechanism translates user-friendly rule definitions into application behavior modifications, eliminating the need for programming knowledge while maintaining full customization capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the customization functionality into distinct, manageable rule data structures including rule conditions, rule actions, and rule parameters. Each rule is broken down into discrete components that can be independently defined and configured. This segmentation allows users to customize application behavior by assembling rules from modular components without needing to understand the underlying program structure or coding logic.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If a second custom application program is developed and integrated with the original application, then customization capability is improved, but system complexity and integration requirements increase

Engineering Contradiction:
Improvecustomization capabilityVSAvoidsystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the customization functionality directly into the existing application program by implementing a rule-handling component within the application's data processing layer. Instead of developing and integrating a separate custom application, the rule evaluation and execution mechanisms are combined with the application's existing transaction processing. This integration approach maintains customization capability while reducing system complexity by eliminating the need for separate custom application development and inter-program integration.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If comprehensive rule data structures are implemented to store rule collections, rule data, and rule conditions, then rule management capability is improved, but data structure complexity increases

Engineering Contradiction:
Improverule management capabilityVSAvoiddata structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universal rule data structure templates that can accommodate multiple types of rules and conditions through standardized fields (rule conditions, rule actions, rule parameters). These multi-functional data structures can represent diverse business rules without requiring separate complex structures for each rule type. The universal template approach simplifies data structure management by providing a consistent framework that handles various rule scenarios through the same structural pattern.

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

Solution Approach 2:

The patent uses template-based rule data structures that can be copied and reused across different rules. Instead of creating unique complex data structures for each rule, standardized rule templates are defined once and then instantiated multiple times with different parameter values. This copying approach reduces data structure complexity by eliminating redundant structural definitions while maintaining the ability to manage comprehensive rule collections through repeated use of the same template structure.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7756808B2Apparatus and product of manufacture for using condition data structures separately from rule data structures in business transactions
Publication Date: 2010.07.13 SAP SE
  • US7756808B2 patent drawing
  • US7756808B2 patent drawing
  • US7756808B2 patent drawing

AI summary

Techniques enable a user, such as a business analyst or a system administrator, to define business process rules that control the processing of transaction data by a computer application. A data structure is used to store business process rules. The data structure includes a condition portion and an execution portion of a rule. At runtime, the computer system executing a computer application determines whether a condition portion of a rule is met, and in response to a determination that the condition portion is met, performs an execution portion of the rule.