Accessing and displaying shared data

• US 10,409,816 B2
• Filed: 08/23/2016
• Issued: 09/10/2019
• Est. Priority Date: 08/23/2016
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Venkiteswaran, Kevin, Torres, Marcus
• Primary Examiner(s): Kuddus, Daniel A
• Application Number:
  US15/244,524
• Publication Number:
  US 20180060371A1
• Time in Patent Office: 1,113 Days
• CPC Class Codes: G06F 16/24552 Database cache management

Abstract

Disclosed are examples of systems, apparatus, methods, and computer program products for accessing and displaying shared data. In some implementations, a shared cache can be maintained. A first component and a second component can be identified. A shared record can be identified as associated with the first component and the second component. It can be determined that the shared record is valid. Shared record data from the shared record can be displayed through the first component and the second component in a user interface.

Claims

1. A system comprising:

a database system implemented using a server system comprising one or more hardware processors, the database system configurable to cause;

maintaining a shared cache storing a plurality of database records shared by a plurality of components;

identifying a first one of the components comprising a first set of data elements;

identifying a second one of the components comprising a second set of data elements, the first component and the second component configured according to a unique record tag;

determining that a value of at least one data element of the second set of data elements is different from a value of at least one data element of the first set of data elements;

identifying, responsive to determining that the value of the at least one data element of the second set of data elements is different from the value of the at least one data element of the first set of data elements and using the shared cache, a first one of the shared records as being associated with the first component and the second component, the first shared record comprising shared record data corresponding to the first set of data elements and the second set of data elements;

updating the shared record data responsive to;

determining that the at least one data element of the second set of data elements and the at least one data element of the first set of data elements map to corresponding shared record data of the first shared record, and

determining that the value of the at least one data element of the second set of data elements is different from the value of the at least one data element of the first set of data elements;

determining, using the shared cache, that the first shared record is valid; and

responsive to determining that the first shared record is valid;

displaying the first component in a user interface at a display device, the displayed first component providing at least a first portion of the shared record data via the first set of data elements, and

displaying the second component in the user interface at the display device, the displayed second component providing at least a second portion of the shared record data via the second set of data elements.

2. The system of claim 1, the database system further configurable to cause:

identifying, using the shared cache, a second one of the shared records as being associated with the first component and the second component; and

determining, using the shared cache, that the second shared record is invalid;

processing, using the database system, an indication to update the second shared record; and

providing the updated second shared record to the shared cache.

3. The system of claim 1, wherein maintaining the shared cache comprises:

processing, using the shared cache, a first request for shared record data corresponding to the first set of data elements;

processing, using the shared cache, a second request for shared record data corresponding to the second set of data elements;

identifying the first shared record;

generating a combined data request based on the first request and the second request;

processing, using the database system, the combined data request; and

responsive to processing the combined data request, providing at least a portion of shared record data corresponding to the first set of data elements and the second set of data elements to the shared cache.

4. The system of claim 1, the database system further configurable to cause:

processing a request to display a third component; and

responsive to the request to display the third component, displaying the third component in the user interface at the display device, the displayed third component providing the first portion of the shared record data and the second portion of the shared record data using the shared cache.

5. The system of claim 1, wherein the components comprise one or more of:

a highlights component, a details component, a feed component, a related list component, a recently viewed component, an opportunity history component, a tasks component, a leads component, a calendar component, or a publisher component.

6. The system of claim 1, wherein the first set of data elements comprises one or more of:

an account identifier, an opportunity identifier, a record type, a feed comment, a feed post, a parent record identifier, a closing date, an owner identifier, or a next task.

7. The system of claim 1, wherein the first shared record represents one or more of:

an account, an opportunity, a lead, a case, a contact, a contract, a campaign, a solution, a quote, or a purchase order.

8. A method comprising:

maintaining a shared cache storing a plurality of database records shared by a plurality of components;

identifying a first one of the components comprising a first set of data elements;

identifying a second one of the components comprising a second set of data elements, the first component and the second component configured according to a unique record tag;

determining that a value of at least one data element of the second set of data elements is different from a value of at least one data element of the first set of data elements;

identifying, responsive to determining that the value of the at least one data element of the second set of data elements is different from a value of the at least one data element of the first set of data elements and using the shared cache, a first one of the shared records as being associated with the first component and the second component, the first shared record comprising shared record data corresponding to the first set of data elements and the second set of data elements;

updating the shared record data responsive to;

determining that the at least one data element of the second set of data elements and the at least one data element of the first set of data elements map to corresponding shared record data of the first shared record, and

determining that the value of the at least one data element of the second set of data elements is different from the value of the at least one data element of the first set of data elements;

