Automatic Event Detection via Dummy Records and Timestamp Discovery

Solution Overview

Problem

Current integration platforms require manual configuration and extensive knowledge of enterprise applications and APIs for event detection, making the process time-consuming and complex for developers.

Innovation Solution

A method and system for automatic event detection using a CRUD action connector, which involves creating a dummy record, searching for timestamp fields, and performing CRUD operations to detect creation and update events without manual configuration, leveraging Natural Language Processing techniques to identify queryable timestamp fields.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration is used for event detection, then developers can detect events in enterprise applications, but the process becomes time-consuming and complex requiring extensive knowledge of APIs

Engineering Contradiction:

Improveevent detection capabilityVSAvoidconnector development time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs self-configuration by automatically discovering enterprise applications, extracting metadata, and generating event detection rules without requiring manual developer intervention. The integration platform autonomously queries the enterprise application, analyzes its structure, and configures the event detector based on the discovered information.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by automatically discovering the enterprise application structure and metadata before event detection is needed. This preliminary discovery phase includes querying the application, analyzing its schema, and pre-configuring detection rules, so that when events need to be detected, the system is already prepared.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If manual configuration is used for event detection, then developers can detect events in enterprise applications, but the device complexity and difficulty increase due to requiring extensive API knowledge

Engineering Contradiction:

Improveevent detection capabilityVSAvoidconnector configuration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system performs self-configuration by automatically discovering enterprise applications, extracting metadata, and generating event detection rules without requiring manual developer intervention. The integration platform autonomously queries the enterprise application, analyzes its structure, and configures the event detector based on the discovered information.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces the manual mechanical process of configuration with an automated information processing system. Instead of developers manually configuring event detectors, the system uses automatic discovery, metadata extraction, and rule generation to substitute the manual configuration process.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Extent of automation

If automatic event detection is implemented, then manual intervention is reduced, but the system must automatically discover and configure detection rules

Engineering Contradiction:

Improveevent detection automationVSAvoidautomatic configuration complexity

Core Design Contradiction:

Extent of automationVSDevice complexity

Solution Approach 1:

The system performs self-configuration by automatically discovering enterprise applications, extracting metadata, and generating event detection rules without requiring manual developer intervention. The integration platform autonomously queries the enterprise application, analyzes its structure, and configures the event detector based on the discovered information.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by automatically discovering the enterprise application structure and metadata before event detection is needed. This preliminary discovery phase includes querying the application, analyzing its schema, and pre-configuring detection rules, so that when events need to be detected, the system is already prepared.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11645269B2Automatic events detection from enterprise applications

Publication Date: 2023.05.09 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Embodiments provide a computer-implemented method for automatic detection of an event from an enterprise application, comprising: initiating a CRUD action connector of an integration platform; providing a business object name to the action connector; randomly obtaining a sample record from the enterprise application; creating a dummy record in the enterprise application, wherein the dummy record has a dummy record ID and a first time range within which the dummy record is created; and searching for a first timestamp field in a business object schema to determine whether the first timestamp field is queryable, wherein the first timestamp field indicates when the dummy record is created. If the first timestamp field exists, and the first timestamp field is queryable, then a first event indicating creation of the dummy record is detectable; if the first timestamp field does not exist, then the first event is undetectable.