[Projekt: xRM-ContactManagement][TicketNr.: 2002650][360Degree_entity:...

[Projekt: xRM-ContactManagement][TicketNr.: 2002650][360Degree_entity: Optimierte documentation committen]

entity/360Degree_entity/documentation.adoc

@@ -83,11 +83,11 @@ The result of this process will, in this case, appear as "sub-headlines" of the
 
 === Providers and Consumers
 
-The dependencies (relations) between the 360Degree Context and the Contexts referencing the 360Degree View in their MainViews is, as usual in ADITO, established via a Provider and a Consumer (one for each dependency).
+The dependencies (relations) between the 360Degree Context and the Contexts referencing the 360Degree View in their MainViews are, as usual in ADITO, established via a Provider and a Consumer (one for each dependency).
 
 ==== Providers
 
-The 360Degree Context must have a Provider to for each dependency, named according to the Pattern `<Context name>Objects`. Examples:
+The 360Degree Context must have a Provider for each dependency, named according to the Pattern `<Context name>Objects`. Examples:
 
 * OrganisationObjects, for supplying the 360Degree tab in the OrganisationMain_view
 * PersonObjects, for supplying the 360Degree tab in the PersonMain_view
@@ -286,14 +286,14 @@ import("system.result");
 result.string(vars.get("$field.INFO"));
 ----
 * EntityField DATE_NEW is already present, so there is nothing to do.
-* Create the new EntityField "ACTIVE". For testing purposes, it is enough to configure the fix value "true", preferably via property "expression" of the respective RecordFieldMapping:
+* Create the new EntityField "ACTIVE". For testing purposes, it is enough to configure the fix value "'true'", preferably via property "expression" of the respective RecordFieldMapping:
 +
 .Activity_entity.db.ACTIVE.value.expression.js
 [source%autofit, javascript]
 ----
 import("system.result");
 
-result.string('true');
+result.string("'true'");
 ----
 * Set the Context's property "icon" to the same icon that appears in the side bar to the left of the client - i.e., in this case, select the icon named "VAADIN:HOURGLASS_END".
 * If a grouping according to Activity_entity's EntityField CATEGORY is applied (see below), you may use propertyIcon process for setting code that enables CATEGORY-specific icons to appear beside the grouped datasets.