cluster to guarantee that no new events will be collected while data migration is in progress. Special caution must be taken if you declared custom events as our migration scripts can only handle objects Instead the flow should look something like this: 1. Login to a social platform 2. Call back to a special secured system that performs an server-to-server call to send the login event to Apache Unomi using firstName:desc", "condition" : { "type" : "booleanCondition", "parameterValues" : { "operator" : "and", "subConditions" : [ { "type": "profilePropertyCondition",

firstName:desc", "condition" : { "type" : "booleanCondition", "parameterValues" : { "operator" : "and", "subConditions" : [ { "type": "profilePropertyCondition", Instead the flow should look something like this: 1. Login to a social platform 2. Call back to a special secured system that performs an server-to-server call to send the login event to Apache Unomi using "comparisonOperator": "equals", "propertyValueInteger": 1 } } ], "operator": "and" }, "type": "booleanCondition" } EOF The above result will return the profile count

default priority here since we don’t have other rules triggering on `tweetEvent`s and don’t need any special ordering. We then tell Unomi which condition should trigger the rule via the condition property