Multi-Record Update Problem Detection via Customizable Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In data repositories, multi-record updates can lead to issues where changes made to one record are not accurately reflected across related records, and the complexity of customized workflows makes it difficult to identify and address potential problems before saving changes, potentially causing errors that affect large numbers of records.

Innovation Solution

A method that identifies changes to records in a multi-record update by monitoring both directly selected and related records, using a customizable problem definition object to determine problem conditions, and organizing these conditions for display, allowing actions such as ignoring, cancelling, or correcting changes to prevent errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multi-record updates are performed to efficiently update multiple records at once, then productivity is improved, but the likelihood of errors affecting large numbers of records increases

Engineering Contradiction:
Improveupdate efficiencyVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary validation by monitoring changes to directly selected records and related records before the multi-record update is executed. Problem conditions are identified and presented to the user for review, allowing corrections to be made before the changes are saved, thus preventing errors from propagating to multiple records.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback by automatically detecting problem conditions in both directly selected and related records, organizing these problems for display, and allowing users to take actions (ignore, cancel, or correct) before the update is committed. This feedback loop ensures data integrity while maintaining update efficiency.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If customized workflows are implemented to match customer business practices, then adaptability is improved, but the complexity of identifying and addressing potential problems increases

Engineering Contradiction:
Improveworkflow customizationVSAvoidproblem detection complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The problem definition object is designed to be customizable and can be configured to work with different customized workflows. The same problem definition object framework handles various workflow scenarios, making the system adaptable to different customer business practices while maintaining a consistent approach to problem detection and resolution.

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

3Loss of information

If changes are made to directly selected and related records, then completeness of update is improved, but the difficulty of detecting and measuring potential problems increases

Engineering Contradiction:
Improveupdate completenessVSAvoidproblem detection difficulty
Core Design Contradiction:
Loss of informationVSDifficulty of detecting and measuring

Solution Approach 1:

The system segments problem detection into two distinct parts: monitoring changes to directly selected records and monitoring changes to related records. This segmentation allows the system to comprehensively track all affected records while organizing problems in a manageable way for user review and resolution.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10180957B2Automatic detection of problems in a large-scale multi-record update system and method
Publication Date: 2019.01.15 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10180957B2 patent drawing
  • US10180957B2 patent drawing
  • US10180957B2 patent drawing

AI summary

A method, computer program product, and computer system for identifying, by a computing device, a change to at least one record of a plurality of records in a multi-record update. At least one problem condition associated with the change to the at least one record is determined, wherein the at least one problem condition is determined via at least one problem definition object before the change is saved. The at least one problem condition is organized on a display. An action is executed on the at least one problem condition displayed.