documentation.adoc

= 360Degree_entity

The 360Degree_entity shows the Connection between data models.
The entity has two providers for persons and organizations.

The 360Degree_entity shows direct connections, don´t be confused with the ObjectRelation_entity.

== Adding new modules to the 360° view
You may want to display more modules within the 360degree view (for example after creating and implemeting your own module).

.An Example:
You added a module called "T-Shirts" to your project. Every person-contact can have _n_ "T-Shirts" and whenever a person owns a T-Shirt you want to
display it in the 360degree view. 

Heres is a list of what you need to do whenever you want to do this:

- At first you have to fill/add certain Fields/Processes in your new Context.
    - Add (These have to be written exactly like that, if not already existing):
        - CONTACT_ID, this Field has to contain a CONTACTID. That will be used to find the Connection to your Person or your Organisation.
        - DATE_NEW, this Field has to contain a Date as a Long Value. That will be used as the Date Value you can see in the Timeline View-Template.
        - ACTIVE, in this Field you can specify which Datasets are active or not. You have to declare that in the Value Expression as a Case-When due to the Filter
    - Fill (these can be filled in the specific Entity as a Process)
        - #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
- 
- 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
    - contactIdField: The Field in the Link Context where your Contactid is stored -> OBJECT_ROWID