Hello you are right, the loginEventCondition was removed from Unomi and the
sample wasn't updated. Here's the corrected rule:
{
"metadata": {
"id": "exampleLogin",
"name": "Example Login",
"description": "Copy event properties to profile properties on login"
},
"condition": {
"parameterValues": {
"subConditions": [
{
"type": "eventTypeCondition",
"parameterValues": {
"eventTypeId": "login"
}
}
],
"operator": "and"
},
"type": "booleanCondition"
},
"actions": [
{
"parameterValues": {
"mergeProfilePropertyValue": "eventProperty::target.properties(email)",
"mergeProfilePropertyName": "mergeIdentifier"
},
"type": "mergeProfilesOnPropertyAction"
},
{
"parameterValues": {
},
"type": "allEventToProfilePropertiesAction"
}
]
}
I hope this will fix your issue. I'll also fix the issue in Unomi's source
code.
Regards,
Serge...
On Fri, Aug 23, 2019 at 5:50 PM Nicola Messina <[email protected]> wrote:
> hi,
> I'm studying the login sample, but it didn't work properly, does not merge
> user with the same email, and searching in the karaf.log i found "Couldn't
> resolve condition types : [loginEventCondition]"
>
> LoginEventContition is defined in the exampleLogin rule as condition, but
> this condition is not defined in unomi.
>
> How can i resolve this problem?
>
> By, Nicola
>
