Threshold %ages in Aggregate Threshold Breach Notification Not In Order
Last updated on SEPTEMBER 10, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, External notification (JMS)
When a long running usage session has been terminated which crossed couple of intermediate thresholds, AoC was generated as aggregated one and threshold %ages were not given in increasing order.
A sample as below, where <ThresholdPercent>[90.0, 100.0, 99.0]</ThresholdPercent> seemed to be given in random order. It should be in increasing order.
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