Notification Name Via Profile Tag Unreliable
(Doc ID 2642784.1)
Last updated on MARCH 02, 2020
Applies to:Oracle Communications Network Charging and Control - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (NCC) 18.104.22.168.0 version,
Consider a Scenario where the user is programmatically determining the Notification Template name and setting to a profile tag. On some occasions this works as expected, but with slightly longer names, it seems as though the Profile Tag is not understood and the template is not found.
Consider the below example, where the user set :
There is an extra "1" on the end. This is not always a 1.
So the NOTF node is going wrong somewhere. This needs to be reliable - otherwise the user have to replace the logic with specific NOTF nodes.
The issue can be reproduced at will with the following steps:
1. Create a notification with a long name.
2. Create a control plan with the below nodes:
- a Set Node setting a temporary string to the long name.
- an NOTF node reading from the temporary string field for the notification created in 1.
3. Trigger the Notification.
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