-
-
-
-
Building blocks of the data model
-
Basic concepts
-
Classes
-
Key fields
-
Local lookup lists
-
Fields and data types
-
Defining the columns of a table
-
Relations between classes
-
Global lookup lists
-
Filters
-
Universal connected classes
-
Deleting foreign records
-
Class inheritance
-
Storage of personal data on test and develop environment (scrambling)
-
Building blocks of the data model
-
-
User interface versions
-
Building blocks for user interface design
-
Adding styles with a css
-
Surrounding page
-
Changing snippets
-
Creating a custom login page (pre 3.4)
-
Creating a custom login page
-
Using velocity templates within the blueprint
-
Create your own web pages
-
HTML delivery requirements
-
How to customize system mails
-
User interface versions
-
-
Resource files
-
Velocity - How does it work?
-
Quick Velocity Tutorial
-
Debugging velocity scripts
-
Velocity Command Reference
-
Script Editor Tutorial
-
Using velocity for calculations
-
Using predefined forms in a html design
-
Velocity forms
-
Data field identifiers
-
Macros and methods
-
Velocity library
-
Velocity: using the #macro command
-
velocity and xml
-
Using AJAX in your velocity scripts
-
Resource files
-
-
-
Argon2 password conversion
-
Introduction to security
-
Secure development
-
Security certification
-
Security Exam
-
Field properties concerning security
-
Developing user groups securely
-
Security considerations for user interface
-
Secure file organization
-
Securely using the request
-
Cross Site Scripting (XSS)
-
Other options concerning secure development
-
Security analysis
-
Secure deployment
-
Secure application management
-
Scrambling of testdata
-
Anonymization of personal data
-
Using robots.txt
-
Permission settings
-
Security measures
-
Data encryption
-
Argon2 password conversion
-
-
Search Engine Optimization
-
OTP
-
User Interface migration guide
-
User account management
-
Instructies voor implementatie van visueel editen van nieuwsbrieven
-
Login as another user
-
Support
-
More information about moving to User Interface Version 4.0
-
Standaard page layout
-
Sections moved to layout
-
Aanpassingen in release 2024-7
-
Media library
-
Aanpassingen in release 2024-10
-
Analytics and Matomo
-
Registration forms
-
How to change names of classes and fields?
-
Responsible Disclosure Policy
-
How to upload a blob in Velocity?
-
Aanpassingen in release 2024-2
-
Instances
-
Componenten in onze technologie
-
Google Analytics
-
Street and City helper (postcodecheck)
-
Responsible disclosure-beleid
-
Postcode check service (straat en huisnummer) kosten
-
Expressions
-
Regular Expression Reference
-
Tree layout
Some classes have an hierarchical structure. This means that an object of a class might have a parent and might have children. The file system on your computer is one of the best examples. A directory might have a parent directory and one or more sub directories. In business applications a hierarchical structure is most frequently used for classifications. Like 'type of organization' or 'type of object'.
Follow the next steps to define a hierarchical structure in a class:
- create a class person manager with at least a decimal sortfield and a foreign key field Manager to itself
- go to the class properties:
- set first name and last name as label fields
- select "display as tree"
- set sortfield sort direction "asc" at columns in table
- go to the application and add child records of Person manager, it's important to set the sort field
- reload Person manager to test the sort field
