Friday, September 24, 2021
4 changes · master
Enhancements to existing features
Website visitors can now view all events in one place, making it easier to find events even when they are unsure whether an event is upcoming or already finished. The Contact Us form wording was also made more direct and engaging to encourage customer interaction.
Original PR description
- added the 'All events' filter in the website event page. - improved contact us form Task: https://www.odoo.com/web#id=2581308&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720
CRM forecast filters can now work directly from the filter settings instead of relying on extra action-level setup. This makes forecast views easier to configure and maintain while keeping the visible forecasting behavior consistent for users.
Original PR description
The forecast filter is a feature that allows to generate a date domain from values extracted from the current groupby fields. The purpose of this change is twofold: - remove the dependency on the…
The forecast filter is a feature that allows to generate a date domain from
values extracted from the current groupby fields.
The purpose of this change is twofold:
- remove the dependency on the context of the action:
- the context key forecast_field should be instead directly defined in the
context of the filter and will be sufficient in itself for the filter to
work as intended.
- we no longer require an additional context key (forecast_filter)
- remove the fields added to the state of the model_extension (old version)
and the search_model (new version)
- the only useful information was the forecastStart, and it should be
computed each time the modified domain is requested, therefore it is
not really correct to store it as a state property (no need to
import/export, ...).
REM: the context key forecast_field may still be required in the action context
as it is used by the fillTemporalService and the forecast views, but is not
required there if only the filter feature is needed.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prMarketing automation screens are clearer and easier to use, with key fields and SMS counts visible without extra steps. Archived campaigns, empty mailing actions, test participants, and participant selection wording are now handled more intuitively to reduce confusion for users.
Original PR description
- Always displays 'Unicity' field instead of debug mode - Displays SMS count in automation campaign tree view - Makes mailing actions invisible if it have zero (mail/sms) count - Hides the action buttons in campaign if campaign it archived - Test mode is now indicated with ribbon in participant form view - Improves wording while picking / creating participant in the wizard Task- https://www.odoo.com/web#id=2581308&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720
Resolved issues and error corrections
Fixed an issue where refreshing after choosing to process an operation alone could open a different operation or no operation. This keeps warehouse users on the right transfer and avoids confusion during barcode processing.
Original PR description
When refresh the operation after the wizard asked the user if they wants to group it with other operations into a new batch, the application will refresh on an another operation, or even on no operation at all. How to reproduce: - Open an operation who can be grouped into a new batch (WH/IN/00003 or WH/IN/00004 from the demo data for example); - When the wizard asks you if you want to create a new batch, choose to proceed the transfer alone; - Refresh the page (F5) and then, it opens an another operations instead (or even no operaton at all if you repeat this too much). task-2466028