Multi-tenant Email Object Sharing Model

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing electronic communications, particularly emails, in multi-tenant database systems is challenging due to difficulties in sharing and integrating email content across multiple users and objects, leading to inefficiencies in communication management.

Innovation Solution

Implementing an email object within the multi-tenant database system that allows emails to be related to multiple people or objects via sharing relationships, enabling inheritance of sharing models and attributes, and utilizing recommendation rules and customizations to automate email processing, tagging, and workflow generation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a multi-tenant database system stores and processes emails for multiple customers, then the system can provide centralized email management infrastructure, but the complexity of sharing and integrating email content across multiple users and objects increases

Engineering Contradiction:
Improveemail sharing capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments email content into distinct components (email body, headers, attachments) and separates different aspects of email management (storage, sharing, processing) into independent modules. This allows the system to handle multiple customers' emails without requiring complete system redesign for each customer, reducing overall complexity while maintaining versatility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal email object model that can represent emails from multiple customers and objects within a single database structure. The sharing relationships mechanism allows one email object to be associated with multiple people and objects, enabling the system to handle diverse email management needs without requiring separate specialized systems for each customer.

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

2Productivity

If the system processes emails manually without automation, then customization and control over email handling is maintained, but productivity and efficiency of email management decreases

Engineering Contradiction:
Improveemail processing efficiencyVSAvoidautomation level
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The patent implements preliminary processing actions that are automatically performed when emails are received or created. This includes automatic tagging of emails based on their content and metadata, pre-association with relevant people and objects, and initialization of sharing relationships. These preliminary actions prepare the email for subsequent processing and reduce the need for manual intervention in routine tasks.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system performs self-service processing by automatically analyzing email content, determining appropriate tags and associations, and managing sharing relationships without requiring manual input. The email processing system autonomously identifies relevant information and performs necessary actions based on predefined rules and customer configurations, significantly improving productivity while maintaining appropriate levels of automation.

Inventive Principle:
Principle #25Self-service

3Loss of information

If email content is not integrated with other database objects, then the system structure remains simple, but the ability to track and report on communications across multiple people and objects is limited

Engineering Contradiction:
Improvecommunication tracking completenessVSAvoiddata integration complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements a nested structure where email objects can be associated with multiple people and objects through sharing relationships. This nested association model allows the system to track communications across multiple entities without requiring completely separate database tables for each relationship type. The nested structure maintains information completeness while managing integration complexity through hierarchical organization.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent introduces sharing relationships as an intermediary mechanism that connects email objects with people and other objects. This intermediary layer simplifies the integration process by providing a standardized way to establish and manage associations between different database entities. The sharing relationships table acts as a mediator that handles the complexity of multi-entity connections while maintaining simple access patterns for retrieving integrated information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8935193B2Methods and systems for performing email management customizations in a multi-tenant database system
Publication Date: 2015.01.13 SALESFORCE INC
  • US8935193B2 patent drawing
  • US8935193B2 patent drawing
  • US8935193B2 patent drawing

AI summary

An email object is provided in a multi-tenant database system that can be related to multiple people (e.g., contact, lead, user) or any object represented for storage in the multi-tenant database system via sharing relationships. The email object follows a sharing model such that an email inherits the sharing model or attributes of a parent record specified via sharing relationships. In various aspects, a sharing model provides users with a true value of a multi-tenant database system as users are more informed about communications concerning people or other objects represented for storage in the multi-tenant database system.