-
Type: User story
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 6.0
-
Component/s: Content Views, Query & PageProvider
-
Epic Link:
-
Tags:
-
Impact type:API change
-
Upgrade notes:
-
Sprint:Sprint Vlad 5.9.5-4
-
Story Points:5
Currently the system supports only ordered parameters :
- parameters are expressed with a ? in the NXQL query (or fixed part of the PageProvider)
- values passed as an ordered list of String from the client side
- values expansion is limited to $currentUser and $currentRepository
To make this more useful, we should :
- allow to pass a JSON Object to address the Named Parameters (WhereClause)
- this will match the SearchDocumentModel
- we can use the Properties structure to send a JSON object add parsing for Date and Number parameters
- depends on
-
NXP-16093 Finish named parameters integration
- Resolved
-
NXP-15179 Move up search document type definition in page provider descriptor
- Resolved
- is required by
-
NXP-16063 Error serializing aggregates to JSON
- Resolved
-
NXP-14976 Allow using named fields in widgets
- Resolved
-
NXP-16073 Allow sending the search document model when using Query APIs
- Resolved
-
NXP-14879 Update PageProvider interface and service so as to include Aggregates support
- Resolved
-
NXP-14697 Create query endpoint
- Resolved