Monday, January 13, 2025
3 changes · 18.0
Enhancements to existing features
Searching email templates by category has been optimized so it no longer slows down when there are many templates. This improves responsiveness for databases with large numbers of email templates, reducing searches from several seconds to near-instant in benchmark testing.
Original PR description
When we have thousands of mail.templates, the search was taking seconds. The previous code was searching on every template, computing the `template_category` and then filtering those records to make the domain. Benchmarks done _au-doigt-mouillé_ : with 60k templates, the test was running in 4 seconds and is now running in 0.02 on a reliable test server (aka “my laptop”)
Automation rules now keep their existing filters when trigger fields are edited, reducing the risk of unexpected automation behavior. When a filter is changed, the related trigger fields are updated automatically, making automation setup more reliable for save and UI-change triggers.
Original PR description
Backport of 105e313775a6853d8dcd8ea89af7f710f4e1e2a1 **Purpose** Currently, editing any trigger field of an automation erases the domain, which may lead to unexpected behavior as some "light" automations (i.e. in CRM) hide their domains (for user friendliness). After this commit, any change in the trigger fields won't erase the domain. Also, any change in the domain will update the trigger fields. This is true for: `On save` and `On UI change` triggers. opw-4367901
Documents users can now create server actions and automation rules directly from the cog menu, making it faster to configure document workflows for selected folders. Menu labels and controls were also clarified so business users can more easily find and manage available actions.
Original PR description
Server Actions =========== - Rename Action menu to "Actions on select" - Add an Actions creation in Actions menu (cog wheel) - Redirect to Server Actions Automations ========== - Add an Automations menu in Documents Cog Menu, below Actions on select - If base_automations is not installed -> propose to upgrade to Studio - If base_automations is installed -> redirect to Automations rules lighten as in CRM In the context of providing a partially pre-filled automation rule form for the target folder, we change the `folder_id` label from "Parent folder" to "Folder". task-4334749