Rendering of Search Scopes in Search Recipe
When rendering the results in the Search Results page, CentraSite considers the search scopes that are currently defined in the Search Recipe in a hierarchical order. This rendering behavior can be best understood with the following scenarios:
The predefined scope
Everything overrides all other predefined and custom scopes in the Search Recipe. If you have, for example, the default scope
Assets already defined in the Recipe, and you add the predefined scope
Everything to the Recipe,
CentraSite automatically removes the default scope
Assets from the Recipe and returns all the registry objects, for example, organizations, users, and assets, that match with the scope
Everything. On the other hand, if you have, for example, the predefined scope
Everything already defined in the Recipe,
CentraSite will not allow you to add any other predefined scope and custom scope to the Recipe.
In the same way, if you have, for example, the predefined scope
Service already defined in the Recipe, and you add the predefined scope
Assets to the Recipe,
CentraSite automatically removes the existing scope
Service from the Recipe and returns all the assets that match with the scope
Assets. On the other hand, if you have the predefined scope
Assets already defined in the Recipe,
CentraSite will not allow you to add any other predefined scope, except for
Everything, which takes the priority, and custom scope to the recipe.
If at any time you revert back to the Search Results page, the results get rendered based on the search scopes that are available in the Search Recipe.