-
-
-
-
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
-
Application Migration for application owners with own server. (CrossmarX External)
Definitions
Application <APPLICATION> is to be migrated at <PLANNED DATE AND TIME>. This time is called DDAY
- The new server: <NEW_SERVER_DOMAIN_NAME>
- The new IP address is: <NEW_IP>
- The moved domains: <LIST OF DOMAIN NAMES>
OWNER: the owner of the application and server and domains.
CX: CrossmarX
Preparations
P1) OWNER and CX: Set a date and time for the migration DDAY
P2) OWNER: Add new IP to SPF record(s) if any
P3) OWNER: Two days before DDAY set DNS TTL cache to 300 seconds (or as low as possible if 300 seconds is not allowed) for all domains concerned.
P4) OWNER: Three days before DDAY copy databases (use mysqldump), private blobs, public blobs and application files to the new server.
P5) OWNER: disable mail functionalitity and jobs. To prevent mailing and ftp processes during the test phase.
Add the following lines to $ENGINE_HOME/etc/environment.properties
allow.batches.<APPLICATION>=false
email.override.address.<APPLICATION>=<YOUR_EMAIL_ADDRESS>
email.override.<APPLICATION>=true
P6) OWNER: Reload the environment properties (see /engine/system menu item environment properties) and perform beta tests
DDAY
D1) CX: Disable application on old server in the studio. OWNER: Disable application or shutdown engine on old server
D2) Perform DNS change(s)
D3) Migrate databases to new server. (use mysqldump)
D4) After database restore on new server. Unset the changes in $ENGINE_HOME/etc/environment.properties and
reload the environment properties (see /engine/system menu item environment properties)
D5) Add domain names in the domain names list of the applications (blueprint editor)