Context Service Schema Mapping for CRM Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise software systems lack a standard configuration that meets user requirements, making it difficult for users to configure them optimally for their specific needs due to complexity.

Innovation Solution

An approach that defines a canonical schema and maps it to transactional contexts, allowing users to customize the system configuration through a user interface without coding, using a context service that includes an administration UI and high-performance runtime service to process mappings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a standard configuration is provided for enterprise software systems, then ease of operation is improved, but adaptability to specific user requirements deteriorates

Engineering Contradiction:
Improveease of configurationVSAvoidadaptability to requirements
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system is segmented into multiple configurable layers including schema definitions, mapping configurations, and context services. Each layer can be independently configured to meet specific user requirements while maintaining overall system coherence. This segmentation allows users to customize individual components without affecting the entire system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The configuration system is designed to be dynamic, allowing users to modify schemas, mappings, and service configurations at runtime. The context service dynamically adapts to different transactional contexts and user requirements, enabling the system to evolve from a static standard configuration to a flexible, user-specific configuration.

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If the system provides out-of-the-box configuration, then ease of operation is improved, but device complexity is reduced making it easier for users to configure

Engineering Contradiction:
Improveease of configurationVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

A context service is introduced as an intermediary layer between the user interface and the underlying complex enterprise software system. This mediator handles the complexity of schema mappings and configuration transformations, presenting a simplified interface to users while managing the intricate system complexity behind the scenes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system uses schema copying and mapping mechanisms where standard configurations can be copied and adapted to specific user needs. Users can start with pre-defined schema templates and mappings, then customize them without having to build configurations from scratch, reducing the perceived complexity.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If the system is highly configurable to meet specific requirements, then adaptability is improved, but device complexity increases making it difficult for users to configure

Engineering Contradiction:
Improveadaptability to requirementsVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Standard schemas, mappings, and configuration templates are prepared in advance through preliminary action. These pre-configured elements provide a solid foundation that users can build upon, reducing the complexity of configuration tasks while maintaining high adaptability to specific requirements.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service configuration through automated schema validation, mapping recommendations, and context-aware service selection. The configuration system guides users through the process automatically, reducing the complexity burden while allowing extensive customization.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11526895B2Method and system for implementing a CRM quote and order capture context service
Publication Date: 2022.12.13 ORACLE INT CORP
  • US11526895B2 patent drawing
  • US11526895B2 patent drawing
  • US11526895B2 patent drawing

AI summary

Disclosed is an improved approach for implementing enterprise software systems that addresses the above-described problems with existing systems. The present approach provides an effective and efficient way for defining schemas for services, and to define how to map the schema to particular transactional contexts.