From 83fa304fed427f973dd3c78961d4384d97f168e7 Mon Sep 17 00:00:00 2001
From: Sebastian Listl <s.listl@adito.de>
Date: Wed, 7 Oct 2020 15:21:01 +0200
Subject: [PATCH] ObjectRelationType_entity documentation

---
 entity/ObjectRelationType_entity/documentation.adoc | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/entity/ObjectRelationType_entity/documentation.adoc b/entity/ObjectRelationType_entity/documentation.adoc
index 9c296c2d48..268b6a7387 100644
--- a/entity/ObjectRelationType_entity/documentation.adoc
+++ b/entity/ObjectRelationType_entity/documentation.adoc
@@ -1,3 +1,14 @@
 = ObjectRelationType_entity
 
-Administrative obsolescence of the object_entity
\ No newline at end of file
+This entity is for administrating the different types of ObjectRelations that can be used with the ObjectTree_entity.
+
+== Database Structure
+
+One complete ObjectRelationType can consist of either one or two rows in the table 'AB_OBJECTRELATIONTYPE', depending on whether the ObjectRelationType is double-sided or not. When there are two rows they share the same 'RELATION_TYPE' and the order of them is determined by the 'SIDE'.
+The flag 'HIERARCHY' determines if the relation between to objects will be hierarchical.
+
+== Entity Structure
+
+In the entity, one row represents a "full" ObjectRelationType, so the database entries that make it up are already joined together. 
+
+NOTE: A "second side" of the ObjectRelationType is not mandatory, if it is not set, only one row in the database is needed. Such a relation type makes sense when a relation is the same regardless from which side you view it (e. g. acquaintance).
\ No newline at end of file
-- 
GitLab