| 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
Not all tags are relevant for the general user, e.g. tags that are needed for automatic data processing. To prevent the general user from seeing these tags, a classification tag can be defined as follows in the schema: <classification>tag[tenMyTenant:process,0,1,2,3,4,5,6,10,100]</classification> For the general user, only the tags that are explicitly listed are displayed. The name and value of the tag will be shown. If specified, they are localized. Note: Tags will not be validated by the backend. The same tag name can be used by different clients, but the tag can be used differently by these clients. Since this can lead to problems, it is recommended to assign an appropriate name space to the tag, e.g. the tenant name. In the above example, the tag "process" has been assigned to the name space tenMyTenant. |
| 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 | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
In document lifecycle management, multi-stage and asynchronous processes are not uncommon—quite the contrary. The first process steps are carried out with the highest priority. More complex and currently not absolutely essential process steps are carried out asynchronously with a lower priority. This saves time, and carrying out operations in parallel lets you distribute resources more evenly. To resume a process chain, additional information about the current status state of the process is necessary. In order to not mix an object's metadata with its status state data, there is the possibility to tag objects. . Pure tagging operations do not trigger the creation of new object versions.
Objects can be searched by tags and selected for the next process step. All tagging activities are recorded by the yuuvis® system in the object history (Audit Trail). Thanks to this, you can always retrace who has done what and when. Trouble shooting, reporting on the process status state or general issues are made easy by this centrally stored history.
Characteristics of Tags
...
Difference between metadata and tags:
- Tags do NOT belong to the metadata and thus do not need to be defined in the schema. Moreover, .
- Tags are stored together with the object as value for the
system:tagsproperty similar to metadata. - Pure tag operations do not NOT lead to the creation of a new object version.Tags are always available for the current object version.
- The properties of tags are included in the searchable data.
...
- 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.
| Note | ||
|---|---|---|
| ||
If a new version of an object is created, tags can be manipulated as well. Especially, a POST update of the binary content file removes all tags 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. |
Tag Management
Endpoints
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.
Furthermore, there are endpoints for pure tag operations that do not trigger a new version of the corresponding object, but only a new entry in the audit trail:
...
State information:
- Tags describe the state of an object in a process chain. The state information is specified via an integer value.
Tracing information:
- Tags are provided with a process identification that allows to retrace tag operations and tune the update or deletion permissions for the tag.
Assignment:
- Tags can be added to any object during object creation, during metadata updates or completely independent via a tagging endpoint.
- Multiple tags can be added to one object.
- The number of tags assigned to one object is limited to 50.
Querying on tags:
- The properties of tags are included in the searchable data.
- Tags are queried similar to table properties.
Behavior during POST metadata updates:
- If the
system:tagsproperty is specified in the request body,- all included tags are assigned to the new object version with the given
nameandstate. The same value assystem:lastModificationDateandsystem:traceIdwill be set automatically forcreationDateandtraceIdrespectively for all of them. - each tag that is not included is deleted. The new object version will not have that tag.
- all included tags are assigned to the new object version with the given
- If the property
system:tagsis NOT specified in the request body or is set tonull, all tags will be deleted. The new object version will not have any tag.
Behavior during PATCH metadata updates:
- If the
system:tagsproperty is specified in the request body,- all included tags are assigned to the new object version.
- each tag that is not included is deleted. The new object version will not have that tag.
- If the
system:tagsproperty is NOT specified in the request body, all tags are transferred to the new object version. Theirstate,creationDateandtraceIdremain unchanged. - If the
system:tagsproperty is set tonull, all tags will be deleted. The new object version will not have any tag.
Behavior during POST updates of the binary content file:
- If the tag
nameends with the suffix:resistant, the tag is transferred to the new object version. Its state remains unchanged. - If the tag
namedoes 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
nameends with the suffix:resistant, the tag is transferred to the new object version. Its state remains unchanged. - If the tag
namedoes NOT end with the suffix:resistant, the tag is deleted. It will not be assigned to the new object version.
Any tag operation is documented in the object audit trail.
Tag Properties
Tags are defined by the following properties:
| Property | Type | Description | In a request |
|---|---|---|---|
name | String | Name of the tag for identification. It has to be unique for the corresponding object. The tag names are validated during a tag creation or update process. To pass the validation, they have to match the regular expression [a-z](:?[a-z][a-z0-9]*)* and must not be longer than 32 characters (as of 2022 Spring, no longer than 128 characters). As of version 2021 Summer, the suffix | required |
state | Integer | Represents the status of the corresponding object in a process chain. | required |
creationDate | String | Date and time of the last modification of the tag. It is set automatically by the system. | optional, only available in search queries |
traceId | Hexadecimal lowercase string with maximum length 16 | Process identification of any tag operation. If not specified in the request, a random String value will be set after the tag operation. In a tag update or delete request, the request parameter Per default, | optional, specified by means of the HTTP header X-B3-TraceId |
In a request, the corresponding properties are included directly in the URL for the call of the endpoint. In contrast, if tags are displayed in a response body, their properties are listed as a part of a JSON structure in the value of the property system:tags property.
Handling of the 'traceId'
The traceId is a process identification that provides the possibility to retrace tag operations and tune the update or deletion permissions for the tag. In the HTTP header, the request parameter traceIdMustMatch can be changed from its default value false to true. Thus, two different scenarios are possible:
...
Tagging Endpoints
The following endpoints for pure tag operations do not trigger a new version of the corresponding object, but only a new entry in the audit trail:
- Retrieve object tags by ID – GET /api/dms/objects/{objectId}/tags
- Add object tag by ID – POST /api/dms/objects/{objectId}/tags/{name}/state/{state}
- Update object tag by ID – POST /api/dms/objects/{objectId}/tags/{name}/state/{state}?overwrite=true
- Delete object tag by ID – DELETE /api/dms/objects/{objectId}/tags/{name}
- Add/update object tag by search query – POST /api/dms/objects/tags/{name}/state/{state}?query=<SQL>
Anchor ResistantTags ResistantTags
...
Resistant tags are identified by the suffix :resistant at the end of the string tag nametag name.
Note: The tag name including the suffix must not exceed the length limit of 128 characters.
Summary
This article gave an introduction into the handling of tags as a feature of the lifecycle management of objects in yuuvis® Momentum. In the "Tagging Objects for Processing" tutorial, an exemplary use case is explained.
...