admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2020-02-13 19:28:26 +00:00
parent 3673bb6b5c
commit 70da4d3393
1 changed files with 20 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
devdocs/specs/core-list-graph-datatable-filtering-sorting-paging.txt
View File

@@ -1,13 +1,30 @@
LIST / GRAPH FILTERING SORTING AND COLUMN RETURNED LIST / GRAPH FILTERING SORTING AND COLUMN RETURNED
DataListView objects are used to filter and sort and determine display order and presence of columns returned by: DATALIST
A dataList is a raw source of data for returning to client
All below is based on a datalist which is a predefined list of fields, rights and some query info for joins etc
There are specific datalists made for picklists, viewing all grid data, KPI shit, whatever is required during development
DataLists are hard coded, only a DataListView can be customized to limit, filter, sort what is returned from a pre-defined DataList
DataLists have roles associated with them, only a user of one of those roles can fetch that list (or see it as an option when doing reporting etc)
DATALISTVIEW
A DataListView is a filtered, sorted, reduced version of a DataList
It can be saved and set to private or public
They can be made on the fly in the Client and don't need to be saved as the Client will always send the datalistview json string with the request
DataListView objects are used to filter and sort and determine display order and presence of columns in order to feed these client needs:
DataTables (was grids in v7) DataTables (was grids in v7)
Reports Reports
Select boxes (on forms like selecting a part or a client) Select boxes PickLists (on forms like selecting a part or a client)
When the DataList route is hit it's used to get all of the above types of data. When the DataList route is hit it's used to get all of the above types of data.
A dataListView JSON string is sent with the request in order to have the server sort/filter/return A dataListView JSON string is sent with the request in order to have the server sort/filter/return
PICKLISTS
Picklists are based on a particular DataList with rights for ANYONE
Client will be hard coded to specifiy the exact dataLIst
Users can select a datalistview for a picklist DataList which will in turn affect how it appears and what's returned
- This is like the PartDisplayFormat feature of v7 only for everything!
Users will get the default hard coded DataListView built into the DataList that is specified for that picklist unless it's changed to an alternative datalistview
There is a default PickList format and a default DataTable format pre-defined and hard coded at the server with each dataList definition object There is a default PickList format and a default DataTable format pre-defined and hard coded at the server with each dataList definition object
If the client isn't using a particular dataListView it MUST send the DataListView json as one of the following: If the client isn't using a particular dataListView it MUST send the DataListView json as one of the following:
@@ -43,7 +60,7 @@ AUTHORIZATION:
We provide a DataList suitable for picklists with ANY role access and anything with sensitive info has it's DataList Required roles to higher level We provide a DataList suitable for picklists with ANY role access and anything with sensitive info has it's DataList Required roles to higher level
This way can still supply for picklists but hide sensitive infor for tables etc This way can still supply for picklists but hide sensitive infor for tables etc
Rights to DataListView follow rights to underlying object and also rights to make a datalistview itself Rights to DataListView follow rights to underlying object and also rights to make a datalistview itself
Filter operators: Filter operators: