Dependency Management for Input Items in Workflow Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current information processing systems lack an efficient method for managing and executing complex workflows across multiple services, particularly in scenarios involving scanning, printing, and email delivery, where dependency relationships between input items are not effectively handled.

Innovation Solution

An information processing system that includes a memory for storing an application with process flow information and setting information, allowing for the execution of a series of processes, including receiving display requests, transmitting screen information, and acquiring list information for dependency-based input items from an external service, enabling seamless integration and execution of services like scan translation and acquired document printing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple input fields are used to select items in association with selection operations for acquiring external documents, then the system can handle complex workflows with multiple parameters, but the complexity of managing dependency relationships between input items increases

Engineering Contradiction:
Improvecapability to handle complex workflowsVSAvoidcomplexity of managing dependency relationships
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary component that manages dependency relationships between input items. This intermediary handles the complex logic of determining which input fields should be displayed based on selections made in other fields, thereby resolving the contradiction by offloading the complexity management to a dedicated mediator rather than requiring the entire system to handle it directly

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the management of input fields into independent dependency relationship definitions. Each input field's dependencies are defined separately and can be managed independently, allowing the system to handle complex workflows while maintaining manageable complexity through modular organization of dependency rules

Inventive Principle:
Principle #1Segmentation

2Reliability

If dependency relationships between input items are explicitly managed, then the accuracy of workflow execution is improved, but the ease of operation for non-technical users deteriorates

Engineering Contradiction:
Improveaccuracy of workflow executionVSAvoidease of use for non-technical users
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system enables non-technical users to define dependency relationships between input items through an intuitive interface without requiring specialized knowledge. The interface automatically handles the complex logic of dependency management, allowing users to simply specify their requirements while the system self-manages the technical implementation of dependency relationships

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

An intermediary interface layer is provided between the user and the dependency management system. This intermediary translates simple user actions into complex dependency relationship definitions, maintaining high reliability in workflow execution while preserving ease of operation for non-technical users through automated translation of user intent into technical specifications

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If list information for candidate input items is acquired from external services, then the versatility of the system is improved, but the time required to execute the workflow increases

Engineering Contradiction:
Improveability to integrate external servicesVSAvoidtime required to execute workflow
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining dependency relationships and preparing the structure for acquiring list information from external services. By establishing the dependency framework in advance, the system minimizes the time required during actual workflow execution while maintaining the ability to integrate with various external services

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies local quality by optimizing the acquisition of list information based on specific dependency relationships. Rather than uniformly acquiring all possible information, the system selectively retrieves only the list information relevant to the current workflow context and dependency requirements, thereby reducing overall execution time while maintaining versatility

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10992831B2Information processing system for setting dependency relationships for input items on a screen related to a process flow
Publication Date: 2021.04.27 RICOH CO LTD
  • US10992831B2 patent drawing
  • US10992831B2 patent drawing
  • US10992831B2 patent drawing

AI summary

An information processing system includes a plurality of programs each executing a predetermined process. The information processing system includes a memory that stores an application for executing a series of processes. The memory further stores use screen information. The information processing system further includes circuitry configured to: receive a display request for the use screen from an electronic device; transmit, to the electronic device, the use screen information defining the use screen requested by the received display request and the setting information for the application corresponding to the use screen information; receive, from the electronic device, a first acquisition request that includes a first item detail that is input to a first input item among the input items on the use screen; acquire, from the external service, list information; and transmit the acquired list information to the electronic device.