Before building applications with DataVoke, some key concepts and definitions need to be understood to help accelerate your ability to generate solutions in the DataVoke Framework.
They are as follows:
- Definition of data records (Record Types) that the application will be utilizing.
- Construction of the user interface (Views) that will facilitate CRUD (create, read, update, delete) functions across the data.
- Creation of Statuses and the creation of Security Groups.
Below is a reference table of DataVoke terms and how they translate to traditional database or spreadsheet terminology.
Select the main "Create a new..." Icon, and select “New Record Type”.
Various attributes of the Record Type may be edited in the Record Type Editor.
Here is a detailed description of attributes that may be configured in the Record Type Editor
In the lower portion of the Record Type Editor there are tabs that allow user to edit additional features of the record type including the addition of Properties to the current record type.
Click the plus sign icon below the properties tab to add a new Property.
Here is a detailed description of attributes that may be configured in the Property Editor.
- Select the main 'Create a new...' Icon and select “New View”.
- Choose a Record Type from the selection window, as all views are based off an existing Record Type.
- Properties from the selected Record Type can be selected for the new view.
When all desired properties have been selected, select either “Finish & Load” or “Finish & Suppress Load”. This will force the view to launch without data loaded and can be disabled in the View Editor.
The View now may be edited by selecting the view editor icon.
Here are additional details on editing views.
Statuses are format overlays that can be applied to entire records or individual properties; either automatically or manually. These format overlays are used to control data appearance and behavior within the DataVoke Framework. (1) A New Status may be created by selecting the main create Icon , and selecting “New Status”. This will (2) launch the Status Editor. Here are additional details on status attributes.
Security Groups are objects that define what the Users that belong to them can and cannot do within the application. Security Groups contain basic permissions, which can be further refined by modifying other objects in the application. . A New Security Group may be created by (1) clicking on the main create Icon , and selecting “New Security Group”. This will (2) launch the Security Group Editor.
These are commonly used terms and references that DataVoke and products built on the DataVoke framework use.
|Database||The logical location that contains all the properties, Record Types, Records, Actin chains, statuses etc. Each DataVoke appspace will have it's own database.|
|Category||Use categories to allow administrators to differentiate permissions for Record Types, Properties and Views. This differentiation is enabled by categorizing two properties within a record type with different permissions assigned.
Every record type must have a category assigned. If one isn't selected the category 'General' will be assigned. Properties in the General category inherit the Record Type security settings. To add a category simply type it in the category list.
|Form View||Forms are an alternate way of interacting with records individually instead of in a grid or sub-grid. A grid and form are both added by default when creating a new view. To only show the form in a view, just remove the grid control by dragging it to the red X.|
|Grid View||Grid views are the primary data management tool in DataVoke. Values are displayed much like in a spreadsheet with sort, filter, edit, add, and delete options based on actions and properties available in the View. Use shift and ctrl keys to select values or records for copying.|
|Action||Similar to Macros, actions are pre-defined set of operations that can be edited to perform any operation a designer would like.|
|Action Chain||One or more actions used in sequence in a DataVoke solution.|
|DV||Abbreviation for the DataVoke framework.|
|Link||Links are connections between records of different Record Types. Links can be created or broken automatically via Properties or manually. Examples include using drop-downs, adding sub-grids, or loading data from a view based on a saved value.|
|Collapsible Group||A subsection of a DataVoke View that may have a grid, form view, or other entities included. It may or may not have a distinct name.|
|Property||Components of a Record Type defining data elements similar to columns in a grid or fields in a database.|
|Record||A collection of data which satisfies the Property requirements of a given Record Type and View configuration.|
|Record Type||Used to define a collection of Properties that belong adhere to the same Property requirements. Similar to a data set in a spreadsheet or a table in a database.|
|Status||Formatting applied as an overlay to grid or form data. It may affect the appearance or access to a specific Property or Record. Used with conditional statuses a designer can customize the user experience.|
|Sub-grid||Any view containing a grid that has been assigned a 'Listener View' in the View Editor and has a View Type 'Related View'. The sub-grid will only show records linked/related to the Parent Grid selection. Users can use sub-grids to view and maintain one-to-many relationships in DataVoke.|
|Editors||Each entity in DataVoke has an Editor available giving the Designer specific options to define and configure each aspect of their solution.|
|User||User objects represent individuals with access to the database. User objects are members of one or more User Groups and may be deactivated.|
|User Group||User Groups are objects that define what the Users are able to access in the configuration. These contain basic permissions which can be further refined by adding to specific views.|
|View||Views contain grids, forms, and buttons designed as a user interface. However, in DataVoke, a designer uses hidden views to perform calculations and update records in the background on a scale not seen by the user.|