Service Variant Editor for Enterprise Interface Simplification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise service interfaces are complex and require numerous inputs, making them difficult for users to interact with and understand, especially when only a subset of inputs is relevant for a specific business purpose, leading to user confusion and inefficiency.

Innovation Solution

The implementation of a service variant editor that allows users to create a simplified service interface by hiding unnecessary inputs, setting default values, and defining mandatory fields, generating a WSDL document, and configuring web services to support client-server interaction, thereby reducing the number of inputs users need to provide.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a base enterprise service interface is provided with all necessary inputs, then the service is complete and functional, but the interface becomes complex and difficult for users to interact with

Engineering Contradiction:
Improveservice completenessVSAvoidinterface complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the base service interface into multiple service variants, each tailored to specific business purposes. Users can select the variant that matches their needs, receiving only the relevant inputs for that specific purpose rather than all inputs at once. This segmentation reduces interface complexity while maintaining service completeness through the base service.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of presenting all inputs at once (excessive action), the system provides only the necessary inputs for the selected service variant (partial action). This allows users to interact with a simplified subset of the interface that is sufficient for their specific business purpose, reducing complexity while maintaining functional completeness.

Inventive Principle:
Principle #16Partial or excessive action

2Adaptability or versatility

If all input fields are presented to users, then the service can handle all possible business scenarios, but users experience confusion and inefficiency when only a subset of inputs is relevant

Engineering Contradiction:
Improveservice adaptabilityVSAvoiduser interaction ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system dynamically adapts the service interface based on the selected business purpose. When a user selects a specific service variant, the system dynamically presents only the relevant input fields for that variant, rather than statically presenting all fields. This dynamic adaptation maintains versatility while significantly improving ease of operation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The interface is segmented into multiple service variants, each representing a specific business purpose. Users can select the appropriate variant, and the system then presents only the relevant inputs for that segment. This segmentation maintains adaptability across different business scenarios while improving ease of operation for each specific scenario.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If service variants are created for each business purpose, then user interaction is simplified, but the system complexity increases

Engineering Contradiction:
Improveinterface usabilityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The base service is designed as a universal multi-functional component that can serve multiple business purposes. Service variants are created by configuring different subsets of inputs for the same base service, allowing one base service to fulfill multiple functions. This universality simplifies the overall system architecture while improving interface usability through targeted variants.

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

Solution Approach 2:

Service variants are pre-configured with specific input sets tailored to particular business purposes. This preliminary configuration allows users to simply select their needed variant without having to configure inputs at runtime. The preliminary action of variant creation handles the complexity, while user interaction remains simple.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8839189B2Service variants for enterprise services
Publication Date: 2014.09.16 SAP SE
  • US8839189B2 patent drawing
  • US8839189B2 patent drawing
  • US8839189B2 patent drawing

AI summary

Implementations of the present disclosure include executing a business application on a server device, the business application executing a service based on a base plurality of inputs, accessing a first service variant based on the service, generating a first plurality of input fields based on the first service variant, the first plurality of input fields corresponding to a first plurality of inputs, the first plurality of inputs being a sub-set of the base plurality of inputs, and executing the service based on the first plurality of inputs that is input using the first plurality of input fields.