EspoCRM v7.2.0 released

[murugappan]

@ Yuri, I just parse through the changes. Fantastic job! Only one question: Does this upgrade have any Database restructuring?

[Jakub Grufik]

Great job Yuri!

Thank you.

[yuri]

If anyone has problems with upgrading, please create a separate topic in the corresponding forum category.

Bug reports posted here are moved to the Bug Reports section.

[Kharg]

It's a pleasure helping this project.
Now please, get some well deserved rest!

[yuri]

Thank you for help with finding and fixing bugs.

[Kharg]

Thank you so much, great job!

[yuri]

Release notes on Github: https://github.com/espocrm/espocrm/releases/tag/7.2.0

Enhancements:

• Detail view tabs #2379
• Bottom panel tabs #2384
• Mass Update: Ability to add/remove items #2310
• Import: Errors panel #2372
• Email: Custom fields support #2366
• Separate view for stream note records #2398
• Varchar/Multi-enum/Array fields: Pattern parameter to check a value against #2360
• Command renaming custom entity type #2318

Improvements:

• Shortcut keys #2393
• Theme improvements #2386
• New Glass theme #2392
• Activities panel: Create icon buttons #2399
• Ability to select multiple records on the list view by holding the shift key #2410
• Ability to reset custom sorting #2376
• Layout manager: Ability to hide a label in the list column header #2359
• Layout manager: Ability to specify list column width in pixels #2358
• Stream: Ability to customize Attachments and Post fields #2357
• Server-side validation for uploaded file extensions #2356
• No need for webserver access to node_modules in developer mode #2352
• Uploading files in chunks #2329

Changes:

• Import: Field validation #2373
• Field parameter readOnly to be taken into account server-side #2375

Security:

• Security headers for client page #2402
• More strict server-side field validation #2374

Front-end:

• Ability to define custom dropdown actions for quick view modal in metadata #2353

All issues: https://github.com/espocrm/espocrm/m...e/136?closed=1


Possible compatibility issues

Rest API

Fields that are set as read-only (field parameter, not dynamic logic) will be ignored in POST and PUT requests. Example: When sending a PUT request to update a read-only field, it won't update anymore.

If you are sending an enum value that is not one of the available options, it will cause a validation error.

Example 1: Sending a status 'Success' when available values are 'Planned', 'Held', 'Not Held'.
Example 2: Sending a value null when the empty value is not in the list of available options.
Example 3: Sending a value 'closed won' when the available value is 'Closed Won'.

Omitting an enum field value in a POST request when the field does not have a default value will cause a validation error.