Smart Help Extension for Analytics Environments

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of analytics environments, particularly non-technical users, face difficulties in accessing and understanding the features and functionalities of these systems due to inadequate help documentation, which is often resource-intensive and not tailored to their needs.

Innovation Solution

A smart help browser extension is developed as a user-interface based, reusable, and configurable plugin that provides dynamic help content options such as text, images, or videos, allowing administrators to record custom help content for non-technical users, featuring guided help, in-place help, and recording options.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional help documentation is provided for analytics environments, then users can access information about system features, but the documentation is resource-intensive and not tailored to non-technical users' needs

Engineering Contradiction:
Improvehelp accessibilityVSAvoiddocumentation complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The help system is segmented into multiple delivery formats (text, image, video) and organized by user role (end-user vs. administrator). Non-technical users receive simplified, role-specific help content while administrators access comprehensive documentation, eliminating the need for a single complex documentation set.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Help content is customized based on user type and context. Non-technical users receive simplified, task-oriented help, while administrators receive detailed technical documentation. The help system adapts its content quality and depth to match the specific needs of different user groups.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If comprehensive help content is provided for all users, then all user needs are covered, but non-technical users are overwhelmed with unnecessary technical information

Engineering Contradiction:
Improvehelp content coverageVSAvoidhelp usability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The help system dynamically adapts content based on user role, task context, and interaction history. Non-technical users automatically receive simplified guidance, while administrators can access comprehensive technical information. The system transitions between different help modes seamlessly based on user needs.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system pre-configures help content appropriate to each user type before interaction. Non-technical users are presented with simplified, step-by-step guidance from the outset, while administrators have access to complete documentation. This preliminary customization prevents information overload for non-technical users.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If detailed technical documentation is provided, then complete information is available, but non-technical users cannot easily understand or navigate the content

Engineering Contradiction:
Improveinformation completenessVSAvoidhelp comprehension
Core Design Contradiction:
Loss of informationVSDifficulty of detecting and measuring

Solution Approach 1:

Technical information is segmented into essential and optional components. Non-technical users receive only the essential information needed to perform their tasks, presented in simplified language and formats. Complete technical details remain available but are not presented to users who don't need them.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple versions of help content are created as copies tailored to different user types. Simplified copies are provided to non-technical users with analogies and step-by-step instructions, while complete technical copies are available for administrators. Both copies contain accurate information but at different levels of detail.

Inventive Principle:
Principle #26Copying

4Ease of manufacture

If standardized help content is used for all users, then implementation is simple, but customization for different user needs is limited

Engineering Contradiction:
Improvehelp implementationVSAvoidhelp customization
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The help system is designed as a universal platform that serves multiple user types through a single implementation. The same infrastructure delivers both simplified help to non-technical users and comprehensive documentation to administrators, eliminating the need for separate help systems while maintaining full adaptability.

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

Solution Approach 2:

The system customizes help content by changing parameters such as detail level, format type, and complexity without requiring separate implementations. A single help system dynamically adjusts these parameters based on user role and context, providing customized content while maintaining a unified codebase and implementation approach.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20230259375A1System and method for providing a smart help extension for use with an analytics environment
Publication Date: 2023.08.17 ORACLE INT CORP
  • US20230259375A1 patent drawing
  • US20230259375A1 patent drawing
  • US20230259375A1 patent drawing

AI summary

In accordance with an embodiment, described herein is a system and method for providing a smart help browser extension for use with an analytics environment. An analytic applications environment can be provided by, or otherwise operate at, a computer system providing access to a data warehouse, or data warehouse instance. A smart help browser extension provides a user-interface based, reusable and configurable plugin that can be dynamically configured in order to provide relevant help content. An end-user can be provided with options on how to view the help content, such as via a help bubble of text, an image, or video, for example. The disclosed extension can also provide admins, or other technical users of the analytics environment, with the ability to record custom help content for other (e.g., non-technical) users of the analytics environment.