Autosuggest with termbases: Am I the only one who is constantly bothered that terms defined as "forbidden" via the usage field in the TB still get used for autosuggest?

Question

Any workarounds or info from SDL on fixing this? Seems like it should be relatively simple to implement, as the "forbidden" designation for usage field is already realized for the termbase QA verification routine (under "Check for terms which may have been set as forbidden" under the Project Settings). 
 I found one suggestion proposed in the Ideas subforum ( community.sdl.com/.../forbidden-terms-are-displayed-in-autosuggest) , but no responses or any other relative information on the webs! 
 For customer-supplied termbases with a significant number of "forbidden" entries, pulling the forbidden entries into autosuggest slows down the workflow and reduces the value of autosuggest significantly.

Paul · Answer

Hi TTalbot , 
 
There is a response as the status has been moved onto "Under Community review". This means the product manager has seen it, moved it on from "New" and the action now is this: 
 
"The idea is open for discussion in comments and voting by SDL and the customer community" 
 
So far it's only seen 9 votes so this isn't going to put it very high on the todo list.

Paul · Answer

Hi TTalbot , 
 
I think there probably are, but they may make use of term verification and catch them afterwards or show the forbidden value field in the term recognition window so they see while working not to use it. In a way I think people probably got used to the way it works and may also not be aware of the idea for voting. 
 
I would vote for this one... in fact I already did :-)

Trados Studio > 1. Trados Studio

Autosuggest with termbases: Am I the only one who is constantly bothered that terms defined as "forbidden" via the usage field in the TB still get used for autosuggest?