Backport of commit d227ab66b0 on #1448closesodoo/documentation#1613
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Creation of a new submenu under Applications/General for the Email communication.
Moved advanced of dicuss to this new submenu + adding of content regarding
frequently asked question in support.
Redirection has been done on other files pointing to Discuss/Advanced to match
the new folder email_communication.
Modified content in:
- Email servers: split and move configuration part under email_domain
- Email domain: covering information about SPF DKIM and DMARC configurations by JQU
- Email templates: (how to use the functions) by GOR
- Email common: answering frequently asked questions + common issues by ALA
closesodoo/documentation#1525
X-original-commit: cf6af904f9
Signed-off-by: Vergote Baptiste (bve) <bve@odoo.com>
Adding basic information about `How to make a test tour`.
task-2742841
closesodoo/documentation#1516
X-original-commit: f6c1723fe0
Signed-off-by: Morgane Demesmaeker <edm@odoo.com>
The "Payment Acquirers" category was moved to the /general/ folder
(Miscellaneous section) when the super-categories such as "Finance"
didn't exist yet. Now, it makes more sense to move this category to
"Finance".
task-id 2743227
closesodoo/documentation#1497
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Both the functional and technical name of the `ir.rule` model is "Record
Rule". This commit makes sure that all occurrences of "Access Rule" are
replaced by the correct name "Record Rule" as it was easily confused
with "Access Rights".
Original PR: https://github.com/odoo/documentation/pull/1118closesodoo/documentation#1421
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Requesting a dump from the customers comming from the PaaS is useless
(since support has access to the odoo.sh projects) and counter
productive (since it only makes the migration outage longer while the
customer downloads the file, then uploads it, then we download it,
instead of just the support downloading it)
closesodoo/documentation#1365
X-original-commit: c3c054681c
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
New taxes generated by the TaxCloud integration are by default created without an income or an expense account specified. By default, the journal items corresponding to these taxes therefore end up in the default income account, which is usually the 'Sales' account, when they should in fact go to the 'Tax Payable' account. Because these taxes are automatically generated on-the-fly, the user is usually not able to manually specify the Tax Payable account before the journal items are posted, leading to incorrect accounting entries which then need to be manually repaired through the use of miscellaneous operations.
To solve this issue, our video on TaxCloud integration (https://www.youtube.com/watch?v=JE-NeRNIWeU&t=616s) tells us to create a User-Defined Default for the account field of the tax.repartition.line model. This sets the default account with which new taxes are created. However, this information is missing from the documentation.
This PR brings the documentation up-to-date by explaining how to create this User-Defined Default that specifies the correct Tax Payable account.
closesodoo/documentation#1319
X-original-commit: 35d773a82a
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Syntax was added to explicitly specify a module, class or function with
`--test-tags`: b729a11a12
The documentation was not updated to reflect this, leading to confusion
as people tried to reconcile the documentation with the actual behavior,
without necessarily having seen `odoo-bin --help` which is explicit
about it.
closesodoo/documentation#1279
X-original-commit: 23d0a7a062
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
The default protocol int the POS with "other device"
is on HTTP.
This doc explain how to activate the HTTPS in the POS
closesodoo/documentation#1195
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
The english version has a confusing wording, using "strict ngligence"
instead of "strict liability" in this sentence:
"(...) regardless of the form of action, whether in contract, tort
(including strict negligence) or any other legal (...)"
In FR/BE this would seeem to refer to the notion of "responsabilité
objective" ou "responsabilité sans faute".
Yet this extra precision seems confusing and does not seem to add to the
already broad clause. It seems simpler to omit it.
The typical english wording for this clause is simply:
"regardless of the form of action, whether in contract, tort or otherwise".
