Automatic detection of problems in a large-scale multi-record update system and method

US10204134B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10204134-B2
Application numberUS-201414459664-A
CountryUS
Kind codeB2
Filing dateAug 14, 2014
Priority dateAug 14, 2014
Publication dateFeb 12, 2019
Grant dateFeb 12, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer program product residing on a non-transitory computer readable storage medium having a plurality of instructions stored thereon which, when executed by a processor, cause the processor to perform operations comprising: identifying a change to at least one record of a plurality of records in a multi-record update including a change to at least one field of the at least one record, the multi-record update including making changes to multiple records based on a recording of changes made directly on a single record; determining at least one problem condition associated with the change to the at least one record, wherein the at least one problem condition is determined via at least one problem definition object before the change is saved, wherein the at least one problem definition object includes one or more of at least one field-based problem definition and at least one record-based problem definition, wherein the at least one field-based problem definition determines whether a change to the at least one field is a problem condition and the at least one record-based problem definition determines whether a change to the at least one record as a whole is a problem condition, wherein the at least one problem condition associated with the change to the at least one record is determined by at least one of analyzing the change to the at least one record based upon, at least in part, predefined rules for determining common problems and by allowing a user, via a user interface, to define a set of rules and amend existing problem definitions to detect the at least one problem; organizing the at least one problem condition on a display, wherein organizing includes organizing into a group each of the plurality of records resulting from the change to the at least one record that is determined to be the problem condition defined by the at least one problem definition object; and executing an action on the at least one problem condition displayed for each of the plurality of records organized into the group, wherein executing the action is captured in a single object of data containing information about the order of the one or more changes to the at least one record, wherein the one or more changes is played back in the order in which the user executes the action, wherein the action includes at least one of ignoring the at least one problem condition, cancelling the change to the at least one record, and correcting the change to the at least one record, wherein the action is executed in response to receiving a selection of at least one button in a user interface, wherein the at least one button is associated with at least one of ignoring the at least one problem, cancelling the change, and correcting the change. 2. The computer program product of claim 1 wherein identifying the change to the at least one record includes monitoring changes in a directly selected record of the plurality of records. 3. The computer program product of claim 1 wherein identifying the change to the at least one record includes monitoring changes in a related record of the plurality of records that results from a changed workflow logic. 4. The computer program product of claim 1 wherein the problem definition object is customizable. 5. The computer program product of claim 1 wherein the at least one problem condition is organized on the display based upon, at least in part, at least one of the at least one record that is determined to have the at least one problem condition via the at least one problem definition object due to the change, the at least one problem condition object used to determine the at least one problem condition, and severity of the at least one problem condition. 6. The computer program product of claim 1 wherein the action is executed on at least a portion of the at least one problem condition displayed. 7. A computing system including a processor and a memory configured to perform operations comprising: identifying a change to at least one record of a plurality of records in a multi-record update including a change to at least one field of the at least one record, the multi-record update including making changes to multiple records based on a recording of changes made directly on a single record; determining at least one problem condition associated with the change to the at least one record, wherein the at least one problem condition is determined via at least one problem definition object before the change is saved, wherein the at least one problem definition object includes one or more of at least one field-based problem definition and at least one record-based problem definition, wherein the at least one field-based problem definition determines whether a change to the at least one field is a problem condition and the at least one record-based problem definition determines whether a change to the at least one record as a whole is a problem condition, wherein the at least one problem condition associated with the change to the at least one record is determined by at least one of analyzing the change to the at least one record based upon, at least in part, predefined rules for determining common problems and by allowing a user, via a user interface, to define a set of rules and amend existing problem definitions to detect the at least one problem; organizing the at least one problem condition on a display, wherein organizing includes organizing into a group each of the plurality of records resulting from the change to the at least one record that is determined to be the problem condition defined by the at least one problem definition object; and executing an action on the at least one problem condition displayed for each of the plurality of records organized into the group, wherein executing the action is captured in a single object of data containing information about the order of the one or more changes to the at least one record, wherein the one or more changes is played back in the order in which the user executes the action, wherein the action includes at least one of ignoring the at least one problem condition, cancelling the change to the at least one record, and correcting the change to the at least one record, wherein the action is executed in response to receiving a selection of at least one button in a user interface, wherein the at least one button is associated with at least one of ignoring the at least one problem, cancelling the change, and correcting the change. 8. The computing system of claim 7 wherein identifying the change to the at least one record includes monitoring changes in a directly selected record of the plurality of records. 9. The computing system of claim 7 wherein identifying the change to the at least one record includes monitoring changes in a related record of the plurality of records that results from a changed workflow logic. 10. The computing system of claim 7 wherein the problem definition object is customizable. 11. The computing system of claim 7 wherein the at least one problem condition is organized on the display based upon, at least in part, at least one of the at least one record that is determined to have the at least one problem condition via the at least one problem definition object due to the change, the at least one problem condition object used to determine the at least one problem condition, and severity of the at least one problem condition.

Assignees

Inventors

Classifications

  • Physics · mapped topic

  • Physics · mapped topic

  • Change logging, detection, and notification (replication G06F16/27) · CPC title

  • Bulk updating operations (data conversion details G06F16/258) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10204134B2 cover?
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…
Who is the assignee on this patent?
IBM
What technology area does this patent fall under?
Primary CPC classification G06F17/3038. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 12 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).