Back-end Field Control for Layered Software
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current field control methods for APIs and web services are often hard-coded or configured separately, leading to increased costs and inconsistencies, especially when transitioning to Enterprise Service Architecture (ESA), as there is no common service to manage back-end field control across multiple software layers.
Innovation Solution
A method for providing back-end field control that involves receiving requests to update attributes of business objects, identifying associated software layers, and determining whether the updates comply with settings from those layers, allowing for dynamic and static property management across multiple layers to ensure consistent and restrictive property application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If field control is hard-coded or configured separately for each software layer, then each layer can be developed independently, but this increases costs and causes inconsistencies in field property management
Solution Approach 1:
The patent merges field control functionality across multiple software layers by introducing a field control service that centralizes the management of field properties. Instead of separate hard-coded controls in each layer, the system combines them into a unified service that handles field control requests from any layer, ensuring consistency while allowing independent development.
Solution Approach 2:
The field control service is designed as a universal component that serves multiple software layers (UI layer, A2A layer, web service layer) with a single interface. This multi-functional service handles different types of field control requests uniformly, reducing the need for layer-specific implementations and decreasing overall system complexity.
2Adaptability or versatility
If separate field control configurations are used for different software layers, then each layer can have customized control, but this causes inconsistencies and increased costs
Solution Approach 1:
The field control service implements a feedback mechanism where field control requests from any software layer are routed through the centralized service. The service evaluates the request against stored field control settings and returns consistent control decisions, ensuring that all layers adhere to the same field property rules while allowing legitimate customization through the unified interface.
Solution Approach 2:
The field control service acts as an intermediary between multiple software layers and the underlying field control logic. Instead of layers directly implementing their own control mechanisms, they communicate their needs through the intermediary service, which ensures consistent application of control rules across all layers while maintaining the ability to handle layer-specific requirements.
3Reliability
If a common field control service is implemented across multiple software layers, then consistency is improved, but this requires integrating multiple layers which increases initial complexity
Solution Approach 1:
The patent segments the field control functionality into a distinct, standalone service that can be independently developed and deployed. This segmentation allows the field control service to be integrated into existing software layers without requiring complex reconfiguration of each layer, as the service provides a clear, standardized interface that simplifies the integration process despite the initial complexity of creating the unified service.
Data Source
AI summary
This disclosure involves back-end field control of layered software. For example, a method for providing back-end field control of an interface can comprise receiving a request to update one or more attributes of a business object, where the request is associated with a first software layer. The method then identifies one or more additional software layers associated with the business object and determines whether the request can update to the one or more attributes violate settings of the one or more attributes associated with the one or more additional software layers.