In Qwix the user-facing administration functions are implemented and managed by the Qwix Portal or in some cases the legacy Desktop application*
What views consist of and the features they provide is outlined below. A full list of Standard Views is also listed below for reference
*soon to be discontinued
Below is a brief overview of the parts that every view consists of. All views may not have every part, but they will at least have one of the fundamental parts.
A View has two primary functions:
When creating views in the Qwix framework there are some rules that need to be adhered to. The reason for this is because of the way the framework needs to use the data, particularly the sql in interfacing with the backend API. The rules are as follows.
Please note: If you have a data definition that can not follow all the rules. The solution is to add this as a SQL view first. Then select from this SQL view for you data definition in the Qwix view. Please use the naming convention of qx_Desktop_Name_of_your_view.
Grids are the heart of the Qwix system from an administration perspective. It allows users to view data, in a grid/table based format, with advanced features. in it's most simple form a grid has a number of columns and rows. Below is an example of a basic grid in Qwix:
In this example, the User view is presented. A set of columns, presenting the available information for each user, and list of rows that list each user.
The Control bar allows you to:
The Paging bar allow you to:
The Column header row shows the Captions of all the columns over and above showing the captions of columns it allows the user to perform the following functions:
Clicking this button will toggle the grid mode between normal and compact mode where normal mode is the default state. The default state is configurable in the Settings menu.
Clicking on the filter button will enable or disable the filter mode. Hiding the filter bar will also disable the filter that is currently applied. When the Filter mode is enabled, an additional row will appear below the column header row as shown below. If filters for a view already exist, they will be applied when the view loads and the filter bar will be shown automatically.
The Filters for grids can be quite useful, and have the following general features:
Given the following example row values:
TESTING
WIP
OPEN
The most basic filter is to enter a simple text expression. Entering “tes”, will return the TESTING row, since the grid automatically applies the LIKE wildcard operator (%) by default. So that the filter string looks like this: “tes%”
Additional LIKE syntax can be added as you see fit. Examples:
Logic operators can also be used within filter strings:
Finally, you can use the | (OR) operator for composite filters:
Clicking on the Edit Columns button will present the user with a dialogue where you may make columns visible or invisible in the grid. Simply check the checkbox next to the columns you want visible, and uncheck the columns you want to hide. Alternatively, check/uncheck the ‘Check All’ checkbox to update or reset all columns. Click on the Save button to apply changes. Column visibility remains persistent. A notification in the top-right will inform you of any errors such as saving without making a change or saving without at least one column left as checked.
At the top of each view, a list of TABS will appear. They will list the actions, reports and dashboards related to the view
The Actions TAB presents a dropdown menu when clicked. Clicking it again will hide the menu
Initially, only the groups within the action menu will be displayed. Clicking on any of the groups will expand the actions within and at the same time collapse any other expanded group.
Actions will only be enabled under the following conditions:
Actions that require records to be selected may be executed with one or more grid rows selected. The behaviour is slightly different, but intuitive when selecting multiple rows.
Clicking on an action will then execute one of the following types of actions:
A Simple action that will confirm that you want to execute the action to prevent accidental execution. After execution, it may present additional feedback in the form of a message dialog.
This action will first present the user with a list of values that need to be entered or selected, before executing the action. Validation of the values will be performed, and additional feedback or error messages will be displayed.
If the provided parameters were accepted and the action executed successfully the dialog will be closed and an additional message box may be displayed for feedback. If the action cannot be completed successfully, or the provided parameters are inadequate or incorrect, a dialogue box with the error message will be displayed. After closing the dialogue box, the parameters dialogue will remain, giving the user the opportunity to correct the parameters or cancel the execution of the action by closing the parameters dialogue.
If the Action is dependent on rows being selected, the following options may apply:
The Grid Action type functions the exact same way as a Parameter Action, but instead, you may be provided multiple rows of input, or edit multiple selected rows simultaneously.
When such an action is NOT an EDIT-type action, you can do the following:
When the action is EDIT-type action, each selected row will create an individual pre-populated row in the dialogue. Allowing you to “edit” multiple rows simultaneously.
Upon clicking the SAVE button, each row will be actioned individually. The result of each row is displayed to the right of the row.
Any unsuccessful rows will be indicated, and the parameters may be adjusted. Clicking on the Save button again will ONLY post the unsuccessful rows again.
Just as with the Actions menu, the reports are grouped, expanding a group will present the available reports
Reports may also be configured to require a selected row and will execute the report and pass the KEY of the selected row to the report engine.
Reports will open in a new browser tab.
See Reports for more information
Dashboards function almost exactly the same as reports within the context of a view.
Dashboards will open in a new browser tab.
See Dashboards for more information