[MERGE] Forward-port of branch 13.0 to 14.0
This commit is contained in:
commit
bf7b48fe47
@ -397,7 +397,7 @@ from a sales order, proceed to validate the invoice. After the invoice is poste
|
|||||||
|
|
||||||
.. image:: media/Chile16.png
|
.. image:: media/Chile16.png
|
||||||
:align: center
|
:align: center
|
||||||
:alt: DTE XML File displayed in chatter.
|
:alt: DTE XML File displayed in chatter.
|
||||||
|
|
||||||
The DTE Status is updated automatically by Odoo with a scheduled action that runs every day
|
The DTE Status is updated automatically by Odoo with a scheduled action that runs every day
|
||||||
at night, if you need to get the response from the SII immediately you can do it manually as well.
|
at night, if you need to get the response from the SII immediately you can do it manually as well.
|
||||||
@ -419,7 +419,7 @@ The DTE status workflow is as follows:
|
|||||||
|
|
||||||
.. image:: media/Chile18.png
|
.. image:: media/Chile18.png
|
||||||
:align: center
|
:align: center
|
||||||
:alt: Identification transaction for invoice and Status update.
|
:alt: Identification transaction for invoice and Status update.
|
||||||
|
|
||||||
|
|
||||||
There are several internal status in the SII before you get Acceptance or Rejection, in
|
There are several internal status in the SII before you get Acceptance or Rejection, in
|
||||||
@ -428,7 +428,7 @@ The DTE status workflow is as follows:
|
|||||||
|
|
||||||
.. image:: media/Chile18_2.png
|
.. image:: media/Chile18_2.png
|
||||||
:align: center
|
:align: center
|
||||||
:alt: Descprtion of each DTE status in the chatter.
|
:alt: Descprtion of each DTE status in the chatter.
|
||||||
|
|
||||||
3. The final response from the SII, can take on of these values:
|
3. The final response from the SII, can take on of these values:
|
||||||
|
|
||||||
@ -442,7 +442,7 @@ The DTE status workflow is as follows:
|
|||||||
|
|
||||||
.. image:: media/Chile19.png
|
.. image:: media/Chile19.png
|
||||||
:align: center
|
:align: center
|
||||||
:alt: Email track once it is sent to the customer.
|
:alt: Email track once it is sent to the customer.
|
||||||
|
|
||||||
**Rejected:** Indicates the information in the invoice is incorrect and needs to be
|
**Rejected:** Indicates the information in the invoice is incorrect and needs to be
|
||||||
corrected, the detail of the issue is received in the emails you registered in the
|
corrected, the detail of the issue is received in the emails you registered in the
|
||||||
@ -457,7 +457,7 @@ The DTE status workflow is as follows:
|
|||||||
|
|
||||||
.. image:: media/Chile20.png
|
.. image:: media/Chile20.png
|
||||||
:align: center
|
:align: center
|
||||||
:alt: Message when an invoice is rejected.
|
:alt: Message when an invoice is rejected.
|
||||||
|
|
||||||
|
|
||||||
Crossed references
|
Crossed references
|
||||||
|
@ -153,6 +153,6 @@ purchase lines booked in the accounts and will display them in the
|
|||||||
The theoretical amount represents the amount of money you theoretically could
|
The theoretical amount represents the amount of money you theoretically could
|
||||||
have spend / should have received in function of the date. When your budget
|
have spend / should have received in function of the date. When your budget
|
||||||
is 1200 for 12 months (january to december), and today is 31 of january, the
|
is 1200 for 12 months (january to december), and today is 31 of january, the
|
||||||
theoretical amount will be 1000, since this is the actual amount that could
|
theoretical amount will be 100, since this is the actual amount that could
|
||||||
have been realised.
|
have been realised.
|
||||||
|
|
||||||
|
@ -31,9 +31,8 @@ unlike `Odoo Online <https://www.odoo.com/trial>`__ & `Odoo.sh <https://www.odoo
|
|||||||
You will find here below some useful
|
You will find here below some useful
|
||||||
information on how to integrate your own email solution with Odoo.
|
information on how to integrate your own email solution with Odoo.
|
||||||
|
|
||||||
.. note:: Office 365 email servers don't allow easily to send external emails
|
.. note:: Office 365 email servers don't easily allow to send external emails from hosts like Odoo.
|
||||||
from hosts like Odoo.
|
Refer to `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__
|
||||||
Refer to the `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__
|
|
||||||
to make it work.
|
to make it work.
|
||||||
|
|
||||||
How to manage outbound messages
|
How to manage outbound messages
|
||||||
|
@ -12,9 +12,11 @@ Each build is isolated within its own container (Linux namespaced container).
|
|||||||
The base is an Ubuntu 16.04 system, where all of Odoo's required dependencies,
|
The base is an Ubuntu 16.04 system, where all of Odoo's required dependencies,
|
||||||
as well as common useful packages, are installed.
|
as well as common useful packages, are installed.
|
||||||
|
|
||||||
The Odoo.sh team is open to install any system packages
|
The Odoo.sh team is open to install system packages as long as they are
|
||||||
as long as they are distributed in the official Ubuntu repositories.
|
distributed in the official Ubuntu repositories and meets the platform's
|
||||||
`Leave us a feedback <https://www.odoo.sh/feedback>`_ if you would like a package not yet installed.
|
`dependency requirements <https://www.odoo.sh/faq#install_dependencies>`_.
|
||||||
|
You can use `the feedback form <https://www.odoo.sh/feedback>`_ in order to
|
||||||
|
submit a package request to the Odoo.sh team.
|
||||||
|
|
||||||
If your project requires additional Python dependencies, or more recent releases,
|
If your project requires additional Python dependencies, or more recent releases,
|
||||||
you can define a :file:`requirements.txt` file in the root of your branches listing them.
|
you can define a :file:`requirements.txt` file in the root of your branches listing them.
|
||||||
|
@ -95,7 +95,8 @@ When you push a new commit in one of these branches,
|
|||||||
a new server is started, with a database created from scratch and the new revision of the branch.
|
a new server is started, with a database created from scratch and the new revision of the branch.
|
||||||
The demo data is loaded, and the unit tests are performed by default.
|
The demo data is loaded, and the unit tests are performed by default.
|
||||||
This verifies your changes do not break any of the features tested by them. If you wish, you can
|
This verifies your changes do not break any of the features tested by them. If you wish, you can
|
||||||
disable the tests in the :ref:`branch's settings <odoosh-gettingstarted-branches-tabs-mails>`.
|
disable the tests or allow specific tests to be run with custom tags in the :ref:`branch's settings
|
||||||
|
<odoosh-gettingstarted-branches-tabs-settings>`.
|
||||||
|
|
||||||
Similar to staging branches, the emails are not sent but are intercepted by a mailcatcher and
|
Similar to staging branches, the emails are not sent but are intercepted by a mailcatcher and
|
||||||
scheduled actions are not triggered as often is the database is not in use.
|
scheduled actions are not triggered as often is the database is not in use.
|
||||||
@ -276,9 +277,30 @@ to manually set it up again on every commit. If you choose new build for a stagi
|
|||||||
make a fresh copy from the production build every time a commit is pushed. A branch that is put
|
make a fresh copy from the production build every time a commit is pushed. A branch that is put
|
||||||
back from staging to development will automatically be set to 'Do nothing'.
|
back from staging to development will automatically be set to 'Do nothing'.
|
||||||
|
|
||||||
|
**Modules installation**
|
||||||
|
|
||||||
|
Choose the modules to install automatically for your development builds.
|
||||||
|
|
||||||
|
.. image:: ./media/interface-settings-modulesinstallation.png
|
||||||
|
:align: center
|
||||||
|
|
||||||
|
* *Install only my modules* will install the modules of the branch only. This is the default option.
|
||||||
|
The :ref:`submodules <odoosh-advanced-submodules>` are excluded.
|
||||||
|
* *Full installation (all modules)* will install the modules of the branch, the modules included in the submodules
|
||||||
|
and all standard modules of Odoo. When running the full installation, the test suite is disabled.
|
||||||
|
* *Install a list of modules* will install the modules specified in the input just below this option.
|
||||||
|
The names are the technical name of the modules, and they must be comma-separated.
|
||||||
|
|
||||||
|
If the tests are enabled, the standard Odoo modules suite can take up to 1 hour.
|
||||||
|
This setting applies to development builds only.
|
||||||
|
Staging builds duplicate the production build and the production build only installs base.
|
||||||
|
|
||||||
|
|
||||||
**Test suite**
|
**Test suite**
|
||||||
|
|
||||||
For development branches, you can choose to enable or disable the test suite. It's enabled by default.
|
For development branches, you can choose to enable or disable the test suite. It's enabled by default.
|
||||||
|
When the test suite is enabled, you can restrict them by specifying test tags `test tags
|
||||||
|
<https://www.odoo.com/documentation/12.0/reference/testing.html#test-selection>`_.
|
||||||
|
|
||||||
**Odoo Version**
|
**Odoo Version**
|
||||||
|
|
||||||
|
@ -97,24 +97,6 @@ Production and staging builds are excluded, visitors can only see their status.
|
|||||||
|
|
||||||
.. _odoosh-gettingstarted-settings-modules-installation:
|
.. _odoosh-gettingstarted-settings-modules-installation:
|
||||||
|
|
||||||
Modules installation
|
|
||||||
====================
|
|
||||||
|
|
||||||
Choose the modules to install automatically for your development builds.
|
|
||||||
|
|
||||||
.. image:: ./media/interface-settings-modulesinstallation.png
|
|
||||||
:align: center
|
|
||||||
|
|
||||||
* *Install only my modules* will install the modules of the branch only.
|
|
||||||
The :ref:`submodules <odoosh-advanced-submodules>` are excluded.
|
|
||||||
* *Full installation (all modules)* will install the modules of the branch, the modules included in the submodules
|
|
||||||
and all standard modules of Odoo.
|
|
||||||
* *Install a list of modules* will install the modules specified in the input just below this option.
|
|
||||||
The names are the technical name of the modules, and they must be comma-separated.
|
|
||||||
|
|
||||||
If the tests are enabled, the standard Odoo modules suite can take up to 1 hour.
|
|
||||||
This setting applies to development builds only.
|
|
||||||
Staging builds duplicate the production build and the production build only installs base.
|
|
||||||
|
|
||||||
Custom domains
|
Custom domains
|
||||||
==============
|
==============
|
||||||
|
Loading…
Reference in New Issue
Block a user