sale_crm : prevent the creation of SO from lead form view (avoid bypassing process)
website_quote : "View Quotation" on SO form view should not be a state button, so it is now replaced by a link near the field
The datetime widget use the "keypress" event to detect if it has been
changed. Unfortunately, some keys, such as backspace, do not fire a
keypress event. This commit listen instead on the 'change' event, which
should fire when the input has changed.
from demo to data. Indeed when installing the HR module people
expects some basic data for their daily management: sales
and administration are basic departments used in every
company.
This reverts commit 79c338dcb352be3d40118f998a76e1b7576a35da.
This commit has been done hastily without review. Moreover it
mixes changes related to different stuff.
The commit is then reverted to allow a propre review and cleaning
of the branch.
Modification summary:
KNOWLEDGE
get rid of the module Knwoledge, keep Document Management for docusign, which will be name eSign when merged
SALE/CRM
– Phone Calls becomes Calls, remove scheduled calls menuitem
– Merge Sales/CRM menuitem into Sales/Sales
– Page Views into scoring page views
– Configuration : Attribute, Attribute value in technical features
LEAD AUTOMATION
– Group Campaign and segment
– Report : Move Follow-up into it
WAREHOUSE
– Move traceability menuitems into inventory control
PROJECT
– Service, move it to Configuration, get rid of Products menu
– Invoicing : remove it, there are stat buttons, and contracts are managed in sales.
Timesheet :
– Timesheet profit, rename into Profits.
`purchase_ok` is already in the view,
This field is already set in the view
`product.product_template_form_view`
and `account.product_template_form_view` inherits from this view.
Setting twice a field in a view prevents to correctly change
the field.
opw-641485
In `account.abstract.payment` model,
The `partner_type` and `payment_type` fields had set as default
`supplier` and `outbound`, respectively.
The thing is, the `default_get` method of model `account.payment`
(inheriting on the above model), will keep these default values set,
even if the invoice is customer invoice, which is wrong.
Either, this `default_get` should ignore the current default values,
either, the default values should not be wrong in the first place.
In this revision, I choose the second solution. Therefore, I had
to add the default value `outbound` in the purchase payments
menu action.
opw-641441
`default_debit_account_id` and `default_credit_account_id`
are not required.
The code computing the journal account balance should not
rely on the fact it is.
opw-641433
- Preserved explicit 3rd-party copyright notices
- Explicit boilerplate should not be necessary - copyright law applies
automatically in all countries thanks to Berne Convention + WTO rules,
and a reference to the applicable license is clear enough.
- use a wizard to ask about creating a new bank account + journal
- fix 'Import Statement' action from the dashboard
- make l10n_be_coda new-api-compliant
Let arrow keys, tab and escape pass through. We still want users to be
able to use eg. arrow keys to be used when selecting a radio item. This
will always work in Chrom{e,ium} because they do not dispatch keypress
events for these types of keys, only keydown/keyup events. Firefox does
dispatch keypress events. This makes sure that we do not touch those
types of events in Firefox.
devices have to fire keypresses every 50ms minimum
Previously this was 100ms. This works just as well, but was mainly in
there for testing purposes.
Before this, users were only able to press a key when all other keys
were released to prevent a key from repeating. This works but when
typing you usually press the next key before releasing the current
one. This allows users to do exactly that while still blocking keys from
repeating.
Implement a new way of dealing with barcode events. This was necessary
because the old way of dealing with input coming from barcode devices
did not stop keyevents. This lead to all kinds of issues (eg. barcode
reader output being inserted as tender in a paymentline).
This new class inserts itself so that it handles all keyevents before
everything else. This means that it has authority on what keypress
events pass and which ones do not. It differentiates between 'real'
keyboard input and input coming from devices by buffering events. When a
certain amount of events come in fast enough, it is handled as a barcode
and a 'barcode_scanned' event is emitted on core.bus. When buffered
events are decided to not be a barcode, they are recreated and
redispatched.
Jamin Shah