Data Object Versioning for Concurrent Workflow Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional workflow control systems are limited in collaborative data processing and unique referencing of data objects, as they do not allow concurrent processing by multiple users and are restricted to specific instances of data objects, leading to inappropriate actions when data objects change between notification and action execution.

Innovation Solution

A computer-based system and method that create a data object by preparing a data structure in a database, associating different workflow states with the data object at each processing stage, taking snapshots before transitions, and using unique locating references to enable controlled access to the data object and its snapshots, allowing multiple states to be accessed concurrently by multiple users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional workflow control systems are used to process data objects, then data objects can be processed at different processing stages with workflow states, but multiple users cannot concurrently process the same data object and the system is limited to specific instances of data objects

Engineering Contradiction:
Improveconcurrent processing capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments a data object into multiple versions, where each version represents a specific state at a particular processing stage. This segmentation allows multiple users to concurrently access and process different versions simultaneously without conflict, as each user works with a specific version instance while the system manages version transitions and relationships.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates copies of data objects in the form of versions. When a data object transitions between workflow states, the system creates a new version copy rather than modifying the original. This copying mechanism enables multiple users to work with different copies concurrently, and the system can manage these copies through unique locating references that identify specific versions.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If references to data objects are tightly linked to the time of request rather than action execution, then data object instances can be uniquely identified, but the state of the data object cannot be changed while a user's action is awaited

Engineering Contradiction:
Improvestate change capability during pending actionsVSAvoidreference validity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent takes preliminary action by creating a snapshot of the data object's state before a workflow transition occurs. This snapshot captures the data object at a specific moment and assigns it a unique locating reference. The snapshot remains valid even after the original data object changes state, allowing references to remain valid while the data object evolves through different workflow states.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces snapshots as an intermediary between the data object and user references. The snapshot acts as a stable reference point that mediates between the changing data object and the user's pending actions. This intermediary allows the data object to change state while maintaining valid references to its previous state through the snapshot mechanism.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If snapshots are taken before workflow transitions, then historical states of data objects can be preserved and accessed, but additional storage requirements and processing overhead are introduced

Engineering Contradiction:
Improvedata object history preservationVSAvoidstorage and processing complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent creates simplified copies of data objects in the form of snapshots that capture essential state information at specific workflow transition points. These snapshots store only the necessary data to represent the object's state at that moment, rather than duplicating the entire object structure. This copying approach preserves historical states while minimizing storage overhead compared to full duplications.

Inventive Principle:
Principle #26Copying

4Ease of operation

If unique locating references are created for both data objects and snapshots, then concurrent access by multiple users is enabled, but the system must manage multiple references and their relationships

Engineering Contradiction:
Improveconcurrent access capabilityVSAvoidreference management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements a universal reference management system where the same reference mechanism is used for both data objects and snapshots. The unique locating reference system serves multiple functions: identifying current data objects, referencing historical snapshots, and managing version relationships. This universal approach enables concurrent access by multiple users while using a single unified reference management infrastructure rather than separate systems for objects and snapshots.

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

Data Source

PatentUS8825599B2Computer-based data processing system and method of processing data objects
Publication Date: 2014.09.02 SWISS REINSURANCE CO LTD
  • US8825599B2 patent drawing
  • US8825599B2 patent drawing
  • US8825599B2 patent drawing

AI summary

A computer-based system creates a data object by preparing a data structure for the data object in a database and processes the data object at different processing stages each associating a different workflow state with the data object. The system can take and store automatically a snapshot of the data object, prior to a workflow transition of the data object from a first workflow state to a second workflow state, respectively associated with the snapshot and with the data object. The system also creates a unique locating reference for the snapshot based on a unique locating reference created previously for the data object. When the unique locating reference for the data object is received, controlled access to the data object and the snapshot is provided. Based on one unique locating reference, multiple states of the data object can be easily and efficiently made available concurrently to a user.