SubUnit Object Deleting Message II After Submission
(Doc ID 2901755.1)
Last updated on OCTOBER 12, 2022
Applies to:
Oracle Healthcare Data Repository - Version 8.1.3 and laterInformation in this document applies to any platform.
Symptoms
Oracle Healthcare Data Repository - Version 8.1.3 and later
ACTUAL BEHAVIOR
---------------
When persisting a SubUnit object in HDR, the MessageII field is deleted. It seems HDR sets the internal messageId, and that likely deletes the MessageII for unknown reason.
It seems a messageId set by the service method has no reason to delete the associated "II" from the object.
This was causing audit issues on customers end. When customer corrected by setting the "II" after the service method, then the internal messageId is deleted.
This behavior is incorrect.
EXPECTED BEHAVIOR
-----------------------
Expect SubUnit object Note to delete MessageII after submission
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a subunit object with a message "II",
2. Then persist it,
3. Inspect the returned object.
4. SubUnit object deleting MessageII after submission
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 |