Hi all
Each time I set forbidden terms field (the Status field here below), it goes back to the field I created myself as a picklist with Russian grammar cases (Grammatical case). Of course after clicking OK and reopening Verification Settings window.
Are there any restrictions to the field / picklist naming (only English, no special signs) or what could be the issue?
please advice
Hi Alexander The Great
Please confirm if I am understanding you correctly.
Your context:
As you show in the screen print, you have a long list of picklist fields.
You are setting up a forbidden value against Status - presumably error free.
However when visiting this UI, you see Grammatical Case at the top under the pick list field.
Your perspective:
You are worried Grammatical Case is being set as "the default" when it should be Status?
You are expecting to see Status being listed first - given you have defined a forbidden value?
My response:
If my understanding of your context and perspective is correct ... then please confirm: regardless of how this UI behaves, does Studio correctly verify terminology conflicts against Status that is marked as forbidden?
In my very rudimentary test it works as expected - including having the forbidden values non English with special characters 
Second point I wish to bring your attention to:
Users can define multiple complex forbidden pick list criteria's not just one. In my case it offers type first and in your case it offers Grammatical Case first it totally ok. 
In fact I suspect the order it shows, is based on the order it sees in MultiTerm/Termbase definition 
Looking forward to receiving your thoughts on my comments, have a good day
Lyds
Oana Nagy | RWS Group
_____________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Alexander The Great
Please confirm if I am understanding you correctly.
Your context:
As you show in the screen print, you have a long list of picklist fields.
You are setting up a forbidden value against Status - presumably error free.
However when visiting this UI, you see Grammatical Case at the top under the pick list field.
Your perspective:
You are worried Grammatical Case is being set as "the default" when it should be Status?
You are expecting to see Status being listed first - given you have defined a forbidden value?
My response:
If my understanding of your context and perspective is correct ... then please confirm: regardless of how this UI behaves, does Studio correctly verify terminology conflicts against Status that is marked as forbidden?
In my very rudimentary test it works as expected - including having the forbidden values non English with special characters
Second point I wish to bring your attention to:
Users can define multiple complex forbidden pick list criteria's not just one. In my case it offers type first and in your case it offers Grammatical Case first it totally ok.
In fact I suspect the order it shows, is based on the order it sees in MultiTerm/Termbase definition
Looking forward to receiving your thoughts on my comments, have a good day
Lyds
Oana Nagy | RWS Group
_____________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Translate
