From c7ff8376e59342af334863d0d0c6f40d98ef980a Mon Sep 17 00:00:00 2001
From: "a.voegl" <a.voegl@adito.de>
Date: Tue, 8 Dec 2020 14:40:19 +0100
Subject: [PATCH] [Projekt: Entwicklung - xRM][TicketNr.: 1053175][Erweiterte
360-Grad Ansicht]
---
entity/360Degree_entity/documentation.adoc | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/entity/360Degree_entity/documentation.adoc b/entity/360Degree_entity/documentation.adoc
index b2ad150c07..f19f7f1c59 100644
--- a/entity/360Degree_entity/documentation.adoc
+++ b/entity/360Degree_entity/documentation.adoc
@@ -23,14 +23,14 @@ Heres is a list of what you need to do whenever you want to do this:
- #CONTENTTITLE, this will be the main display Text and the blue Link
- #CONTENTDESCRIPTION, this will be the smaller, mostly longer, Text beneath the #CONTENTTITLE
-- Add an elemnt (with the name of the context you want to add) in the process of the `ObjectType_param` in the *corresponding provider* which is located in the `360Degree_entity`. _We would extend the JSON-Object which is returned in the `PersonObjects`-provider by the name of our t-shirt-context: "TShirt" in our example
--
+- Add an element (with the name of the context you want to add) in the process of the `ObjectType_param` in the *corresponding provider* which is located in the `360Degree_entity`. _We would extend the JSON-Object which is returned in the `PersonObjects`-provider by the name of our t-shirt-context: "TShirt" in our example
+
- In that JSON-Object can also add some Configuration Elements to change the results.
- setGroupBy: here you can declare a DB-Column that will be used as the new group by of that context. A good example is Order. We want to group by the Ordertype so we have to declare ORDERTYPE as our groupBy.
- If your DB-Value is related to a Keyword you also have to use groupByKeyword and add the Container as Value
-- If you have a Connection of 1:N in your Database Schema (like Activity and ActivityLink) you have to add specific Properties in your Context Object. Lets take ActivityLink as a Example.
- - subContext: the Name of the "Link"-Context -> ActivityLink
- - childField: The Field where the LinkID to your Parent is stored -> ACTIVITY_ID
- - parentField: The field in your Parent Context where your Connection to your Child is stored -> ACTIVITYID
+- If you have a Connection of 1:N in your Database Schema (like Task and TaskLink) you have to add specific Properties in your Context Object. Lets take TaskLink as a Example.
+ - subContext: the Name of the "Link"-Context -> TaskLink
+ - childField: The Field where the LinkID to your Parent is stored -> TASK_ID
+ - parentField: The field in your Parent Context where your Connection to your Child is stored -> TASKID
- contactIdField: The Field in the Link Context where your Contactid is stored -> OBJECT_ROWID
\ No newline at end of file
--
GitLab