Saltcorn 0.4.4 contains these enhancements:

In join fields, you can now choose the fieldview based on the type of the joined field. For files, you can choose a file view, such as showing images or download links. In the builder, joined fields now have previews just like fields.

You can now nominate a view of the users table to be the user settings view, which the user can access on their own user settings menu option to adjust user fields (e.g. username, avatar image)

Moment.js is available in expressions, which greatly facilitates date calculations

You can now rename tables (in the table view, in the drop down on the table data card).

Custom HTTP headers can be set  in the user and security settings. For instance, if you would like your site to opt out of FLoC, add this header: Permissions-Policy: interest-cohort=()

Miscellaneous new builder options:

• border direction, for instance to have only a border at the top of the container
• card disable padding. Use this with a container inside the card to set the card background colour or image.
• viewlink text style. Can be used to make a link to another view appear as a header
• filter presets. Toggle filters on fields that have presets can now assume the value of the preset. Precepts are field values that are calculated from the request context and used in forms to auto fill field values with the current time or user ID. In the context of Toggle filters (that is, views of the filter view template with toggle element in them) this is probably most useful for the user ID of the logged-in user, so a user can switch to seeing their own items in a list.

DigitalOcean image: the update DigitalOcean marketplace image marked 0.4.4 will be available shortly and will contain these enhancements:

• unattended upgrades. Underlying system software will be updated as available. Kernel has been updated, the system will automatically reboot resulting in a few seconds unavailability.
• The PostgreSQL extension for UUID datatypes has been enabled

Facility for obtaining LetsEncrypt certificates for https traffic encryption has been improved by:

• Certificates for tenants now be obtained whether the tenants are on a sub domain or on another domain declared in the tenant’s Base URL setting. The principal limitation is that if you add another tenant, to obtain certificates for that tenant you should disable let's encrypt and re-enable it when the new tenant has been created.
• Support for HSTS domains: the workflow for enabling lets encrypt certificates did not work for top level domain is that in force HTTPS traffic with HSTS. These domains are now recognised and can be enabled through their IP address.
• www is no longer treated as a special subdomain. If you would like to serve your site through the www subdomain, you should use your DNS settings to enable this.