Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
As mentioned in this topic.
I have the same issue with the inability to identify the context type when creating a workspace from the Windchill home page. however, one of my TEST servers is currently exhibiting the desired behavior and i do not know what is different about this server. i have seen the same output in 1-2 screen shots for CS Articles in the PTC KB, but PTC TS cannot determine what is causing the context type to be shown after the name in ( ). anyone else experience this?
we are running wc12.0.2
Solved! Go to Solution.
Solution found by PTC Technical Support: Duplicate Container Names!
If you have a Library, Product or Project context with the same name, Windchill will display the context type in the New Workspace UI when invoked from the Windchill Home Page. I spent a lot of time comparing exported user preferences and log files trying to find what enabled this "feature".
The magic is that you must also be a member of both context teams for the context type to appear. That is why it was only working for me and not the others users I checked with.
I am going to validate this by creating a Project with the same name as a Product or Library that has the Organization added to the team which should enable this display for all users 🤞
Initial test with the Guest Role was unsuccessful. Looks like users, groups, or roles need to be added to a team role in the context.
PTC Technical Support has updated CS Article CS432444 which previously defined this capability as unavailable
@ScottMorris, can you reference the knowledge base article. The only one I can see is the one saying its not possible: CS246957. What you are showing is indeed different that what I see where context type is not shown. The reference article seemed to allude to users not being able to see certain contexts based on their role. That does not appear to be the same as your issue.
Great point, totally forgot to reference the CS Article I was looking at: CS432444
The change in display is only happening for my user accounts and not anyone else's. I am going to export user preferences today to compare and hopefully identify which preference I might have changed to enable the display of the context type.
Noting on my system, the context is available in parenthesis from the Creo Server Manager drop down when creating a new workspace. If you use new Workspace from any Windchill page like the Home tab or from a product/library, the context type is not displayed. Please confirm Scott if you are seeing this on those pages I mentioned like creating a workspace from the home tab.
Yes, I am seeing the Context Type displayed in the Create New Workspace UI from the Windchill Home Page
If someone can identify the class that renders the drop down, we can see if there is a switch that controls the display output of the list.
This would definitely be a welcome behavior.
We have a naming convention where we include the context type in every context name. It would be nice to not have to do that!
Solution found by PTC Technical Support: Duplicate Container Names!
If you have a Library, Product or Project context with the same name, Windchill will display the context type in the New Workspace UI when invoked from the Windchill Home Page. I spent a lot of time comparing exported user preferences and log files trying to find what enabled this "feature".
The magic is that you must also be a member of both context teams for the context type to appear. That is why it was only working for me and not the others users I checked with.
I am going to validate this by creating a Project with the same name as a Product or Library that has the Organization added to the team which should enable this display for all users 🤞
Initial test with the Guest Role was unsuccessful. Looks like users, groups, or roles need to be added to a team role in the context.
PTC Technical Support has updated CS Article CS432444 which previously defined this capability as unavailable
Amazing file. An edge case on an edge case on an edge case.
"This place is a X-file wrapped in a cover up and deep-fried in a paranoid conspiracy"