-
-
-
-
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
-
Changing snippets
Snippets are small pieces of velocity code. They are used by the engine to output HTML to the screen. All components you see, in a default application screen, are snippets that are rendered by the engine.
Methods are a convenient way to access certain data or functionality in snippets. For instance the $text snippet has the method $text.getContent(). This gets the content for the $text snippet.
The snippets are part of the user interface. In a new user interface a snippet can be (slightly) different than in the previous user interface. This is important if you are using custom snippets, because you have to check them when upgrading to a higher user interface.
List of all available snippets
In case you need your own snippets, you have to define the snippet in the resource files in the directory snippets. Next you have to define when this snippet has to be applied. Do this in the blueprint properties, on the tab "Custom Snippets".
A simple example
Here's a simple example of the use of a custom snippet. The standard snippet used by the application engine is the boolean.vm.This example adds an image to every yes/no datatype field, in the blue ocean blueprint this is the "Subscribed to newsletter" field from the "person" class. The image has to be added to the resource files and by clicking the checkbox the image shows and not shows.
Here is the code:
#set($name = $widget.getDOMName())
<div class="form-control-static cx_checkbox">
#if($widget.autoSubmit())
#set($class = 'cx_autosubmit')
#end
#set($checked = $widget.getCheckedString())
#if($widget.isDisabled())
#set($disabled = 'disabled')
#end
<input class="$!class" id="$name" name="$name" type="checkbox" value="true" $!checked $!disabled>
<img src='/custom_snippet_pic.jpg' />
</div>
This css is used to show the image when the checkbox is checked
.cx_checkbox img {
display: none;
}
.cx_checkbox input:checked {
float: left;
}
.cx_checkbox input:checked + img {
display: block;
height: 30px;
}
To use the snippet go to "blueprint -> properties -> custom snippets".