When Profile Notifications Use a Preconditions Type of "Check New Value" Then Any Profile Field Update Will Trigger the Notification (Doc ID 1586708.1)

Last updated on AUGUST 19, 2019

Applies to:

Symptoms

Configured Profile Notifications are unexpectably being generated when subscribers' profiles are updated, even though the updated profile field, or tag, is not configured to generate a notification.

To reproduce the issue, put the SMS's (Service Management System) ccsProfileDaemon process into debug mode.

1. Configure a Profile Notification (Services -> Subscriber Management -> Notification Management).
   The Profile Value may be anything, but the Precondition Type in the drop-down menu must be set to 'Check New Value'.
    
2. Set the Compare Value to '=' and in Compare Value 1 field define a value.
   For example:
   
   
   
3. Alter a Profile Field of the target subscriber, which is not the one selected in the notification preconditions.  Use the screens or the acsProfile tool, for example:
   
4. As seen in the ccsProfileDaemon debug output, the Profile Notification is triggered, irrespective of the configured Profile Field being modified.
   

Note: If no Compare Value is defined, then a notification is not triggered.

When configuring a Profile Notification, which has a precondition that checks a new value is equal to a set value, the expectation is that the notification is only triggered when that profile field is used or updated.  However, if the Profile Field  has a defined Compare Value, then any time any Profile Field is modified, a notification is triggered and sent out.

Changes

Configuration of new Profile Notifications, as defined in Symptoms section above.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.