-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Won't Fix
-
Affects Version/s: 7.10, 8.10
-
Fix Version/s: None
-
Component/s: Layouts & Widgets, Seam / JSF UI, Search Tab
Studio-side:
- create simple vocabulary myVocab with several values
- create custom document model
- add 2 String fields (A and B) to the customer schema
- in the layouts, set field A with a Text widget
- in the layouts, set field B with a Single Vocabulary widget
- create a Search Content View named mySearchCV
- set field A as a Terms widget (this should be set as Checkbox by default inside the configuration panel)
- set field B as a Single Vocabulary widget
Server-side:
- synchronize Studio project
- create 2 or 3 documents with values filled in for title, and fields A and B
- head over to the Search tab
- select search mySearchCV
- click one of the field A aggregate values
- save the search and name it mySavedTestSearch
- click the Workspace tab
- select Searches in the left panel
- observe the vocabulary field is not resolved, only the id is displayed in the Summary tab (see unresolvedVocabSummary.png)
- observe the vocabulary field is resolved in the Edit tab (see resolvedVocabEdit.png)