UI Transaction Data Layer with Centralized Stored Procedure Logic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The fragmentation of business logic across web and database layers in enterprise software systems leads to inconsistencies, performance issues, security vulnerabilities, and difficulties in maintaining data integrity and compliance, exacerbated by the use of different tools and languages by separate development teams.

Innovation Solution

A centralized system that uses stored procedures to manage business logic within the database, ensuring consistent application across layers through a hierarchical structure and directory system, with standardized stored procedures for data operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If business logic is distributed across web and database layers with separate development teams, then each team can use specialized tools and languages, but inconsistencies and synchronization difficulties arise

Engineering Contradiction:
Improveteam specializationVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary layer (API layer or service layer) between the web layer and database layer that standardizes data access and business logic execution. This intermediary enforces consistent data access patterns, validation rules, and transaction management across all teams, preventing inconsistencies while allowing each team to use their specialized tools and languages independently.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If business logic is implemented in both web code and database code, then validation can occur at multiple layers, but duplication and synchronization issues occur

Engineering Contradiction:
Improvevalidation coverageVSAvoidlogic duplication
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts business logic and validation rules from both web code and database code into a centralized location (the intermediary layer or a separate business logic layer). This extraction eliminates duplication by providing a single source of truth for all business rules, while still enabling validation at multiple layers through the centralized logic being invoked by both web and database operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a universal business logic layer that serves multiple functions: validation, transaction management, data access coordination, and business rule enforcement. This single multi-functional layer replaces the need for separate validation and logic implementation in both web and database code, reducing complexity while maintaining comprehensive validation coverage.

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

3Productivity

If web and database teams work independently with different tools, then development productivity increases, but debugging and troubleshooting become challenging

Engineering Contradiction:
Improvedevelopment speedVSAvoidissue localization
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The intermediary layer serves as a standardized interface that both web and database teams interact with, creating clear boundaries and contracts. When issues occur, the intermediary layer's standardized structure makes it easier to trace problems through the system, identify whether they originate from web code, database code, or data itself, and locate the specific source of errors.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements comprehensive logging, error handling, and monitoring mechanisms in the intermediary layer that provide immediate feedback about data operations, validation results, and system state. This feedback system enables rapid debugging and troubleshooting by providing clear information about where and why issues occur, allowing independent teams to quickly identify and resolve problems without extensive cross-team coordination.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12625860B2Data management system for UI transactions
Publication Date: 2026.05.12 BANK OF AMERICA CORP
  • US12625860B2 patent drawing
  • US12625860B2 patent drawing
  • US12625860B2 patent drawing

AI summary

Comprehensive systems and methods manage software lifecycle processes in an enterprise environment, and ensures consistent, secure, and efficient handling of software applications, packages, and distribution methods. The system features a web application interface that validates user input, enforces multi-level authentication, and manages user roles and permissions. A directory system dynamically selects stored procedures based on input data and current database structure, executing operations entirely within the database. Stored procedures enforce business logic, manage complex data relationships, support data encryption, and anonymize sensitive information. Hierarchical data structures organize records with multi-level granularity, temporal tracking, and partitioning. The database management system optimizes operations, implements automatic failover, and supports real-time data synchronization. The system also includes advanced error handling, real-time monitoring with predictive alerts, a secure audit trail, and a reporting module integrating with external business intelligence tools. Automated maintenance and disaster recovery ensure scalable, secure software lifecycle management.