Harmonized, side-by-side, and new objects in the enhanced model
Key Takeaway
Starting Spring '22, Agentforce Consumer Goods builds side-by-side objects in the Enhanced Data Model as advanced versions of existing objects. It doesn't make them by adding fields to existing objects (harmonized objects) or by creating brand-new objects (new objects).
Starting Spring '22, Agentforce Consumer Goods extended its data model with harmonized objects, side-by-side objects, and new objects to support new features. As a result, older standard features and newer advanced features live together in the same org. A consultant needs to know which processes, visits, and app flows belong to which model.
Three kinds of objects
Agentforce Consumer Goods extended its data model in three ways. Each way changes the model differently and produces its own kind of object in the Enhanced Data Model: harmonized objects, side-by-side objects, and new objects.
| What it is | |
|---|---|
| Harmonized objects | An existing object that received new fields |
| Side-by-side objects | An advanced version of an existing object |
| New objects | An object that didn't exist before Spring '22 |
Harmonized objects and side-by-side objects both start from an existing object, so they are easy to mix up. A harmonized object is the existing object itself with new fields added. A side-by-side object is an advanced version of the existing object, built next to it instead of adding fields to it.
Picture a consultant, Lena, sorting the objects in an org into the three categories. For each object, she first asks whether it existed before Spring '22. If it didn't, it's a new object. For an object that already existed, she asks what changed. If the existing object received new fields, it's a harmonized object. If an advanced version of the existing object was built, that advanced version is a side-by-side object.