A request for properties, relations, or another subpath of a record type specified by an alias (e.g., /c/{firma}/prilohy/properties.json) no longer ends with a 500 error. As with the list and record views, it now redirects to the main record type name (/c/{firma}/priloha/properties.json).

When the database rejects saving a document in the web interface (for example, a goods receipt for a product for which there is insufficient material according to the bill of materials), the actual reason is now displayed instead of the message "Server error occurred". In this case, the API with the as-gui parameter returns a 400 error with a message instead of a 500 error.