-
-
-
-
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
-
How to configure the REST API?
The REST API provides a standarized way of communicating with other applications.
How to setup?
- Define a REST API for your application
Go to Deployment - REST API Settings. Here you can define a REST API by selecting a REST API version and an Application Branch. Hand over the name of the setting - Define credentials for you REST API user
Go to Deployment - API Credentials. Here you can choose a login name and a password for the user of the REST API. Select a user group. As 'Type' select 'Login from REST API'.
Next, hand over this information to the developer of the application that uses the REST API. The name of the setting should be used as variable VERSION in the API documentation. The credentials (login name and password) are used to login.
Documentation of the REST API
To inform the developer about the content of the REST API, specific documentation is available by using this request: /engine?service=application&cmd=getapidoc.This provides the REST API documentation for the current user.
Each class in the application can be provided with additional documentation. You can do this at the class details on the tab "Other settings", paragraph "Advanced", property "REST API Description". The additional documentation will automatically be included in the REST API documentation.