Multi-tenant Reusable Component Creation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional re-usable components are limited to single-entity use and are non-programmable, preventing them from being shared across multiple entities and customized for various applications.

Innovation Solution

Creating re-usable components using a multi-tenant on-demand database service, allowing them to be defined with names and attributes, enabling sharing and customization across multiple tenants, and integrating with other components to provide functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If re-usable components are created for single-entity use only, then they can be simple and easy to manage, but they cannot be shared across multiple entities

Engineering Contradiction:
Improvecomponent shareabilityVSAvoidcomponent structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements multi-tenancy in database services, allowing a single database service instance to serve multiple tenants simultaneously. Each tenant can create and manage their own re-usable components within the shared service, enabling components to be universally accessible across multiple entities while maintaining tenant isolation through logical separation mechanisms

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

2Adaptability or versatility

If re-usable components are made programmable with parameters, then they can be customized for various applications, but they become more complex and difficult to manage

Engineering Contradiction:
Improvecomponent customizationVSAvoidcomponent programmability
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic configuration capabilities where re-usable components can have adjustable parameters and properties that can be modified at runtime without changing the underlying component structure. This allows components to adapt to different applications and requirements while maintaining a standardized foundation, reducing the complexity burden of full programmability

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If multiple instances of re-usable components are created for different entities, then each entity can have customized components, but maintenance and updates become difficult

Engineering Contradiction:
Improveentity-specific customizationVSAvoidcomponent maintenance
Core Design Contradiction:
Adaptability or versatilityVSEase of repair

Solution Approach 1:

The patent merges the management of re-usable components into a centralized multi-tenant database service where all tenants share a common infrastructure. This allows updates and maintenance to be performed centrally on the service level, automatically propagating to all tenants, while still allowing each tenant to customize their component instances without creating separate maintenance burdens

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9791993B2System, method and computer program product for creating a re-usable component utilizing a multi-tenant on-demand database service
Publication Date: 2017.10.17 SALESFORCE INC
  • US9791993B2 patent drawing
  • US9791993B2 patent drawing
  • US9791993B2 patent drawing

AI summary

In accordance with embodiments, there are provided mechanisms and methods for creating a re-usable component for use in association with a multi-tenant on-demand database service. These mechanisms and methods for creating a re-usable component for use in association with a multi-tenant on-demand database service can allow the re-usable component to be utilized by multiple tenants of the multi-tenant on-demand database service.