Last updated on FEBRUARY 22, 2016
Applies to:Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.
There are two ways to disable existing notification at order level.
1. Delete a notification in cartridge. Rebuild the cartridge and deploy with same cartridge version.
2. Disable the notification in cartridge at order level by unchecking the “Enabled” option in “Detail” tab. Rebuild the cartridge and deploy with same cartridge version.
Expected OOTB behaviour:
- Notification should be disabled .
- Notification is still active with status as “ENABLED” in “OM_DEF_NOTIFICATION” table
OOTB Cartridge “OracleCgbuSIFalloutPIP” had a dummy event which needed to be removed. customer would not like to undeploy the existing cartridge in PROD as many orders are in progress.
Also customer would not want to increase the version of the cartridge and deploy since multiple version of cartridge affect server performance.
With notification event still alive , it is getting triggered for the new orders of the cartridge with same version and causing exceptions.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms