Skip to main content
D
dmansfeld1-Visitor
1-Visitor
February 8, 2017
Solved

Invisible Vocabulary

  • February 8, 2017
  • 2 replies
  • 9661 views

Hi,

I have a problem. When trying to add a new term/modelTag, I dont see any vocabularies (and yes, they exist). Therefore I am unable to create new modelTags.

Any idea what can be done about it?

2017-02-08.png

*this is open drop down list for vocabulary

Edit:

TW version: 7.3.1-b39

​Browsers: Chrome, Firefox, Edge - all do the same

Thanks in advance for your thoughts.

Best answer by posipova

Update: Tomcat 8.0.39 or higher implements a stricter URL check and that request has a pair of curly braces in it that causes it to fail the check now.

http://localhost:7315/Thingworx/ModelTags/?Accept=application%2Fjson-compressed&_twsr=1&Content-Type=application%2Fjson&{}&_=1488386940987 


Curly braces aren't supposed to be in the URL strings, so it now fails the stricter check.


Workaround is to use Tomcat 8.0.38 or lower for now (minimum 8.0.33). Submitted as Jira PSPT-3410.

2 replies

P
posipova20-Turquoise
20-Turquoise
February 8, 2017

Could you please provide the thingworx version and the browser you are using? Might also open a support ticket to file the defect, if confirmed.

And just to make sure - are you logged in as Administrator?

D
dmansfeld1-VisitorAuthor
1-Visitor
February 8, 2017

Yep, I am.

TW version: 7.3.1-b39

Browsers: Chrome, Firefox, Edge - all do the same

P
posipova20-Turquoise
20-Turquoise
February 8, 2017

Strange, I'm on the same version and I am able to see the dropdown:

What happens if you go into a vocabulary directly (through the model tags section in the composer) and add a term manually?

Also what is your backend database? At this point I would say you should open a support ticket and have an engineer do a webex to investigate the issue.

T
tcoufal1-Visitor
1-Visitor
February 9, 2017

Hi,

I am having the same problem. I am running 7.3.0 on CentOS.

Opened the case, they couldnt reproduce the issue though.

P
posipova20-Turquoise
20-Turquoise
February 10, 2017

We are seeing multiple reports on this issue now, and although unable to reproduce locally - now this should be enough to gather the common variable in all of the problematic environments. I will keep this topic updated once we get any new information on the cause/resolution.

Terms & ConditionsAccessibility statement