Predefined Transformation Rules for Service Data Type Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data type mismatches between Business Object Models and service consumers, such as User Interfaces, often require manual coding to create new entities, hiding the relationship between original and new data types, which is inefficient and not transparent.
Innovation Solution
A system and method that execute predefined transformation rules on service portions without generating code in the service layer, allowing for data type conversions between Business Object Models and service consumers, maintaining metadata relationships and being reusable across multiple fields and consumers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual coding is used to wrap additional code into the service consumer layer to handle data type mismatches, then data type transformation can be achieved, but the relationship between original and new data types is hidden and the system complexity increases
Solution Approach 1:
The patent introduces transformation rules as an intermediary mechanism between the Business Object Model and service consumers. These rules define explicit mappings between source and target data types, allowing transformations without manual coding while preserving the relationship between original and new data types through a declarative rule-based approach
Solution Approach 2:
The patent extracts the data type transformation logic from the service layer code into separate transformation rules. This separation allows the transformation logic to be independently defined, managed, and executed, reducing the complexity of the service layer while maintaining transformation capabilities
2Adaptability or versatility
If new entities are created in the repository when fields are wrapped by coding, then data type mismatches can be handled, but the transparency of metadata relationships is lost
Solution Approach 1:
Transformation rules serve as an intermediary that preserves metadata relationships by explicitly defining the mapping between source and target data types. This approach maintains transparency in the relationship between original and transformed data, avoiding the information loss that occurs when manual coding hides these relationships
Solution Approach 2:
The patent applies transformation rules preliminarily to fields before they are consumed by service consumers. This preliminary transformation ensures data type compatibility is established in advance, maintaining metadata relationships throughout the data flow without requiring post-processing or complex entity creation
3Reliability
If data type transformations are manually calculated by developers, then specific transformation logic can be implemented, but the transformation process is inefficient and not reusable
Solution Approach 1:
The patent creates transformation rules with universal applicability that can be reused across multiple fields and service consumers. These rules define generic transformation logic that can be applied consistently throughout the system, improving productivity by eliminating the need for manual calculation and implementation for each specific case while maintaining reliability through standardized logic
Solution Approach 2:
Transformation rules are predefined and stored in the repository before being applied to fields. This preliminary definition allows the transformation logic to be established once and reused multiple times, significantly improving development efficiency while ensuring consistent and reliable transformations across the system
Data Source
AI summary
The present disclosure is directed to executing transformation rules. In some implementations, a method includes receiving a request to apply a predefined transformation rule to a portion of a service. In response to at least the request, the predefined transformation rule is identified from a plurality of predefined transformation rules included in a business model. Each of the plurality of predefined transformation rules are configured to update at least one service independent of generating code in a service layer. The predefined transformation rule is assigned to the portion of the service.