-
-
-
- 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
-
Secure file organization
The following page is about securely organizing your files.
- Use .pm as a rule, .vm as an exception
Make every Velocity file a .pm file. Only if a file should be able to be opened from anywhere, make it a .vm file. Always use .pm files for:
1. Helpers, like calculations
2. Templates
3. Headers and footers of classes and sections
4. Files that are only parsed
Only use .vm's for pages that can be called directly from outside of the application. For Ajax calls, use .am files. - Be explicit about permissions when using .vm files
When using .vm files, think about which usergroups should be able to use the file. To do this, make use of the file permission system. Older .vm files may still have permission logic in their first few lines. If a .vm file has no file permissions set, and no permission logic in the first few lines of the file, this needs attention! - Think about the application of permissions when using scripts
Realise that in .vm files permissions are not automatically applied. Any Velocity method that returns data, has access to ALL data. Permissions have to be applied explicitly. When using queries for instance, this can be done by calling setApplyReadPermission(true). - Never get test data in a file used on production data
To test a file, the best practice is to use a separate file. We have seen examples of calculations in .vm files where the record for the calculation could be determined by an id from the request. Although this isn't directly harmful. If this file makes it's way to production it poses a security threat as anyone can now run this calculation with any record by supplying their own record id to the request.
Another unsafe testing method is providing a hard coded testing id if no user is present, eg. id = 6. If this file makes it to a production environment, then the person record with id = 6 may not be a test user!