Unified Workflow System for Client Service Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing client service software applications often require separate development and maintenance for associate use, leading to inefficiencies and complexities, especially when handling sensitive data or requiring compliance with regulations.

Innovation Solution

A guided workflow processing system that allows client service applications to automatically prefill transactions, enabling associates to initiate automatic functions that prefill forms and fields for clients, thus streamlining the workflow and reducing the need for separate applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If separate web-based applications are built for associate use to assist customers, then associates can provide face-to-face assistance, but the complexity of managing multiple applications increases and maintenance burden doubles

Engineering Contradiction:
Improveassociate ability to assist customersVSAvoidnumber of applications to manage
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements a unified web-based application that serves dual purposes: customer self-service and associate-assisted service. The system uses a single application framework with role-based access control, where the same application assets (forms, workflows, data models) serve both customer and associate functions. This eliminates the need for separate applications while maintaining ease of operation for associates.

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

Solution Approach 2:

The patent merges previously separate customer-facing and associate-facing applications into a single unified platform. By combining these functions, the system reduces complexity from managing multiple applications to managing one, while still providing specialized capabilities for both user types through a common interface and shared backend infrastructure.

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If new technology or applications are developed for associate use, then associates can perform transactions, but the time to market increases and internal maintenance resources are consumed

Engineering Contradiction:
Improvetransaction capability for associatesVSAvoiddevelopment and maintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements pre-configured transaction templates and workflows that are prepared in advance within the unified application framework. These templates include pre-defined forms, validation rules, and processing logic that can be activated for associate use without requiring new development. This allows rapid deployment of transaction capabilities while minimizing development time and maintenance overhead.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent reuses existing application assets (forms, workflows, data validation rules) from the customer self-service portion of the system and applies them to associate-assisted transactions. By copying and adapting proven components rather than building new functionality, the system achieves adaptability for associate transactions while significantly reducing development time and maintenance burden.

Inventive Principle:
Principle #26Copying

3Ease of operation

If associates are provided with access to customer service systems, then they can assist with transactions, but security risks increase when sensitive data is exposed

Engineering Contradiction:
Improveassociate transaction assistanceVSAvoiddata security exposure
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent implements role-based access control that provides different levels of data access and functionality to different user roles within the same application. Associates receive targeted access permissions specific to their job functions, allowing them to assist with transactions while exposing only the minimum necessary sensitive data. This localizes security controls to specific user contexts, maintaining ease of operation while mitigating security risks.

Inventive Principle:
Principle #3Local quality

4Productivity

If multiple separate applications are maintained for different user types, then specific functions can be optimized, but the overall system complexity and training requirements increase

Engineering Contradiction:
Improvetransaction processing efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal application platform that handles both customer self-service and associate-assisted transactions through a single codebase and shared infrastructure. The system maintains productivity by optimizing transaction processing through common efficient workflows while reducing architectural complexity by eliminating redundant application layers. Role-based permissions enable different user types to access appropriate functions without requiring separate application architectures.

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

Data Source

PatentUS20250045662A1Methods and systems for guided workflow processing in client service software applications
Publication Date: 2025.02.06 FMR CORP
  • US20250045662A1 patent drawing
  • US20250045662A1 patent drawing
  • US20250045662A1 patent drawing

AI summary

Computerized methods and apparatuses, including computer program products, for guided workflow processing include a server computing device which determines a guided workflow transaction path based upon input received from a first client device. The server initiates a transaction based upon the transaction path, including capturing data elements associated with a user of a second client device. The server stores the captured data elements, including a transaction identification token and a state of the transaction path. The server receives a request to continue the transaction from the second client device and retrieves the data elements. The server generates a user interface form based upon the state of the transaction path and displays the user interface form on the second client device. The server processes the transaction based upon input received from the second client device via the user interface form.