property has been added to store the properties as flattened in Elasticsearch and should avoid mapping explosion for dynamic properties. If there is dynamic properties that you want to send with your flattenedProperties by JSON schema but these value will be stored as flattened and will not create dynamic mapping contrary to the properties field of the events. Here is an example for objects that used dynamic value “world!”, which is then used in the log message triggered by the action. You can now use unomi to trigger a “view” event and see the corresponding message in the Unomi logs. Once you’re done with

https://localhost:9443/cxs/rules \ --header "Content-Type: application/json" \ -d @- << EOF { "itemId": "form-mapping-example", "itemType": "rule", "linkedItems": null, "raiseEventOnlyOnceForProfile": false, "raiseEventOnlyOnceForSession": false, "priority": -1, "metadata": { "id": "form-mapping-example", "name": "Example Form Mapping", "description": "An example of how to map event properties to profile your rule is properly deployed you can use the following SSH shell command : unomi:rule-view form-mapping-example The parameter is the itemId of the rule. If you want to see all the rules deployed in the

accesses the profile information. It is interesting to note that there is not necessarily a one to one mapping between users and profiles as users can be captured across applications and different observation the associated `ActionType. Example actions include: “Set user property x to value y” or “Send a message to service x”. CONDITIONTYPE `ConditionType`s define new conditions that can be applied to items the tracked condition and coming from that source. This is, in particular, used to implement form mapping (a solution that allows clients to update user profiles based on values provided when a form is