We have introduced a second version of the Extract API that adds the IAP
account token to the `get_result` and `validate` routes.
There are also other changes in this commit:
- The deprecated stuff has been removed as it's been deprecated for a
while and won't be supported anymore in the future.
- The `status` table of the `get_result` route has been added as it was
missing for some reason.
- The documentation regarding the `/validate` routes have been removed
for security reasons.
closesodoo/documentation#6280
X-original-commit: a8c6272899
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Louis Baudoux (lba) <lba@odoo.com>
In the CLI, `--unaccent` try to enable PostgreSQL unaccent extention
when odoo is responsible to create new database(s).
closesodoo/documentation#6241
X-original-commit: 1639d22efd
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Rémy Voet (ryv) <ryv@odoo.com>
Added a note to make it clearer that for fiduciaries, a single API key
is valid for all databases linked to the user.
taskid-3570700
closesodoo/documentation#6228
X-original-commit: 323d3563c9
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Tom Aarab (toaa) <toaa@odoo.com>
Updated screenshots and typos for 16.3
Forward to 16.4:
- Change: Dashboard links are improved, and audit features can be found
in the journal items view.
closesodoo/documentation#6162
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
A new way to disable IAP accounts has been introduced recently.
This feature is mostly used in neutralization scripts to prevent
customers from accidentaly consuming their credits on their
staging/testing databases.
Documenting it will help users re-enable their accounts if they still
wish to use it in a testing environment.
closesodoo/documentation#6137
X-original-commit: fa604a95b0
Signed-off-by: Louis Baudoux (lba) <lba@odoo.com>
Remove parenthesis around a term that's fairly straightforward to
understand and later used as a title Add a much-needed point.
closesodoo/documentation#6124
X-original-commit: 6f3ed657fc
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Stanislas Gueniffey (stgu) <stgu@odoo.com>
Results of seeing a lot of wrong and missing configuration
on consultancy project for Outlook accounts.
The Multi outgoing mail server is harder to maintain than having
a unique mail server with an Odoo db correctly configured.
Insisting on the mail.default.from (ICP) and the From Filtering
parameters that NEEDS TO BE set up.
task-3512379
[FIX] Maintain: Azure_oauth: configuration mail server Outlook
Co-author-by: tiku-odoo <tiku@odoo.com>
Co-author-by: jqu-odoo <jqu@odoo.com>
Results of seeing a lot of wrong and missing configuration
on consultancy project for Outlook accounts.
The Multi outgoing mail server is harder to maintain than having
a unique mail server with an Odoo db correctly configured.
Insisting on the mail.default.from (ICP) and the From Filtering
parameters that NEEDS TO BE set up.
task-3512379
closesodoo/documentation#6034
X-original-commit: 41b9ba6383
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
The bill reference is no longer detected since a few months because it
had poor results and wasn't very useful.
closesodoo/documentation#6008
X-original-commit: cade61dd56
Signed-off-by: Louis Baudoux (lba) <lba@odoo.com>
Many users don't start odoo-bin in --workers (multi-processing) mode but
instead leave the default configuration which use the development/demo
multi-threaded server, even in production.
This commit rewords the section about the difference between the
built-in servers and highlight the many advantages of the
multi-processing on. It repeats that information when it comes to
running a dedicated cron server, that it should use the multi-processing
server instead of the default multi-threading one.
closesodoo/documentation#5932Fixes: odoo/odoo#88984Closes: odoo/odoo#128571
X-original-commit: 8e9ae99423
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
Signed-off-by: Julien Castiaux (juc) <juc@odoo.com>
