Compare commits

...

8 Commits

Author SHA1 Message Date
Felicious
fd58a0d4a8 [IMP] inventory: remove rescheduling
X-original-commit: 8ad53481d1
Co-authored-by: brse-odoo <brse@odoo.com>
2024-03-21 04:24:47 +01:00
tiku-odoo
3943ff6f4b [IMP] hosting: add admonition block on subscription
closes odoo/documentation#8255

X-original-commit: 9df807a532
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-03-20 16:50:21 +00:00
tiku-odoo
78004f6ae3 [IMP] developer: external api add admonition block
closes odoo/documentation#8238

X-original-commit: d6f5e74971
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-03-20 14:52:37 +00:00
tiku-odoo
133abb2ab1 [REM] voip: onsip scrub per onsip
closes odoo/documentation#8237

X-original-commit: 7b728a22f4
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-03-20 14:52:36 +00:00
Xavier (XPL)
637671bad0 [FIX] website: domain names
closes odoo/documentation#8233

X-original-commit: b7ffab804b
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-03-20 14:52:32 +00:00
Felicious
bc0ceff831 [DEL] remove usage; contains packages + packagings
closes odoo/documentation#8220

X-original-commit: 281d3976da
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
2024-03-20 12:46:15 +00:00
Colu
05e34a4859 [IMP] database management: update on-premise page
task-3627193

closes odoo/documentation#8213

X-original-commit: 739309b258
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-03-20 12:46:08 +00:00
Christophe Monniez
256061731f [REL] saas-17.2 2024-03-19 12:57:27 +00:00
28 changed files with 129 additions and 369 deletions

View File

@@ -26,7 +26,7 @@ SOURCE_DIR = content
HTML_BUILD_DIR = $(BUILD_DIR)/html
ifdef VERSIONS
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-17.2
endif
ifneq ($(CURRENT_LANG),en)
HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)

View File