determining, using the shared cache, that the first shared record is valid; and

responsive to determining that the first shared record is valid;

causing display of the first component in a user interface at a display device, the displayed first component providing at least a first portion of the shared record data via the first set of data elements, and

causing display of the second component in the user interface at the display device, the displayed second component providing at least a second portion of the shared record data via the second set of data elements.

9. The method of claim 8, the method further comprising:

identifying, using the shared cache, a second one of the shared records as being associated with the first component and the second component; and

determining, using the shared cache, that the second shared record is invalid;

processing an indication to update the second shared record; and

providing the updated second shared record to the shared cache.

10. The method of claim 8, the method further comprising:

processing, using the shared cache, a first request for shared record data corresponding to the first set of data elements;

processing, using the shared cache, a second request for shared record data corresponding to the second set of data elements;

identifying the first shared record;

generating a combined data request based on the first request and the second request;

processing the combined data request; and

responsive to processing the combined data request, providing at least a portion of shared record data corresponding to the first set of data elements and the second set of data elements to the shared cache.

11. The method of claim 8, the method further comprising:

processing a request to display a third component; and

responsive to the request to display the third component, causing display of the third component in the user interface at the display device, the displayed third component providing the first portion of the shared record data and the second portion of the shared record data using the shared cache.

12. The method of claim 8, wherein the components comprise one or more of:

a highlights component, a details component, a feed component, a related list component, a recently viewed component, an opportunity history component, a tasks component, a leads component, a calendar component, or a publisher component.

13. The method of claim 8, wherein the first set of data elements comprises one or more of:

an account identifier, an opportunity identifier, a record type, a feed comment, a feed post, a parent record identifier, a closing date, an owner identifier, or a next task.

14. A computer program product comprising computer-readable program code to be executed by one or more hardware processors when retrieved from a non-transitory computer-readable medium, the program code comprising instructions configurable to cause:

maintaining a shared cache storing a plurality of database records shared by a plurality of components;

identifying a first one of the components comprising a first set of data elements;

identifying a second one of the components comprising a second set of data elements, the first component and the second component configured according to a unique record tag;

determining that a value of at least one data element of the second set of data elements is different from a value of at least one data element of the first set of data elements;

identifying, responsive to determining that the value of the at least one data element of the second set of data elements is different from the value of the at least one data element of the first set of data elements and using the shared cache, a first one of the shared records as being associated with the first component and the second component, the first shared record comprising shared record data corresponding to the first set of data elements and the second set of data elements;

updating the shared record data responsive to;

determining that the at least one data element of the second set of data elements and the at least one data element of the first set of data elements map to corresponding shared record data of the first shared record, and

determining that the value of the at least one data element of the second set of data elements is different from the value of the at least one data element of the first set of data elements;

determining, using the shared cache, that the first shared record is valid; and

responsive to determining that the first shared record is valid;

displaying the first component in a user interface at a display device, the displayed first component providing at least a first portion of the shared record data via the first set of data elements, and

displaying the second component in the user interface at the display device, the displayed second component providing at least a second portion of the shared record data via the second set of data elements.

15. The computer program product of claim 14, the instructions further configurable to cause:

identifying, using the shared cache, a second one of the shared records as being associated with the first component and the second component; and

determining, using the shared cache, that the second shared record is invalid;

processing an indication to update the second shared record; and

providing the updated second shared record to the shared cache.

16. The computer program product of claim 14, the instructions further configurable to cause:

processing, using the shared cache, a first request for shared record data corresponding to the first set of data elements;

processing, using the shared cache, a second request for shared record data corresponding to the second set of data elements;

identifying the first shared record;

generating a combined data request based on the first request and the second request;

processing the combined data request; and

responsive to processing the combined data request, providing at least a portion of shared record data corresponding to the first set of data elements and the second set of data elements to the shared cache.

17. The computer program product of claim 14, the instructions further configurable to cause:

processing a request to display a third component; and

responsive to the request to display the third component, displaying the third component in the user interface the display device, the displayed third component providing the first portion of the shared record data and the second portion of the shared record data using the shared cache.

18. The computer program product of claim 14, wherein the components comprise one or more of:

a highlights component, a details component, a feed component, a related list component, a recently viewed component, an opportunity history component, a tasks component, a leads component, a calendar component, or a publisher component.

19. The computer program product of claim 14, wherein the first set of data elements comprises one or more of:

an account identifier, an opportunity identifier, a record type, a feed comment, a feed post, a parent record identifier, a closing date, an owner identifier, or a next task.

20. The computer program product of claim 14, wherein the first shared record represents one or more of:

an account, an opportunity, a lead, a case, a contact, a contract, a campaign, a solution, a quote, or a purchase order.