Runtime Custom Field Extension in Database Systems

Solution Overview

Problem

Service requestors face delays and costs when extending software applications to include custom features, as they need to communicate with developers to modify complex on-site systems, which is time-consuming and costly.

Innovation Solution

A method that allows extension logic to be stored in a backend database system, enabling custom fields to be added dynamically during runtime by extending database tables, business logic, and application programming interfaces, allowing service requestors to extend the software system without developer intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service requestors communicate with developers to add custom fields, then the software system can be extended with custom features, but the process takes time and costs money

Engineering Contradiction:

Improvecustom field extension capabilityVSAvoidextension implementation time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables service requestors to extend the software system themselves by adding custom fields through the user interface without requiring developer intervention. The extension logic is automatically executed by the system, allowing users to perform extensions independently and immediately.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The software system is pre-configured with extension logic in the backend database system that enables custom field additions. The necessary infrastructure (database tables, business logic, APIs) is prepared in advance to support runtime extensions, so when users add custom fields, the system can immediately process these extensions without requiring preliminary developer setup.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If service requestors communicate with developers to add custom fields, then the software system can be extended with custom features, but the extension process costs money

Engineering Contradiction:

Improvecustom field extension capabilityVSAvoidextension cost

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system enables service requestors to extend the software system themselves by adding custom fields through the user interface without requiring developer intervention. The extension logic is automatically executed by the system, allowing users to perform extensions independently and immediately.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If the software system is complex and located on-site, then it provides robust functionality, but extending it requires developer involvement

Engineering Contradiction:

Improvesystem extendabilityVSAvoidextension simplicity

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system introduces an intermediary layer - the extension logic in the backend database system that acts as a mediator between the user interface and the complex on-site software system. This intermediary handles the complexity of extending database tables, business logic, and APIs, while presenting a simple user interface to service requestors.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables service requestors to extend the software system themselves by adding custom fields through the user interface without requiring developer intervention. The extension logic is automatically executed by the system, allowing users to perform extensions independently and immediately.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS10417248B2Field extension in database system

Publication Date: 2019.09.17 SAP SE

AI summary

In one embodiment, a method stores extension logic for a business context for an application in a backend database system. The extension logic is stored with respect to a database table, business logic to handle transactions in the backend system, and an application programming interface to the application. A request for a custom field is received through a runtime version of the application, the custom field specifying a business context in which the custom field is associated. The method determines the extension logic associated with the business context in the backend database system. Further, the method uses the extension logic to extend the database table with the custom field, extend the business logic to handle transactions for the custom field in the backend system, and extend the application programming interface to the application. The custom field is extended during runtime of the application.