Companion App Invocation via Browser Plug-in HTML Tag Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for establishing context between disconnected applications require human interaction, costly integration code, or rigid custom integrations, leading to high costs, user discontent, and regulatory risks, as well as the need for frequent regression testing and separate client installations.
Innovation Solution
A service-based architecture that uses a browser plug-in to generate a filtered set of HTML tags from a calling application's display page, which are sent to a web service to create a fully formed HTTP request, allowing seamless invocation of a companion application without configuration data or integration code on the client system, maintaining the relationship between applications centrally.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If custom programmatic integrations are created between applications, then context can be established between disconnected applications, but the integration becomes rigid and requires regression testing every time applications change
Solution Approach 1:
The patent introduces a script-driven interface as an intermediary layer between the calling application and companion application. This interface uses HTML tag extraction and script execution to establish context without requiring direct rigid integrations between applications, allowing flexible adaptation when applications change.
Solution Approach 2:
The integration process is segmented into independent components: HTML tag extraction from the calling application, script configuration for context establishment, and companion application invocation. This segmentation allows each component to be modified independently without affecting the entire integration.
2Productivity
If script driven approaches are used to extract data from screens, then data can be passed to another application, but configuration data must be stored on user desktops creating training and quality issues
Solution Approach 1:
The patent extracts the configuration management burden from the client desktop environment and relocates it to a centralized server environment. HTML tags are extracted from the calling application display, and script configurations are managed centrally rather than being stored on individual user desktops.
3Reliability
If custom integrations are developed for every pair of applications, then specific context relationships can be established, but the cost and time of writing integrations increases significantly
Solution Approach 1:
The patent creates a universal script-driven interface that can work with multiple different application pairs through a common mechanism. Instead of developing custom integrations for each application pair, the same HTML extraction and script execution framework serves multiple application combinations, reducing overall complexity.
4Reliability
If regression testing is performed every time applications change, then integration reliability is maintained, but upgrade time and cost increase considerably
Solution Approach 1:
The patent introduces dynamic adaptability through script-driven interfaces that can automatically adjust to application changes. Instead of requiring static rigid integrations that break with application updates, the script-based approach dynamically adapts to new application versions, reducing the need for extensive regression testing.
Data Source
AI summary
A service to invoke a companion application or service is disclosed. In various embodiments, an indication to invoke a companion application is received in the context of a display page of a calling application. A service a call comprising a filtered set of data values derived from the display page is sent to an external service. A request associated with the companion application is received from the external service and used to invoke the companion application.