code in resource and project.
This library was once used to perfom resource allocation: scheduling
tasks and things like that. However this feature cannot be accessed
through the interface since a long time.
The feature is now removed from the project code. The library has been
removed. Some code in resource used only in the project code
has also been removed, as well as a test linked to this code.
Bootstrap bind on document to do an element, in some case the bounce effect
on the edit button might cancel the bootstrap action.
e.g in the crm.claim form view, the `group` tag arround a notebook element
break the tab change on the notebook.
opw-646012
note: in 8.0 the issue didn't happen since the tab change was done by
jquery ui which happened before the bounce effect.
- Added reverse for purchase_ids/purchase_line_ids/invoice_ids/invoice_line_ids
- Put first everything in a dictionary by invoice to create and
then create invoice by invoice
Due to commit 1576bc9891,
when name_search() is called on analytic accounts with
multiple path components (e.g. A/B/C), the intermediary
searches are done without the extra domain criterions,
because they should only apply to the leaf.
However because the limit was applied for each step
of the multi-path search, it was quite likely that
no valid results were found in the final filtering,
returning no result at all.
In fact the intermediary steps should not apply the
limit at all, because the leaves we're looking for
may actually be located under parents that are not
found when the limit is applied on each step.
This commits removes the limit (hopefully without
too much of an extra penalty for large databases)
It also introduces a better fallback in case the
multi-path search did not produce any result,
for example if the name of the lead really contains
a '/', and it was not meant to be a path separator.
The next action date (date_action) should be red if in the past, not if the
deadline date is in the past.
Introduced at 9f68a37
Courtesy of @sve-odoo 🎅
When assigning a move to picking upon confirmation,
it took into account the locations/group of the picking,
but it should also check they are of the same picking type.
When clicking on the BOM state button from product.product, and clicking
on create afterward, it must open mrp.bom view with the product and product variant
already set(as with product.template).
opw:645045
features :
- [REM] removed unnecessary action about stages and installer
and the file containing it.
- [REM] hr_recruitment: removed useless doc directory, containing
only crap and useless notes.
- [REM] hr_recruitment: removed unused wizard creating a partner from
an applicant. As we have all the necessary stuff in the form view this
wizard does not seem necessary. As it is not used, let us drop it.
By default the rules are propagate True, so when you cancel a purchase order,
it will cancel all subsequent moves and put the procurement to cancel too.
This means that for an MTO product it will put the original sale order in shipment exception.
If it is not propagate, it will not cancel the subsequent moves and put the procurement in exception.
The advantage of this change, is that when procurements are created from orderpoints and
you cancel the purchase orders, then you don't need to go run/cancel
the procurements in exception anymore (if propagate True)
If the price in a price list line is based on "Supplier Prices on the product form",
the model "product.supplierinfo" and "pricelist.partnerinfo" must be readable by the
public user.
opw:645709
The enterprise web client had to be modified to fix a crash. This crash
does not occur in the community web client, but this commit makes sure
that the semantics of the notification manager is the same as the
enterprise version, to prevent future problems.
The new-api record prefetching algorithm attempts
to load data for all known records from the requested
model (i.e. all IDs present in the environment cache),
regardless of how indirectly/remotely they were
referenced. An indirect parent record may therefore
be prefetched along with its directly browsed children,
possibly crossing company boundaries involuntarily.
This patch implements a fallback mechanism when
the prefetching failed due to what looks like an
ACL restriction.
The implementation of `_read_from_database` handle
ACL directly and set an `AccessError` as cache value
for restricted records.
If a model (like `mail.message`) overwrites `read` to
implements its own ACL checks and raises an `AccessError`
before calling `super()` (which will then call
`_read_from_database`), the cache will be not fill,
leading to an unexpected exception.
If this commit messae looks familiar to you, that's
simply because this is the new-api counterpart of
b7865502e4
The module is useless if the ofxparse python library is not installed.
Declare this dependency in the manifest so the requirement is checked
upon module installation.
- Use less instead of sass
- Use class name of both old and new designs
- Small CSS tweaks to support both designs
- JS compatibility fixes + a little cleanup
- The ctrl-enter shortcut only reconciles balanced entries
Display claim_count and claim_count_out only to salesman and contact creation
group members as it requires these access rights to be computed.
Fixes#2458, Closes#7734
* fix a crash when grouping on non-many2one fields (due to the
group.values object being not initialized)
* display correct label when grouping on selection fields
We should have a better way to deal with fields differences. There is
this weird concept called "abstraction", which could be applied and
would allow everyone to focus on their business and not on dealing with
this, but that would probably not fit with our codebase.
Many2One fields were broken in views opened by default in edit mode, since rev.
a0ddaf8. The autocomplete widget was appended to the DOM at
'.oe_application > *:visible:last', but since the mentionned rev., the views
are rendered in fragments detached from the DOM, and once they are ready, the
old content is detached and the new one is attached instead. It means that by
appending the autocomplete widget within '.oe_application > *:visible:last',
it is detached from the DOM with the previous content, and Many2One fields can
thus not work.
This rev. simply removes the appendTo option of autocomplete, so that the
widget is directly appended to the body.
Also updates a tour's selector matching an autocomplete ul as it isn't inside
the .modal anymore.
The state of a crm claim has been removed in f14eddb.
Thus, it is not possible to know the closure date and this commit hides
the field in the view.
opw-645826
Because of the fix in commit 4fbecc35e1,
and the newly added word-break for oe_tag class, the kanban column
counter gets split in multiple lines for folded kanban columns,
resulting in
"
9
9
+
"
instead of "99+".
A jquery selector $('td[id^=]') may have been valid once uppon a time,
but it cause error on current jquery versions.
Also in some case when we want to add a field on a view, there may be
a mess to detect the parent.
opw-645557
Unlink typical domain evaluation (ir.rule, filters,...), the evaluated domain
for automated actions did not included time in the context so it was not
possible to make time based conditions in domain.
This should be used with care as filters 'Based on Timed Condition' are still
possible and will probably be enough (and safer) in most cases.
The field "state" in "sale.report" model must consider the state used
by "sale.order.line" to be consistent with the view created in this model.
The function _sale_count in 'product.product' model must return
the number of product included in a "confirmed" or "done" sale order line.
opw:644200
Domains like `[('x2m_field_ids', 'not ilike', 'foo')]` now have a more
logical semantic. The negation is applied on the relation and not the
`name_search`.
Christophe Simonis