External Survivorship Rules as Default Criteria Ignores Attribute Group Comparison Criteria
(Doc ID 1966209.1)
Last updated on MARCH 02, 2017
Applies to:Siebel Universal Customer Master - Version 188.8.131.52 SIA  and later
Information in this document applies to any platform.
On : 184.108.40.206 SIA  version, Universal Customer Master
When web service "PersonService" , operation "createPerson" is invoked to update a contact, external rules survivorship is not working.
The contact first name is not updated even though the update came from a higher confidence source system.
Updates from higher confidence systems should be accepted when source survivorship is used.
The issue can be reproduced at will with the following steps:
1) Add three new systems:
2) Create a new Contact Attribute Group "Test Name" with the next fields
a) First Name
b) Last Name
c) Mother Maiden Name
3) Create a survivorship rule with the next parameters:
Name: Test SR
Object Name: Contact
Start Date: 21/12/2014
Default Criteria: External <-------
default rule set: Active
Business Service Name: Business Rule Service <-------
Busin ess Service Method: RunRules <-------
Rule Module Name: Contact Completeness <-------
4) Add the "Test Name" attribute group with the next values:
comparison rule: source
5) Configure the source confidence for the attribute group:
Add the three systems created in the next order
confidence level: 100
confidence level: 90
confidence level: 80
The web service called is "PersonService" and the operation is "createPerson"
To check that the service is working we send some request the first with the system 3(that has the loss confidence level) after that we send a sencod request with diferent values in fiel FistName an with the system 2(that has a higher confidence level), we expect that the fiel FirstName will be update on the golden record, but the golden preserve the first value.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|