LSH 2.4 - Unable To Remove Unassigned Term (Doc ID 2192712.1)

Last updated on OCTOBER 13, 2016

Applies to:

Oracle Life Sciences Data Hub - Version 2.4.6 and later
Information in this document applies to any platform.

Symptoms

On : 2.4.6.6 version, Definition Component

ACTUAL BEHAVIOR
---------------
It is not possible to remove a term if the associated object was deleted. It seems that LSH is maintaining a link in the backend between term and object, which prevents the term to be dropped.

EXPECTED BEHAVIOR
-----------------------
If the term is de-classified before the object deletion, the term itself can be dropped afterwards.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create domain  - select Smoke subtype
2. Assign Security to new domain: Smoke
3. Go to Classification > Terms > Maintain Terms for SmokeHierarchy: add new term
3. Assign Classification: select SmokeHierarchy
4. Update Domain > Search and Add Value: new_term > Apply
5. Go to Classification > Terms > Maintain Terms for SmokeHierarchy: select <new_term> term > Remove > Apply


9. Create a new domain (ronnie6), and a new term <new_term> Assign SmokeGroup and SmokeHierarchy > add "new_term" term
10. Try to remove the term while it is associated with the domain - not possible
11. Update the domain and remove the associated term
12. Try to remove the term from Classification > Terms > success

Cause

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