Overview
The Cart Enricher reacts to these cart events:
- Added to cart - In the graph database, when a user adds a product to the cart, the enricher draws an edge of type "ADDED_TO_CART" between the session node and the product node. This creates the product node and the session node, if either doesn't exist yet. Each edge of this type has a timestamp property. If, during a session, the customer adds the product to his cart multiple times, then the enricher draws multiple edges between the session and the product node.
- Modified cart
- Removed from cart
Events
The Cart Enricher is triggered by cart events, such as added to cart in the Context service:
| Triggered by Schema | Payload example |
|---|---|
context/commerce/RemovedFromCart | |
context/commerce/ModifiedCart | |
context/commerce/AddedToCart |
The Cart Enricher draws an edge between the session node and the product node in the Secure Graph service documentation.
| Node or Relation | properties |
|---|---|
nodes/commerce/Session | |
nodes/commerce/Product | |
relations/commerce/Session/commerce/Product/commerce/ADDED_TO_CART | |
relations/commerce/Session/commerce/Product/commerce/ADDED_TO_CART/count |
Metamodel
The following interactive graphic displays the schemas that invoke this enricher and the schemas the enricher can affect in the graph.
Glossary
| Term | Description |
|---|---|
| authorization | The process of determining whether a given microservice has permission to gain consent. |
| consent | Permission to access (read, write) specific profile data, for example, permission to read/write age estimation or physical address. A consumer and a tenant can grant and revoke consent for subsets of their respective data. |
| consent class | A string alias, defined by developers, that references a set of profile data (also called "schemas") for which consent can be granted and revoked. This string is exposed to users (consumers and tenants) as a reference through which they control consent. For example, the Consent Class "Purchases" might reference a set of data that includes items purchased, purchase dates, and purchase prices. Toggling consent for "Purchase" would enable and disable consent for that entire set of data. |
| consent reference | A unique, randomized string that serves as a passcode to decrypt data associated with one or more schemas. Various service calls require a consent reference. For example:
|
| consumer | The end user whose actions yield profile data in the graph. A profile describes a single consumer. |
| context | Data that affects the state of the graph. This data can be collected from consumer-triggered events or from third-party sources such as weather stations. |
| Context Adapter | A microservice that receives data and, optionally, adapts it for entry into the graph. For example, a Context Adapter can adapt address data by adding a ZIP code and normalizing the street labels (for example, changing "St" to "Street"). The Context Adapter then passes the data through the Context service, which caches it so that enrichers can subsequently persist the data in the graph. |
| context repository | A temporary cache for adapted context data, before it is further processed by enrichers and persisted in the graph. |
| context service | An internal microservice that manages the insertion of, and the retrieval of, context data in the Context Repository. |
| encryption key | A unique, randomized string used to encrypt and decrypt specific data in the graph. Each data element is encrypted with a different encryption key. Decryption, using this key, is required to access, view, and alter the data. |
| enricher | A microservice that retrieves data from the Context Repository and/or Graph, possibly alters or extends it, and then persists data in the graph. An enricher can interpret data points, or sets of data points, to yield new data to persist. For example, an enricher can interpret purchasing data and contemporaneous weather station data to yield new data indicating that the consumer is a rainy-day shopper. |
| graph | The database that stores profile data as nodes, edges, and properties, and allows semantic queries. For example, the graph can represent a consumer"s shoe order as follows:
|
| identity | One of many independent units of data used to identify a unique profile, such as an email address, browser type, or version. |
| profile | Technical definition: Data in the graph that is associated with a single consumer and is interdependent (in other words, it can be traversed through node-edge relationships). Business definition: Data about a single consumer, collected and derived from events that are triggered by, or are logically associated, with that consumer. |
| schema | A string representation of a path in the graph which represents an abstraction, rather than a concrete instance, of a particular data structure. Schemas are used to define graph read/write permissions for Hybris Profile microservices. A microservice must explicitly register one or more schemas representing the graph structure(s) it intends to access and alter. A schema has one of the following two forms: |
| tenant | A registered entity with a shared commercial goal that subscribes to SAP Hybris Profile services and packages to reach that goal. A tenant can also develop and contribute enrichers and context adapters to the SAP Hybris Profile suite. Within YaaS, a tenant is a project. |
If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.
Use our private help channel. Receive updates over email and contact our specialists directly.
If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.