IP Library Granted Patent US 9,798,813
Granted Patent B2
US 9,798,813 · App. 14/335,024 · Granted Oct 24, 2017

Extensible person container

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,798,813
App. No.
14/335,024
Granted
Oct 24, 2017
Kind
B2
Abstract

The technology disclosed relates to representing users in different contexts within customer relationship management (CRM) environments. In particular, it relates to creating a person object model for each user in the CRM environment by linking a plurality of user records in the CRM environment that is separately created by different organizations and departments. The person object model also incorporates online social identities of the users, according to one implementation. This inclusive linked model provides a comprehensive view of the users to handlers of the CRM environment, thus facilitating an enhanced overall CRM experience.

Claims (45)

1. A method of resolving uncoordinated person objects and person-related objects in a database, the method including:

receiving a query directed to a first person for objects stored in a database, in which multiple users in multiple departments created uncoordinated person objects that do not share a common key, and in which the person objects are linked to person-related objects;

identifying a plurality of candidate person objects responsive to the query for the first person, wherein the identified candidate person objects share at least some matching data;

transmitting data for display to a user that lists the candidate person objects;

receiving data from the user specifying linking among the candidate person objects;

linking the specified candidate person objects to a coordinating customer relations management (CRM) object using a system-generated unique person identifier as a common key and preserving linkage to respective person-related objects associated with the specified candidate person objects, thereby creating a first person-related set;

identifying one of the person objects in the first person-related set as a lead active person object;

receiving a subsequent request for CRM data related to the first person, retrieving the coordinating CRM object, and using the links from the coordinating CRM object to at least some coordinated person objects in the first person-related set; and

transmitting responsive data for display that lists data from the coordinated person objects, featuring data from the lead active person object.

2. The method of claim 1 , wherein the lead active person object is identified based on most recent account activity in the first person-related set.

3. The method of claim 1 , wherein the lead active person object is identified as an oldest person object in the first person-related set.

4. The method of claim 1 , wherein the coordinating CRM object and person objects that share the unique person identifier are doubly-linked by pointers.

5. The method of claim 1 , further including transmitting responsive data for display that includes data from person-related objects for companies and opportunities associated with the first-person related set.

6. The method of claim 1 , further including transmitting responsive data for display that includes data from person-related objects for companies and user activities associated with the first-person related set.

7. The method of claim 1 , further including transmitting responsive data for display that includes data from person-related objects for companies associated with the first-person r elated set.

8. A system that resolves uncoordinated person objects and person-related objects in a database, the system including:

a processor, memory coupled to the processor, and program instructions loaded in the memory that, when executed on the processor, cause the processor to carry out steps of:

receiving a query directed to a first person for objects stored in a database, in which multiple users in multiple departments created uncoordinated person objects that do not share a common key, and in which the person objects are linked to person-related objects;

identifying a plurality of candidate person objects responsive to the query for the first person, wherein the identified candidate person objects share at least some matching data;

transmitting data for display to a user that lists the candidate person objects;

receiving data from the user specifying linking among the candidate person objects;

linking the specified candidate person objects to a coordinating customer relations management (CRM) object using a system-generated unique person identifier as a common key and preserving linkage to respective person-related objects associated with the specified candidate person objects, thereby creating a first person-related set;

identifying one of the person objects in the first person-related set as a lead active person object;

receiving a subsequent request for CRM data related to the first person, retrieving the coordinating CRM object and using the links from the coordinating CRM object to at least some coordinated person objects in the first person-related set; and

transmitting responsive data for display that lists data from the coordinated person objects, featuring data from the lead active person object.

9. The system of claim 8 , wherein the lead active person object is identified based on most recent account activity in the first person-related set.

10. The system of claim 8 , wherein the lead active person object is identified as an oldest person object in the first person-related set.

11. The system of claim 8 , wherein the coordinating CRM object and person objects that share the unique person identifier are doubly-linked by pointers.

12. The system of claim 8 , further including transmitting responsive data for display that includes data from person-related objects for companies and opportunities associated with the first-person related set.

13. The system of claim 8 , further including transmitting responsive data for display that includes data from person-related objects for companies and user activities associated with the first-person related set.

14. The system of claim 8 , further including transmitting responsive data for display that includes data from person-related objects for companies associated with the first-person related set.

15. A non-transitory computer readable medium with program instructions loaded therein that, when executed on the processor, cause the processor to carry out steps of:

receiving a query directed to a first person for objects stored in a database, in which multiple users in multiple departments created uncoordinated person objects that do not share a common key, and in which the person objects are linked to person-related objects;

identifying a plurality of candidate person objects responsive to the query for the first person, wherein the identified candidate person objects share at least some matching data;

transmitting data for display to a user that lists the candidate person objects;

receiving data from the user specifying linking among the candidate person objects;

linking the specified candidate person objects to a coordinating customer relations management (CRM) object using a system-generated unique person identifier as a common key and preserving linkage to respective person-related objects associated with the specified candidate person objects, thereby creating a first person-related set;

identifying one of the person objects in the first person-related set as a lead active person object;

receiving a subsequent request for CRM data related to the first person, retrieving the coordinating CRM object, and using the links from the coordinating CRM object to at least some coordinated person objects in the first person-related set; and

transmitting responsive data for display that lists data from the coordinated person objects, featuring data from the lead active person object.

16. The non-transitory computer readable medium with program instructions of claim 15 , wherein the lead active person object is identified based on most recent account activity in the first person-related set.

17. The non-transitory computer readable medium with program instructions of claim 15 , wherein the lead active person object is identified as an oldest person object in the first person-related set.

18. The non-transitory computer readable medium with program instructions of claim 15 , wherein the linked coordinating CRM object and person objects that share the unique person identifier are doubly-linked by pointers.

19. The non-transitory computer readable medium with program instructions of claim 15 , further including instructions that implement transmitting responsive data for display that includes data from person-related objects for companies and opportunities associated with the first-person related set.

20. The non-transitory computer readable medium with program instructions of claim 15 , further including instructions that implement transmitting responsive data for display that includes data from person-related objects for companies and user activities associated with the first-person related set.

Assignments (2)
CHANGE OF NAME Recorded Oct 25, 2024
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 069268/0034 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2014
From: WALTERS, JEANINE; MARKHAM, BLAKE WHITLOW; KURUGANTI, ADITYA SESHA; RYAN, JOSEPH; TAMM, STEVEN; WINTERS, JASON
To: SALESFORCE.COM, INC.
Reel/Frame 033342/0844 →