MO-Audit Algorithm In CASE MO gets Triggered By Refreshing Case Page Even there are no changes
(Doc ID 2904491.1)
Last updated on JUNE 04, 2024
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.7.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 2.7.0.3.0 version, ENV - Environment
ACTUAL BEHAVIOR
---------------
When Case is loaded/refreshed without any changes, Sync Request is created (MO – Audit Algorithm is triggered).
EXPECTED BEHAVIOR
-----------------------
If Case is loaded/refreshed without any changes, Sync Request should NOT be created (MO – Audit Algorithm should NOT be triggered).
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. MO – Audit Algorithm plugged in to CASE Maintenance Object is triggered just by loading/refreshing the Case page, even without any changes.
This causes Sync Request record to be created, even though it should not be created in the first place.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
There would be several Sync Requests that would be created for the Cases unnecessarily.
This would quickly take up DB space with clutter Sync Request records.
Also, there are instances wherein outbound messages won't be sent to 3rd party due to the issue.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |