EspoCRM v10.0 released

[yuri]

A major release bringing new features and improvements.

Enhancements:

• Multiple pipelines #3623
• Cascading links #3594
• Cascade removal and restore #3603
• Record locking #3592
• Categories for custom entity types #3587

Improvements:

• Notification grouping #3606
• Collapsible popup notifications #3643
• Notification sound #3661
• Viewing last viewed record in one click #3608
• Transactional save #3596
• Navbar: URL tab opening in new browser tab #3583
• OIDC: Support PKCE #3589
• URL field: Protocol Required parameter #3600
• Configurable order in record dashlets #3625
• Formula: More strict type checking in entity and record functions #3615
• Formula: record\find methods applying order through select framework #3617
• Formula: Validation exception function #3626
• Config get/set CLI commands #3666
• Email account reset #3667
• Image field: Capture parameter #3672
• Config parameters enabling upgrade and extension upload via admin UI #3676

Framework improvements:

• TypeScript support #3648
• Late after save/remove hooks #3597
• PDF: Ability to add fonts #3578

Changes:

• Restrict access to disabled links #3585
• Move allowInternalNotes parameter from clientDefs to streamDefs #3640

Compatiblity:

• SelectManager support removed #3628
• Backend deprecations removal #3630
• Frontend deprecations removal #3631
• Record service changes #3627
• ORM: Entity::get does not support deprecated link access anymore #3629
• Change in AuthToken interface #3671
• Drop jobs with serviceName support #3673
• Drop support of service class implementations in popup notifications #3675
• Modal view deprecations removal #3659
• Removed deprecated Espo.ui, Espo.utils #3652

Other:

• Collaborators enabled for Tasks and Cases by default #3584

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

[yuri]

If you have issues with upgrade, please create a separate topic in the Installation and Upgrade Help section.

If you have manual customizations, check the release notes' compatibility issues before upgrading.

[yuri]

Note that the Docker setup requires a migration step: https://docs.espocrm.com/administrat...-to-espocrm-10

[murugappan]

Thank you for wonderful new features and improvements, yuri . Congratulations for the innovative changes. These are my views/suggestion:

(1) The section titles in the release notes would be more clearer if "Enhancements" is renamed "New Features" as enhancements is the same improvements. By defining it as Enhancements i tend to look for the original feature in previous releases from which the enhancement was made.
(2) Under "Improvements", i assume that these are changes made to some feature in the old releases that have been modified to add additional functionalities. Hence these would be "Enhancement". If my assumptions are correct, it would be good to state which release the feature was originally added. This will help us to retrace the enhancement path.
(3) It would be great also if a link is included in the release notes (above) to the Espocrm User Guide where full details of the feature is explained. Why this helps is that we may not have used the feature before but as business needs change and the need to use the feature surfaces we would immediately get to the documentation. This avoids us wading through through the extensive documentation provided for Espocrm. You have one example of this in you comments in the above post on Docker. Please note that Espocrm is most extensively documented software we have seen not forgetting to mention the great support from Espocrm developers and users.
(4) Would be good to see an additional section "Fixes" which would define all the corrections made to existing features which my have broken parts. Why this would help is that I tend to ignore the fixes most of the time unless the break prevented us from using the feature.

The above views are some of the things we think would be helpful. On the hand, it may result in too much effort overload which we understand.

[yuri]

Thank you for using the product.

We've been using the Enhancements/Improvements terms since the beginning, which we adopted from the GitHub's default tag names back then. Enhancements are meant for new big things (enhancement of the product), Improvements are for smaller things, usually extending existing things. But the line between them is often blurry. Things that categorized as Improvements are real 'features'.

Maybe we could use some different naming, but I'd rather avoid renaming 'Enhancement' to 'Features'. Maybe there are some other alternatives we could I adopt.

As for documentation link. Often, by the time we make a release, there isn't any documentation more comprehensive than the description in the linked GitHub issue. Usually, we add more detailed documentation later. If the doc article exists, I include the link to it in the issue description.