Active Business Client Widget for Context Data Rendering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional client-server interaction methods, particularly in enterprise service architecture, are inadequate for delivering business context data across multiple channels and devices, leading to inconsistent user experiences due to interdependencies between data model, interaction control, and appearance layers, which require sophisticated knowledge and programming skills, resulting in high development and maintenance costs.
Innovation Solution
The implementation of an active business client that processes and renders business context data, enabling the generation of user interface components on client devices to provide actionable context data, independent of server-specific UI definitions, allowing for multi-channel and multi-modal user experiences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If traditional MVC architecture is used to decouple data model, interaction control, and appearance layers, then data organization is improved, but the layers remain interdependent requiring sophisticated knowledge and programming skills, resulting in high development and maintenance costs
Solution Approach 1:
The patent segments the business application into independent microservices that can be developed, deployed, and scaled separately. Each microservice encapsulates specific business logic and data models, eliminating the interdependencies between layers in traditional MVC architecture. This allows teams to work on different services independently without requiring sophisticated integration knowledge.
Solution Approach 2:
The patent introduces a universal service registry and discovery mechanism that enables any client application to interact with any microservice through standardized interfaces. This universal communication layer replaces the need for custom integration code between MVC layers, reducing development and maintenance costs while maintaining architectural stability.
2Ease of manufacture
If monolithic application approach is used, then development is simpler, but the system cannot deliver content effectively across various channels and form factors, failing to support multi-channel multi-modal OCA user experiences
Solution Approach 1:
The patent divides the monolithic application into independent microservices, each responsible for specific functionality. This segmentation allows the system to serve multiple channels and form factors by composing different services in channel-specific ways, maintaining development simplicity through independent service units while achieving high adaptability.
Solution Approach 2:
The patent implements dynamic service composition and routing that adapts the application behavior based on the client channel and form factor. The system dynamically selects and composes appropriate microservices for each interaction, enabling the same backend services to deliver optimized content across diverse channels without requiring separate monolithic applications for each channel.
3Extent of automation
If traditional ERP-centric workflows are used, then business process management is established, but consistent user experience across multiple platforms cannot be provided
Solution Approach 1:
The patent introduces an API gateway and service mesh as intermediaries between ERP workflows and client applications. These intermediaries translate ERP-centric workflow operations into platform-agnostic service calls, ensuring consistent user experience across multiple platforms while maintaining the automation capabilities of ERP systems.
Solution Approach 2:
The patent creates universal service interfaces that encapsulate ERP workflow functionality, allowing the same business processes to be accessed consistently across different client platforms. The service layer provides a unified view of ERP workflows that adapts to various user interfaces and interaction models while maintaining backend process consistency.
Data Source
AI summary
Methods and apparatuses enable rendering business context data in a desktop widget. The business context data describes a resource, a view, and actionable context data that relate to a business scenario. The business context data is processed to determine a UI component to generate to represent the business context data. The component is then generated and rendered in a desktop widget to provide access to the actionable context data on a client device via the desktop widget. An active business client receives and processes the business context data. The active business client can operate as a widget engine for the business context data to enable the rendering of the business context data on the client device.