These menus were visible to all employees, but the reports use
hr.salary.rule.category that is only available to HR Officers/Managers.
As these reports are not meant to be available for employees anyway, we
hide them.
(this bug has been spotted by the nightly crawler that clicks on every
menu as demo user)
The variable `date` is compared to the field `name` in the selection
query. `name` is filled in with datetime data. In particular, in the
module currency_rate_live, datetime.now() is used in the name. It is
necessary to make an appropriate comparison to make sure we select the
updated rate right away.
This controller is mainly used by im_livechat which don't send html message. It is more secure to force it in plain text. If anonoymous user write html tags, it will be escaped and sanitize.
Posting message is done in 'html' since mention add html tag in body. Clickable url is done server to allow link in mail and chat message. Plaintext are transform into html, and html message are simply parsed to transform url into clickable link.
When adding a line to a confirmed sale order,
the procurements are automatically created, with
this product.
Therefore, the product of the line should no longer be changed,
as otherwise, the product on the procurement would no longer
be the same product than on the sale order line.
To be able to change the product of a line on a
confirmed sale order, you must therefore first
delete all procurements.
When using the editable list on the sale order form,
it was not possible to add a new line on a confirmed sale order,
while it should
(when `Allow to edit sales order` is chosen in the Sales settings).
The reason was that the fields `tax_id` and `product_id` were
set as readonly when the SO state was not draft.
When using the popup/dialog view, it worked by luck, because
the line `state`, which is a stored related field to the sale order state,
was not correctly computed, and was seen as `draft`, while it should
actually be `sale`, for a confirmed sale order.
We change the readonly condition of these fields,
which is now based on the fact wether or not
the line is already invoiced or not, which makes
more sense.
opw-651573
- Add recipients as followers, and automatically refresh the follower's list
(before this rev., one needed to reload the record to see the followes' list
updated)
- Don't display needactions on chatter's messages
- Simplify buttons of suggested partner's dialog, as it should only offer two
possibilities: Save or Cancel
- Replace unnecessary t-raw's by t-esc's
When looking for a so_line linked to the task, the sale_service module accidentaly removed the already referenced so_line.
The desired behaviour is:
1/ Check if task is linked to so_line, if yes reference it
2/ If not, then let the dict as it was before, do not put False if there already was a value (for example something that sale_timesheet might have found)
- Extract sub-templates for client action's sidebar to ease the livechat
integration
- Handle livechat's channel_type and messages in chat manager
- Make scrollBottom work in the frontend
Introduce test rules in demo data instead of during the test, because their
creation/update restarts the registry. Moreover, the registry is only patched
after all installations. So the test must be run at post-install phase.
On initialisation summernote call update method with oStyle.range is undefined.
The range can be undefined because the update is call before any selection and attach method from summernote call the update without range.
The method summernote_table_update try to use the range and raise an exception.
fix: Check if oStyle.range exits.
Issue: when the user create a pricelist item, the function fields (name, price) are updated only on save (the form view) and not on change.
In the pricelist form view, the 'item_ids' one2many receive empty value from the modal (name, price).
Fix: update 'name' and 'price' field to the new v8 api.
1) Domain of account.analytic.line
When an expense is created with a cost of zero, the quantity delivered
on the SO line is not updated.
2) Delivered quantity updateable if manual tracking
The delivered quantity cannot be manually modified if it is calculated.
Therefore, we need to restrict the condition to a manual tracking.
3) Upselling conditions
Upselling is possible only for a product invoiced on ordered quantities
for which we delivered more than expected.
Richard deMeester