Here is the rule I created, after I run this I then create two profiles
with the same SSN. Unfortunately, I see the mergedWith attribute is null
for both profiles.

require 'httparty'
require 'json'

rule = {
  metadata: {
    id: "exampleMerger",
    name: "Example Merger",
    description: "Dedup on SSN"
  },
  condition: {
    type: "profileUpdatedEventCondition",
    parameterValues: { }
  },
  actions: [
    {
      parameterValues: {
        mergeProfilePropertyValue: "eventProperty::target.properties(ssn)",
        mergeProfilePropertyName: "mergeIdentifier"
      },
      type: "mergeProfilesOnPropertyAction"
    }
  ]
}

request = HTTParty.post("http://127.0.0.1:8181/cxs/rules";,
  body: rule.to_json,
  basic_auth: { username: "karaf", password: "karaf" },
  headers: {
    "Content-Type" => "application/json"
  })

if request.code != 200
  raise "Unable to create rule: #{request}"
end

Even though I get a 204 response, I see the rule is created in /cxs/rules.

On Tue, Nov 6, 2018 at 11:38 AM Michael Ghen <m...@mikeghen.com> wrote:

> Hello again,
>
> I am trying to set up Unomi so that profiles are merged based on first
> name, last name, and SSN. I'm not finding a clear example for exactly how
> to do this. I would like to get an example working and add it to this
> tutorial I have going.
>
> It looks like I need to set up a rule for this, I'm thinking I can use the
> profileUpdatedEventCondition. What I'm confused about is what the action
> should look like? I see the note in the documentation
> about MergeProfileOnPropertyAction. I'm just not sure how the rule JSON
> should look.
>
> Also, it seems like only 1 property can be used for merging profiles, is
> that correct?
>
>
>

Reply via email to