Assets are files that you can use when building a configurator. Images are one of the most common assets. Another common kind is the data source, which contains tabular data from e.g. a MS Excel or CSV file.
Typically assets are imported from files you already have, such as images, documents or 3D models. However, some assets can also be created and edited directly in the asset editor, or imported automatically with workflows.
When you upload a file, you may be asked what kind of asset you'd like to create with it. Each asset serves a particular purpose: images can be displayed, files downloaded and data source filtered. Other assets are used for 3D visualization and more will be added over time.
Assets are organized into asset bundles, which can be assigned to a configurator to allow it to use those assets. You can further organize the assets in a bundle with folders.
An asset bundle can be assigned to multiple configurators, thus ensuring that the same data is used in all of them. If you have multiple configurators that share a common data set, this is a great way to prevent inconsistencies and simplify maintenance.
On the other hand, you can also assign multiple asset bundles to a single configurator. This may be useful when you have a lot of assets and want to organize them into separate bundles.
Asset bundles are versioned. You control when the changes you make to an asset bundle go live. You can edit the assets of a bundle for as long as you want, without affecting any of your configurators. Only once you publish your changes will a new version of your asset bundle be created. You decide which configurators should use that new version, allowing you to update your configurators one by one – or all at once, the choice is yours!
Of course you can also revert to an earlier version of your asset bundle at any time. The version history of an asset bundle allows you to assign any past version to your configurator.
Any changes you make to an asset bundle are automatically collected into a draft. You can either publish a draft or delete it, if you want to discard those changes.
You can also assign a bundle draft to a configurator draft to test your changes. When you later publish the bundle draft, you can choose to have the configurator draft be published automatically as well. (also works the other way around!)