| Product Version |
|
|---|
| Report Note | presentable |
|---|
| Assignee | Antje |
|---|
Resources & Remarks  https://wiki.optimal-systems.de/pages/viewpage.action?pageId=57442949
- Antje: Cleaning up the Tutorial → moving things to Concepts
Modification History | Name | Date | Product Version | Action |
|---|
| Antje | 08 FEB 2021 | 2.4 | New page properties macro. | | Antje | 28 APR 2021 | 2021 Summer | Info added: number of tags per object limited to 50. |
Modified: | Note |
|---|
| | If a new version of an object is created, e.g. by a POST update of the metadata or the binary content file, 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. |
To be added in table row "name": As of version 2021 Summer, the suffix :resistant triggers a specific behavior of the tag. If a tag name matches the expression [a-z](:?[a-z][a-z0-9]*)*:resistant, the tag will behave as like a resistant tag as described below.
new section: As of version 2021 Summer, 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 update of the metadata or the binary content file, those 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. The resistant Resistant tags are identified by the suffix :resistant at the end of the string tag name.
|