Editing Support Device for RPA Operation Flow Conversion

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Process analysis software often creates operation flows that cannot be directly converted into Robotics Process Automation (RPA) scenarios due to constraints, particularly with incomplete nested structures, making it difficult for non-technical users to modify these flows to meet RPA requirements.

Innovation Solution

An editing support device that includes an input acceptance unit for operation flows, a determination unit to identify incomplete nested states, and an error output unit to specify error nodes, facilitating user modifications by highlighting necessary corrections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If process analysis software creates operation flows with flexible control structures (including goto statements), then the operation flows can express complex business processes freely, but the operation flows cannot be directly converted to RPA scenarios due to incomplete nested structures

Engineering Contradiction:

Improveflexibility of operation flowVSAvoidconvertibility to RPA scenario

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary analysis of the operation flow before conversion to RPA scenario, identifying incomplete nested structures and goto statements in advance. This allows the system to prepare conversion rules and guidance beforehand, making the conversion process more reliable while preserving the original flexible operation flow design.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The conversion rule management system acts as an intermediary between process analysis software and RPA scenario creation. It translates flexible operation flows with goto statements into RPA-compatible formats by applying conversion rules, thereby maintaining adaptability while ensuring convertibility to RPA scenarios.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If a user who is not a software developer modifies operation flow to meet RPA scenario constraints, then the operation flow can be converted to RPA scenario, but it is difficult for the user to understand and modify the operation flow correctly

Engineering Contradiction:

Improveconvertibility to RPA scenarioVSAvoidease of modification for non-technical user

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system provides feedback to non-technical users by identifying specific nodes causing incomplete nested structures and explaining the conversion requirements. This feedback mechanism guides users on how to modify their operation flows to meet RPA scenario constraints without requiring deep technical knowledge.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The conversion rule management system serves as an intermediary that translates technical RPA conversion requirements into user-friendly guidance. It mediates between the complex conversion rules and non-technical users, making the modification process accessible and easy to understand.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If the operation flow includes incomplete nested structures (such as goto statements), then the operation flow can express complex control logic, but the operation flow cannot be directly input to the RPA product

Engineering Contradiction:

Improveexpressiveness of control logicVSAvoidease of conversion to RPA scenario

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system performs preliminary analysis to identify incomplete nested structures and goto statements before conversion. By detecting these elements in advance, the system can apply appropriate conversion rules to transform complex control logic into RPA-compatible formats, maintaining expressiveness while enabling conversion.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The conversion rule management system changes the parameters and structure of operation flows by applying transformation rules. It converts goto statements and incomplete nested structures into equivalent RPA-compatible control structures, preserving the original control logic expressiveness while adapting to RPA requirements.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS20250103415A1Editing support device, editing support method, and editing support program

Publication Date: 2025.03.27 NIPPON TELEGRAPH & TELEPHONE CORP

AI summary

An editing support device accepts input of operation flow indicating a series of operations on a computer by nodes indicating the operations and an edge connecting the nodes. Next, the editing support device determines whether or not a nested state of a control structure of the operation flow is incomplete on the basis of a connection relationship between the nodes of the operation flow. Here, in a case where the nested state of the control structure of the operation flow is incomplete, the editing support device determines that an error is included in the operation flow and specifies a node that is a cause of the error in the operation flow as an error node. Then, the editing support device outputs information on the specified error node.