This commit is contained in:
2022-02-09 21:56:58 +00:00
parent 899d584106
commit 8745bc84b7

View File

@@ -26,7 +26,7 @@ In most cases reports will display the data in the same sorting order as being v
#### Last report
This menu item shows the name of the last report rendered in this form to save time in selection when the same report is regularly used.
This menu item shows the name of the last report rendered in this form to save time in selection when the same report is used again. This item is set automatically to the last report selected for this form.
#### Extensions
@@ -34,11 +34,13 @@ This menu item shows the name of the last report rendered in this form to save t
#### Search
The search menu item links to the [search form](home-search.md) and automatically causes the search form to only show results for the type of object that was being viewed in the data table before clicking search. For example if you are viewing a Customers data table then clicking on search will automatically select `Customer` as the only type to search for.
The search menu item links to the [search form](home-search.md) and automatically causes the search form to only show results for the type of object that was being viewed in the data table before clicking search.
For example if you are viewing a Customers data table then clicking on search will automatically select `Customer` as the only type to search for.
#### Help
The help menyu item will open a specific help document from the manual related to the form being viewed.
The help menu item will open a specific help page from this manual related to the form being viewed.
#### About AyaNova
@@ -79,7 +81,7 @@ If you want to leave the existing filter and create a new one select `save a cop
If there was no saved filter previously selected then the `save a copy` button will be the only save button displayed.
`All users` - if you want to make your filter available to all users select the `All users` checkbox and save. If this is not selected the filter will be private and not be available to any other user.
`All users` - if you want to make your filter available to all users select the `All users` checkbox and save. If this is not selected the filter will not be available to any other user.
##### Deleting filters
@@ -95,7 +97,7 @@ Here you can select which columns will be included for display in the data table
There is a `reset to default` menu option to reset the selections back to their default locations and visibility.
Some columns do not have an `include` checkbox option because they are the primary identifier for a record and need to be visible to be able to open the record and identify it.
Some columns do not have an `include` checkbox option because they are the primary identifier for a record and need to be visible to be able to identify and open the record.
Column settings are independent of filters.
@@ -117,18 +119,6 @@ Column headers not only display the name of that column but also provide control
Column header names are designed to wrap around in cases where they would not all fit horizontally to ensure as much data as possible can be displayed on all screen sizes.
#### Selecting records
In many data tables records can be selected individually for [reporting](ay-report.md) or [extension](ay-extensions.md) purposes:
![selecting object](img/form-data-table-selecting-records.png)
In most tables the leftmost column consists of checkboxes for selecting individual rows of records. The checkbox selection column header can be used to select or deselect all visible records in the display.
Note that this **selects** _visible_ records only so if you are viewing 10 records at a time but there are 100 only the 10 visible records will be selected. However it **de-selects** _all_ previously selected records regardless of whether they are visible or not.
This is by design to allow a user to make selecting subsets of records easier but clearing all selections easy as well.
#### Sorting columns
Columns are sorted by clicking on their names to toggle their sort mode betwen ascending, descending or unsorted. The column headers will display an arrow indicating the sort direction and a number indicating the order they were selected which affects the data returned:
@@ -141,11 +131,13 @@ This results in a list ordered by customer name first from a to z then by work o
To remove a sort click on the column header name until the sort arrow indicator disappears.
The column position does not affect the sort order only the selection made.
The column position does not affect the sort order.
##### Sorting on Type fields
Type fields can not be sorted in alphabetical order as they do not have a Name stored in the database, only a number. They sort by the underlying internal numerical value that indicates that particular type. This means you will see the column is sorted with identical types grouped together, however the displayed translated text representing these types is not sorted alphabetically. Type fields have square brackets around their translated display names in the column to indicate they are a type rather than a text field.
Type fields can not be sorted in alphabetical order as they do not have a Name stored in the database, only a number. They sort by the underlying internal numerical value that indicates that particular type. This means you will see the column is sorted with identical types grouped together, however the displayed translated text representing these types is not sorted alphabetically.
Type fields have square brackets around their translated display names, for example [ Project ], in the column to indicate they are a type rather than a text field.
#### Filtering columns
@@ -175,9 +167,11 @@ Once you have your filters selected how you like them you can save all the filte
Text filters will be affected by the [filtering is case sensitive](adm-global-settings.md#filtering-is-case-sensitive) global administration setting. The default is for them to _not_ be case sensitive.
##### Filtering dates
##### Filtering dates and time zones
When viewing data in AyaNova that is filtered with one of the relative date filters (for example a filter of "TODAY"), this time zone setting is taken into account in order to ensure that the user sees data appropriate to _their time zone_. This means that two people with browsers in different time zones using a filter of TODAY for a date field may see different list of results from each other.
When viewing data in AyaNova that is filtered with one of the relative date filters (for example a filter of "TODAY"), the User's local time zone setting is taken into account in order to ensure that the user sees data appropriate to _their time zone_.
This means that two people with browsers in different time zones using a filter of TODAY for a date field may see different lists of results from each other.
##### Filtering TAGS
@@ -189,28 +183,41 @@ Tag filter types supported:
###### Equality
Exactly equal compare entire search term array to tag array in db - all terms in search exactly present and no others in db record
e.g. {red,green,blue} will return records with tags {green,red,blue} but _not_ match {red,green,blue,orange}
Will match when exactly the same tags in search are present (in any order) in the record and no other tags.
For example an Equals tag filter with {red,green,blue} will return records with tags {green,red,blue} but _not_ match {red,green,blue,orange}
###### Not equal
The opposite of Equality; specifically exclude rows that exactly match all the search terms
e.g. {red,green,blue} will return records with tags {red,green,blue,orange} but _not_ match {green,red,blue}
For example a Not equal filter with {red,green,blue} will return records with tags {red,green,blue,orange} but _not_ match {green,red,blue}
###### NO value
Will return records with no tags set at all
Will return records with no tags set at all.
###### Has value
Will return records with any tag set
Will return records with any tag set.
###### Contains
Returns records that contain the specified search tags. Records may have other additional tags but that's ok as long as it has the search term ones
e.g. {red,green,blue} will return records with tags {green,red,blue} and also {red,green,blue,orange}
Returns records that contain the specified search tags. Records may have other additional tags but that's ok as long as it has the search term ones.
For example a contains filter for tags {red,green,blue} will return records with tags {green,red,blue} and also {red,green,blue,orange}
###### Not contains
All terms in search query _NOT_ present in db record, doesn't care what else is in db record as long as it's not the search terms (order insensitive)
e.g. {red,green,blue} will not return records with tags {green,red,blue} and also not return {red,green,blue,orange} but would return {red,green,black}
All tags in search query _NOT_ present in db record, doesn't care what else is in db record as long as it's not the search terms (in any order).
For example a Not contains filter for tags {red,green,blue} will not return records with tags {green,red,blue} and also not return {red,green,blue,orange} but would return {red,green,black}
#### Selecting records
In many data tables records can be selected individually for [reporting](ay-report.md) or [extension](ay-extensions.md) purposes:
![selecting object](img/form-data-table-selecting-records.png)
In most tables the leftmost column consists of checkboxes for selecting individual rows of records.
The checkbox selection column header can be used to select or deselect multiple records at once. When selecting, it **selects** only the **currently visible** records but when de-selecting it removes selection from **all** records **visible or not**. This is by design to allow a user to make selecting paged subsets of records easier but clearing all selections easy as well.