Key Command Functionality in Electronic Documents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current electronic document systems are limited by cumbersome help commands that require users to manually scroll through extensive lists for information, offering limited functionality and requiring users to learn specific commands for each data field, making data retrieval inefficient.

Innovation Solution

The introduction of key commands that allow users to access ancillary information beyond specific data fields, enabling a secondary display with relevant data, such as warranty information, by executing key applications that retrieve and present specific information directly related to the form context.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If help commands are made universal for all data fields, then ease of operation is improved, but functionality is limited and users must manually scroll through extensive lists

Engineering Contradiction:
Improveease of operationVSAvoiddata retrieval efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system dynamically adapts the help command behavior based on the current data field context. When a user activates the help command, the system determines the relevant ancillary information for that specific field and presents it in a tailored manner, rather than showing a static universal list. This dynamic adaptation allows the same command to serve multiple functions while maintaining efficiency.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The help command is customized for each data field by identifying and presenting only the relevant ancillary information specific to that field. For example, when helping with a warranty field, the system presents warranty-specific information rather than a generic list of all possible information types. This local customization improves both ease of operation and retrieval efficiency.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If help commands are specific to each data field, then functionality is improved, but users must learn multiple specific commands increasing complexity

Engineering Contradiction:
ImprovefunctionalityVSAvoidcommand complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A single help command serves multiple data fields by automatically adapting its behavior based on context. The system maintains a universal help command interface that can assist with any data field, eliminating the need for users to learn multiple field-specific commands. The command's functionality is extended through contextual awareness, allowing one command to perform many functions.

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

Solution Approach 2:

The help command system serves itself by automatically determining which ancillary information is relevant based on the current data field context. Rather than requiring users to specify which type of help they need, the system autonomously identifies and presents appropriate information, reducing the burden on users to learn and remember different command variations.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If a universal help command interface is used, then ease of operation is improved, but the interface becomes cumbersome requiring manual scrolling through all available information

Engineering Contradiction:
Improveease of operationVSAvoidtime for data retrieval
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system extracts and presents only the relevant ancillary information for the current data field, separating it from the broader context of all possible information. By taking out only the necessary information rather than presenting everything, the system eliminates the need for manual scrolling through extensive lists while maintaining ease of operation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The help command provides partial information (only the relevant ancillary information for the current field) rather than excessive information (all possible information). This partial action approach reduces the amount of information the user must review, saving time while still providing sufficient help for completing the form efficiently.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7624340B2Key command functionality in an electronic document
Publication Date: 2009.11.24 SAP SE
  • US7624340B2 patent drawing
  • US7624340B2 patent drawing
  • US7624340B2 patent drawing

AI summary

Key command functionality is provided in an electronic document through a recognition of input data. The input data is received in a data field of the electronic document. If the input data is a help command, a help application is launched. The help application provides for the determination of a stored input data value to be inserted in the corresponding data field. If the input data is not a help command, but is a key command, the corresponding key application is identified and accessed. The key application is thereupon launched, where the key application executes steps for determining information ancillary to the form but useful for completing the form.