Appearance
Objects
Once uploaded, your data is stored as objects — each one a single unit you generate content from. Examples: products, product variants, categories, places.
The only required attribute is uid, which uniquely identifies the object within an engine and is used to match updates.
In the data section you can browse all objects in a table and filter them with the query UI.
If autogenerate is enabled for the data pool, any new or changed object runs through the engine's workflow. If an upload doesn't actually change an object's data, no new run starts.
Objects hold only your structured data — generated content is stored separately as content assets.
Generating the same object in multiple languages is handled in the workflow (with a Language Router), not on the object itself.