Versioning Assets

When assets change, you can easily replace the existing asset with a new version. the original is still there to revert to if necessary. This will ensure that users always get the latest version of the assets and also allows the newest version to be available to any connecting systems.
The file name must match the current asset file name exactly and is case sensitive. If it does not match exactly, it will load as a new asset and may create confusion for users.
The new version must be loaded to the same folder as the original asset in order to replace it.
Best Practice is to version the asset with the same file type. If you receive a file type different than the one currently loaded and the same file type is not available, archive the old asset and upload the new one. It will then be treated like a new asset.

Follow these steps

 1. Navigate to the folder where the original asset is located.

If you are unsure where the asset lives, search for the asset, then use the breadcrumb to move to the folder.

2. Click Upload Assets in the upper right of the main window.

3. Select the asset you want to version.

Select whether or not you wish to Create Version or Rename the asset.If you select Rename, BrandNext adds a number 1 to the end of the file name and ingests it into the system as a new asset.  The uploader will get a notification that a new asset needs metadata to be applied to it.

If you do not wish to create a version or rename the asset, click on the X to close the window.

4. Click Done once the green status bar reached the end.
 
A versioned asset will go to uploader to adjust metadata if need be.
There is a version description field that should be filled out in the Apply Metadata screen. This is a short reason why this asset was versioned.
Example: “Replaced image on page 4”, or “corrected ingredient list”
5. Click Complete and Close, then ok to confirm
Once you have entered what changed, you can complete this step.
6. Complete the workflow by clicking on the blue complete button.
The CLC will get a notification that a New Version has been created.
The CLC can approve or reject a version.  Best practice here is for the CLC to review the version description to be sure it is clear.
If the CLC rejects the version, an email will be sent back to the uploader with a reason.
7. Click the complete button
To see the versioning of assets, the CLC or Admin can go to Classic view and look at the Versions tab to the right on the asset detail page. the newest version is shown at the top of the list.