Transfer of Only SystemObject on an EUID is Allowed
Last updated on MARCH 06, 2018
Applies to:Oracle Healthcare Master Person Index - Version 4.0.2 and later
Information in this document applies to any platform.
On Oracle Healthcare Master Person Index (OHMPI) 4.0.2 version,
The GUI functionality to move system objects from one EUID to another allows the last SO on an EUID to be transferred.
This effectively deletes the old EUID for that SO as it's not possible to reverse this transaction.
Other actions (like merges and assumed matches) can be reversed, but not this one.
Transferring SO's in the GUI is new functionality over what the Customer has previously (4.0.2 vs 1.1.8).
However, the deleteSystemObject() API isn't allowing the last active SO on an EUID to be deleted (as this will result in the deletion of the EUID) but the transferSystemObject() API does allow the last active SO to be move (resulting the deletion of the EUID).
SR 15404352401 has been raised for the problem with the deleteSystemObject(), and the feedback was that the idea is not allow EUIDs to be deleted, but the transferSystemObject() API (as exposed via the GUI) is allowing this to happen. This is inconsistent behaviour.
If anything, Customer would prefer it to be the other way around (transfer to not allow the last active SO to be transferred, but delete to allow the last one to be removed).
Because the GUI can be used to do the transfer, there is a concern that the transfer can't be undone which increases the risk of someone doing an action that can't be fixed.
The transaction should be able to be reversed in some form or another (like an update can be reversed by doing another update with the original details, or merge can be unmerged, etc), but this one can't be.
The issue can be reproduced with the following steps:
1. Create two system objects (and hence two EUIDs).
2. Use the GUI to compare the two EUIDs (eg. use the Compare function in the Dashboard)
3. Expand to view the source system records
4. Click on the icon to transfer one of the source system records to the other EUID.
5. View the transaction history -- it'll show the transfer as just another transaction
6. Try to access the old EUID using the Person Search -- it'll tell you that the active EUID is the other EUID (just as if it were a merge)
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