@@ -22,7 +22,7 @@ copyright = 'Odoo S.A.'
# `version` is the version info for the project being documented, acts as replacement for |version|,
# also used in various other places throughout the built documents.
# `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
version = release = 'master'
version = release = 'saas-17.2'
# `current_branch` is the technical name of the current branch.
# E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
@@ -213,6 +213,7 @@ sphinx.transforms.i18n.docname_to_domain = (
# is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
versions_names = {
'master': "Master",
'saas-17.2': "Odoo Online",
'saas-17.1': "Odoo Online",
'17.0': "Odoo 17",
'saas-16.4': "Odoo Online",

View File

@@ -20,7 +20,7 @@ To Odoo Online
- Odoo Online is *not* compatible with **non-standard apps**.
- The database's current version must be :doc:`supported <supported_versions>`.
#. Create a :ref:`duplicate <duplicate_premise>` of the database.
#. Create a :ref:`duplicate of the database <on-premise/duplicate>`.
#. In this duplicate, uninstall all **non-standard apps**.
#. Use the database manager to grab a *dump with filestore*.
#. `Submit a support ticket <https://www.odoo.com/help>`_ including the following:
@@ -59,6 +59,11 @@ Transferring an Odoo Online database
Click the gear icon (:guilabel:`⚙`) next to the database name on the `Odoo Online database
manager <https://www.odoo.com/my/databases/>`_ to display its version number.
.. warning::
If there is an active Odoo subscription linked to the database being migrated, reach out to
the Customer Service Manager or `submit a support ticket <https://www.odoo.com/help>`_ to
complete the subscription transfer.
To on-premise
-------------

View File

@@ -7,159 +7,110 @@ On-premise
Register a database
===================
To register your database, you just need to enter your Subscription Code in the
banner in the App Switcher. Make sure you do not add extra spaces before or after
your subscription code. If the registration is successful, it will turn green and
will provide you with the Expiration Date of your freshly-registered database. You
can check this Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard
(Odoo 10).
To register your database, enter your subscription code in the banner in the app dashboard. If the
registration is successful, the banner will turn green and display the database expiration date.
Registration Error Message
--------------------------
.. tip::
The expiration date is also displayed at the bottom of the Settings page.
If you are unable to register your database, you will likely encounter this
message:
.. image:: on_premise/error_message_sub_code.png
:alt: Something went wrong while registering your database, you can try again or contact Odoo
Help
Solutions
~~~~~~~~~
* Do you have a valid Enterprise subscription?
* Check if your subscription details get the tag "In Progress" on
your `Odoo Account
<https://accounts.odoo.com/my/subscription>`__ or with your Account Manager
* Have you already linked a database with your subscription reference?
* You can link only one database per subscription.
(Need a test or a development database? `Find a partner
<https://www.odoo.com/partners>`__)
* You can unlink the old database yourself on your `Odoo Contract
<https://accounts.odoo.com/my/subscription>`__ with the button "Unlink database"
.. image:: on_premise/unlink_single_db.png
A confirmation message will appear; make sure this is the correct database as
it will be deactivated shortly:
.. image:: on_premise/unlink_confirm_enterprise_edition.png
* Do you have the updated version of Odoo 9?
* From July 2016 onward, Odoo 9 now automatically change the uuid of a
duplicated database; a manual operation is no longer required.
* If it's not the case, you may have multiple databases sharing the same
UUID. Please check on your `Odoo Contract
<https://accounts.odoo.com/my/subscription>`__, a short message will appear
specifying which database is problematic:
.. image:: on_premise/unlink_db_name_collision.png
In this case, you need to change the UUID on your test databases to solve this
issue. You will find more information about this in :ref:`this section <duplicate_premise>`.
For your information, we identify database with UUID. Therefore, each database
should have a distinct UUID to ensure that registration and invoicing proceed
effortlessly for your and for us.
* Check your network and firewall settings
* The Update notification must be able to reach Odoo's subscription
validation servers. In other words, make sure that the Odoo server is able
to open outgoing connections towards:
* services.odoo.com on port 443 (or 80)
* services.openerp.com on port 443 (or 80) for older deployments
* Once you activated your database, you must keep these ports open, as the
Update notification runs once a week.
Error message due to too many users
-----------------------------------
If you have more users in your local database than provisionned in your
Odoo Enterprise subscription, you may encounter this message:
.. image:: on_premise/add_more_users.png
:alt: This database will expire in X days, you have more users than your subscription allows
When the message appears you have 30 days before the expiration.
The countdown is updated everyday.
Solutions
~~~~~~~~~
- **Add more users** on your subscription: follow the link and Validate
the upsell quotation and pay for the extra users.
- **Deactivate users** as explained in this `documentation <documentation.html#deactivating-users>`_
and **Reject** the upsell quotation.
Once your database has the correct number of users, the expiration message
will disappear automatically after a few days, when the next verification occurs.
We understand that it can be a bit frightening to see the countdown,
so you can :ref:`force an Update Notification <force_ping>` to make the message disappear
right away.
Database expired error message
------------------------------
If your database reaches its expiration date before your renew your subscription,
you will encounter this message:
.. image:: on_premise/database_expired.png
:alt: This database has expired.
This **blocking** message appears after a non-blocking message that lasts 30 days.
If you fail to take action before the end of the countdown, the database is expired.
Solutions
~~~~~~~~~
* Renew your subscription: follow the link and renew your subscription - note that
if you wish to pay by Wire Transfer, your subscription will effectively be renewed
only when the payment arrives, which can take a few days. Credit card payments are
processed immediately.
* Contact our `Support <https://www.odoo.com/help>`__
None of those solutions worked for you? Please contact our
`Support <https://www.odoo.com/help>`__
.. _force_ping:
.. _duplicate_premise:
.. _on-premise/duplicate:
Duplicate a database
====================
You can duplicate your database by accessing the database manager on your
server (<odoo-server>/web/database/manager). In this page, you can easily
duplicate your database (among other things).
Duplicate a database by accessing the database manager on your server
(`<odoo-server>/web/database/manager`). Typically, you want to duplicate your production database
into a neutralized testing database. It can be done by checking the neutralize box when prompted,
which executes all :file:`neutralize.sql` scripts for every installed module.
.. image:: on_premise/db_manager.gif
Common error messages and solutions
===================================
When you duplicate a local database, it is **strongly** advised to change
the duplicated database's uuid (Unniversally Unique Identifier), since this
uuid is how your database identifies itself with our servers. Having two
databases with the same uuid could result in invoicing problems or registration
problems down the line.
Registration error
------------------
.. note::
From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a
manual operation is no longer required.
In case of a registration error, the following message should be displayed.
The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical -->
System Parameters`, we advise you to use a `uuid generator <https://www.uuidtools.com>`_ or to
use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any
other record by clicking on it and using the edit button.
.. image:: on_premise/error-message-sub-code.png
:alt: Database registration error message
.. image:: on_premise/db_uuid.png
To resolve the issue:
- Check the **validity of your Odoo Enterprise subscription** by verifying if your subscription
details have the tag :guilabel:`In Progress` on your `Odoo Account
<https://accounts.odoo.com/my/subscription>`_ or contact your Account Manager.
- Ensure that **no other database is linked** to the subscription code, as only one database can be
linked per subscription.
.. tip::
If a test or a development database is needed, you can :ref:`duplicate a database
<on-premise/duplicate>`.
- Verify that **no databases share the same UUID** (Universally Unique Identifier) by opening your
`Odoo Contract <https://accounts.odoo.com/my/subscription>`_. If two or more databases share the
same UUID, their name will be displayed.
.. image:: on_premise/unlink-db-name-collision.png
:alt: Database UUID error message
If that is the case, manually change the database(s) UUID or `send a support ticket
<https://www.odoo.com/help>`_.
- As the update notification must be able to reach Odoo's subscription validation servers, ensure
your **network and firewall settings** allow the Odoo server to open outgoing connections
towards:
- `services.odoo.com` on port `443` (or `80`)
- for older deployments, `services.openerp.com` on port `443` (or `80`)
These ports must be kept open even after registering a database, as the update notification runs
once a week.
Too many users error
--------------------
If you have more users in a local database than provisioned in your Odoo Enterprise subscription,
the following message should be displayed.
.. image:: on_premise/add-more-users.png
:alt: Too many users on a database error message
When the message appears, you have 30 days to act before the database expires. The countdown is
updated every day.
To resolve the issue, either:
- **Add more users** to your subscription by clicking the :guilabel:`Upgrade your subscription` link
displayed in the message to validate the upsell quotation and pay for the extra users.
- :ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation.
.. important::
If you are on a monthly subscription plan, the database will automatically update to reflect the
added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the
database. You can create the upsell quotation by clicking the banner to update the subscription
or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue.
Once your database has the correct number of users, the expiration message disappears automatically
after a few days, when the next verification occurs.
Database expired error
----------------------
If your database expires before you renew your subscription, the following message should be
displayed.
.. image:: on_premise/database-expired.png
:alt: Database expired error message
This message appears if you fail to act before the end of the 30-day countdown.
To resolve the issue, either:
- Click the :guilabel:`Renew your subscription` link displayed in the message and complete the
process. If you pay by wire transfer, your subscription will be renewed when the payment arrives
which can take a few days. Credit card payments are processed immediately.
- `Send a support ticket <https://www.odoo.com/help>`_.
.. toctree::

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.3 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.5 KiB

View File

Before

Width:  |  Height:  |  Size: 4.6 KiB

After

Width:  |  Height:  |  Size: 4.6 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 89 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 17 KiB

View File

Before

Width:  |  Height:  |  Size: 6.9 KiB

After

Width:  |  Height:  |  Size: 6.9 KiB

View File

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

View File

@@ -14,5 +14,4 @@ Advanced operations
advanced_operations_warehouse/cross_dock
advanced_operations_warehouse/stock_warehouses
advanced_operations_warehouse/putaway
advanced_operations_warehouse/usage
advanced_operations_warehouse/cluster_picking

View File

@@ -83,7 +83,7 @@ form.
Set the :guilabel:`Package Use` field to :guilabel:`Reusable Box`.
.. seealso::
:ref:`Packages <inventory/management/packages>`
:doc:`Packages <../../product_management/product_tracking/package>`
.. example::
A package intended for cluster picking is named `CLUSTER-PACK-3` for easy identification. For

View File

@@ -1,195 +0,0 @@
=======================
Packages and packagings
=======================
In Odoo, there are a variety of ways to specify the amount of products being bought, stocked, and
sold. *Packages* and *packagings* are all available to streamline inventory flows, allowing for a
variety of configurations for products as they enter and leave the warehouse.
.. _inventory/management/packages:
Packages
========
Packages are a physical container that holds one or several products from a picking, typically used
for outgoing deliveries or internal transfers. Packages can be a reusable or disposable (shipping)
box, and are **not** specific to a product.
Reusable boxes temporarily hold products during a picking to be brought to either a packing or
shipping area. Disposable boxes are the actual shipping containers (e.g. cardboard boxes, envelopes,
shipping bags, etc). These are used to ship the products out to customers.
Multiple items in a sales order (SO) can be separated into different packages to accommodate the
products. For example, an :abbr:`SO (Sales Order)` that has 20 boxes of pencils and 4 boxes of
erasers can be separated into two separate packages, each containing 10 boxes of pencils and 2 boxes
of erasers.
.. note::
Products do *not* have to be divided equally. Products can be divided into as many packages that
are needed to accommodate the :abbr:`SO (Sales Order)`.
In Odoo, the quantity of products in each package needs to be recorded, so there is a full history
for each product, including which package each item is shipped out in.
To use this method, ensure the :guilabel:`Packages` option is enabled, by navigating to
:menuselection:`Inventory app --> Configuration --> Settings --> Operations`. Click the
:guilabel:`Packages` check box, and then :guilabel:`Save` to activate the feature.
On a delivery order, assign which package to use by clicking on the :guilabel:`≣ (Detailed
Operations)` icon to the right of each product in the :guilabel:`Operations` tab.
.. image:: usage/detailed-operations-icon.png
:align: center
:alt: Find detailed operations icon to the right on the product line.
Clicking the :guilabel:`≣ (Detailed Operations)` icon of a product reveals a pop-up window. In this
window, the :guilabel:`Product` name, :guilabel:`Demand`, and :guilabel:`Quantity Done` are clearly
displayed above the customizable product line.
Here, the warehouse location the product is coming from can be modified, in addition to the
:guilabel:`Source Package` and :guilabel:`Destination Package`, which represents what package(s) the
product(s) will be packaged into.
Click :guilabel:`Add a line` to include each additional package used. Enter the desired amount in
the :guilabel:`Done` field to specify the amount of products that will go into the
:guilabel:`Destination Package`.
Multiple packages in a single delivery
--------------------------------------
Although a :abbr:`DO (Delivery Order)` is typically associated with a single package, orders can be
split by clicking the :guilabel:`≣ (Detailed Operations)` icon next to the products on an :abbr:`SO
(Sales Order)` line. This opens the :guilabel:`Detailed Operations` window with an editable table to
specify which products are intended for which package.
.. example::
To package 10 boxes of pencils with 2 boxes of erasers from the same :abbr:`SO (Sales Order)`,
begin by navigating to the :abbr:`DO (Delivery Order)`. Then, select the :guilabel:`≣ (four
horizontal lines)` icon to the right of the product, `Box of Pencils`. Clicking the icon opens
the :guilabel:`Detailed Operations` window that is used to detail how products, like the 20 `Box
of Pencils`, are packaged.
Type in `10` under the :guilabel:`Done` field to package 10 products into the
:guilabel:`Destination Package`. To specify the destination package, type the name of an existing
package (such as `PACK0000006`) under the field, :guilabel:`Destination Package`. If the package
does not exist, Odoo displays the :guilabel:`Create` button to create a new package. Click
:guilabel:`Add a line` to assign the remaining products in another package, `PACK0000007`.
.. image:: usage/add-destination-package.png
:align: center
:alt: Detailed operations pop-up where the amount of product going in a pack can be specified.
Select :guilabel:`Detailed Operations` on the product line for `Box of Erasers` and similarly set
2 :guilabel:`Done` products to `PACK0000006` and `PACK0000007` each.
.. image:: usage/put-in-pack-button.png
:align: center
:alt: Put in pack button to match the done amount matches the demand.
Once all the products for each line have been entered, click :guilabel:`Confirm` to return to the
:abbr:`DO (Delivery Order)`.
The :guilabel:`Done` quantity on the :abbr:`DO (Delivery Order)` updates as products are selected
for each package. When the :guilabel:`Done` amount matches the :guilabel:`Demand` amount, click the
:guilabel:`Validate` button to complete the delivery order.
.. tip::
The :guilabel:`Put In Pack` button is intended to quickly package all products in the :abbr:`DO
(Delivery Order)` into one new package. The option to rename the package, or modify its contents,
is available in the :guilabel:`Detailed Operations` pop-up.
Clicking on the :guilabel:`Packages` smart button in the upper-right corner of the delivery order
reveals a separate page, showing all the packages used in that :abbr:`DO (Delivery Order)`.
Packagings
==========
*Packaging* is product specific, and refers to a disposable container that holds several units of a
specific product. Unlike packages, packagings cannot be reusable, and each specific packaging must
be defined on the individual product form.
For example, different packages for cans of soda can be configured as a 6-pack, a 12-pack, or a case
of 36. Each flavor of soda would need a `6`, `12`, and `36` can packaging configured on the
individual product since packagings are product specific, not generic.
Set up packagings
-----------------
To use packagings, ensure the :guilabel:`Product Packagings` feature is enabled. To do that,
navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Then, under the
:guilabel:`Products` heading, check the box next to :guilabel:`Product Packagings`, and click
:guilabel:`Save`.
In Odoo, product packagings are used on sales/purchase orders and inventory transfers.
Next, to create packagings, navigate to :menuselection:`Inventory app --> Products --> Products` and
click on the desired product, then click :guilabel:`Edit` on the product page.
Under the :guilabel:`Inventory` tab, scroll down to the :guilabel:`Packaging` section, and click
:guilabel:`Add a line`. Then, a pop-up window appears, in which the following information for each
packaging should be entered:
- :guilabel:`Packaging`: name of packaging that appears on sales/purchase orders as a packaging
option for the product
- :guilabel:`Contained quantity`: amount of product in the packaging
- :guilabel:`Barcode`: identifier used with the :ref:`Barcode app <barcode/operations/intro>` to
trace the packaging of a product during stock moves or pickings. Leave blank if not in use
- :guilabel:`Company`: indicates the packaging is only available at the selected company. Leave
blank to make the packaging available across all companies.
.. example::
Create a packaging type for 6 cans of the product, `Grape Soda`, by naming the
:guilabel:`Packaging` to `6-pack` and setting the :guilabel:`Contained quantity` to `6` in the
pop-up window that appears after clicking on :guilabel:`Add a line`.
.. image:: usage/create-product-packages.png
:align: center
:alt: Create 6-pack case for product.
When all the necessary information has been entered, either click :guilabel:`Save & Close` to save
the packaging and return to the product detail form, or :guilabel:`Save & New` to save the packaging
and create another one in a fresh pop-up window.
.. example::
View all product packagings in the :guilabel:`Inventory` tab of the product form.
.. image:: usage/display-product-packaging.png
:align: center
:alt: Show packaging and contained quantities, specified on the product page form in the
Inventory tab.
View all packagings
-------------------
To view all packagings that have been created, go to :menuselection:`Inventory app --> Configuration
--> Product Packagings`. Doing so reveals the :guilabel:`Product Packagings` page with a complete
list of all packagings that have been created for all products. Create new packagings by clicking
:guilabel:`Create`.
.. example::
Two soda products, `Grape Soda` and `Diet Coke`, have three types of packaging configured. On the
:guilabel:`Product Packagings` page, each product can sold as a `6-Pack` that contains 6
products, `12-Pack` of 12 products, or a `Case` of 32 products.
.. image:: usage/packagings.png
:align: center
:alt: List of different packagings for products.
Apply packagings
----------------
When creating a sales order in the :menuselection:`Sales` app, specify the packagings that should be
used for the product(s). The chosen packaging is displayed on the :abbr:`SO (Sales Order)` under the
:guilabel:`Package` field.
.. example::
18 cans of the product, `Grape Soda`, is packed using three 6-pack packagings.
.. image:: usage/packagings-sales-order.png
:align: center
:alt: Assign packagings on the Sales Order Line.
.. tip::
Packaging can be used in conjunction with Odoo :ref:`Barcode <inventory/barcode/software>`. When
receiving products from suppliers, scanning the packaging barcode automatically adds the number
of units in the packaging to the internal count of the product.

View File

@@ -1,7 +1,7 @@
.. _use-routes:
==========================
Routes and Pull/Push Rules
Routes and push/pull rules
==========================
In inventory management, the supply chain strategy determines when products should be
@@ -33,11 +33,10 @@ in the manufacturing process), while others are directly stored in their respect
:align: center
:alt: View of a generic push to rule when receiving products.
Here is an example of a fulfillment route. In the morning, items are picked for all the orders
that need to be prepared during the day. These items are picked from storage locations and moved to
the picking area, close to where the orders are packed. Then, the orders are packed in their
respective boxes and conveyors bring them close to the shipping docks, ready to be delivered to
customers.
Here is an example of a fulfillment route. In the morning, items are picked for all the orders that
need to be prepared during the day. These items are picked from storage locations and moved to the
picking area, close to where the orders are packed. Then, the orders are packed in their respective
boxes, and conveyor belts bring them to the shipping docks, ready to be delivered to customers.
.. image:: use_routes/pull-from-rule-example.png
:align: center
@@ -50,8 +49,8 @@ With *Pull Rules*, a demand for some products triggers procurements, while *Push
triggered by products arriving in a specific location.
Pull Rules are used to fulfill a sales order. Odoo generates a need at the *Customer Location* for
each product in the order. Because pull rules are triggered by a need, Odoo looks for a pull
rule defined on the *Customer Location*.
each product in the order. Because pull rules are triggered by a need, Odoo looks for a pull rule
defined on the *Customer Location*.
In this case, a "delivery order" pull rule that transfers products from the *Shipping Area* to the
*Customer Location* is found, and a transfer between the two locations is created.
@@ -130,7 +129,7 @@ can view the warehouse's pre-configured routes for :guilabel:`Incoming Shipments
.. image:: use_routes/example-preconfigured-warehouse.png
:align: center
:alt: A preconfigured warehouse in Odoo Inventory.
:alt: A pre-configured warehouse in Odoo Inventory.
Some more advanced routes, such as pick-pack-ship, are also available. The user can select the
route that best fits their business needs. Once the :guilabel:`Incoming Shipments` and
@@ -270,15 +269,8 @@ source location:
the available stock of the source location. If there is no stock available, the system tries to
find a rule to bring the products to the source location.
In the *Scheduling* section, you can determine how Odoo behaves when one of the chain's pickings is
rescheduled. In case you decide to **Propagate Rescheduling**, the next move is also to be
rescheduled.
If you prefer having the choice to reschedule the next move, you can decide to receive an alert in
the form of a *next activity*.
Sample full route flow
======================
Example flow
============
In this example, let's use a custom *Pick - Pack - Ship* route to try a full flow with an advanced
custom route.

View File

@@ -169,7 +169,7 @@ the :guilabel:`Packages` feature.
:alt: Enable the packages feature.
.. seealso::
- :ref:`Packages <inventory/management/packages>`
- :doc:`Packages <../product_management/product_tracking/package>`
- :doc:`2-step delivery <../shipping_receiving/daily_operations/receipts_delivery_two_steps>`
- :doc:`3-step delivery <../shipping_receiving/daily_operations/delivery_three_steps>`

View File

@@ -5,8 +5,9 @@ Use VoIP services in Odoo with OnSIP
Introduction
============
Odoo *VoIP* can be set up to work together with `OnSIP <https://www.onsip.com/>`_. OnSIP is a VoIP
provider. An account is needed with OnSIP in order to use this service.
Odoo *VoIP* can be set up to work together with `OnSIP (Odoo Landing Page)
<https://info.onsip.com/odoo/>`_. OnSIP is a VoIP provider. An account is needed with OnSIP in order
to use this service.
Before setting up an account with OnSIP, make sure the company's home area, and the areas that will
be called, are covered by OnSIP services.
@@ -128,14 +129,13 @@ Incorrect number
~~~~~~~~~~~~~~~~
If an *Incorrect Number* message appears in the Odoo widget, make sure to use the international
format for the number. This means leading with the :guilabel:`+ (plus)` sign, followed by the
international country code.
format for the number. This means leading with the international country code.
A country code is a locator code that allows access to the desired country's phone system. The
country code is dialed first, prior to the target number. Each country in the world has its own
specific country code.
For example, `+16505555555` (where `+1` is the international prefix for the United States).
For example, `16505555555` (where `1` is the international prefix for the United States).
.. image:: onsip/onsip05.png
:align: center

View File

@@ -37,12 +37,13 @@ Search for the desired domain name and check its availability.
Ensure the Website app is installed if the domain name registration option does not appear.
Select the desired domain name, fill in the :guilabel:`Domain Owner` form, and click
:guilabel:`Register`. The chosen domain name is directly linked to the database, but you still need
to :ref:`map your domain name to your Odoo website <domain-name/db-map>`.
:guilabel:`Register`. The chosen domain name is directly linked to the database.
.. image:: domain_names/domain-owner.png
:alt: Filling in the domain owner information
Next, you should :ref:`map your domain name to your Odoo website <domain-name/website-map>`.
.. important::
A verification email from `noreply@domainnameverification.net` will be sent to the email address
provided in the :guilabel:`Domain Owner` form. It is essential to verify your email address to
@@ -268,7 +269,7 @@ To make your custom domain name the *web base URL* of your database, access your
custom domain name and log in as an administrator :dfn:`(a user part of the Settings access right
group under Administration)`.
.. warning::
.. important::
If you access your database with the original Odoo address (e.g., `mycompany.odoo.com`), the *web
base URL* of your database will be updated accordingly. To prevent the automatic update of the
*web base URL* when an administrator logs in to the database, activate the :ref:`developer mode

View File

@@ -12,6 +12,12 @@ easily available over XML-RPC_ and accessible from a variety of languages.
Check out the `manual <https://www.php.net/manual/en/xmlrpc.installation.php>`_
for the installation steps.
.. note::
Access to data via the external API is only available on *Custom* Odoo pricing plans. Access to
the external API is not available on *One App Free* or *Standard* plans. For more information
visit the `Odoo pricing page <https://www.odoo.com/pricing-plan>`_ or reach out to your Customer
Success Manager.
.. seealso::
- :doc:`Tutorial on web services <../howtos/web_services>`