User interface for commerce architecture

Patent metadata

Field	Value
Publication number	US-11442952-B2
Application number	US-201916264391-A
Country	US
Kind code	B2
Filing date	Jan 31, 2019
Priority date	Sep 24, 2018
Publication date	Sep 13, 2022
Grant date	Sep 13, 2022

Abstract

Disclosed herein are method, system and device embodiments for setting up a graphical user interface (GUI) for a commerce architecture. An embodiment operates by providing a GUI that displays a first button for adding a first data source and a second button for adding a second data source, the second data source being related to the first data source, receiving a first response via the first button to add the first data source and a second response via the second button to add the second data source, providing a view of a first data schema and a second data schema, wherein the first data schema includes at least one object from the first or the second data source, and wherein the second data schema is a canonical data model, mapping the at least one object of the first data schema to at least one object of the second data schema, and providing a single entity view of the at least one object of the second data schema.

First claim

What is claimed is:

1. A method, comprising:
providing, by a computing device, a graphical user interface (GUI) comprising a first button for adding a first data source and a second button for adding a second data source, wherein the first and second data sources comprise customer records related to a common customer;
receiving, by the computing device, a first authentication permission from a user in response to adding the first data source via the first button and a second authentication permission from the user in response to adding the second data source via the second button;
providing, by the computing device, a view of a first data schema and a second data schema in the GUI, wherein the first data schema comprises at least one object displaying a first value indicating a first quantity of the customer records from the first or the second data source collapsed under the at least one object and wherein the second data schema is a canonical data model of the customer records;
mapping, by the computing device in the GUI with one or more visual logic connectors, the first quantity of the customer records in the first data schema to at least one object of the canonical data model of the customer records in the second data schema based on attribute definitions, wherein the one or more visual logic connectors display a mapping value indicating a second quantity of mapped customer records between the at least one object in the first data schema and the at least one object in the second data schema;
identifying, by the computing device in the GUI, an unmatched record in the first quantity of the customer records by a difference between the first value and the mapping value;
expanding, by the computing device in the GUI, the at least one object having the first quantity of the customer records to reveal the unmatched record; and
adding, by the computing device in the GUI, a new record corresponding to the unmatched record to the at least one object in the second data schema.

2. The method of claim 1 , further comprising:
displaying, by the computing device, a second value on the at least one object of the canonical data model to indicate a second quantity of the customer records in the at least one object.

3. The method of claim 1 , further comprising:
providing, by the computing device, a single entity view of the at least one object of the second data schema for the common customer, wherein the single entity view includes the customer records from the first and second data sources related to the common customer and the first and second data sources corresponding to the customer records.

4. The method of claim 3 , wherein providing the single entity view comprises:
transforming the at least one object of the first data schema based on a plurality of formatting rules;
determining a match between the at least one object of the customer records in the first data schema and the at least one object of the canonical data model of the customer records in the second data schema based on a plurality of matching rules; and
updating the at least one object of the canonical data model of the customer records in the second data schema as a master record of the at least one object of the first data schema based on a plurality of updating rules.

5. The method of claim 1 , further comprising:
managing, by the computing device in the GUI, the at least one object of the canonical data model of the customer records in the second data schema in response to a data management request.

6. The method of claim 5 , wherein the data management request is submitted by a requestor to manage privacy information of the common customer.

7. The method of claim 5 , wherein the data management request is submitted by a requestor to merge two customer records related to the common customer in the canonical data model into a single profile of the common customer.

8. The method of claim 1 , further comprising providing, by the computing device, a third button to add a third party data source related to the common customer.

9. The method of claim 8 , further comprising adding the third part data source through an application program interface (API).

10. The method of claim 1 , further comprising:
displaying, by the computing device in the GUI, a mapping of a category of data sources to the common customer, wherein the category visually displaying a quantity of data sources in the category.

11. The method of claim 1 , further comprising:
displaying, by the computing device, a quantity of total customer records added from the first and the second data sources and a quantity of unique customer records for the canonical data model of the customer records.

12. The method of claim 1 , further comprising:
displaying, by the computing device, a plurality of records in response to a search request, wherein each of the plurality of records displays a corresponding data source.

13. A system, comprising:
a memory; and
at least one processor coupled to the memory, wherein the at least one processor is configured to:
provide a graphical user interface (GUI) comprising a first button for adding a first data source and a second button for adding a second data source, wherein the first and second data sources comprise customer records related to a common customer;
receive a first authentication permission from a user in response to adding the first data source via the first button and a second authentication permission from the user in response to adding the second data source via the second button;
provide a view of a first data schema and a second data schema in the GUI, wherein the first data schema comprises at least one object displaying a first value indicating a first quantity of the customer records from the first or the second data source collapsed under the at least one object and wherein the second data schema is a canonical data model of the customer records;
map, in the GUI with one or more visual logic connectors, first quantity of the customer records in the first data schema to at least one object of the canonical data model of the customer records in the second data schema based on attribute definitions, wherein the one or more visual logic connectors display a mapping value indicating a second quantity of mapped customer records between the at least one object in the first data schema and the at least one object in the second data schema;
identify, in the GUI, an unmatched record in the first quantity of the customer records by a difference between the first value and the mapping value;
expand, in the GUI, the at least one object having the first quantity of the customer records to reveal the unmatched record; and
add, in the GUI, a new record corresponding to the unmatched record to the at least one object in the second data schema.

14. The system of claim 13 , wherein the at least one processor is further configured to:
provide a single entity view of the at least one object of the second data schema for the common customer, wherein the single entity view includes the customer records from the first and second data sources related to the common customer and the first and second data sources corresponding to the customer records.

15. The system of claim 14 , wherein to provide the single entity view, the at least one processor is configured to:
transform the at least one object of the first data schema based on a plurality of formatting rules;
determine a match between the at least one object of the customer records in the first data schema and the at least one object of the canonical data model of the customer records in

Assignees

• Salesforce Com Inc
• Salesforce Inc

Inventors

• Woodward David
• Chadda Abhinav
• Hacker David
• Ness Steven
• Lagrotte Matt
• Moody Jason
• Bill Christopher
• Barde Kaustubh
• Lodovisi Lydia
• Flamion Sarah
• Hall Jamin

Classifications

• G06F3/0484

  for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range · CPC title

• G06F16/211 Primary

  Schema design and management · CPC title

• G06F16/2322

  using timestamps · CPC title

• G06F16/212

  with details for data modelling support · CPC title

• G06F16/288

  Entity relationship models · CPC title