EspoCRM

Enhancements:

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

Improvements:

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

Changes:

• Import: Field validation https://github.com/espocrm/espocrm/issues/2373
• Field parameter readOnly to be taken into account server-side https://github.com/espocrm/espocrm/issues/2375

Security:

• Security headers for client page https://github.com/espocrm/espocrm/issues/2402
• More strict server-side field validation https://github.com/espocrm/espocrm/issues/2374

Front-end:

• Ability to define custom dropdown actions for quick view modal in metadata https://github.com/espocrm/espocrm/issues/2353

All issues: https://github.com/espocrm/espocrm/milestone/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.