Profile Date Compare Node is not using TimeZone conversion at runtime
(Doc ID 1988221.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 to 5.0.2 [Release 5.0]
Information in this document applies to any platform.
The problem is that the Profile Date Compare node does not take into account the timezone when comparing the date in the profile tag (first converted from CET to GMT and stored as GMT) with sysDate.
It happens in Product Version 5.0.2 in the following conditions :
1. Set from GUI the date as "26 Feb 2015" -> the date is first converted from CET to GMT before it is stored in the profile tag as an unsigned integer: 1424905200 (25 February 2015 23:00:00);
2. At runtime on 26/2/2015, I am comparing the current date against the stored date using the PDC (Profile Date Compare) node;
3. Rather than taking the "TODAY" exit, it concludes that the date in the profile tag is actually yesterday, and takes the "PAST" exit.
This is incorrect. It is expected that the node should take the timezone into account - which is set correctly in the ACS call context.
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