Non-Programmatic Integration System for Synchronized User Sign-On
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for integrating different software applications are often inadequate due to proprietary formats, requiring programmatic modifications or costly replacements, which are costly and disruptive, and may violate licensing terms.
Innovation Solution
A non-programmatic integration system that collects data from mapped locations within applications using an API, allowing seamless integration without modifying source code, and automatically manages user sign-on and sign-off based on user identifier changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If programmatic integration methods are used to integrate different applications, then integration capability is improved, but system complexity and cost increase due to source code modification requirements
Solution Approach 1:
The patent introduces an intermediary component (integration manager or adapter layer) that sits between the different applications and coordinates their interactions. This mediator handles data transformation and communication protocols without requiring modifications to the source code of the integrated applications, thereby maintaining integration capability while reducing system complexity.
Solution Approach 2:
The integration system is divided into separate modular components including data collection modules, transformation modules, and interface modules. Each module handles specific integration tasks independently, allowing the system to adapt to different applications without requiring comprehensive source code modifications, thus improving adaptability while controlling complexity.
2Adaptability or versatility
If programmatic integration methods are used to integrate different applications, then integration capability is improved, but implementation cost increases due to source code modification and licensing constraints
Solution Approach 1:
By using an intermediary integration layer that communicates with applications through standard interfaces and APIs, the system avoids the need to modify proprietary source code. This approach eliminates licensing costs associated with code modification and reduces implementation expenses while maintaining integration functionality.
Solution Approach 2:
The system creates virtual copies or representations of data and functionality from the integrated applications through non-intrusive data collection methods. Instead of modifying original applications, the integration system generates equivalent data structures and interfaces, reducing implementation costs by avoiding source code changes and associated licensing fees.
3Ease of operation
If application data is collected from mapped locations for integration, then data accessibility is improved, but data accuracy may deteriorate due to format variations across applications
Solution Approach 1:
The system dynamically adjusts data collection parameters and transformation rules based on the specific application and data format being accessed. By changing parameters such as data mapping configurations, extraction patterns, and validation criteria according to the source application's format, the system maintains high data accuracy while preserving ease of access across different application interfaces.
Solution Approach 2:
The integration system applies format-specific data collection and transformation rules tailored to each individual application's data structure. Instead of using a uniform approach for all applications, the system customizes data extraction and validation parameters for each local context, ensuring data accuracy is maintained for each specific application format while keeping the overall system easy to operate.
Data Source
AI summary
Systems and methods for automatically signing a user on to an integration application when a user signs on to another application and signing a user off when the user signs off of the other application. The integration application automatically non-programmatically collects data from a mapped location of a mapped source reference of the other application. The collected data includes a user identifier value. The integration continuously monitors the collected user identifier value for a difference in the collected user identifier value. If the collected user identifier value is recognized by the integration application, the user is signed into the integration application using the collected user identifier value, and if a difference in the collected user identifier value is detected, the user is signed off of the integration application.