Multi-tenant Email Object Model for CRM Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing and storing emails in a multi-tenant database system is challenging due to difficulties in threading and relating emails to multiple people or objects, and existing solutions fail to efficiently integrate email content with CRM applications, leading to loss of rich information.
Innovation Solution
A new email object model is introduced that allows emails to be associated with multiple contacts, leads, accounts, opportunities, and other objects, enabling one-to-many relationships and threading, with email content stored separately to optimize storage and retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If emails are stored entirely in the database, then data accessibility and retrieval are improved, but storage capacity and cost efficiency deteriorate
Solution Approach 1:
The email data is segmented into two storage locations: the database stores metadata and structural information, while external storage handles the actual email content and attachments. This segmentation resolves the contradiction by keeping critical data accessible in the database while moving bulk content to external storage to maximize capacity efficiency.
Solution Approach 2:
An intermediary reference mechanism is introduced between the database and external storage. The database contains references to external storage locations, allowing efficient access to email content without storing it directly in the database. This intermediary approach enables both quick retrieval and cost-effective storage.
2Device complexity
If a single database table is used to store all email data, then system simplicity is maintained, but data organization and retrieval efficiency deteriorate
Solution Approach 1:
The database structure is segmented into multiple tables: one for email metadata, another for threading information, and a third for associations with CRM objects. This segmentation improves retrieval efficiency by allowing targeted queries on specific tables without overwhelming the system with monolithic data structures.
Solution Approach 2:
The database system is designed to handle multiple functions: storing email data, managing threading relationships, and associating emails with CRM objects like contacts and accounts. This multi-functionality is achieved through a normalized multi-table structure that efficiently supports various query patterns and business logic.
3Ease of manufacture
If emails are not associated with CRM objects, then data entry simplicity is maintained, but integration value and functionality deteriorate
Solution Approach 1:
The database structure includes pre-defined association tables and foreign key relationships that enable automatic linking of emails to CRM objects. This preliminary structuring allows for easy automated data entry while maintaining strong integration capabilities, as the system is pre-configured to handle relationships between emails and CRM entities.
Solution Approach 2:
The system provides universal association capabilities that allow emails to be linked to multiple types of CRM objects (contacts, accounts, opportunities, tasks). This multi-functional association mechanism enhances integration value while maintaining ease of use through standardized relationship management interfaces.
Data Source
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 storage model such that some portions of an email are available using one form of storage and some portions of the email are available using another form of storage. In various aspects, a storage model provides users with a better value of a multi-tenant database system as storage requirements may be satisfied while providing users access to email content.