-
-
-
- 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)
-
- 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
-
- 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
-
-
- 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
-
- 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
-
General mail settings
The application can send and receive emails.
Sending emails
Some emails are related to user accounts, like verfication of an email adress. Other mails are defined in the blueprint, like email triggers, or in velocity files.
To send proper emails, you have to prepare the application:
- Set a from email address in the blueprint properties (as "Email address") or in the General settings (as "Email address"). The email address in the blueprint properties can contain a velocity script to allow a context sensitive from addresses.
- Create a SPF record in the DNS server for the given email address. The SPF record allows the server of your application to send out emails using the goven email address as 'from'. Check: www.kitterman.com/spf/validate.html. Get a test email account at https://www.mail-tester.com/ to check if an email send from this server is allowed
- In some case it is not possible to set the SPF-record for the from address, i.e. when you do not have access to the DNS. In case you have an other email address with access to the DNS, but you do not want to use that email adress as from address, you can set the other email address as 'On behalf email address' in the General settings.
Read more about how to improve your mailings.
Receiving emails
Contact CrossmarX when you want your application to receive emails.