When you upload a content to ADx, its Version Status is set to
Working Copy. After the first check-in, status changes to
Current and Version changes to
Note that you cannot see the preview of a working copy.
Later, when you want to work with the content again, you need to check it out:
Status changes to
Working Copy again and you can make your changes.
Having finished working with the content, you need to check in the content again. Version is automatically increased according to the mode you select (
Selecting the check-in mode:
When you check in a content, its
Version Status changes to
Current and all other copies have the status
Previous. However, all versions of the same content share the same
To view all versions of a content instance:
- Select the content.
- Click More.
- Click Versions.
When you select a content, you can view versioning information for on the right-side panel under Versioning.
The following video shows how to check out, update, and check in a content. It also shows the difference between a content's
Chronical Id (found on the Details page, under Versioning) and
Id (found on the Details page, under Technical).
The following table highlights and explains the procedure in the video and shows the time of each step.
|Copy the content ||0:20|
|In Swagger, find the ||0:33|
|Add a content name and attach a resource||0:44|
|Check in the content. Notice that the working copy is no longer visible and the version status for this content is now ||1:36|
|Try to call the ||1:58-2:10|
|Check out the content. Notice that now the current version is locked, and a new working copy shows.||2:36|
|Try to call the ||2:56-3:03|
|Notice that the (Technical) ||3:30|
|Notice that both the new working copy and the current version have the same ||4:28|
|View all versions of the content. Use the ||5:30|
|View all versions in UI.||6:43|
|Notice that the (Technical) ||7:07|
The following video shows how to update a content's file without versioning.
Versioning operations are also exposed via ADx REST API.