When Profile Notifications Use a Preconditions Type of "Check New Value" Then Any Profile Field Update Will Trigger the Notification
Last updated on APRIL 14, 2015
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.
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.
- 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'.
- Set the Compare Value to '=' and in Compare Value 1 field define a value.
- 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:
- 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.
Configuration of new Profile Notifications, as defined in Symptoms section above.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms