-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 22.1
-
Fix Version/s: 3.12.0
-
Component/s: Content Views, Ergonomy / UX / UI
-
Epic Link:
-
Tags:
-
Backlog priority:500
-
Sprint:NOS 11.1.6 - 2019-04 1, NOS 11.1.8 - 2019-05 01
-
Story Points:3
This info is not available in studio making mandatory to use a generic widget and configuring it to use that field (using JSF UI, or an element in Web UI).
AC
- ancestorId is available in the registries as part of the system schema for general configuration
- When configuring a predicate, only = and <> operators are available if technically possible, otherwise validation error with following message:
ancestorId field used in [predicate / aggregate name] can only accept the = and <> operators.
- When configuring an aggregate, field is available for terms / significant terms
- In automation chains, benefits from autocomplete, etc
- When configuring a predicate, only = and <> operators are available if technically possible, otherwise validation error with following message:
- causes
-
NXS-5338 Fix ecm:ancestorId preventing designer from loading
- Resolved
-
NXS-5339 Don't expose ecm:ancestorId in aggregates
- Resolved
- depends on
-
NXS-2944 Add missing system schema in "Widgets by property" in search
- Open
-
NXP-15078 NXQL query by ancestor id
- Resolved
- is duplicated by
-
NXS-5199 ecm:ancestorId is not available in pageprovider predicate configuration
- Resolved