...
| Page Properties | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
Resources & Remarks
Modification History
Modify:
|
| Excerpt |
|---|
Tags are used to describe the status of an object within a process chain independently of the object's metadata, which means no need of definition in the schema and no triggering of new versions. |
...
| Note | ||
|---|---|---|
| ||
If a new version of an object is created, e.g. by tags can be manipulated as well. Especially, a POST update of the metadata or the binary content file , removes all tags are removed from the object. The new version will not have any tags. In order to assign version-independent processing information, please use resistant tags as described below. |
...
Tags can be set in any object creation body in the system property system:tags. In the same way, it is also possible to set, modify or remove tags for the new version of an object in any metadata POST/PATCH update call. A POST update without the explicit specification of already existing tags will remove them from the corresponding object.
...
Resistant Tags
As of version 2021 SummerAutumn, it is possible to assign resistant tags that are automatically transferred to the new version of an object . If a new version of an object is created, e.g., by a POST created during an update of the metadata or the binary content file, those file.
>> POST /api/dms/objects/{objectId}/contents/file
The resistant tags will be removed from the old object version and assigned to the new object version. As usual, the previous object version will not have any tags afterwards. However, the new version will have all the resistant tags assigned to it that were originally assigned to the previous version. Conventional non-resistant tags will not be reassigned to the new object version.
Resistant tags are identified by the suffix :resistant at the end of the string tag name.
...