Table of Contents | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Version management enables tracking and maintaining different versions of an asset through a structured process. This functionality relies on Workcopy Management, which supports creating, editing, and publishing versions of assets.
...
Published Asset (Current Version):
An asset is considered to be the current version if its status is the one considered online. For example,
Published
is the online status of the default delivered workflow for assets (wkfasset).
Workcopy Creation (Draft Version):
When creating a new version, we do the following :A workcopy of the published asset is created.
It inherits all metadata from the published asset but is assigned a new ID and the default status of the structure (
Draft
for the default workflow of assets).The
copietravail
property references the published asset.
Editing the Workcopy:
The workcopy can be edited, saving changes without affecting the published version.
Publishing the Workcopy:
When the workcopy is ready to become the new current version, it is published. It triggers the following modificationsThe system archives the previously published asset and stores it in a new instance with a the status marked as archived.
The workcopy becomes the new published asset with the same ID as the original asset.
The workcopy instance is deleted at this point
...
A workcopy is created to edit the asset.
The new asset instance will have the following:
ID:
24
Status:
Draft
(or the default initial status defined inwkfasset
)The same property values as the current asset.
copietravail: Points to the current version (
23
).uid:
AssetTypeasset_23
2. Publishing the Workcopy
...
Expand | ||
---|---|---|
| ||
|
Useful links :
Functional documentation : Version management