Page Properties | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
Resources & Remarks https://wiki.optimal-systems.de/pages/viewpage.action?pageId=57442949
Modification History
|
Excerpt |
---|
The basic idea for the usage of tags is to describe the state of an object within a process chain. They basically consist of a name and a state value and can be assigned to any object. |
Section | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
- Tags do NOT belong to the metadata and thus do not need to be defined in the schema.
- Tags are stored together with the object as value for the
system:tags
property similar to metadata. - Pure tag operations do NOT lead to the creation of a new object version.
- Tags can only be attached to the current version of an object, whereas previous versions cannot have tags.
- For version-specific information, metadata provide the suitable options. They have to be defined in the schema.
...
Behavior during POST updates of the binary content file:
- If the tag
name
ends with the suffix:resistant
, the tag is transferred to the new object version. Its state remains unchanged. - If the tag
name
does NOT end with the suffix:resistant
, the tag is deleted. It will not be assigned to the new object version.
Behavior during POST restoring actions of an old version (as of 2022 Spring):
- If the tag
name
ends with the suffix:resistant
, the tag is transferred to the new object version. Its state remains unchanged. - If the tag
name
does NOT end with the suffix:resistant
, the tag is deleted. It will not be assigned to the new object version.
...