Mass Decision Mode for Mobile Payment Batch Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile applications lack a mass decision mode that allows users to efficiently manage multiple objects with a single action, limiting their ability to approve, reject, or process large sets of data, such as payments, in a corporate environment.

Innovation Solution

A mobile application implementing a mass decision mode that allows users to select a default action for a majority of objects and a deviant action for specific objects, with the ability to switch between mass and deviant decision modes to manage payments or other data sets efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If users process each object individually in existing mobile applications, then decision accuracy is maintained, but productivity is reduced due to time-consuming sequential processing

Engineering Contradiction:
Improveprocessing speedVSAvoidtime for individual approvals
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent merges multiple individual decision-making actions into a single batch operation. Users can select multiple objects from a list and apply a default action to all selected objects simultaneously, consolidating what would have been multiple sequential operations into one action, thereby significantly improving productivity and reducing time loss.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary selection of objects before the final decision action. Users can pre-select multiple objects that require the same action, and the system prepares the batch for processing. This preliminary grouping enables efficient bulk processing while maintaining the ability to review and modify selections before execution.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If users process each object individually, then detailed review is possible, but ease of operation deteriorates due to repetitive manual steps

Engineering Contradiction:
Improveoperational simplicityVSAvoidnumber of processing steps
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

Multiple repetitive operational steps are merged into a single batch operation. Instead of opening, reviewing, and deciding on each object separately, users can select multiple objects and apply a default action to all of them in one step, dramatically simplifying the operational process and reducing the number of required interactions.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system provides a universal batch processing mechanism that can handle multiple different object types and actions through a single interface. The same selection and action mechanism works for various operations (approve, reject, delete, etc.) across different object types, making the system easier to operate without requiring separate procedures for each case.

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

3Productivity

If a single default action is applied to all selected objects, then productivity is improved through batch processing, but adaptability worsens due to inability to handle exceptions

Engineering Contradiction:
Improvebatch processing efficiencyVSAvoidhandling of deviant cases
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system applies different qualities of processing to different objects within the same batch. Most selected objects receive the default action, but individual objects can be identified as exceptions and handled differently. This local differentiation allows the system to maintain high productivity for the majority while providing adaptability for specific cases that require different treatment.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system applies the default action to only the portion of selected objects that qualify for it, while excluding exceptions. Users can review the batch and remove objects that should not receive the default action, ensuring that the action is applied partially to the appropriate subset rather than excessively to all selected objects, thereby maintaining both efficiency and accuracy.

Inventive Principle:
Principle #16Partial or excessive action

4Measurement precision

If the system provides detailed individual processing options, then measurement precision is maintained, but loss of time increases due to extended decision-making process

Engineering Contradiction:
Improvedecision accuracyVSAvoidtime for review and approval
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary review and selection of objects for batch processing. Users can review the selected objects before applying the default action, and the system prepares a summary of the batch for confirmation. This preliminary step ensures that decisions are made with adequate review while preventing unnecessary delays by having the review process already initiated and organized.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback to users about the batch of objects selected for processing, including a summary of what will be affected. Users can review this feedback and modify their selection or cancel the batch operation if inappropriate objects are included. This feedback mechanism ensures decision accuracy while keeping the process efficient by providing clear, concise information rather than requiring detailed individual review of each object.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9275414B2Mass decision mode in a mobile application
Publication Date: 2016.03.01 SAP SE
  • US9275414B2 patent drawing
  • US9275414B2 patent drawing
  • US9275414B2 patent drawing

AI summary

Systems and methods of providing a mass decision mode in a mobile application are provided. An object management module receives a plurality of objects to be presented to a user via a mass decision mode graphical user interface (GUI) of a client application residing on a client device. A mass decision module generates the mass decision mode GUI, the mass decision mode GUI including a description of the respective objects of the plurality of objects and a mass decision option. The mass decision option is an option to apply a deviant decision to a first portion of the one or more objects and to apply a default decision to a remainder portion of the one or more objects upon being selected. A deviant decision module assigns, upon receiving a selection of an object of the one or more objects, the deviant decision to the object.