Bulk Application Update Management via Segmented Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current application platforms, such as Salesforce, face challenges in managing large numbers of application updates for multiple subscribers, leading to inefficiencies in user interface usability and processing time, as they require users to manage updates one product and version at a time, resulting in lengthy wait times and cumbersome workflows.

Innovation Solution

A system and method that enables users to visualize and manage multiple applications and subscribers simultaneously, allowing grouping by various parameters, and performing operations like scheduling and editing updates in bulk, utilizing an intermediate module and communication module to streamline data handling and reduce processing delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the current application platform interface is used to manage multiple application updates for multiple subscribers, then the system can provide application updates to subscribers, but the user interface becomes unusable and processing time exceeds 20 minutes when the number of update items exceeds 50

Engineering Contradiction:
Improveupdate management efficiencyVSAvoiduser interface usability
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system segments the large set of update items into multiple pages, with each page displaying a manageable subset of update items. The interface divides the overwhelming list into discrete, navigable units that users can interact with efficiently, preventing interface unresponsiveness while maintaining access to all update items through pagination controls.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-loading and displaying summary information for multiple update items simultaneously on the interface. This allows users to overview and manage multiple updates without waiting for sequential loading, reducing perceived processing time and improving operational efficiency before actual update execution.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the current application platform requires users to log in to every single application to obtain subscribers and manage updates, then complete subscriber information can be obtained, but the processing time requires approximately 20 minutes to complete

Engineering Contradiction:
Improvesubscriber information accuracyVSAvoidupdate management time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system merges the authentication and data retrieval processes by implementing a single sign-on mechanism that grants access to subscriber information across multiple applications simultaneously. This consolidation eliminates the need for repeated logins to each application, maintaining reliable access to complete subscriber data while reducing total processing time from 20 minutes to a fraction of that time.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system implements a universal authentication interface that functions across all applications within the platform. This multi-functional login system allows users to obtain subscriber information for multiple applications through a single authentication event, rather than requiring separate login procedures for each application, thereby significantly reducing time loss while maintaining data accuracy.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If the system allows single operations on large numbers of applications and subscribers, then user effort is reduced significantly, but the system must handle tens of thousands of update items simultaneously

Engineering Contradiction:
Improveuser effortVSAvoidsystem processing complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system introduces an intermediary batch processing layer that sits between the user interface and the underlying application update mechanisms. This intermediary layer receives single user operations targeting large numbers of applications and subscribers, then systematically distributes and manages the complexity of handling tens of thousands of update items through coordinated batch processing, shielding users from system complexity while enabling efficient bulk operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11119752B2Scalably providing multiple application updates to multiple subscribers
Publication Date: 2021.09.14 CERTINIA INC
  • US11119752B2 patent drawing
  • US11119752B2 patent drawing
  • US11119752B2 patent drawing

AI summary

Presented here is a system and method to enable a user to manage a large number of applications and a large number of subscribers. The technology presented here can manage up to tens of thousands of update items without a noticeable delay to the user. The technology enables the user to visualize information about multiple applications and multiple numbers of subscribers at the same time, and group the multiple subscribers and multiple applications according to various parameters, such as application name, organization type, update version, etc. Once grouped, the user can perform various operations on the group, such as schedule the updates and/or edit the updates, by adding or removing a large number of items at once. Further, the system is structured so that the operations on the large number of items can be performed without a noticeable delay to the user.