Monday, May 8, 2023
5 changes
Enhancements to existing features
Odoo Sign now automatically suggests the signing order based on role sequence numbers, reducing manual setup when preparing signature requests. Users can still adjust the order manually when the suggested sequence does not match the business process.
Original PR description
In sign it is possible to define an order for signature, however the current process is really manual and there are some things that could be automated to improve the usage of this feature. This commit adds a sequence number to the sign.item.role model, which will be used for automatically defining the order of signature. In case the order is not good, it's also possible to change it manually. task-3270748
Appraisal surveys now use the standard survey type system instead of a separate appraisal marker. This simplifies survey setup and keeps appraisal-specific surveys managed from the appraisal area, reducing the risk of users changing them from the general survey app.
Original PR description
[IMP] hr_appraisal_survey: simplify survey form In order to ease the creation of survey, we continue the simplification of the option form in survey started in odoo/odoo#115297. With the introduction…
[IMP] hr_appraisal_survey: simplify survey form In order to ease the creation of survey, we continue the simplification of the option form in survey started in odoo/odoo#115297. With the introduction of the field survey_type in survey_survey, the field is_appraisal is now redundant. The use of is_appraisal field has been replaced by the use of survey_type (== 'appraisal'). Although the survey_type appraisal exists, it isn't visible to the user because that survey type can only be created and viewed in hr_appraisal module. Indeed, we want to avoid that the user creates/modifies/deletes appraisal survey in the survey module. So we don't display the survey type selection in hr_appraisal module and in the survey module, the selection is displayed without the appraisal option. Technical notes: - The appraisal survey type is added in the survey type selection field in hr_appraisal_survey. To avoid displaying it in the survey module, we hide it in css (because the radio widget doesn't support hiding an option). - Although the replacement of the 'is_appraisal' field by the appraisal survey type could greatly simplify the uninstall_hook, we have decided to keep all the cleaning. Indeed, now that we don't add a new field to distinguish the appraisal survey the domain remains correct after uninstalling hr_appraisal_survey even if then the survey_type option 'appraisal' doesn't exist anymore. Note that as one action domain is dependant of the added field survey_id (survey_question_answer), even if we wanted, we couldn't get rid of it completly. Task-3061869
Financial reports can now use default values for editable fields and accept text or yes/no inputs, not only numbers. This helps businesses prefill report data more accurately when accounting or tax lock dates are changed, reducing repeated manual entry and unnecessary recalculation.
Original PR description
This commit adds support for several things: - Editable expressions can now accept strings and boolean values. - Editable expressions can have default values. To define a default value for an…
This commit adds support for several things: - Editable expressions can now accept strings and boolean values. - Editable expressions can have default values. To define a default value for an expression, another expression needs to be added with a `_default_` prefix. For example, if the expression label is `balance`, its default expression will be called `_default_balance`. Expressions prefixed with `_default_` are not evaluated when opening the report; we just skip them. This way, we don't recompute them all the time for no reason. The `account.report.external.value` is evaluated based on the lock_date + 1 day. - `tax_lock_date` for the tax report - `fiscalyear_lock_date` for all other reports Hence, the default values are going to be evaluated when a user makes changes through the `account.change.lock.date` wizard. If the lock date is not set, the default values are not going to be evaluated at all. Options: - date_from is either the previous lock date or the beginning of the fiscal year - date_to is the lock date + 1 day task-3098957
Project task planning now shows an empty row for the current user when the Gantt schedule is otherwise empty. This makes it easier to create or schedule assigned tasks without having to start from only an unassigned tasks row, while avoiding the clutter and performance cost of showing every user.
Original PR description
In Project, ease the creation/scheduling of tasks when the Gantt view is empty. Indeed, by default, only the 'unassigned tasks' line is visible, which feels unnatural to use when tasks are already assigned to some users, and you simply want to plan them. As we can't display all users without distinction for performance (and navigation) issues, we are displaying an empty line for the current user instead. task-3254242
Enterprise apps were updated to stay compatible with recent advanced search improvements in Odoo. This keeps spreadsheet and Studio search-related tools working correctly, including better handling of dynamic search expressions.
Original PR description
We adapt the enterprise code to the changes brought by the related community PR: https://github.com/odoo/odoo/pull/112326 Task Id: 3063564