Handover Component for Business Object Data Transition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing enterprise IT systems face challenges in customizing transaction processing to meet specific business requirements across different industries and geographic regions, as commercial application programs often need modifications that require extensive knowledge of data models, process models, and programming techniques.
Innovation Solution
A handover component, also known as a business object transition service, is introduced to transform business objects of one type into another based on user-defined data-transition rules, enabling customization and operation across multiple applications and business contexts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If commercial application programs are modified to meet specific business requirements, then adaptability is improved, but device complexity increases
Solution Approach 1:
The patent segments the customization functionality into a separate handover component that operates independently from the core application program. This component handles data transitions between different business processes, allowing customization without modifying the underlying application structure. The handover component acts as an intermediary layer that can be configured independently, thus improving adaptability while maintaining system integrity and avoiding increased complexity in the core system.
2Adaptability or versatility
If application programs are customized for specific industries or regions, then adaptability is improved, but ease of operation deteriorates
Solution Approach 1:
The handover component enables business users to define and configure data transition rules without requiring knowledge of programming techniques or application internals. The component provides a self-service mechanism where users can specify how data should transition between business processes through configuration rather than code modification, making customization accessible to non-technical users and maintaining ease of operation while improving adaptability.
3Adaptability or versatility
If data transition rules are made customizable, then adaptability is improved, but device complexity increases
Solution Approach 1:
The handover component serves as an intermediary between the core application program and the customization requirements. It provides a standardized interface for defining data transition rules without exposing the complexity of the underlying data models or process logic. This mediator layer allows users to configure customizations through a simplified interface while the component handles the complex transformations internally, thus improving adaptability without increasing perceived system complexity.
Data Source
AI summary
Techniques are described to enable a user to define data-transition rules that control how a handover component of a computer application transforms business objects of one type to business objects of another type. The handover component is logically situated between a preceding business process that uses a preceding type of business object and a second business process that uses a second type of business object. Based on the user-defined data-transition rules, the handover component performs a split/merge process that determines the succeeding business objects to be generated based on the preceding business objects received from the preceding business process and then generates the succeeding business objects based on the received preceding business objects and the user-defined data-transition rules.