Dynamic Feature Check for Enterprise Software Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise software users face challenges in transitioning from on-premise, legacy systems to cloud-based SaaS due to missing functionality and features, which can disrupt critical business processes.
Innovation Solution
A method and system that dynamically execute all features of a software application from one architecture to another, using a Dynamic Feature Check (DFC) to determine which features are supported by the new architecture, ensuring seamless transition without losing functionality, by processing business objects through either the legacy or cloud-based application based on feature support.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If enterprise software transitions from on-premise legacy systems to cloud-based SaaS architecture, then accessibility and modernization are improved, but functionality and features are lost
Solution Approach 1:
The patent segments the feature set into individual checkable items, allowing the system to evaluate each feature independently. The feature check mechanism divides the transition process into discrete steps where each feature is verified and routed appropriately, enabling partial migration while maintaining lost functionalities through the legacy system.
Solution Approach 2:
The patent introduces a feature check mechanism as an intermediary layer between the user interface and the backend systems. This mediator dynamically determines whether to route requests to the new SaaS architecture or the legacy on-premise system based on feature availability, thus preserving functionality while enabling cloud transition.
2Adaptability or versatility
If all features are maintained during transition, then functionality is preserved, but migration complexity increases
Solution Approach 1:
The patent implements a dynamic feature check mechanism that adapts the system behavior based on real-time feature availability. Rather than using a static migration approach, the system dynamically routes requests based on which features are supported by the new architecture, simplifying the migration process while maintaining all functionalities.
Solution Approach 2:
The patent changes the parameter of feature availability detection from a static configuration to a dynamic runtime check. By implementing feature checks that execute during operation, the system can maintain all functionalities without requiring complex pre-planning or manual configuration of migration paths.
3Adaptability or versatility
If dynamic feature checking is implemented, then functionality is maintained, but system complexity increases
Solution Approach 1:
The patent creates a universal feature check mechanism that handles multiple features through a single integrated system. Rather than implementing separate check logic for each feature, the system uses a multi-functional check process that can evaluate any feature, reducing overall system complexity while maintaining all functionalities.
Solution Approach 2:
The patent implements a self-service feature check system that automatically determines routing decisions without requiring manual intervention. The system checks feature availability and autonomously routes requests to appropriate backend systems, reducing the complexity of system integration and management.
Data Source
AI summary
A method, system, and computer-readable medium, including receiving a request to process a business object including an indication of at least one feature that can be invoked in the processing of the business object; determining the at least one feature associated with the business object based on the indication thereof included with the business object; determining whether the at least one feature associated with the business object can be executed by a second application based on an indication of a set of features supported by the second application; processing, in response to a determination that the at least one feature can be executed by the second application, the business object by the second application; and processing, in response to a determination that the at least one feature is not supported by the second application, the business object by a first application that supports a first set of features.