Views¶
Introduction¶
Views can be configured on each module page of an app to allow the records to be displayed in different list and report formats. An app's modules pages are those defined from the App Builder Modules page, such as the Profiles, Employees, or Audit Trail pages.
Creating a View¶
On each module page, hover over the View Settings button on the right side of the page to open the module's settings dialog. To pin the dialog so it remains fixed on the screen, click the pin icon.
After a view is created or updated, when the Save button is clicked, a Save Options dialog is displayed in which the view's name is defined and allows the view's sharing configuration to be defined.
In the Sharing section of the dialog, selection can be made for all users and only certain profiles in the system can display the relevant view with the Visible to Specific Profiles selection. Additionally, if the view that is being worked on is to be edited, the Save button under the dialog that opens when the Save button is clicked should be clicked. If it is desired to be saved as new, the Save as New button should be clicked.
Supported View Structures¶
In the system, four different view structures are supported:
- Grid: The interface that presents a view in list format. Records can be displayed as a list or a grouped list.
- Calendar: The interface that presents the records in the module in a calendar view.
- Report: A view type that can offer different views depending on the report type. This view supports three different report types: Summary Report, List, and Single Report.
- Kanban: The interface that presents the records in the module in Kanban view according to a selected dropdown list.
Default Fields in the View Structure¶
Property Name | Supported View Type | Validation | Description |
---|---|---|---|
View Type | — | Required | The list of Grid, Calendar, Report, or Kanban views supported on the system. |
Choose Your Criteria | All | Optional | The part where the records that are wanted to be listed in the view are filtered. Filtering can be done for more than one field according to the value of the fields in the module. And or Or operators can be used between created filters. When the filter is not used, users can view all the records they can access depending on their profile privileges in the relevant module. For example: Approval Status=Approved And Price > $1000 . |
Grouping | Grid | Optional | Used when it is desired to display the records by grouping them on the list screen according to the values of the fields in the module. Grouping is supported for a maximum of two fields selected in a view. |
Columns | Grid, Report | Required | The part where the fields of the created views that are desired to be displayed on the list screen are defined with drag-and-drop. Among the fields in the module, the fields that have been approved for display in the list are listed in the Available Fields section. When the records in this field are transferred to Visible Fields, they can now be displayed on the view list screen. The order of the fields on the list screen is determined by the order in the Visible Fields. If you want, you can edit the field order in this section. |
Date | Calendar | Required when present | The radio box selection area in the Calendar Settings section. In order for the records to be displayed on the relevant calendar day, they must be matched with a date field in the module. For example, the appointment date in the My Appointments view may be suitable for this. |
Date Range | Calendar | Required when present | The radio box selection area in the Calendar Settings section. In order for records to be displayed in a date range on the calendar, they must be matched with a start and end date field in the module. For example, leave start and leave end dates in the My Leaves view. |
Report Type | Report | Required | Three different types are supported in the Report view:
|
Calculation Fields | Report | Optional | Allows sum, average, minimum, and maximum operations to be performed according to fields such as calculable number and decimal in the module. |
Group By | Report | Required | Summary Reports are created by grouping them according to a specific field. For example, gender selection in the Gender Distribution ratio summary report. |
Total Count | Report | Optional | Provides the display of the number of records that meet the grouping and criteria conditions, apart from the operations such as sum, average in the Calculation Fields field of the Summary Report. |
Chart Type | Report | Required | The chart selection field to be displayed in the Summary Report, such as Line Chart, Pie Chart, etc. |
Horizontal Name | Report | Required | The naming of the data on the X-axis of the chart view in the Summary Report. |
Vertical Name | Report | Required | The naming of the data on the Y-axis of the chart view in the Summary Report. |
Grouping | Kanban | Required | A created Kanban view must be grouped by a dropdown field. The dropdown fields in the module are listed in the Grouping field. If there is no dropdown field in the module, Kanban view cannot be created. |