![No UI](https://img.shields.io/static/v1?label=UI&message=none&color=inactive) The "Relation Marker" plugin marks two assets with a nodereference field related to the relationship type of the two assets [MINITOC] ## Properties To be configured in *{home}/appserver/conf/custom.properties*. ##### relationMarker.license > type: String, **required: yes**, since 1.1, default: - License key (delivered by brix IT Solutions). ##### relationMarker.nodereferenceFieldId > type: InformationFieldId, **required: yes**, default: - The nodereference field for tagging the asset ##### relationMarker.relationKeywordRootId > type: NodeId, required: no, default: - The root node of relations in the keyword structure. If not configured, the plugin will read the rootId from the nodereferencefield > > > > > The keywords for the relations will be generated automatically (if not already present when searching by name) ## Screenshot ![keywords](keywords.png) ## Compatibility Matrix | Relation Marker | CELUM (min. version) | | ---------------- | -------------------------- | | 1.0 - 1.3 | 5.13.3 (tested up to 6.5) | | 1.4.0 | 5.13.3 (tested with 6.8) | ## Release Notes #### 1.0.0 > Released 23.11.2018 Initial Version #### 1.1.0 > Released 07.12.2018 - added a task to map old relations #### 1.2.0 > Released 07.12.2018 - if the rootnode property isn't set, the application will read the rootnode id from the nodereferencefield #### 1.3.3 > Released 29.01.2019 - added license - bug fixes #### 1.4.0 > Released 15.06.2020 - added a queue so that many relation changes only trigger a single metadata update