diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 9aa971e7f..1410b48d9 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-09-01 15:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -161,8 +161,8 @@ msgstr "" #: ../../content/administration/install/deploy.rst:76 #: ../../content/administration/install/install.rst:338 -#: ../../content/administration/install/install.rst:514 -#: ../../content/administration/install/install.rst:698 +#: ../../content/administration/install/install.rst:525 +#: ../../content/administration/install/install.rst:720 msgid "PostgreSQL" msgstr "" @@ -898,7 +898,7 @@ msgid "Odoo will automatically be started at the end of the installation." msgstr "" #: ../../content/administration/install/install.rst:105 -#: ../../content/administration/install/install.rst:433 +#: ../../content/administration/install/install.rst:444 msgid "Linux" msgstr "" @@ -913,8 +913,8 @@ msgstr "" #: ../../content/administration/install/install.rst:113 #: ../../content/administration/install/install.rst:186 #: ../../content/administration/install/install.rst:313 -#: ../../content/administration/install/install.rst:492 -#: ../../content/administration/install/install.rst:676 +#: ../../content/administration/install/install.rst:503 +#: ../../content/administration/install/install.rst:698 msgid "Prepare" msgstr "" @@ -925,8 +925,8 @@ msgstr "" #: ../../content/administration/install/install.rst:123 #: ../../content/administration/install/install.rst:198 #: ../../content/administration/install/install.rst:380 -#: ../../content/administration/install/install.rst:566 -#: ../../content/administration/install/install.rst:748 +#: ../../content/administration/install/install.rst:577 +#: ../../content/administration/install/install.rst:770 msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in version `0.12.5 `_ for it to support headers and footers. See our `wiki `_ for more details on the various versions." msgstr "" @@ -1028,95 +1028,95 @@ msgid "Finally it provides greater control over the system's set up, and allows msgstr "" #: ../../content/administration/install/install.rst:257 -#: ../../content/administration/install/install.rst:436 -#: ../../content/administration/install/install.rst:620 +#: ../../content/administration/install/install.rst:447 +#: ../../content/administration/install/install.rst:642 msgid "Fetch the sources" msgstr "" #: ../../content/administration/install/install.rst:259 -#: ../../content/administration/install/install.rst:438 -#: ../../content/administration/install/install.rst:622 +#: ../../content/administration/install/install.rst:449 +#: ../../content/administration/install/install.rst:644 msgid "There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**." msgstr "" #: ../../content/administration/install/install.rst:262 -#: ../../content/administration/install/install.rst:441 -#: ../../content/administration/install/install.rst:625 +#: ../../content/administration/install/install.rst:452 +#: ../../content/administration/install/install.rst:647 msgid "Archive" msgstr "" #: ../../content/administration/install/install.rst:264 -#: ../../content/administration/install/install.rst:443 -#: ../../content/administration/install/install.rst:627 +#: ../../content/administration/install/install.rst:454 +#: ../../content/administration/install/install.rst:649 msgid "Community Edition:" msgstr "" #: ../../content/administration/install/install.rst:266 #: ../../content/administration/install/install.rst:272 -#: ../../content/administration/install/install.rst:445 -#: ../../content/administration/install/install.rst:451 -#: ../../content/administration/install/install.rst:629 -#: ../../content/administration/install/install.rst:635 +#: ../../content/administration/install/install.rst:456 +#: ../../content/administration/install/install.rst:462 +#: ../../content/administration/install/install.rst:651 +#: ../../content/administration/install/install.rst:657 msgid "`Official download page `_" msgstr "" #: ../../content/administration/install/install.rst:267 -#: ../../content/administration/install/install.rst:446 -#: ../../content/administration/install/install.rst:630 +#: ../../content/administration/install/install.rst:457 +#: ../../content/administration/install/install.rst:652 msgid "`GitHub repository `_" msgstr "" #: ../../content/administration/install/install.rst:268 -#: ../../content/administration/install/install.rst:447 -#: ../../content/administration/install/install.rst:631 +#: ../../content/administration/install/install.rst:458 +#: ../../content/administration/install/install.rst:653 msgid "`Nightly server `_" msgstr "" #: ../../content/administration/install/install.rst:270 -#: ../../content/administration/install/install.rst:449 -#: ../../content/administration/install/install.rst:633 +#: ../../content/administration/install/install.rst:460 +#: ../../content/administration/install/install.rst:655 msgid "Enterprise Edition:" msgstr "" #: ../../content/administration/install/install.rst:273 -#: ../../content/administration/install/install.rst:452 -#: ../../content/administration/install/install.rst:636 +#: ../../content/administration/install/install.rst:463 +#: ../../content/administration/install/install.rst:658 msgid "`GitHub repository `_" msgstr "" #: ../../content/administration/install/install.rst:278 -#: ../../content/administration/install/install.rst:457 -#: ../../content/administration/install/install.rst:641 +#: ../../content/administration/install/install.rst:468 +#: ../../content/administration/install/install.rst:663 msgid "Git" msgstr "" #: ../../content/administration/install/install.rst:280 -#: ../../content/administration/install/install.rst:459 -#: ../../content/administration/install/install.rst:643 +#: ../../content/administration/install/install.rst:470 +#: ../../content/administration/install/install.rst:665 msgid "The following requires `Git `_ to be installed on your machine and that you have basic knowledge of Git commands. To clone a Git repository, you must choose between cloning with HTTPS or SSH. If you do not know the difference between the two, the best option is most likely HTTPS. If you are following the :doc:`Getting started ` developer tutorial, or plan on contributing to Odoo source code, choose SSH." msgstr "" #: ../../content/administration/install/install.rst:287 -#: ../../content/administration/install/install.rst:466 -#: ../../content/administration/install/install.rst:650 +#: ../../content/administration/install/install.rst:477 +#: ../../content/administration/install/install.rst:672 msgid "**The Enterprise Git repository does not contain the full Odoo source code**. It is only a collection of extra add-ons. The main server code is in the Community version. Running the Enterprise version actually means running the server from the Community version with the addons-path option set to the folder with the Enterprise version. You need to clone both the Community and Enterprise repository to have a working Odoo Enterprise installation. See :ref:`setup/install/editions` to get access to the Enterprise repository." msgstr "" #: ../../content/administration/install/install.rst:296 -#: ../../content/administration/install/install.rst:475 -#: ../../content/administration/install/install.rst:659 +#: ../../content/administration/install/install.rst:486 +#: ../../content/administration/install/install.rst:681 msgid "Clone with HTTPS" msgstr "" #: ../../content/administration/install/install.rst:303 -#: ../../content/administration/install/install.rst:482 -#: ../../content/administration/install/install.rst:666 +#: ../../content/administration/install/install.rst:493 +#: ../../content/administration/install/install.rst:688 msgid "Clone with SSH" msgstr "" #: ../../content/administration/install/install.rst:316 -#: ../../content/administration/install/install.rst:495 -#: ../../content/administration/install/install.rst:679 +#: ../../content/administration/install/install.rst:506 +#: ../../content/administration/install/install.rst:701 msgid "Python" msgstr "" @@ -1129,14 +1129,14 @@ msgid "During installation, check **Add Python 3 to PATH**, then click **Customi msgstr "" #: ../../content/administration/install/install.rst:324 -#: ../../content/administration/install/install.rst:500 -#: ../../content/administration/install/install.rst:684 +#: ../../content/administration/install/install.rst:511 +#: ../../content/administration/install/install.rst:706 msgid "If Python 3 is already installed, make sure that the version is 3.7 or above, as previous versions are not compatible with Odoo." msgstr "" #: ../../content/administration/install/install.rst:331 -#: ../../content/administration/install/install.rst:507 -#: ../../content/administration/install/install.rst:691 +#: ../../content/administration/install/install.rst:518 +#: ../../content/administration/install/install.rst:713 msgid "Verify also that pip_ is installed for this version." msgstr "" @@ -1145,8 +1145,8 @@ msgid "Odoo uses PostgreSQL as database management system. `Download and install msgstr "" #: ../../content/administration/install/install.rst:343 -#: ../../content/administration/install/install.rst:525 -#: ../../content/administration/install/install.rst:708 +#: ../../content/administration/install/install.rst:536 +#: ../../content/administration/install/install.rst:730 msgid "By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to create a new PostgreSQL user:" msgstr "" @@ -1183,8 +1183,8 @@ msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Crea msgstr "" #: ../../content/administration/install/install.rst:359 -#: ../../content/administration/install/install.rst:537 -#: ../../content/administration/install/install.rst:720 +#: ../../content/administration/install/install.rst:548 +#: ../../content/administration/install/install.rst:742 msgid "Dependencies" msgstr "" @@ -1193,14 +1193,14 @@ msgid "Before installing the dependencies, you must download and install the `Bu msgstr "" #: ../../content/administration/install/install.rst:365 -#: ../../content/administration/install/install.rst:551 -#: ../../content/administration/install/install.rst:722 +#: ../../content/administration/install/install.rst:562 +#: ../../content/administration/install/install.rst:744 msgid "Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo community directory." msgstr "" #: ../../content/administration/install/install.rst:368 -#: ../../content/administration/install/install.rst:554 -#: ../../content/administration/install/install.rst:725 +#: ../../content/administration/install/install.rst:565 +#: ../../content/administration/install/install.rst:747 msgid "It can be preferable to not mix python modules packages between different instances of Odoo or with your system. You can use virtualenv_ to create isolated Python environments." msgstr "" @@ -1209,8 +1209,8 @@ msgid "Navigate to the path of your Odoo Community installation (`CommunityPath` msgstr "" #: ../../content/administration/install/install.rst:385 -#: ../../content/administration/install/install.rst:571 -#: ../../content/administration/install/install.rst:753 +#: ../../content/administration/install/install.rst:582 +#: ../../content/administration/install/install.rst:775 msgid "For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is needed:" msgstr "" @@ -1219,8 +1219,8 @@ msgid "Download and install `nodejs `_." msgstr "" #: ../../content/administration/install/install.rst:389 -#: ../../content/administration/install/install.rst:575 -#: ../../content/administration/install/install.rst:757 +#: ../../content/administration/install/install.rst:586 +#: ../../content/administration/install/install.rst:779 msgid "Install `rtlcss`:" msgstr "" @@ -1229,32 +1229,32 @@ msgid "Edit the System Environment's variable `PATH` to add the folder where `rt msgstr "" #: ../../content/administration/install/install.rst:399 -#: ../../content/administration/install/install.rst:582 -#: ../../content/administration/install/install.rst:764 +#: ../../content/administration/install/install.rst:593 +#: ../../content/administration/install/install.rst:786 msgid "Running Odoo" msgstr "" #: ../../content/administration/install/install.rst:401 -#: ../../content/administration/install/install.rst:584 -#: ../../content/administration/install/install.rst:766 +#: ../../content/administration/install/install.rst:595 +#: ../../content/administration/install/install.rst:788 msgid "Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the command-line interface of the server. It is located at the root of the Odoo Community directory." msgstr "" #: ../../content/administration/install/install.rst:404 -#: ../../content/administration/install/install.rst:587 -#: ../../content/administration/install/install.rst:769 +#: ../../content/administration/install/install.rst:598 +#: ../../content/administration/install/install.rst:791 msgid "To configure the server, you can either specify :ref:`command-line arguments ` or a :ref:`configuration file `." msgstr "" #: ../../content/administration/install/install.rst:407 -#: ../../content/administration/install/install.rst:590 -#: ../../content/administration/install/install.rst:772 +#: ../../content/administration/install/install.rst:601 +#: ../../content/administration/install/install.rst:794 msgid "For the Enterprise edition, you must add the path to the `enterprise` addons to the `addons-path` argument. Note that it must come before the other paths in `addons-path` for addons to be loaded correctly." msgstr "" #: ../../content/administration/install/install.rst:411 -#: ../../content/administration/install/install.rst:594 -#: ../../content/administration/install/install.rst:776 +#: ../../content/administration/install/install.rst:605 +#: ../../content/administration/install/install.rst:798 msgid "Common necessary configurations are:" msgstr "" @@ -1263,117 +1263,135 @@ msgid "PostgreSQL user and password." msgstr "" #: ../../content/administration/install/install.rst:414 -#: ../../content/administration/install/install.rst:599 -#: ../../content/administration/install/install.rst:781 +#: ../../content/administration/install/install.rst:610 +#: ../../content/administration/install/install.rst:803 msgid "Custom addon paths beyond the defaults, to load your own modules." msgstr "" #: ../../content/administration/install/install.rst:416 -#: ../../content/administration/install/install.rst:601 -#: ../../content/administration/install/install.rst:783 +#: ../../content/administration/install/install.rst:612 +#: ../../content/administration/install/install.rst:805 msgid "A typical way to run the server would be:" msgstr "" #: ../../content/administration/install/install.rst:423 -msgid "Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password and `mydb` is the default database to serve on `localhost:8069`." +msgid "Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password and `mydb` is the name of the PostgreSQL database." msgstr "" -#: ../../content/administration/install/install.rst:428 -#: ../../content/administration/install/install.rst:612 -#: ../../content/administration/install/install.rst:799 -msgid ":doc:`The exhaustive list of arguments for odoo-bin `." +#: ../../content/administration/install/install.rst:427 +#: ../../content/administration/install/install.rst:622 +#: ../../content/administration/install/install.rst:820 +msgid "After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open http://localhost:8069 in your web browser and log in with the base administrator account: Use `admin` for the :guilabel:`Email` and, again, `admin` for the :guilabel:`Password`. That's it, you just logged into your own Odoo database!" msgstr "" -#: ../../content/administration/install/install.rst:497 +#: ../../content/administration/install/install.rst:433 +#: ../../content/administration/install/install.rst:628 +#: ../../content/administration/install/install.rst:826 +msgid "From there, you can create and manage new :doc:`users `." +msgstr "" + +#: ../../content/administration/install/install.rst:435 +#: ../../content/administration/install/install.rst:630 +#: ../../content/administration/install/install.rst:828 +msgid "The user account you use to log into Odoo's web interface differs from the :option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/install/install.rst:439 +#: ../../content/administration/install/install.rst:634 +#: ../../content/administration/install/install.rst:832 +msgid ":doc:`The exhaustive list of CLI arguments for odoo-bin `." +msgstr "" + +#: ../../content/administration/install/install.rst:508 msgid "Odoo requires Python 3.7 or later to run. Use your package manager to download and install Python 3 on your machine if it is not already done." msgstr "" -#: ../../content/administration/install/install.rst:516 +#: ../../content/administration/install/install.rst:527 msgid "Odoo uses PostgreSQL as database management system. Use your package manager to download and install PostgreSQL (supported version: 10.0 and later)." msgstr "" -#: ../../content/administration/install/install.rst:519 +#: ../../content/administration/install/install.rst:530 msgid "On Debian/Unbuntu, it can be achieved by executing the following:" msgstr "" -#: ../../content/administration/install/install.rst:533 -#: ../../content/administration/install/install.rst:716 +#: ../../content/administration/install/install.rst:544 +#: ../../content/administration/install/install.rst:738 msgid "Because your PostgreSQL user has the same name as your Unix login, you will be able to connect to the database without password." msgstr "" -#: ../../content/administration/install/install.rst:539 +#: ../../content/administration/install/install.rst:550 msgid "For libraries using native code, it is necessary to install development tools and native dependencies before the Python dependencies of Odoo. They are available in `-dev` or `-devel` packages for Python, PostgreSQL, libxml2, libxslt1, libevent, libsasl2 and libldap2." msgstr "" -#: ../../content/administration/install/install.rst:543 +#: ../../content/administration/install/install.rst:554 msgid "On Debian/Unbuntu, the following command should install all the required libraries:" msgstr "" -#: ../../content/administration/install/install.rst:557 -#: ../../content/administration/install/install.rst:728 +#: ../../content/administration/install/install.rst:568 +#: ../../content/administration/install/install.rst:750 msgid "Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:" msgstr "" -#: ../../content/administration/install/install.rst:574 +#: ../../content/administration/install/install.rst:585 msgid "Download and install **nodejs** and **npm** with your package manager." msgstr "" -#: ../../content/administration/install/install.rst:596 -#: ../../content/administration/install/install.rst:778 +#: ../../content/administration/install/install.rst:607 +#: ../../content/administration/install/install.rst:800 msgid "PostgreSQL user and password. Odoo has no defaults beyond `psycopg2's defaults `_: connects over a UNIX socket on port `5432` with the current user and no password." msgstr "" -#: ../../content/administration/install/install.rst:608 -#: ../../content/administration/install/install.rst:790 -msgid "Where `CommunityPath` is the path of the Odoo Community installation and `mydb` is the default database to serve on `localhost:8069`." +#: ../../content/administration/install/install.rst:619 +#: ../../content/administration/install/install.rst:812 +msgid "Where `CommunityPath` is the path of the Odoo Community installation and `mydb` is the name of the PostgreSQL database." msgstr "" -#: ../../content/administration/install/install.rst:617 +#: ../../content/administration/install/install.rst:639 msgid "Mac OS" msgstr "" -#: ../../content/administration/install/install.rst:681 +#: ../../content/administration/install/install.rst:703 msgid "Odoo requires Python 3.7 or later to run. Use your preferred package manager (homebrew_, macports_) to download and install Python 3 on your machine if it is not already done." msgstr "" -#: ../../content/administration/install/install.rst:700 +#: ../../content/administration/install/install.rst:722 msgid "Odoo uses PostgreSQL as database management system. Use `postgres.app `_ to download and install PostgreSQL (supported version: 10.0 and later)." msgstr "" -#: ../../content/administration/install/install.rst:704 +#: ../../content/administration/install/install.rst:726 msgid "To make the command line tools bundled with `postgres.app` available, make sure to setup your `$PATH` variable by following the `Postgres.app CLI Tools Instructions `_." msgstr "" -#: ../../content/administration/install/install.rst:737 +#: ../../content/administration/install/install.rst:759 msgid "Non-Python dependencies need to be installed with a package manager:" msgstr "" -#: ../../content/administration/install/install.rst:739 +#: ../../content/administration/install/install.rst:761 msgid "Download and install the **Command Line Tools**:" msgstr "" -#: ../../content/administration/install/install.rst:745 +#: ../../content/administration/install/install.rst:767 msgid "Download and install the package manager of your choice (homebrew_, macports_)." msgstr "" -#: ../../content/administration/install/install.rst:746 +#: ../../content/administration/install/install.rst:768 msgid "Install non-python dependencies." msgstr "" -#: ../../content/administration/install/install.rst:756 +#: ../../content/administration/install/install.rst:778 msgid "Download and install **nodejs** with your preferred package manager (homebrew_, macports_)." msgstr "" -#: ../../content/administration/install/install.rst:794 +#: ../../content/administration/install/install.rst:816 msgid "Some versions of python on Mac might lead to the following error message: `current limit exceeds maximum limit`. In that case, add the following parameter `--limit-memory-hard 0` to avoid the problem." msgstr "" -#: ../../content/administration/install/install.rst:804 +#: ../../content/administration/install/install.rst:837 #: ../../content/administration/maintain/update.rst:147 msgid "Docker" msgstr "" -#: ../../content/administration/install/install.rst:806 +#: ../../content/administration/install/install.rst:839 msgid "The full documentation on how to use Odoo with Docker can be found on the official Odoo `docker image `_ page." msgstr "" @@ -2179,7 +2197,7 @@ msgid "The URL you want to use for your database (e.g., `example.odoo.com`)" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:56 -msgid "Which brand you want to migrate" +msgid "Which branch you want to migrate" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:57 diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 96aa45995..4b855bcfd 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-09-01 15:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -204,13 +204,13 @@ msgstr "" #: ../../content/applications/finance/accounting/bank/misc/interbank.rst:14 #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:69 #: ../../content/applications/finance/accounting/bank/reconciliation/use_cases.rst:16 -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:22 +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:16 #: ../../content/applications/finance/accounting/bank/setup/manage_cash_register.rst:9 #: ../../content/applications/finance/accounting/bank/setup/outstanding_accounts.rst:20 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:32 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:29 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:290 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:331 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:332 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:34 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/germany.rst:58 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/italy.rst:18 @@ -229,8 +229,9 @@ msgstr "" #: ../../content/applications/finance/accounting/payables/supplier_bills/invoice_digitization.rst:22 #: ../../content/applications/finance/accounting/payables/supplier_bills/manage.rst:31 #: ../../content/applications/finance/accounting/receivables/customer_invoices/cash_rounding.rst:14 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:55 #: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:20 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:42 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:46 #: ../../content/applications/finance/accounting/receivables/customer_payments/batch.rst:15 #: ../../content/applications/finance/accounting/receivables/customer_payments/batch_sdd.rst:20 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:39 @@ -1151,119 +1152,99 @@ msgid "`Odoo Tutorials: Accounting Basics `_" msgstr "" #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:3 -msgid "Manage a bank in a foreign currency" +msgid "Manage a bank account in a foreign currency" msgstr "" #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:5 -msgid "In Odoo, every transaction is recorded in the default currency of the company. Reports are all based on the currency of the company. But for transactions occurring in another currency, Odoo stores both the value in the currency of the company and the value in the currency of the transaction." +msgid "In Odoo, every transaction is recorded in the default currency of the company, and reports are all based on that default currency. When you have a bank account in a foreign currency, for every transaction, Odoo stores two values:" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:11 -msgid "When you have a bank account in a foreign currencies, for every transaction, Odoo stores two values:" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:9 +msgid "The debit/credit in the currency of the *company*;" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:14 -msgid "The debit/credit in the currency of the company" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:10 +msgid "The debit/credit in the currency of the *bank account*." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:16 -msgid "The debit/credit in the currency of the bank account" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:12 +msgid "Currency rates are updated automatically using the web services of a banking institution. By default, Odoo uses the European Central Bank's web services but other options are available." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:18 -msgid "Currency rates are updated automatically using yahoo.com, or the European Central bank web-services." +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:19 +msgid "Activate multi-currencies" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:25 -msgid "Activate the multi-currency feature" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:21 +msgid "To work with multiple currencies, go to :menuselection:`Accounting --> Configuration --> Settings --> Currencies` and tick :guilabel:`Multi-Currencies`. Under :guilabel:`Post Exchange difference entries in:`, provide a :guilabel:`Journal`, a :guilabel:`Gain Account`, a :guilabel:`Loss Account`, and then click on :guilabel:`Save`." msgstr "" #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:27 -msgid "In order to allow your company to work with multiple currencies, you should activate the multi-currency mode. In the accounting application, go into :menuselection:`Configuration --> Settings --> Accounting & Finance Features` make sure the **Allow Multi-currencies** box is ticked. Provide a **Currency Exchange Gain / Loss** account, then click on **Apply**." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:34 msgid "Configure currencies" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:36 -msgid "Once the Odoo is configured to support multiple currencies, you should activate the currencies you plan to work with. To do that, go to the menu :menuselection:`Configuration --> Currencies`. All the currencies are created by default, but you should activate the ones you plan to support (to activate a currency, check its \"Active\" field)." +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:29 +msgid "Once Odoo is configured to support multiple currencies, they are all created by default, but not necessarily active. To activate the new currencies, click on :guilabel:`Activate Other Currencies` under the :guilabel:`Multi-Currencies` setting or go to :menuselection:`Accounting --> Configuration --> Accounting: Currencies`." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:42 -msgid "After having activated the currencies, you can configure the parameters to automate the currency rate update. These options are also in the settings of the Accounting application, in the bottom of the page:" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:34 +msgid "When the currencies are activated, you can choose to **automate** the currency rate update, or leave it on **manual**. To configure the rate update, go back to :menuselection:`Accounting --> Configuration --> Settings --> Currencies`, check :guilabel:`Automatic Currency Rates`, set :guilabel:`Interval` to your desired frequency, and then click on :guilabel:`Save`. You also have the option to choose the :guilabel:`Service` you wish to obtain currency rates from." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:49 -msgid "Click on the **Update Now** link to update the currency rates now." +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:40 +msgid "Click on the Update now button (:guilabel:`🗘`) besides the :guilabel:`Next Run` field to update the currency rates manually." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:52 +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:44 msgid "Create a new bank account" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:54 -msgid "In the accounting application, we first go to :menuselection:`Configuration --> Accounting / Bank account`, and we create a new one." +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:46 +msgid "In the accounting application, go to :menuselection:`Accounting --> Configuration --> Journals` and create a new one. Enter a :guilabel:`Journal Name` and set the :guilabel:`Type` to `Bank`. In the :guilabel:`Journal Entries` tab, enter a **short code**, a **currency**, and then finally click on the :guilabel:`Bank Account` field to create a new account. In the pop-up window of the account creation, enter a name, a code (ex.: 550007), set its type to `Bank and Cash`, set a currency type, and save. When you are back on the **journal**, click on the :guilabel:`Account Number` field, and in the pop-up window, fill out the :guilabel:`Account Number`, :guilabel:`Bank` of your account, and save." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:60 -msgid "Once you save this bank account, Odoo will create all the documents for you:" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:59 +msgid "Upon creation of the journal, Odoo automatically links the bank account to the journal. It can be found under :menuselection:`Accounting --> Configuration --> Accounting: Chart of Accounts`." msgstr "" #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:63 -msgid "An account in the trial balance" +msgid "Vendor bill in a foreign currency" msgstr "" #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:65 -msgid "A journal in your dashboard" +msgid "To pay a bill in a foreign currency, simply select the currency next to the :guilabel:`Journal` field and register the payment. Odoo automatically creates and posts the foreign **exchange gain or loss** as a new journal entry." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:67 -msgid "Information about the bank account in the footer of your invoices if checked the box **Show in Invoices Footer**" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:74 +msgid "Note that you can pay a foreign bill with another currency. In that case, Odoo automatically converts between the two currencies." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:71 -msgid "Example: A vendor bill in a foreign currency" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:78 +msgid "Unrealized Currency Gains/Losses Report" msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:73 -msgid "Based on the above example, let's assume we receive the following bill from a supplier in China." +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:80 +msgid "This report gives an overview of all unrealized amounts in a foreign currency on your balance sheet, and allows you to adjust an entry or manually set an exchange rate. To access this report, go to :menuselection:`Reporting --> Management: Unrealized Currency Gains/Losses`. From here, you have access to all open entries in your **balance sheet**." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:76 -msgid "In the :menuselection:`Purchase --> Vendor Bills` , this is what you could see:" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:89 +msgid "If you wish to use a different currency rate than the one set in :menuselection:`Accounting --> Configuration --> Settings --> Currencies`, click the :guilabel:`Exchange Rates` button and change the rate of the foreign currencies in the report." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:81 -msgid "Once you are ready to pay this bill, click on register payment on the bill to record a payment." +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:97 +msgid "When manually changing **exchange rates**, a yellow banner appears allowing you to reset back to Odoo's rate. To do so, simply click on :guilabel:`Reset to Odoo's Rate`." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:87 -msgid "That's all you have to do. Odoo will automatically post the foreign exchange gain or loss at the reconciliation of the payment with the invoice, depending if the currency rate increased or decreased between the invoice and the payment date." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:92 -msgid "Note that you can pay a foreign bill with another currency. In such a case, Odoo will automatically convert between the two currencies." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:96 -msgid "Customers Statements" -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:98 -msgid "Customers and vendor statements are managed in the currency of the invoice. So, the amount due by your customer (to your vendor) is always expressed in the currency of the invoice." -msgstr "" - -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:102 -msgid "If you have several invoices with different currencies for the same customer, Odoo will split the customer statement by currency, as shown in the report below." +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:104 +msgid "In order to update your **balance sheet** with the amount of the :guilabel:`adjustment` column, click on the :guilabel:`Adjustment Entry` button. In the pop-up window, select a :guilabel:`Journal`, :guilabel:`Expense Account` and :guilabel:`Income Account` to calculate and process the **unrealized gains and losses**." msgstr "" #: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:109 -msgid "In the above report, the account receivable associated to Camptocamp is not managed in a secondary currency, which means that it keeps every transaction in its own currency. If you prefer, you can set the account receivable for this customer in a secondary currency and all its debts will automatically be converted to this currency." +msgid "You can set the date of the report in the :guilabel:`Date` field. Odoo automatically reverses the booking entry to the date set in :guilabel:`Reversal Date`." msgstr "" -#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:115 -msgid "In such a case, the customer statement always has only one currency. In general, this is not what the customer expect as he prefers to see the amounts in the currency of the invoices he received;" +#: ../../content/applications/finance/accounting/bank/setup/foreign_currency.rst:112 +msgid "Once posted, the :guilabel:`adjustment` column should indicate `0.00`, meaning all **unrealized gains/losses** have been adjusted." msgstr "" #: ../../content/applications/finance/accounting/bank/setup/manage_cash_register.rst:3 @@ -2059,7 +2040,7 @@ msgid "You can also get the last number used in AFIP for a specific Document Typ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/argentina.rst:515 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:651 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:653 #: ../../content/applications/finance/accounting/others/multicurrencies/invoices_payments.rst:64 msgid "Vendor Bills" msgstr "" @@ -2274,7 +2255,7 @@ msgid "**l10n_cl_edi:** Includes all technical and functional requirements to ge msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:26 -msgid "**l10n_cl_reports:** Adds the reports Propuesta F29 y Balance Tributario (8 columnas)." +msgid "**l10n_cl_reports:** Adds the reports Propuesta F29 y Balance Tributario (8 columnas)." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:32 @@ -2336,19 +2317,19 @@ msgid "Certificate" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:103 -msgid "In order to generate the electronic invoice signature, a digital certificate with the extension ``.pfx`` is required, proceed to this section and load your file and password." +msgid "In order to generate the electronic invoice signature, a digital certificate with the extension ``pfx`` is required, proceed to this section and load your file and password." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:114 -msgid "A certificate can be shared between several users. If this is the case leave the user field empty, so all your billing users can use the same one. On the other hand, if you need to restrict the certificate for a particular user, just define the users in the certificate." +msgid "A certificate can be shared between several users. If this is the case leave the user field empty, so all your billing users can use the same one. On the other hand, if you need to restrict the certificate for a particular user, just define the users in the certificate." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:119 -msgid "In some cases, depending on the certificate format, it is possible that the field Subject Serial Number is not loaded automatically. If this is the case, you can manually edit this field by filling it with the Certificate’s legal representative RUT." +msgid "In some cases, depending on the certificate format, it is possible that the field Subject Serial Number is not loaded automatically. If this is the case, you can manually edit this field by filling it with the Certificate's legal representative RUT." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:124 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:702 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:871 msgid "Financial Reports" msgstr "" @@ -2445,7 +2426,7 @@ msgid "The document type is essential information that needs to be displayed in msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:233 -msgid "Each document type can have a unique sequence per company. As part of the localization, the Document Type includes the country on which the document is applicable and the data is created automatically when the localization module is installed." +msgid "Each document type can have a unique sequence per company. As part of the localization, the Document Type includes the country on which the document is applicable and the data is created automatically when the localization module is installed." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:253 @@ -2526,362 +2507,365 @@ msgstr "" msgid "**Use Documents**: This field is used to define if the journal will use Document Types. It is only applicable to Purchase and Sales journals that can be related to the different sets of document types available in Chile. By default, all the sales journals created will use documents." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:308 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:307 msgid "For the Chilean localization, it is important to define the default Debit and Credit accounts as they are required for one of the debit notes use cases." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:312 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:313 msgid "CAF" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:314 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:315 msgid "A CAF (Folio Authorization Code) is required, for each document type that is issued to your customers, the CAF is a file the SII provides to the Emisor with the folio/sequence authorized for the electronic invoice documents." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:318 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:319 msgid "Your company can make several requests for folios and obtain several CAFs, each one associated with different ranges of folios. The CAFs are shared within all the journals, this means that you only need one active CAF per document type and it will be applied on all journals." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:322 -msgid "Please refer to the SII documentation to check the detail on how to acquire the CAF: `SII Timbraje `_." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:323 +msgid "Please refer to the `SII documentation `_ to check the detail on how to acquire the CAF." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:326 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:327 msgid "The CAFs required by the SII are different from Production to Test (Certification mode). Make sure you have the correct CAF set depending on your environment." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:333 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:334 msgid "Once you have the CAF files you need to associate them with a document type in Odoo, in order to add a CAF, just follow these steps:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:336 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:337 msgid "Access to :menuselection:`Accounting --> Settings --> CAF`" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:337 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:338 msgid "Upload the file." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:338 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:339 msgid "Save the CAF." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:344 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:345 msgid "Once loaded, the status changes to *In Use*. At this moment, when a transaction is used for this document type, the invoice number takes the first folio in the sequence." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:348 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:349 msgid "In case you have used some folios in your previous system, make sure you set the next valid folio when the first transaction is created." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:354 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:355 msgid "Usage and Testing" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:357 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:358 msgid "Electronic Invoice Workflow" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:359 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:360 msgid "In the Chilean localization the electronic Invoice workflow covers the Emission of Customer Invoices and the reception of Vendor Bills, in the next diagram we explain how the information transmitted to the SII and between the customers and Vendors." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:369 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:370 msgid "Customer invoice Emission" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:371 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:372 msgid "After the partners and journals are created and configured, the invoices are created in the standard way, for Chile one of the differentiators is the document type which is selected automatically based on the Taxpayer." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:375 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:376 msgid "You can manually change the document type if needed." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:382 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:383 msgid "Documents type 33: Electronic Invoice must have at least one item with tax, otherwise the SII rejects the document validation." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:386 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:389 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:813 msgid "Validation and DTE Status" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:388 -msgid "When all the invoice information is filled, either manually or automatically when it’s created from a sales order, proceed to validate the invoice. After the invoice is posted:" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:391 +msgid "When all the invoice information is filled, either manually or automatically when it's created from a sales order, proceed to validate the invoice. After the invoice is posted:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:391 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:394 msgid "The DTE File (Electronic Tax Document) is created automatically and added in the chatter." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:392 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:395 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:759 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:823 msgid "The DTE SII status is set as: Pending to be sent." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:398 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:401 msgid "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. The DTE status workflow is as follows:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:407 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:410 msgid "In the first step the DTE is sent to the SII, you can manually send it using the button: Enviar Ahora, a SII Tack number is generated and assigned to the invoice, you can use this number to check the details the SII sent back by email. The DTE status is updated to Ask for Status." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:412 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:415 msgid "Once the SII response is received Odoo updates the DTE Status, in case you want to do it manually just click on the button: Verify on SII. The result can either be Accepted, Accepted With Objection or Rejected." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:421 -msgid "There are several internal status in the SII before you get Acceptance or Rejection, in case you click continuously the Button Verify in SII, you will receive in the chatter the detail of those intermediate statuses:" -msgstr "" - -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:429 -msgid "The final response from the SII, can take on of these values:" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:424 +msgid "There are several internal status in the SII before you get Acceptance or Rejection, in case you click continuously the Button Verify in SII, you will receive in the chatter the detail of those intermediate statuses:" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:432 -msgid "**Accepted:** Indicates the invoice information is correct, our document is now fiscally valid and it’s automatically sent to the customer." +msgid "The final response from the SII, can take on of these values:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:435 -msgid "**Accepted with objections:** Indicates the invoice information is correct but a minor issue was identified, nevertheless our document is now fiscally valid and it’s automatically sent to the customer." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:434 +msgid "**Accepted:** Indicates the invoice information is correct, our document is now fiscally valid and it's automatically sent to the customer." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:443 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:437 +msgid "**Accepted with objections:** Indicates the invoice information is correct but a minor issue was identified, nevertheless our document is now fiscally valid and it's automatically sent to the customer." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:445 msgid "**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 SII, if it is properly configured in Odoo, the details are also retrieved in the chatter once the email server is processed." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:448 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:450 msgid "If the invoice is Rejected please follow this steps:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:450 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:452 msgid "Change the document to draft." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:451 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:453 msgid "Make the required corrections based on the message received from the SII." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:452 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:454 msgid "Post the invoice again." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:460 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:462 msgid "Crossed references" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:462 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:464 msgid "When the Invoice is created as a result of another fiscal document, the information related to the originator document must be registered in the Tab Cross Reference, which is commonly used for credit or debit notes, but in some cases can be used on Customer Invoices as well. In the case of the credit and debit notes, they are set automatically by Odoo:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:472 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:474 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:450 msgid "Invoice PDF Report" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:474 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:476 msgid "Once the invoice is accepted and validated by the SII and the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally valid:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:482 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:484 msgid "If you are hosted in Odoo SH or On-Premise, you should manually install the ``pdf417gen`` library. Use the following command to install it: ``pip install pdf417gen``." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:486 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:488 msgid "Commercial Validation" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:488 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:490 msgid "Once the invoice has been sent to the customer:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:490 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:492 msgid "DTE partner status changes to “Sent”." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:491 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:493 msgid "The customer must send a reception confirmation email." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:492 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:494 msgid "Subsequently, if all the commercial terms and invoice data are correct, they will send the Acceptance confirmation, otherwise they send a Claim." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:494 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:496 msgid "The field DTE acceptation status is updated automatically." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:502 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:504 msgid "Processed for Claimed invoices" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:504 -msgid "Once the invoice has been Accepted by the SII **it can not be cancelled in Odoo**. In case you get a Claim for your customer the correct way to proceed is with a Credit Note to either cancel the Invoice or correct it. Please refer to the Credit Notes section for more details." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:506 +msgid "Once the invoice has been Accepted by the SII **it can not be cancelled in Odoo**. In case you get a Claim for your customer the correct way to proceed is with a Credit Note to either cancel the Invoice or correct it. Please refer to the :ref:`chile/credit-notes` section for more details." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:513 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:515 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:426 msgid "Common Errors" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:515 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:517 msgid "There are multiple reasons behind a rejection from the SII, but these are some of the common errors you might have and which is the related solution." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:518 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:520 msgid "Error: ``RECHAZO- DTE Sin Comuna Origen.``" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:520 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:522 msgid "*Hint:* Make sure the Company Address is properly filled including the State and City." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:522 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:524 msgid "Error en Monto: ``- IVA debe declararse.``" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:524 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:528 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:526 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:530 msgid "*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:526 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:528 msgid "Error: ``Rut No Autorizado a Firmar.``" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:530 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:532 msgid "Error: ``Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : (Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) > 6 meses.``" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:533 -msgid "*Hint:* Try to add a new CAF related to this document as the one you’re using is expired." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:535 +msgid "*Hint:* Try to add a new CAF related to this document as the one you're using is expired." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:535 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:537 msgid "Error: ``Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element is not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).``" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:538 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:540 msgid "*Hint:* Make sure the field Document Type and VAT are set either in the Customer and in the main company." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:541 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:543 msgid "GLOSA: ``Usuario sin permiso de envio.``" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:543 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:545 msgid "*Hint:* This error indicates that most likely, your company has not passed the `Certification process `_ in the SII - Sistema de Facturación de Mercado. If this is the case, please contact your Account Manager or Customer Support as this certification is not part of the the Odoo services, but we can give you some alternatives." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:552 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:554 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:556 msgid "Credit Notes" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:554 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:556 msgid "When a cancellation or correction is needed over a validated invoice, a credit note must be generated. It is important to consider that a CAF file is required for the Credit Note, which is identified as document 64 in the SII." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:563 -msgid "Refer to the CAF section where we described the process to load the CAF on each document type." -msgstr "" - -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:567 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:619 -msgid "Use Cases" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:566 +msgid "Refer to the :ref:`CAF section ` where we described the process to load the CAF on each document type." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:570 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:622 +msgid "Use Cases" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:573 msgid "Cancel Referenced document" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:572 -msgid "In case you need to cancel or invalid an Invoice, use the button Add Credit note and select Full Refund, in this case the SII reference Code is automatically set to: Anula Documento de referencia." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:575 +msgid "In case you need to cancel or invalid an Invoice, use the button Add Credit note and select Full Refund, in this case the SII reference Code is automatically set to: Anula Documento de referencia." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:580 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:583 msgid "Corrects Referenced Document Text" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:582 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:585 msgid "If a correction in the invoice information is required, for example the Street Name, use the button Add Credit note,select Partial Refund and select the option “Solo corregir Texto”. In this case the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:590 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:593 msgid "Odoo creates a Credit Note with the corrected text in an invoice and price 0." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:597 -msgid "It’s important to define the default credit account in the Sales journal as it is taken for this use case in specific." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:600 +msgid "It's important to define the default credit account in the Sales journal as it is taken for this use case in specific." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:601 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:604 msgid "Corrects Referenced Document Amount" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:603 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:606 msgid "When a correction on the amounts is required, use the button Add Credit note and select Partial Refund. In this case the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:612 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:615 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:584 msgid "Debit Notes" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:614 -msgid "As part of the Chilean localization, besides creating credit notes from an existing document you can also create debit Notes. For this just use the button “Add Debit Note”. The two main use cases for debit notes are detailed below." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:617 +msgid "As part of the Chilean localization, besides creating credit notes from an existing document you can also create debit Notes. For this just use the button “Add Debit Note”. The two main use cases for debit notes are detailed below." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:622 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:625 msgid "Add debt on Invoices" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:624 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:627 msgid "The most common use case for debit notes is to increase the value of an existing invoice, you need to select option 3 in the field Reference code SII:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:632 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:635 msgid "In this case Odoo automatically includes the source invoice in the cross reference section:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:639 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:642 msgid "Cancel Credit Notes" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:641 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:644 msgid "In Chile the debits notes are used to cancel a validated Credit Note, in this case just select the button Add debit note and select the first option in the wizard: *1: Anula Documentos de referencia.*" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:653 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:655 msgid "As part of the Chilean localization, you can configure your Incoming email server as the same you have register in the SII in order to:" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:656 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:658 msgid "Automatically receive the vendor bills DTE and create the vendor bill based on this information." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:657 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:659 msgid "Automatically Send the reception acknowledgement to your vendor." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:658 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:660 msgid "Accept or Claim the document and send this status to your vendor." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:662 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:663 msgid "Reception" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:664 -msgid "As soon as the vendor email with the attached DTE is received: 1. The vendor Bill mapping all the information included in the xml. 2. An email is sent to the vendor with the Reception acknowledgement. 3. The DTE status is set as: Acuse de Recibido Enviado" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:665 +msgid "As soon as the vendor email with the attached DTE is received: 1. The vendor Bill mapping all the information included in the xml. 2. An email is sent to the vendor with the Reception acknowledgement. 3. The DTE status is set as: Acuse de Recibido Enviado" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:674 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:675 msgid "Acceptation" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:676 -msgid "If all the commercial information is correct on your vendor bill, you can accept the document using the button: Aceptar Documento, once this is done the DTE Acceptation Status changes to: Accepted and an email of acceptance is sent to the vendor." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:677 +msgid "If all the commercial information is correct on your vendor bill then you can accept the document using the :guilabel:`Aceptar Documento` button. Once this is done the DTE Acceptation Status changes to :guilabel:`Accepted`` and an email of acceptance is sent to the vendor." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:686 @@ -2889,36 +2873,177 @@ msgid "Claim" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:688 -msgid "In case there is a commercial issue or the information is not correct on your vendor bill, you can Claim the document before validating it, using the button: Claim, once this is done the DTE Acceptation Status change to: Claim and an email of acceptance is sent to the vendor." +msgid "In case there is a commercial issue or the information is not correct on your vendor bill, you can Claim the document before validating it, using the button: Claim, once this is done the DTE Acceptation Status change to: Claim and an email of acceptance is sent to the vendor." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:696 -msgid "If you claim a vendor bill, the status changes from draft to cancel automatically. Considering this as best practice, all the Claim documents should be canceled as they won’t be valid for your accounting records." +msgid "If you claim a vendor bill, the status changes from draft to cancel automatically. Considering this as best practice, all the Claim documents should be canceled as they won't be valid for your accounting records." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:705 -msgid "Balance Tributario de 8 Columnas" +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:701 +msgid "Delivery Guide" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:707 -msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time, so that a real and complete knowledge of the status of a company." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:703 +msgid "To install the Delivery Guide module, go to :menuselection:`Apps` and search for :guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery Guide`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:708 +msgid "*Chile - E-Invoicing Delivery Guide* has a dependency with *Chile - Facturación Electrónica*. Odoo will install the dependency automatically when the Delivery Guide module is installed." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:711 -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:727 -msgid "You can find this report in :menuselection:`Accounting --> Accounting --> Reports`" +msgid "The Delivery Guide module includes sending the DTE to SII and the stamp in PDF reports for deliveries." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:718 +msgid "Once all configurations have been made for electronic invoices (e.g., uploading a valid company certificate, setting up master data, etc.), Delivery Guides need their own CAFs. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the CAFs for electronic Delivery Guides." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:723 +msgid "Verify the following important information in the *Price for the Delivery Guide* configuration:" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:725 +msgid ":guilabel:`From Sales Order`: Delivery Guide takes the product price from the Sales Order and shows it on the document." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:727 +msgid ":guilabel:`From Product Template`: Odoo takes the price configured in the product template and shows it on the document." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:729 +msgid ":guilabel:`No show price`: no price is shown in the Delivery Guide." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:731 +msgid "Electronic delivery guides are used to move stock from one place to another and they can represent sales, sampling, consignment, internal transfers, and basically any product move." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:735 +msgid "Delivery Guide from a Sales Process" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:737 +msgid "When a Sales Order is created and confirmed, a Delivery Order is generated. After validating the Delivery Order, the option to create a Delivery Guide is activated." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:744 +msgid "When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up, showing the following:" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:751 +msgid "This warning message means the user needs to indicate the next sequence number Odoo has to take to generate the Delivery Guide, and only only happens the *first time* a Delivery Guide is created in Odoo. After the first document has been correctly generated, Odoo takes the CAFs next available number to generate the following Delivery Guide and so on." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:756 +msgid "After the Delivery Guide is created:" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:758 +msgid "The DTE file (Electronic Tax Document) is automatically created and added to the chatter." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:765 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:829 +msgid "The DTE Status is automatically updated by Odoo with a scheduled action that runs every day at night. To get a response from the SII immediately, press the :guilabel:`Send now to SII` button." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:768 +msgid "Once the Delivery Guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:776 +msgid "Electronic Receipt" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:778 +msgid "To install the Electronic Receipt module, go to :menuselection:`Apps` and search for :guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:783 +msgid "*Chile - Electronic Receipt* has a dependency with *Chile - Facturación Electrónica*. Odoo will install the dependency automatically when the E-invoicing Delivery Guide module is installed." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:786 +msgid "This module contains the electronic receipt and daily sales report, which are automatically sent to SII." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:793 +msgid "Once all configurations have been made for Electronic Invoices (e.g., uploading a valid company certificate, setting up master data, etc.), Electronic Receipts need their own CAFs. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the CAFs for Electronic Receipts." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:798 +msgid "Electronic Receipts are useful when clients do not need an Electronic Invoice. By default, there is a partner in the database called *Anonymous Final Consumer* with a generic RUT 66666666-6 and taxpayer type of *Final Consumer*. This partner can be used for Electronic Receipts or a new record may be created for the same purpose." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:803 +msgid "Although Electronic Receipts should be used for final consumers with a generic RUT, it can also be used for specific partners. After the partners and journals are created and configured, the Electronic Receipts are created in the standard way as Electronic Invoice, but the type of document :guilabel:`(39) Electronic Receipt` should be selected, like so:" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:815 +msgid "When all of the Electronic Receipt information is filled, either manually or automatically from a Sales Order, proceed to validate the receipt. By default, Electronic Invoice is selected as the Document Type, however in order to validate the receipt correctly, make sure to edit the Document Type and change to Electronic Receipt." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:820 +msgid "After the receipt is posted:" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:822 +msgid "The DTE file (Electronic Tax Document) is created automatically and added to the chatter." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:832 +msgid "Please refer to the :ref:`DTE Workflow ` for Electronic Invoices as the workflow for Electronic Receipt follows the same process." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:836 +msgid "Daily Sales Report" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:838 +msgid "Once Electronic Receipts have been created, the system creates a daily sales report containing all Electronic Receipts per day. This report is electronically stamped and sent to the SII overnight in XML format. These daily reports can be found in :menuselection:`Reports --> Daily Sales Reports`." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:846 +msgid "A list of daily reports is displayed with all daily DTE sent to SII." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:852 +msgid "If no Electronic Receipt was made on a particular day, the report is sent but it will not have any receipts in it. The report will also have an answer from the SII if it was accepted or rejected (depending on the company's certificate and validated receipts)." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:861 +msgid "For Chilean localization, note that the feature tax included in the price is *not* supported for the Electronic Receipt." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:864 +msgid "If a Daily Sales Report has already been created for a specific day in another system, the daily report in Odoo will be rejected due to the sequence number used. If that is the case, the user has to manually click on :guilabel:`Retry` in order for a new sequence number to be generated (this action is automatically done by Odoo). Afterwards, users can manually verify report status with SII or wait for Odoo to update status later at night." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:874 +msgid "Balance Tributario de 8 Columnas" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:876 +msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time, so that a real and complete knowledge of the status of a company." +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:880 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:896 +msgid "You can find this report in :menuselection:`Accounting --> Accounting --> Reports`" +msgstr "" + +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:887 msgid "Propuesta F29" msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:720 +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:889 msgid "The form F29 is a new system that the SII enabled to taxpayers, and that replaces the Purchase and Sales Books. This report is integrated by Purchase Register (CR) and the Sales Register (RV). Its purpose is to support the transactions related to VAT, improving its control and declaration." msgstr "" -#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:724 -msgid "This record is supplied by the electronic tax documents (DTE’s) that have been received by the SII." +#: ../../content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst:893 +msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the SII." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst:3 @@ -3867,10 +3992,12 @@ msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:16 #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/france.rst:182 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:93 msgid "Name" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:17 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:94 msgid "Technical name" msgstr "" @@ -3968,7 +4095,6 @@ msgid "These codes are confidential and should be stored safely." msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/egypt.rst:76 -#: ../../content/applications/finance/payment_acquirers/ogone.rst:9 msgid "Configuration on Odoo" msgstr "" @@ -4501,7 +4627,7 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/memento.rst:218 #: ../../content/applications/finance/accounting/getting_started/memento.rst:228 #: ../../content/applications/finance/accounting/getting_started/memento.rst:244 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:107 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:111 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:68 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:81 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:131 @@ -4533,7 +4659,7 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/memento.rst:218 #: ../../content/applications/finance/accounting/getting_started/memento.rst:228 #: ../../content/applications/finance/accounting/getting_started/memento.rst:244 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:107 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:111 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:68 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:81 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:131 @@ -7693,7 +7819,7 @@ msgid "EUR" msgstr "" #: ../../content/applications/finance/accounting/fiscal_localizations/localizations/peru.rst:140 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:113 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:117 msgid "1000" msgstr "" @@ -9045,6 +9171,7 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst:176 #: ../../content/applications/finance/accounting/getting_started/initial_configuration/setup.rst:193 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:52 #: ../../content/applications/finance/accounting/reporting/declarations/tax_returns.rst:125 #: ../../content/applications/finance/accounting/taxation/taxes/default_taxes.rst:40 msgid ":doc:`../../fiscal_localizations/overview/fiscal_localization_packages`" @@ -9460,7 +9587,7 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/memento.rst:86 #: ../../content/applications/finance/accounting/receivables/customer_invoices/credit_notes.rst:83 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:90 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:94 msgid "Journal Entries" msgstr "" @@ -9695,7 +9822,7 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/memento.rst:218 #: ../../content/applications/finance/accounting/getting_started/memento.rst:228 #: ../../content/applications/finance/accounting/getting_started/memento.rst:244 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:107 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:111 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:68 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:81 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:131 @@ -9704,8 +9831,8 @@ msgstr "" #: ../../content/applications/finance/accounting/getting_started/memento.rst:220 #: ../../content/applications/finance/accounting/getting_started/memento.rst:246 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:109 -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:111 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:113 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:115 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:70 #: ../../content/applications/finance/accounting/receivables/customer_payments/check.rst:133 msgid "Account Receivable" @@ -13212,6 +13339,194 @@ msgstr "" msgid "`Odoo Academy: Deferred Revenues (Recognition) `_" msgstr "" +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:3 +msgid "Electronic invoicing (:abbr:`EDI (electronic data interchange)`)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:5 +msgid "EDI, or electronic data interchange, is the inter-company communication of business documents, such as purchase orders and invoices, in a standard format. Sending documents according to an EDI standard ensures that the machine receiving the message can interpret the information correctly. Various EDI file formats exist and are available depending on your company's country." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:10 +msgid "EDI feature enables automating the administration between companies and might also be required by some governments for fiscal control or to facilitate the administration." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:13 +msgid "Electronic invoicing of your documents such as customer invoices, credit notes or vendor bills is one of the application of EDI." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:16 +msgid "Odoo supports, among others, the following formats." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:21 +msgid "Format Name" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:22 +msgid "Applicability" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:23 +msgid "Factur-X (CII)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:24 +msgid "Default format on Odoo (enabled by default)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:25 +msgid "Peppol BIS Billing 3.0 (UBL)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:26 +msgid "For companies whose countries are part of the `EAS list `_" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:28 +msgid "E-FFF" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:29 +msgid "For Belgian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:30 +msgid "XRechnung (UBL)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:31 +msgid "For German companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:32 +msgid "Fattura PA (IT)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:33 +msgid "For Italian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:34 +msgid "CFDI (4.0)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:35 +msgid "For Mexican companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:36 +msgid "Peru UBL 2.1" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:37 +msgid "For Peruvian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:38 +msgid "SII IVA Llevanza de libros registro (ES)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:39 +msgid "For Spanish companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:40 +msgid "UBL 2.1 (Columbia)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:41 +msgid "For Colombian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:42 +msgid "Egyptian Tax Authority" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:43 +msgid "For Egyptian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:44 +msgid "E-Invoice (IN)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:45 +msgid "For Indian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:46 +msgid "NLCIUS (Netherlands)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:47 +msgid "For Dutch companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:48 +msgid "EHF 3.0" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:49 +msgid "For Norwegian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:57 +msgid "Go to :menuselection:`Accounting --> Configuration --> Journals --> Customer Invoices --> Advanced Settings --> Electronic Invoicing` and enable the formats you need for this journal." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:64 +msgid "Once an electronic invoicing format is enabled, XML documents are generated when clicking on :guilabel:`Confirm` in documents such as invoices, credit notes, etc. These documents are either visible in the attachment section, or embedded in the PDF." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:69 +msgid "For E-FFF, the xml file only appears after having generated the PDF (:guilabel:`Print` or :guilabel:`Send & Print` button), since the PDF needs to be embedded inside the xml." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:71 +msgid "By default, the :guilabel:`Factur-X` option is enabled. It means that an XML file is automatically included in the PDF document that is sent." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:73 +msgid "The formats available depend on the country registered in your company's :guilabel:`General Information`." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:75 +msgid "Odoo supports the **Peppol BIS Billing 3.0** format that can be used via existing access points." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:79 +msgid "Add new formats to a database created before July 2022" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:81 +msgid "If your database was created before July 2022 and you wish to use one of the formats available from July 2022, you have to :ref:`install ` the module :guilabel:`Import/Export electronic invoices with UBL/CII` (module’s technical name: `account_edi_ubl_cii`) and your country-specific module." +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:87 +msgid "If you want to use the Belgian format E-FFF in a database created prior to July 2022, you need to :ref:`install `:" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:95 +msgid "Belgium - E-Invoicing (UBL 2.0, e-fff)" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:96 +msgid "`l10n_be_edi`" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:97 +msgid "Import/Export electronic invoices with UBL/CII" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:98 +msgid "`account_edi_ubl_cii`" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/electronic_invoicing.rst:101 +msgid "Once the new module is installed, UBL 2.0 and UBL 2.1 formats no longer appear in the journal since UBL BIS Billing 3.0 is available and more widely supported." +msgstr "" + #: ../../content/applications/finance/accounting/receivables/customer_invoices/epc_qr_code.rst:3 msgid "Add EPC QR Codes to invoices" msgstr "" @@ -13564,39 +13879,47 @@ msgstr "" msgid "This document is about the *Payment Terms* feature, not *Terms & Conditions*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:44 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:42 +msgid ":doc:`cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:43 +msgid "`Odoo Tutorials: Payment Terms `_" +msgstr "" + +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:48 msgid "Go to :menuselection:`Accounting --> Configuration --> Payment Terms` and click on *Create*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:46 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:50 msgid "The **Description on the Invoice** is the text displayed on the document (sale order, invoice, etc.)." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:49 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:53 msgid "In the **Terms** section, you can add a set of rules, called *terms*, to define what needs to be paid and by which due date." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:52 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:56 msgid "To add a term, click on *Add a line*, and define its *Type*, *Value*, and *Due Date Computation*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:55 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:59 msgid "Terms are computed in the order they are set up." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:56 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:60 msgid "The **balance** should always be used for the last line." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:62 msgid "In the following example, 30% is due on the day of issuance, and the balance is due at the end of the following month." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:67 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:71 msgid "Using Payment Terms" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:69 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:73 msgid "Payment Terms can be defined in the **Due Date** field, with the **Terms** drop-down list, on:" msgstr "" @@ -13624,11 +13947,11 @@ msgstr "" msgid "To set specific payment terms on a bill. This is mostly useful when you need to manage vendor terms with several installments. Otherwise, setting the *Due Date* is enough." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:80 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:84 msgid "You can also define a **Due Date** manually. If Payment Terms are already defined, empty the field so you can select a date." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:83 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:87 msgid "Payment Terms can be defined with the **Payment Terms** field on:" msgstr "" @@ -13640,52 +13963,44 @@ msgstr "" msgid "To set specific payment terms automatically on new sales orders, invoices, and bills of a contact. This can be modified in the contact’s *Form View*, under the *Sales & Purchase* tab." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:92 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:96 msgid "Invoices with specific Payment Terms generate different *Journal Entries*, with one *Journal Item* for every computed *Due Date*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:95 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:99 msgid "This makes for easier *Follow-ups* and *Reconciliation* since Odoo takes each due date into account, rather than just the balance due date. It also helps to get an accurate *Aged Receivable report*." msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:103 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:107 msgid "In this example, an invoice of $1000 has been issued with the following payment terms: *30% is due on the day of issuance, and the balance is due at the end of the following month.*" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:107 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:111 msgid "Due date" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:109 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:113 msgid "February 21" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:109 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:113 msgid "300" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:111 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:115 msgid "March 31" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:111 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:115 msgid "700" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:113 +#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:117 msgid "Product Sales" msgstr "" -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:116 -msgid "The $1000 debited on the Account Receivable is split into two distinct *Journal Items*. Both of them have their own **Due Date**." -msgstr "" - #: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:120 -msgid ":doc:`cash_discounts`" -msgstr "" - -#: ../../content/applications/finance/accounting/receivables/customer_invoices/payment_terms.rst:121 -msgid "`Odoo Tutorials: Terms and Conditions (T&C) and Payment Terms `_" +msgid "The $1000 debited on the Account Receivable is split into two distinct *Journal Items*. Both of them have their own **Due Date**." msgstr "" #: ../../content/applications/finance/accounting/receivables/customer_invoices/snailmail.rst:5 @@ -14970,11 +15285,11 @@ msgid "If you can not do that and if you really negotiate some prices with tax e msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:77 -msgid "always store the default price TAX EXCLUDED on the product form, and apply a tax (price included on the product form)" +msgid "always store the default price **tax excluded** on the product form, and apply a tax (price excluded on the product form)" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:80 -msgid "create a pricelist with prices in TAX INCLUDED, for specific customers" +msgid "create a pricelist with prices in **tax included**, for specific customers" msgstr "" #: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:83 @@ -14997,63 +15312,87 @@ msgstr "" msgid "but we want to sell it at 10€, tax included, in our shops or eCommerce website" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:97 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:99 +msgid "eCommerce" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:101 +msgid "If you only use B2C or B2B prices on your website, simply select the appropriate setting in the **Website** app settings." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:104 +msgid "If you have both B2B and B2C prices on a single website, please follow these instructions:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:106 +msgid "Activate the :ref:`developer mode ` and go to :menuselection:`General Settings --> Users & Companies --> Groups`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:108 +msgid "Open either `Technical / Tax display B2B` or `Technical / Tax display B2C`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:109 +msgid "Under the :guilabel:`Users` tab, add the users requiring access to the price type. Add B2C users in the B2C group and B2B users in the B2B group." +msgstr "" + +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:113 msgid "Setting your products" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:99 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:115 msgid "Your company must be configured with tax excluded by default. This is usually the default configuration, but you can check your **Default Sale Tax** from the menu :menuselection:`Configuration --> Settings` of the Accounting application." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:107 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:123 msgid "Once done, you can create a **B2C** pricelist. You can activate the pricelist feature per customer from the menu: :menuselection:`Configuration --> Settings` of the Sale application. Choose the option **different prices per customer segment**." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:112 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:128 msgid "Once done, create a B2C pricelist from the menu :menuselection:`Configuration --> Pricelists`. It's also good to rename the default pricelist into B2B to avoid confusion." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:116 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:132 msgid "Then, create a product at 8.26€, with a tax of 21% (defined as tax not included in price) and set a price on this product for B2C customers at 10€, from the :menuselection:`Sales --> Products` menu of the Sales application:" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:125 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:141 msgid "Setting the B2C fiscal position" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:127 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:143 msgid "From the accounting application, create a B2C fiscal position from this menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax included in price)" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:136 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:152 msgid "Test by creating a quotation" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:138 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:154 msgid "Create a quotation from the Sale application, using the :menuselection:`Sales --> Quotations` menu. You should have the following result: 8.26€ + 1.73€ = 9.99€." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:145 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:161 msgid "Then, create a quotation but **change the pricelist to B2C and the fiscal position to B2C** on the quotation, before adding your product. You should have the expected result, which is a total price of 10€ for the customer: 8.26€ + 1.74€ = 10.00€." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:153 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:169 msgid "This is the expected behavior for a customer of your shop." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:156 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:172 msgid "Avoid changing every sale order" msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:158 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:174 msgid "If you negotiate a contract with a customer, whether you negotiate tax included or tax excluded, you can set the pricelist and the fiscal position on the customer form so that it will be applied automatically at every sale of this customer." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:163 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:179 msgid "The pricelist is in the **Sales & Purchases** tab of the customer form, and the fiscal position is in the accounting tab." msgstr "" -#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:166 +#: ../../content/applications/finance/accounting/taxation/taxes/B2B_B2C.rst:182 msgid "Note that this is error prone: if you set a fiscal position with tax included in prices but use a pricelist that is not included, you might have wrong prices calculated for you. That's why we usually recommend companies to only work with one price reference." msgstr "" @@ -16631,7 +16970,6 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:15 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:15 #: ../../content/applications/finance/payment_acquirers/mollie.rst:14 -#: ../../content/applications/finance/payment_acquirers/ogone.rst:15 #: ../../content/applications/finance/payment_acquirers/paypal.rst:17 #: ../../content/applications/finance/payment_acquirers/sips.rst:15 msgid "Credentials tab" @@ -16756,7 +17094,7 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:12 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:12 #: ../../content/applications/finance/payment_acquirers/mollie.rst:11 -#: ../../content/applications/finance/payment_acquirers/ogone.rst:12 +#: ../../content/applications/finance/payment_acquirers/ogone.rst:9 #: ../../content/applications/finance/payment_acquirers/paypal.rst:14 #: ../../content/applications/finance/payment_acquirers/sips.rst:12 #: ../../content/applications/finance/payment_acquirers/stripe.rst:12 @@ -16856,10 +17194,9 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/authorize.rst:53 #: ../../content/applications/finance/payment_acquirers/buckaroo.rst:47 #: ../../content/applications/finance/payment_acquirers/mollie.rst:31 -#: ../../content/applications/finance/payment_acquirers/ogone.rst:88 #: ../../content/applications/finance/payment_acquirers/paypal.rst:144 #: ../../content/applications/finance/payment_acquirers/sips.rst:32 -#: ../../content/applications/finance/payment_acquirers/stripe.rst:130 +#: ../../content/applications/finance/payment_acquirers/stripe.rst:134 #: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:39 msgid ":doc:`../payment_acquirers`" msgstr "" @@ -17036,100 +17373,125 @@ msgstr "" msgid "`Ogone `_, also known as **Ingenico Payment Services** is a France-based company that provides the technology involved in secure electronic transactions." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:17 -msgid "Odoo needs your **API Credentials** to connect with your Ogone account, which comprise:" +#: ../../content/applications/finance/payment_acquirers/ogone.rst:10 +msgid "`Ogone's documentation `_." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:19 -msgid "**PSPID**: The ID solely used to identify the account with Ogone. You chose it when you opened your account." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:13 +msgid "Settings in Ogone" msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:21 -msgid ":ref:`API User ID `: The ID solely used to identify the user with Ogone." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:16 +msgid "Create an API user" msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:22 -msgid ":ref:`API User Password `: Value used to identify the user with Ogone." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:18 +msgid "Log into your Ogone account and head to the :guilabel:`Configuration` tab." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:23 -msgid ":ref:`SHA Key IN `: Key used in the signature Odoo send to Ogone." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:20 +msgid "You need to create an **API user** to be used in the creation of transactions from Odoo. While you can use your main account to do so, using an **API user** ensures that if the credentials used in Odoo are leaked, no access to your Ogone configuration is possible. Additionally, passwords for **API users** do not need to be updated regularly, unlike normal users." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:24 -msgid ":ref:`SHA Key OUT `: Key used in the signature Ogone send to Odoo." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:25 +msgid "To create an **API user**, go to :menuselection:`Configuration --> Users` and click on :guilabel:`New User`. The following fields must be configured:" msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:26 -msgid "You can copy your credentials from your Ogone account, and paste them in the related fields under the **Credentials** tab." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:30 +msgid ":guilabel:`UserID`: you can choose anything you want." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:31 +msgid ":guilabel:`User's Name, E-mail and Timezone`: you can enter the information you want." msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:32 -msgid "API User ID and Password" +msgid ":guilabel:`Profile`: should be set to :guilabel:`Admin`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:34 -msgid "If you already created a user and have both its ID and password, just copy them. You can also generate a new password from :menuselection:`Configuration --> Users --> Your chosen user --> change password`." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:33 +msgid ":guilabel:`Special user for API`: should be checked." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:38 -msgid "If you don't have a user, create one by going to :menuselection:`Configuration --> Users --> New User`. Set your **User ID** to get your **password** when you save your new user." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:35 +msgid "After the creation of the user, you are required to generate a password. Save the password and **UserID**, as they will be required later on during the setup." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:48 -msgid "SHA Key IN" +#: ../../content/applications/finance/payment_acquirers/ogone.rst:39 +msgid "If you already have an user set up, make sure it is activated without any error. If not, simply click the :guilabel:`Activate(Errors)` button to reset the user." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:50 -msgid "In order to retrieve the SHA Key IN, log into your ogone account, go to :menuselection:`Configuration --> Technical Information --> Data and origin verification --> Checks for e-Commerce & Alias Gateway`, and retrieve **SHA Key IN**." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:43 +msgid "Set up Ogone for Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:45 +msgid "Ogone must now be configured to accept payments from Odoo. Head to :menuselection:`Configuration --> Technical Information --> Global Security Parameters`, select :guilabel:`SHA-1` as :guilabel:`Hash Algorithm` and :guilabel:`UTF-8` as :guilabel:`character encoding`. Then, go to the :guilabel:`Data and Origin verification` tab of the same page and leave the URL field of the :guilabel:`e-Commerce and Alias Gateway` section blank." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:52 +msgid "If you need to use another algorithm, such as `sha-256` or `sha-512`, within Odoo, activate the :ref:`developer mode ` and go to :menuselection:`General Settings --> Technical --> System Parameters`. From here, search for `payment_ogone.hash.function` and change the value line to the desired algorithm (`sha-256` or `sha-512`)." msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:57 -msgid "SHA Key OUT" +msgid "You are now required to generate **SHA-IN** passphrases. **SHA-IN** and **SHA-OUT** passphrases are used to digitally sign the transaction requests and responses between Odoo and Ogone. By using these secret passphrases and the `sha-1` algorithm, both systems can ensure that the information they receive from the other was not altered or tampered with." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:59 -msgid "In order to retrieve the SHA Key OUT, log into your ogone account, go to :menuselection:`Configuration --> Technical Information --> Transaction feedback --> All transaction submission modes`, and get or generate your **API Key** and **Client Key**. Be careful to copy your API key as you'll not be allowed to get it later without generating a new one." +#: ../../content/applications/finance/payment_acquirers/ogone.rst:62 +msgid "Enter the same **SHA-IN** passphrase in both :guilabel:`Checks for e-Commerce & Alias Gateway` and :guilabel:`Checks for DirectLink and Batch (Automatic)`. You can leave the IP address field blank." msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:65 -msgid "If you are trying Ogone as a test, with the Test Account, change the **State** to *Test Mode*. We recommend doing this on a test Odoo database, rather than on your main database." +msgid "Your **SHA-IN** and **SHA-OUT** passphrases should be different, and between 16 and 32 characters long. Make sure to use the same **SHA-IN** and **SHA-OUT** passphrases throughout the entire Ogone configuration, as Odoo only allows a single **SHA-IN** and single **SHA-OUT** passphrase." msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:69 -msgid "Configuration on Ogone" -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/ogone.rst:71 -msgid "Now that Odoo can communicate with Ogone, we need to make sure that Ogone can send information to your database." +msgid "In order to retrieve the **SHA-OUT** key, log into your Ogone account, go to :menuselection:`Configuration --> Technical Information --> Transaction feedback --> All transaction submission modes`, and get or generate your **API Key** and **Client Key**. Be careful to copy your API key as you’ll not be allowed to get it later without generating a new one." msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:74 -msgid "To do so, log into your Ogone account and go to :menuselection:`Configuration --> Technical Information --> Transaction feedback --> Direct HTTP server-to-server request`." +msgid "When done, head to :menuselection:`Configuration --> Technical Information --> Transaction Feedback` and check the following options:" msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:77 -msgid "Then, fill the form with the following data:" +msgid "The :guilabel:`URL` fields for :guilabel:`HTTP redirection in the browser` can be left empty, as Odoo will specify these URLs for every transaction request." msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:79 -msgid "In the **Timing of the request**, select *Online but switch to a deferred request when the online requests fail*." +msgid ":guilabel:`I would like to receive transaction feedback parameters on the redirection URLs`: should be checked." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:0 -msgid "Enter your Odoo databases URL in both **URLs** followed by ``/payment/ogone/return``." -msgstr "" - -#: ../../content/applications/finance/payment_acquirers/ogone.rst:0 -msgid "For example: ``https://yourcompany.odoo.com/payment/ogone/return``" +#: ../../content/applications/finance/payment_acquirers/ogone.rst:81 +msgid ":guilabel:`Direct HTTP server-to-server request`: should to be set to `Online but switch to a deferred request when the online request fails`." msgstr "" #: ../../content/applications/finance/payment_acquirers/ogone.rst:83 -msgid "Select *POST* for the **Request Method**." +msgid "Both **URL** fields should contain the same following URL, with `` replaced by your database: `https:///payment/ogone/return`." msgstr "" -#: ../../content/applications/finance/payment_acquirers/ogone.rst:85 -msgid "Save, and you are ready to go!" +#: ../../content/applications/finance/payment_acquirers/ogone.rst:86 +msgid ":guilabel:`Dynamic eCommerce Parameters` should contain the following values: `ALIAS`, `AMOUNT`, `CARDNO`, `CN`, `CURRENCY`, `IP`, `NCERROR` `ORDERID`, `PAYID`, `PM`, `STATUS`, `TRXDATE`. Other parameters can be included (if you have another integration with Ogone that requires them), but are not advised." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:90 +msgid "In the :guilabel:`All transaction submission modes` section, fill out **SHA-OUT** passphrase and disable `HTTP request for status change`." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:93 +msgid "To allow your customers to save their credit card credentials for future use, head to :menuselection:`Configuration --> Alias --> My alias information`. From this tab, you can configure how the user can have its card details saved, for how long the information is saved, if a checkbox to save the card information should be displayed, etc." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:99 +#: ../../content/applications/finance/payment_acquirers/paypal.rst:11 +msgid "Settings in Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:101 +msgid "To set up Ogone in Odoo, head to :menuselection:`Accounting --> Configuration --> Payment Acquirers` and open the Ogone acquirer. In the :guilabel:`Credentials` tab, enter the **PSPID** of your Ogone account, and fill out the other fields as configured in your :ref:`Ogone portal `." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/ogone.rst:106 +msgid "If you wish to run tests with Ogone, within the accounting app, go to :menuselection:`Configuration --> Payment Acquirers`. Click on :guilabel:`Ogone`, enable :guilabel:`Test Mode` and enter your credentials in the :guilabel:`Credentials` tab. We recommend doing this on an Odoo test database, rather than on your main database." msgstr "" #: ../../content/applications/finance/payment_acquirers/paypal.rst:3 @@ -17140,10 +17502,6 @@ msgstr "" msgid "`Paypal `_ is available and popular worldwide. It doesn't charge any subscription fee, and creating an account is very easy. That's why we recommend it for starters in Odoo. It works as a seamless flow where the customer is routed to the Paypal website to register the payment." msgstr "" -#: ../../content/applications/finance/payment_acquirers/paypal.rst:11 -msgid "Settings in Odoo" -msgstr "" - #: ../../content/applications/finance/payment_acquirers/paypal.rst:19 msgid "Odoo needs your **API Credentials** to connect with your PayPal account, which comprise:" msgstr "" @@ -17516,7 +17874,15 @@ msgid "Przelewy24 (P24)" msgstr "" #: ../../content/applications/finance/payment_acquirers/stripe.rst:119 -msgid "To enable specific local payment methods with Stripe, list them as supported payment icons. To do so, go to :menuselection:`Payment Acquirers --> Stripe --> Configuration` and add the desired payment methods in the **Supported Payment Icons** field. If the desired payment method is already listed, you don't have anything to do. If a payment icon record doesn't exist in the database, its related payment method is considered enabled with Stripe." +msgid "To enable some of these local payment methods with Stripe, list them as supported payment icons. To do so, go to :menuselection:`Payment Acquirers --> Stripe --> Configuration` and add the desired payment methods in the **Supported Payment Icons** field. If the desired payment method is already listed, you don't have anything to do." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:129 +msgid "If a payment icon record does not exist in the database and its related local payment method is listed above, it is considered enabled with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_acquirers/stripe.rst:131 +msgid "If a local payment method is not listed above, it is not supported and cannot be enabled." msgstr "" #: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:3 diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 45c6f3843..ee5007307 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-09-01 15:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,7 +17,7 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../content/applications/inventory_and_mrp.rst:5 -msgid "Inventory & Mrp" +msgid "Inventory & MRP" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory.rst:8 @@ -3216,7 +3216,7 @@ msgid "In some cases, like for a retail shop storing vegetables and fruits, we h msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:23 -msgid "Let’s suppose there are one warehouse location *WH/Stock* and two sub-locations *WH/Stock/Vegatable* and *WH/Stock/Fruits*." +msgid "Let’s suppose there are one warehouse location *WH/Stock* and two sub-locations *WH/Stock/Vegetables* and *WH/Stock/Fruits*." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:25 diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 3d891c25e..f91a66890 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-11-02 08:37+0000\n" +"POT-Creation-Date: 2022-09-01 15:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -105,167 +105,167 @@ msgstr "" msgid "Pricing and FAQ" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:3 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:5 msgid "SMS Pricing and FAQ" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:6 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:8 msgid "What do I need to send SMSs?" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:7 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:9 msgid "SMS Text Messaging is an In-App Purchase (IAP) service that *requires prepaid credits* to work." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:11 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:13 msgid "How many types of SMSs are there?" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:12 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:14 msgid "There are 2 types: GSM7 and UNICODE." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:14 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:16 msgid "**GSM7** is the standard format, with a limit of 160 characters per message, that includes the following characters:" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:23 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:25 msgid "**UNICODE** is the format applied if a special character, that *is not* in the GSM7 list, is used. Limit per SMS: 70 characters." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:27 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:29 msgid "For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above these limits, the content is divided into a multi-part message* and the limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The system will inform you in real-time about the number of SMS your message represents." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36 msgid "How much does it cost to send an SMS?" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:35 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:37 msgid "The price of an SMS depends on the destination and the length (number of characters) of the message." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:37 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:39 msgid "To see the **price per country, please consult**: `Odoo SMS - FAQ `_." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:39 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:41 msgid "The number of SMSs a message represents will be always available to you in your database." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:51 msgid "How do I buy credits?" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:50 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:52 msgid "Go to :menuselection:`Settings --> Buy Credits`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:57 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:59 msgid "Or go to :menuselection:`Settings --> View my Services`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:65 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:67 msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:70 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:72 msgid "More common questions" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:72 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:74 msgid "**Is there an expiration time for my credits?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:74 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:76 msgid "No, credits do not expire." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:77 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:79 msgid "**Can I send an SMS to a phone number (which is not a mobile phone) because I see the icon in front of the field “phone”?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:80 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:82 msgid "Only if that phone number supports SMS (e.g. SIP phones)." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:83 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:85 msgid "**Do I receive an invoice to buy my credits?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:85 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:87 msgid "Yes." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:88 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:90 msgid "**Can the recipient answer to me?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:90 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:92 msgid "No, it is not possible to reply to the SMS." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:93 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:95 msgid "**What happens if I send multiple SMS but I do not have enough credits to send them all?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:95 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:97 msgid "The whole transaction is counted as a single one, so no SMS will be sent until you have enough credits to send them all." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:99 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:101 msgid "**Do I have a history of the sent SMSs?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:101 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:103 msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of the SMSs sent is available on :ref:`developer mode ` under :menuselection:`Technical --> SMS`." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:106 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:108 msgid "**Can I send as many SMSs I want at once?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:108 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:110 msgid "Yes, if you have enough credits." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:111 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:113 msgid "**If I have a number that does not exist in the list of recipients, will I lose credits?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:113 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:115 msgid "Not if the phone number is in the wrong format (e.g. too many digits). Otherwise, if the SMS is sent to the wrong person or to a fake number, the credit will be lost." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:117 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:119 msgid "**What happens if I send my SMS to a paying number (e.g.: a contest to win a ticket for a festival)?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:119 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:121 msgid "The SMS will not be delivered to that kind of number, so you won’t be charged." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:122 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:124 msgid "**Can I identify the numbers that do not exist when I send several SMSs?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:124 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:126 msgid "Only the ones that have an invalid format." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:127 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:129 msgid "**How does the GDPR regulation affect this service?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:129 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:131 msgid "Please find our `Privacy Policy here `__." msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:131 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:133 msgid "**Can I use my own SMS provider?**" msgstr "" -#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:133 +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:135 msgid "Yes, but it is not possible out of the box. Our experts can help you customize your database to make it happen. Please, check our success packs `here `_." msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 8daf95e31..50cedd32e 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-09-01 15:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -945,7 +945,7 @@ msgid "In some cases, a serial to USB adapter may be needed." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:17 -msgid "If your scale is `compatibale with Odoo IoT Box `_, there is no need to set up anything because it will be automatically detected as soon as it is connected." +msgid "If your scale is `compatible with Odoo IoT Box `_, there is no need to set up anything because it will be automatically detected as soon as it is connected." msgstr "" #: ../../content/applications/productivity/iot/devices/scale.rst:24 @@ -1210,650 +1210,1251 @@ msgstr "" msgid "Open any email; the shortcut should be displayed." msgstr "" -#: ../../content/applications/productivity/studio.rst:8 +#: ../../content/applications/productivity/studio.rst:6 msgid "Studio" msgstr "" -#: ../../content/applications/productivity/studio.rst:10 -msgid "Learn all you need in order to build custom applications: customize views, create specific reports, automate actions, define approval workflows, etc." +#: ../../content/applications/productivity/studio.rst:16 +msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, on any app, add or modify:" msgstr "" -#: ../../content/applications/productivity/studio.rst:14 +#: ../../content/applications/productivity/studio.rst:19 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:20 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:21 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:22 +msgid ":doc:`Automated actions `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:23 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:24 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:25 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:27 +msgid "Or you can :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/productivity/studio.rst:30 msgid "`Odoo Tutorials: Studio `_" msgstr "" -#: ../../content/applications/productivity/studio/concepts.rst:5 -msgid "Concepts" +#: ../../content/applications/productivity/studio/automated_actions.rst:3 +msgid "Automated actions (automations)" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:3 -msgid "Understanding Automated Actions" +#: ../../content/applications/productivity/studio/automated_actions.rst:5 +msgid "Automated actions are used to trigger automatic changes based on user actions (e.g., apply a modification when a field is set to a specific value) or on time conditions (e.g., archive a record 7 days after its last update)." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:6 -msgid "Automated actions are used to trigger actions. They are based on conditions and happen on top of Odoo’s default business logic." +#: ../../content/applications/productivity/studio/automated_actions.rst:9 +msgid "To create an automated action with Studio, go to :guilabel:`Automations` from anywhere within Studio." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:9 -msgid "Examples of automated actions include: creating a next activity upon a quote's confirmation; adding a user as a follower of a confirmed invoice if its total is higher than a certain amount; or preventing a lead from changing stage if a field is not filled in." +#: ../../content/applications/productivity/studio/automated_actions.rst:12 +msgid "For every automated action you create, the following elements should be defined: the :ref:`studio/automated-actions/model`, the :ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-actions/apply-on`, and the :ref:`studio/automated-actions/action`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:16 -msgid "Let's understand how to properly define *when* an automated action runs and *how* to create one:" +#: ../../content/applications/productivity/studio/automated_actions.rst:25 +msgid "Model" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:18 -msgid "The first step is to choose the :doc:`Model ` on which the action is applied." +#: ../../content/applications/productivity/studio/automated_actions.rst:27 +msgid "Select the model where the automated action should be applied." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:19 -msgid "The **Trigger** field defines the event that causes the automated action to happen:" +#: ../../content/applications/productivity/studio/automated_actions.rst:30 +msgid "The model you are on when you click on :guilabel:`Automations` is pre-selected by default." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:21 -msgid "*On Creation*: when a new record is created. Note that the record is created once saved for the first time." +#: ../../content/applications/productivity/studio/automated_actions.rst:35 +msgid "Trigger" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:23 -msgid "*On Update*: when the record is updated. Note that the update happens once the record is saved." +#: ../../content/applications/productivity/studio/automated_actions.rst:37 +msgid "Define when the automated action should be applied. Six triggers are available." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:24 -msgid "*On Creation & Update*: on the creation and/or on the update of a record once the form is saved." +#: ../../content/applications/productivity/studio/automated_actions.rst:42 +msgid "On Creation" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:25 -msgid "*On Deletion*: on the removal of a record under the condition set." +#: ../../content/applications/productivity/studio/automated_actions.rst:44 +msgid "The action is triggered when a record is created and then saved." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:26 -msgid "*Based on Form Modification*: when the value of the specified *Trigger* field is changed in the interface (user sees the changes before saving the record). Note that this action can only be used with the *Execute Python Code* action type." +#: ../../content/applications/productivity/studio/automated_actions.rst:49 +msgid "On Update" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:29 -msgid "*Based on Timed Condition*: a delay happens after a specific date/time. Set a *Delay after trigger date* if you need a delay to happen before the *Trigger Date*. Example: to send a reminder 15min before a meeting. If the date/time is not set on the form of the model chosen, the date/time considered is the one of the creation/update of the record." +#: ../../content/applications/productivity/studio/automated_actions.rst:51 +msgid "The action is triggered when a previously saved record is edited and then saved." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:34 -msgid "For every Trigger option, **conditions** can be applied, such as:" +#: ../../content/applications/productivity/studio/automated_actions.rst:53 +msgid "Use :guilabel:`Trigger Fields` to specify which fields - and only those - trigger the action on their update." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:36 -msgid "*Before Update Domain*: if designated, this condition must be satisfied before the record is updated." +#: ../../content/applications/productivity/studio/automated_actions.rst:55 +msgid "To detect when a record changes from one state to another, define a :guilabel:`Before Update Domain` filter, which checks if the condition is satisfied before the record is updated. Then set an :ref:`studio/automated-actions/apply-on` filter, which checks if the condition is met after the record is updated." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:38 -msgid "*Apply on*: if designated, this condition must be satisfied before executing the action rule (*Action To Do*), and after the update." +#: ../../content/applications/productivity/studio/automated_actions.rst:61 +msgid "If you want the automated action to happen when an email address is set on a contact, define the :guilabel:`Before Update Domain` to `Email is not set`, and the :guilabel:`Apply on` domain to `Email is set`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:41 -msgid "The **Active** option is to be turned off when the rule should be hidden and not executed." +#: ../../content/applications/productivity/studio/automated_actions.rst:72 +msgid "On Creation & Update" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:43 -msgid "Under **Action To Do** choose the type of server action that must be executed once records meet the *Trigger* conditions:" +#: ../../content/applications/productivity/studio/automated_actions.rst:74 +msgid "The action is triggered when a record is created and saved or edited afterward and saved." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:45 -msgid "*Execute Python Code*: a block of code is executed. A *Help* tab with the variables that can be used is available." +#: ../../content/applications/productivity/studio/automated_actions.rst:79 +msgid "On Deletion" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:47 -msgid "*Create New Record*: a new record with new values is created." +#: ../../content/applications/productivity/studio/automated_actions.rst:81 +msgid "The action is triggered when a record is deleted." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:48 -msgid "*Update a Record*: updates the record that triggered the action." +#: ../../content/applications/productivity/studio/automated_actions.rst:84 +msgid "This trigger is rarely used, as archiving records is usually preferred to deletion." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:49 -msgid "*Execute several actions*: defines an action that triggers other server actions." +#: ../../content/applications/productivity/studio/automated_actions.rst:89 +msgid "Based on Form Modification" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:50 -msgid "*Send Email*: an automatic :doc:`email ` is sent." +#: ../../content/applications/productivity/studio/automated_actions.rst:91 +msgid "The action is triggered when any change is done to a trigger field's value on the :ref:`Form view `, even before saving the record. This trigger only works on the user interface when a modification is made by a user. If the field is changed through another action and not by the user, the action will not run." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:51 -msgid "*Add Followers*: followers are notified of changes in the task." +#: ../../content/applications/productivity/studio/automated_actions.rst:97 +msgid "This trigger can only be used with the :ref:`Execute Python Code action `, so development is required." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:52 -msgid "*Create Next Activity*: creates an activity such as: *Call*, *Email*, *Reminder*." +#: ../../content/applications/productivity/studio/automated_actions.rst:103 +msgid "Based on Timed Condition" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:53 -msgid "*Send SMS Text Message*: sends an :doc:`SMS `." +#: ../../content/applications/productivity/studio/automated_actions.rst:105 +msgid "The action is triggered when a trigger field's date or date & time value is reached." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:56 -msgid "Example" +#: ../../content/applications/productivity/studio/automated_actions.rst:107 +msgid "To trigger the action after the :guilabel:`Trigger Date`, add a number of minutes, hours, days, or months under :guilabel:`Delay after trigger date`. To trigger the action before, add a negative number instead." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:58 -msgid "This is the process of which the update of the *Email* field on the Lead/Opportunity *Model*, with a *Trigger Condition* set to *On Update*, goes through:" +#: ../../content/applications/productivity/studio/automated_actions.rst:112 +msgid "If you want to send a reminder email 30 minutes before the start of a calendar event, select the :guilabel:`Start (Calendar Event)` under :guilabel:`Trigger Date` and set the :guilabel:`Delay after trigger date` to **-30** :guilabel:`Minutes`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:65 -msgid "The user creates the record without an email address set." +#: ../../content/applications/productivity/studio/automated_actions.rst:121 +msgid "By default, the scheduler checks for trigger dates every 4 hours." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:66 -msgid "The user updates the record defining an email address." +#: ../../content/applications/productivity/studio/automated_actions.rst:126 +msgid "Apply on" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:67 -msgid "Once the change is saved, the automation checks if any of the *Watched Fields* are being updated (for the example: field name *email_from* (Email)." +#: ../../content/applications/productivity/studio/automated_actions.rst:128 +msgid "Define on which records of the model the automated action should be applied. It works the same way as when you apply filters on a model." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:69 -msgid "If true, it checks if the record matches the *Before Update Domain* (for the example: *email is not set*)." +#: ../../content/applications/productivity/studio/automated_actions.rst:134 +msgid "Action" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:71 -msgid "If true, it checks (*after the update*) whether the record matches the *Apply on* domain (for the example: *email is set*)." +#: ../../content/applications/productivity/studio/automated_actions.rst:136 +msgid "Determine what the automated action should do (server action). There are eight types of action to choose from." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:73 -msgid "If true, the chosen *Action To Do* is performed on the record." +#: ../../content/applications/productivity/studio/automated_actions.rst:142 +msgid "Execute Python Code" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:76 -msgid ":doc:`understanding_general`" +#: ../../content/applications/productivity/studio/automated_actions.rst:144 +msgid "The action is used to execute Python code. The available variables are described on the :guilabel:`Python Code` tab, which is also used to write your code, or on the :guilabel:`Help` tab." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:77 -msgid ":doc:`../use_cases/automated_actions`" +#: ../../content/applications/productivity/studio/automated_actions.rst:147 +msgid "To allow the action to be run through the website, tick :guilabel:`Available on the Website` and add a :guilabel:`Website Path`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:3 -msgid "Understanding General Concepts" +#: ../../content/applications/productivity/studio/automated_actions.rst:153 +msgid "Create a new Record" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:7 -msgid "Odoo Studio is a toolbox that allows you to add models or adapt functionalities on top of Odoo’s standard behavior without coding knowledge. You can also create custom views and modify existing ones without having to get into the XML code." +#: ../../content/applications/productivity/studio/automated_actions.rst:155 +msgid "The action is used to create a new record on any model." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:11 -msgid "Even for experienced developers, typing out code requires time. By using Odoo Studio, you can quickly get your models up and going and focus on the crucial parts of your application. The result is a user-friendly solution that makes customizations and designing new applications easy with or without programming skills." +#: ../../content/applications/productivity/studio/automated_actions.rst:158 +msgid "Selecting a :guilabel:`Target Model` is only required if you want to target another model than the one you are on." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:15 -msgid "Getting started" +#: ../../content/applications/productivity/studio/automated_actions.rst:161 +msgid "To link the record that triggered the creation of the new record, select a field under :guilabel:`Link Field`. For example, you could create a contact automatically when a lead is turned into an opportunity." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:17 -msgid "One you start using Odoo Studio, you automatically create a new *module* that contains all your modifications. These modifications can be done on existing screens (*views*), by adding new *fields* in existing applications, or by creating an entirely new *model*." +#: ../../content/applications/productivity/studio/automated_actions.rst:164 +msgid ":guilabel:`Data to Write` tab: the tab is used to specify the new record's values. After selecting a :guilabel:`Field`, select its :guilabel:`Evaluation Type`:" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:22 -msgid "What is a Module?" +#: ../../content/applications/productivity/studio/automated_actions.rst:167 +msgid ":guilabel:`Value`: used to directly give the field's raw value in the :guilabel:`Value` column." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:25 -msgid "An Odoo **Module** can contain a number of elements, such as: business objects (models), object views, data files, web controllers, and static web data. An application is a collection of modules." +#: ../../content/applications/productivity/studio/automated_actions.rst:168 +msgid ":guilabel:`Reference`: used to select the record under the :guilabel:`Record` column and let Studio add the internal ID in the :guilabel:`Value` column." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:29 -msgid "In object-oriented programming, models usually represent a concept from the real world. Example: Odoo has models for Sales Orders, Users, Countries, etc. If you were to build an application to manage Real Estate sales, a model that represents the Properties for sale would probably be your first step." +#: ../../content/applications/productivity/studio/automated_actions.rst:172 +msgid "If an automated action creates a new task in a project, you can assign it to a specific user by setting the :guilabel:`Field` to :guilabel:`Responsible User (Project)`, the :guilabel:`Evaluation Type` to :guilabel:`Reference`, and the :guilabel:`Record` to a specific user." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:38 -msgid "What is a Model (also called Object)?" +#: ../../content/applications/productivity/studio/automated_actions.rst:181 +msgid ":guilabel:`Python expression`: used to dynamically define the newly created record’s value for a field using Python code in the :guilabel:`Value` column." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:40 -msgid "A **Model** determines the logical structure of a database and fundamentally determines in which manner data can be stored, organized, and manipulated. In other words, a model is a table of information that can be bridged with other tables." +#: ../../content/applications/productivity/studio/automated_actions.rst:187 +msgid "Update the Record" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:45 -msgid "What are Fields?" +#: ../../content/applications/productivity/studio/automated_actions.rst:189 +msgid "The action is used to set value(s) for field(s) of any record on the current model." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:47 -msgid "**Fields** compose models. It is where a record (a piece of data) is registered." +#: ../../content/applications/productivity/studio/automated_actions.rst:192 +msgid "The process to fill in the :guilabel:`Data to Write` tab is the same as described under :ref:`studio/automated-actions/action/new-record`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:49 -msgid "Example: on the Real Estate application, fields on the Properties model would include the price, address, a picture, a link to the current owner, etc." +#: ../../content/applications/productivity/studio/automated_actions.rst:198 +msgid "Execute several actions" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:50 -msgid "There are 2 main types of fields in Odoo: *basic (or scalar) fields* and *relational fields*." +#: ../../content/applications/productivity/studio/automated_actions.rst:200 +msgid "The action is used to trigger multiple actions at the same time. To do so, click on :guilabel:`Add a line` under the :guilabel:`Actions` tab. In the :guilabel:`Child Actions` pop-up, click on :guilabel:`Create` and configure the action." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:53 -msgid "Basic fields represent simple values, like numbers or text. Relational fields represent relations between models. So, if you have a model for *Customers* and another one for *Properties*, you would use a relational field to link each Property to its Customer." +#: ../../content/applications/productivity/studio/automated_actions.rst:207 +msgid "Send Email" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:56 -msgid "Relational Fields in detail" +#: ../../content/applications/productivity/studio/automated_actions.rst:209 +msgid "The action is used to send an email to a contact linked to a specific record. To do so, select or create an :guilabel:`Email Template`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:59 -msgid "**Relational Fields** provide the option to link the data of one model with the data of another model." +#: ../../content/applications/productivity/studio/automated_actions.rst:215 +msgid "Add Followers" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:60 -msgid "In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*." +#: ../../content/applications/productivity/studio/automated_actions.rst:217 +msgid "The action is used to subscribe existing contacts to the record." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:66 -msgid "An **One2many** field is a *one-way* direction of selecting *multiple* records from a table." +#: ../../content/applications/productivity/studio/automated_actions.rst:222 +msgid "Create Next Activity" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:68 -msgid "Example: a Sales Order can contain multiple Sales Order Lines, which also contain multiple fields of information." +#: ../../content/applications/productivity/studio/automated_actions.rst:224 +msgid "The action is used to schedule a new activity linked to the record. Use the :guilabel:`Activity` tab to set it up as usual, but instead of the :guilabel:`Assigned to` field, select an :guilabel:`Activity User Type`. Select :guilabel:`Specific User` and add the user under :guilabel:`Responsible` if the activity should always be assigned to the same user. To dynamically target a user linked to the record, select :guilabel:`Generic User From Record` instead and change the :guilabel:`User field name` if necessary." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:69 -msgid "A **Many2one** field is a *one-way* direction of selecting *one* record from a table." +#: ../../content/applications/productivity/studio/automated_actions.rst:232 +msgid "After a lead is turned into an opportunity, you want your automated action to set up a call for the user responsible for the lead. To do so, set the :guilabel:`Activity` to :guilabel:`Call` and set the :guilabel:`Activity User Type` to :guilabel:`Generic User From Record`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:70 -msgid "Example: you can have many product categories, but each product can only belong to one category." +#: ../../content/applications/productivity/studio/automated_actions.rst:243 +msgid "Send SMS Text Message" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:71 -msgid "A **Many2many** field is a *two-way* direction of selecting records from a table." +#: ../../content/applications/productivity/studio/automated_actions.rst:245 +msgid "The action is used to send an SMS to a contact linked to the record. To do so, select or create an :guilabel:`SMS Template`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:72 -msgid "Example: multiple tags can be added to a lead’s form." +#: ../../content/applications/productivity/studio/automated_actions.rst:249 +msgid "If you want sent messages to be logged in the Chatter, tick :guilabel:`Log as Note`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:75 -msgid "An *One2many* field must have a *Many2one* related to it." +#: ../../content/applications/productivity/studio/fields.rst:3 +msgid "Fields and widgets" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:78 -msgid "What are Views?" +#: ../../content/applications/productivity/studio/fields.rst:5 +msgid "Fields structure the models of a database. If you picture a model as a table or spreadsheet, fields are the columns where data is stored in the records (i.e., the rows). Fields also define the type of data that is stored within them. How the data is presented and formatted on the :abbr:`UI (User Interface)` is defined by their widget." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:80 -msgid "**Views** define how records are displayed. They are specified in XML which means that they can be edited independently from the models that they represent. There are various types of views in Odoo, and each of them represents a mode of visualization. Some examples are: *form*, *list*, *kanban*." +#: ../../content/applications/productivity/studio/fields.rst:10 +msgid "From a technical point of view, there are 15 field types in Odoo. However, you can choose from 20 fields in Studio, as some field types are available more than once with a different default widget." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:85 -msgid "What is a Menu?" +#: ../../content/applications/productivity/studio/fields.rst:14 +msgid ":guilabel:`New Fields` can only be added to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views. On other views, you can only add :guilabel:`Existing Fields` :dfn:`(fields already on the model)`." msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:87 -msgid "A **Menu** is a button that executes an action. In Odoo Studio, to create menus (models) and rearrange their hierarchy, click on *Edit Menu*." +#: ../../content/applications/productivity/studio/fields.rst:21 +msgid "Simple fields" msgstr "" -#: ../../content/applications/productivity/studio/concepts/understanding_general.rst:95 -msgid "`Studio Basics `_" +#: ../../content/applications/productivity/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." msgstr "" -#: ../../content/applications/productivity/studio/how_to.rst:5 -msgid "How To" +#: ../../content/applications/productivity/studio/fields.rst:26 +#: ../../content/applications/productivity/studio/fields.rst:325 +msgid "Non-default widgets, when available, are presented as bullet points below." msgstr "" -#: ../../content/applications/productivity/studio/how_to/export_import.rst:3 -msgid "Export and Import Modules" +#: ../../content/applications/productivity/studio/fields.rst:31 +msgid "Text (`char`)" msgstr "" -#: ../../content/applications/productivity/studio/how_to/export_import.rst:5 -msgid "When you do customizations in Odoo Studio, a new module is created in your database, making it easy to use Studio for prototyping." +#: ../../content/applications/productivity/studio/fields.rst:33 +msgid "The :guilabel:`Text` field is used for short text containing any character. One text line is displayed when filling out the field." msgstr "" -#: ../../content/applications/productivity/studio/how_to/export_import.rst:8 -msgid "To export these customizations, activate Studio on the main dashboard and, under the menu *Customizations*, click on *Export*. The default filename is *customizations.zip*." +#: ../../content/applications/productivity/studio/fields.rst:36 +#: ../../content/applications/productivity/studio/fields.rst:220 +msgid ":guilabel:`Badge`: displays the value inside a rounded shape, similar to a tag. The value cannot be edited on the UI, but a default value can be set." msgstr "" -#: ../../content/applications/productivity/studio/how_to/export_import.rst:16 -msgid "The module created contains the definition of custom models and fields, as well as the UI elements of any customization in an XML format." +#: ../../content/applications/productivity/studio/fields.rst:38 +#: ../../content/applications/productivity/studio/fields.rst:71 +msgid ":guilabel:`Copy to Clipboard`: users can copy the value by clicking a button." msgstr "" -#: ../../content/applications/productivity/studio/how_to/export_import.rst:18 -msgid "To import and install the customizations in another instance, connect to the destination database, activate Studio and, under *Customizations*, click on *Import*." +#: ../../content/applications/productivity/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." msgstr "" -#: ../../content/applications/productivity/studio/how_to/export_import.rst:25 -msgid "Studio does not know which apps are customized (because the same view can be modified on different apps), therefore, it *does not* add the underlying modules as dependencies of the exported module. In other words, the applications installed on the source database should be installed on the destination database." +#: ../../content/applications/productivity/studio/fields.rst:40 +msgid ":guilabel:`Image`: displays an image using a URL. The value cannot be edited manually, but a default value can be set." msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:3 -msgid "Customizing the Rainbow Man" +#: ../../content/applications/productivity/studio/fields.rst:44 +msgid "This works differently than selecting the :ref:`Image field ` directly, as the image is not stored in Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget. For example, it can be useful if you want to save disk space." msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:5 -msgid "The Rainbow Man in Odoo is an animation shown once the user completes certain tasks and clicks on certain buttons. It is a way to make the software fun to use, and rewarding, for employees." +#: ../../content/applications/productivity/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:13 -msgid "On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, once they are selected in Studio, under their *Properties*, the *Rainbow Man* effect can be applied." +#: ../../content/applications/productivity/studio/fields.rst:52 +msgid "Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from Odoo next to the field." msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:14 -msgid "By default, the feature is active:" +#: ../../content/applications/productivity/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:16 -msgid "when opportunities are marked as won;" +#: ../../content/applications/productivity/studio/fields.rst:66 +msgid "Multiline Text (`text`)" msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:17 -msgid "when users empty their inboxes;" +#: ../../content/applications/productivity/studio/fields.rst:68 +msgid "The :guilabel:`Multiline Text` field is used for longer text containing any type of character. Two text lines are displayed on the UI when filling out the field." msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:18 -msgid "when the user finishes a tour;" +#: ../../content/applications/productivity/studio/fields.rst:82 +msgid "Integer (`integer`)" msgstr "" -#: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:19 -msgid "when the user finishes doing reconciliations." +#: ../../content/applications/productivity/studio/fields.rst:84 +msgid "The :guilabel:`Integer` field is used for all integer numbers (:dfn:`positive, negative, or zero, without a decimal`)." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:3 -msgid "Customizing Reports" +#: ../../content/applications/productivity/studio/fields.rst:87 +msgid ":guilabel:`Percentage Pie`: displays the value inside a percentage circle, usually for a computed value. The value cannot be edited on the UI, but a default value can be set." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:9 -msgid "Odoo uses HTML and CSS technologies to create reports. HTML is a markup language that uses tags, also called elements. It is the core of any webpage because it provides its basic structure. CSS interacts with HTML elements to add style to the page, establishing how the HTML is shown to the user. Odoo’s reports also use Bootstrap’s grid layout, which is the containers, rows, and columns to align content, and support Odoo's website themes." +#: ../../content/applications/productivity/studio/fields.rst:89 +#: ../../content/applications/productivity/studio/fields.rst:118 +msgid ":guilabel:`Progress Bar`: displays the value next to a percentage bar, usually for a computed value. The field cannot be edited manually, but a default value can be set." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:11 -msgid "When creating a new report, choose the purpose of it and if you would like the report to include header and footer (company logo, name, address, phone, email address, etc.)." +#: ../../content/applications/productivity/studio/fields.rst:91 +msgid ":guilabel:`Handle`: displays a drag handle icon to order records manually in :ref:`List view `." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:17 -msgid "Under the tab **Add**, you find the fields to be dragged and dropped to the view. *Fields*, *Data tables*, *Subtotal & Total*, and *Address Book* are dynamic elements (meaning that they need a :doc:`one2many or a many2many <../concepts/understanding_general>` related object). *Text*, *Title Block*, *Image*, and *Text in Cell* are static elements." +#: ../../content/applications/productivity/studio/fields.rst:103 +msgid "Decimal (`float`)" msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:26 -msgid "Once the element is added to the view, select it to see its **Options**. The first section shows the hierarchy of the selected object and its properties, allowing you to individually edit them. Fields with related objects have their directives shown on *Field Expression*." +#: ../../content/applications/productivity/studio/fields.rst:105 +msgid "The :guilabel:`Decimal` field is used for all decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:34 -msgid "Under **Visible if**, define the rule(s) to set visibility conditions to fields." +#: ../../content/applications/productivity/studio/fields.rst:109 +msgid "Decimal numbers are displayed with two decimals after the decimal point on the UI, but they are stored in the database with more precision." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:36 -msgid "Example: if choosing to display a product image, you could set a visibility rule to only display the ones that are *set* in the product form, avoiding having a plain icon when they are not set." +#: ../../content/applications/productivity/studio/fields.rst:112 +msgid ":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field `. It is recommended to use the later as it offers more functionalities." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:40 -msgid "**Visible for** is used to set which :doc:`groups ` can have access to specific elements in the report. **Limit visibility to groups**, under *Report*, sets the visibility of the report to specifics groups, meaning that users belonging to other groups do not see the same final document." +#: ../../content/applications/productivity/studio/fields.rst:115 +msgid ":guilabel:`Percentage`: displays a percent character `%` after the value." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:46 -msgid "Under the **Report** tab, name your report, choose the paper format, and if the report should be added to the *Print* menu list on its respective document form." +#: ../../content/applications/productivity/studio/fields.rst:116 +msgid ":guilabel:`Percentage Pie`: displays the value inside a percentage circle, usually for a computed value. The field cannot be edited manually, but a default value can be set." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:53 -msgid "If activating the :ref:`developer mode `, additional fields such as *Class* under *Options*, and *Reload from attachment* under *Report*, become visible." +#: ../../content/applications/productivity/studio/fields.rst:120 +msgid ":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum of 59 minutes." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:56 -msgid "*Class*: add custom CSS classes to the selected element (e.g. Bootstrap classes such as *text-danger*)." +#: ../../content/applications/productivity/studio/fields.rst:131 +msgid "Monetary (`monetary`)" msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:59 -msgid "*Reload from attachment*: saves the report as an attachment of the document when printed. When the report is reprinted, it re-downloads that attachment instead of re-printing it. This means that if the underlying record (e.g. Invoice) changes when compared to the first impression, the report does not reflect the changes because they were done after the attachment was created. This is typically useful for reports linked to documents that should not change, such as Invoices." +#: ../../content/applications/productivity/studio/fields.rst:133 +msgid "The :guilabel:`Monetary` field is used for all monetary values." msgstr "" -#: ../../content/applications/productivity/studio/how_to/reports.rst:67 -msgid "Actions in Odoo Studio can be undone until you *Close* the toolbox. Once you have closed Studio, changes can not be undone anymore." +#: ../../content/applications/productivity/studio/fields.rst:136 +msgid "When you first add a :guilabel:`Monetary` field, you are prompted to add a :guilabel:`Currency` field if none exists already on the model. Odoo offers to add the :guilabel:`Currency` field for you. Once it is added, add the :guilabel:`Monetary` field again." msgstr "" -#: ../../content/applications/productivity/studio/use_cases.rst:5 -msgid "Use Cases" +#: ../../content/applications/productivity/studio/fields.rst:149 +msgid "Html (`html`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:3 -msgid "Advanced Use Cases: Automated Actions" +#: ../../content/applications/productivity/studio/fields.rst:151 +msgid "The :guilabel:`Html` field is used to add text that can be edited using the Odoo HTML editor." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:5 -msgid "**Case scenario 1: when a Belgian lead is created, a 3-stars priority should be automatically applied.**" +#: ../../content/applications/productivity/studio/fields.rst:153 +msgid ":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing raw HTML." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:8 -msgid "Under *Automations*, click on *Create* and set the following rules:" +#: ../../content/applications/productivity/studio/fields.rst:164 +msgid "Date (`date`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:10 -msgid "*Model*: Lead/Opportunity" +#: ../../content/applications/productivity/studio/fields.rst:166 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:11 -msgid "*Active*: On" +#: ../../content/applications/productivity/studio/fields.rst:168 +msgid ":guilabel:`Remaining Days`: the remaining number of days before the selected date is displayed (e.g., *In 5 days*), based on the current date." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:12 -msgid "*Trigger*: On Creation & Update" +#: ../../content/applications/productivity/studio/fields.rst:180 +msgid "Date & Time (`datetime`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:13 -msgid "*Apply on*: Country > Country Name = Belgium" +#: ../../content/applications/productivity/studio/fields.rst:182 +msgid "The :guilabel:`Date & Time` field is used to select a date on a calendar and a time on a clock. The user's current time is automatically used if no time is set." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:14 -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:53 -msgid "*Action To Do*: Update the Record" +#: ../../content/applications/productivity/studio/fields.rst:185 +msgid ":guilabel:`Date`: used to record the time without displaying it on the UI." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:15 -msgid "*Data to Write*: Lead/Opportunity > Value > 3" +#: ../../content/applications/productivity/studio/fields.rst:186 +msgid ":guilabel:`Remaining days`: displays the remaining number of days before the selected date (e.g., *In 5 days*), based on the current date and time." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:22 -msgid "Check :doc:`this doc ` in order to have another automated action example." +#: ../../content/applications/productivity/studio/fields.rst:198 +msgid "Checkbox (`boolean`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:25 -msgid ":doc:`../concepts/understanding_automated_actions`" +#: ../../content/applications/productivity/studio/fields.rst:200 +msgid "The :guilabel:`Checkbox` field is used when a value should only be true or false, indicated by checking or unchecking a checkbox." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:26 -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:61 -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:138 -#: ../../content/applications/productivity/studio/use_cases/views.rst:28 -msgid ":doc:`../concepts/understanding_general`" +#: ../../content/applications/productivity/studio/fields.rst:203 +msgid ":guilabel:`Button`: displays a radio button. The widget works without switching to the edit mode." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:3 -msgid "Advanced Use Cases: Filters and Status Bar" +#: ../../content/applications/productivity/studio/fields.rst:204 +msgid ":guilabel:`Toggle`: displays a toggle button. The widget works without switching to the edit mode." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:5 -msgid "**Case scenario 1: on Sales, set a filter on Belgian customers and define it as the default one (the user should still be able to unset the filter).**" +#: ../../content/applications/productivity/studio/fields.rst:215 +msgid "Selection (`selection`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:8 -msgid "On your customer’s page, use *Filters* > *Add Custom Filter* to group customers by country. Now, under *Favorites*, *Save Current Search* enabling *Use by default* and *Save*." +#: ../../content/applications/productivity/studio/fields.rst:217 +msgid "The :guilabel:`Selection` field is used when users should select a single value from a group of predefined values." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:15 -msgid "On *Filter Rules* in Studio mode, select the respective filter and enable *Default Filter*." +#: ../../content/applications/productivity/studio/fields.rst:222 +msgid ":guilabel:`Badges`: displays all selectable values simultaneously inside rectangular shapes, organized horizontally." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:21 -msgid "**Case scenario 2: add a status bar on the product form to manage its life cycle. Set the values: ‘Prototype’, ‘In use’ and ‘Deprecated’. By default, the Kanban view must be grouped by status.**" +#: ../../content/applications/productivity/studio/fields.rst:224 +msgid ":guilabel:`Priority`: displays star symbols instead of values, which can be used to indicate an importance or satisfaction level, for example. This has the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are already predefined." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:26 -msgid "On your product form, *Add a pipeline status bar* and name its values. Status bars are *selection* fields that give you the ability to follow a specific flow. They are useful to show you the progress that has been made." +#: ../../content/applications/productivity/studio/fields.rst:228 +#: ../../content/applications/productivity/studio/fields.rst:352 +msgid ":guilabel:`Radio`: displays all selectable values at the same time as radio buttons." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:28 -msgid "On the *Views* menu, access *Kanban* and, under its *View* options, set the *Default Group by* as *Pipeline status bar*." +#: ../../content/applications/productivity/studio/fields.rst:231 +msgid "By default, radio buttons are organized vertically. Tick :guilabel:`display horizontally` to switch the way they are displayed." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:34 -msgid "Now, open your product form and set the right status for that product. As you move products throughout stages (also through the product’s form), stages are shown in the Kanban view." +#: ../../content/applications/productivity/studio/fields.rst:243 +msgid "Priority (`selection`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:38 -msgid "To make modifications in the pipeline status bar, for example, remember to go back to *Form View*." +#: ../../content/applications/productivity/studio/fields.rst:245 +msgid "The :guilabel:`Priority` field is used to display a three-star rating system, which can be used to indicate importance or satisfaction level. This field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and four priority values predefined. Consequently, the :guilabel:`Badge`, :guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets have the same effects as described under :ref:`Selection `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:44 -msgid "**Case scenario 2.a: when a product goes from ‘In use’ to ‘Deprecate’, set its cost to 0€.**" +#: ../../content/applications/productivity/studio/fields.rst:253 +msgid "To change the number of available stars by adding or removing values, click :guilabel:`Edit Values`. Note that the first value is equal to 0 stars (i.e., when no selection is made), so having four values results in a three-star rating system, for example." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:46 -msgid "Create an :doc:`automated action <../concepts/understanding_automated_actions>` with the selected values:" +#: ../../content/applications/productivity/studio/fields.rst:266 +msgid "File (`binary`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:49 -msgid "*Model*: Product Template" +#: ../../content/applications/productivity/studio/fields.rst:268 +msgid "The :guilabel:`File` field is used to upload any type of file, or sign a form (:guilabel:`Sign` widget)." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:50 -msgid "*Trigger*: On Update" +#: ../../content/applications/productivity/studio/fields.rst:271 +msgid ":guilabel:`Image`: users can upload an image file, which is then displayed in :ref:`Form view `. This has the same effect as using the :ref:`Image field `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:51 -msgid "*First Domain*: Pipeline status bar = In use" +#: ../../content/applications/productivity/studio/fields.rst:274 +msgid ":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then browsed from the :ref:`Form view `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:52 -msgid "*Second Domain*: Pipeline status bar = Deprecated" +#: ../../content/applications/productivity/studio/fields.rst:276 +msgid ":guilabel:`Sign`: users can electronically sign the form. This has the same effect as selecting the :ref:`Sign field `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:54 -msgid "*Data to Write*: Cost (Product Template) > Value > 0" +#: ../../content/applications/productivity/studio/fields.rst:288 +msgid "Image (`binary`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:3 -msgid "Advanced Use Cases: Creating Models and Adding Fields" +#: ../../content/applications/productivity/studio/fields.rst:290 +msgid "The :guilabel:`Image` field is used to upload an image and display it in :ref:`Form view `. This field type is a :ref:`File field ` with the :guilabel:`Image` widget selected by default. Consequently, the :guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have the same effects as described under :ref:`File `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:5 -msgid "**Case scenario 1: on the leads’ form, if the chosen country is France, show a field 'Pay by check?'**" +#: ../../content/applications/productivity/studio/fields.rst:297 +msgid "To change the display size of uploaded images, select :guilabel:`Small`, :guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:8 -msgid "On your leads’ form, add a *Related Field* to *Country > Country Name*." +#: ../../content/applications/productivity/studio/fields.rst:303 +msgid "Sign (`binary`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:10 -msgid "Now, add a *Checkbox* field and define its invisibility options as *Country* (carefully select the one just created) *> is not = > France.*" +#: ../../content/applications/productivity/studio/fields.rst:305 +msgid "The :guilabel:`Sign` field is used to sign the form electronically. This field type is a :ref:`File field ` with the :guilabel:`Sign` widget selected by default. Consequently, the :guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have the same effects as described under :ref:`File `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:11 -msgid "You can now hide the related field created (*Country*) if you wish." +#: ../../content/applications/productivity/studio/fields.rst:311 +msgid "To give users the :guilabel:`Auto` option when having to draw their signature, select one of the available :guilabel:`Auto-complete with` fields (:ref:`Text `, :ref:`Many2One `, and :ref:`Related Field ` on the model only). The signature is automatically generated using the data from the selected field." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:19 -msgid "Another approach is to use the country’s ID. To do so, go to :menuselection:`Contacts --> Configuration --> Countries`, select France (for example), and on the URL check its *ID*." +#: ../../content/applications/productivity/studio/fields.rst:320 +msgid "Relational fields" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:21 -msgid "The related field invisibility path should now be *Country* (carefully select the one just created) *> is not = > 75*." +#: ../../content/applications/productivity/studio/fields.rst:322 +msgid "Relational fields are used to link and display the data from records on another model." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:22 -msgid "Again, hide the related field with the country’s ID if you prefer." +#: ../../content/applications/productivity/studio/fields.rst:330 +msgid "Many2One (`many2one`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:28 -msgid "**Case scenario 2: create a model called 'Properties' and add fields called: company, value, name, address, active, image.**" +#: ../../content/applications/productivity/studio/fields.rst:332 +msgid "The :guilabel:`Many2One` field is used to link another record (from another model) to the record being edited. The record's name from the other model is then displayed on the record being edited." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:31 -msgid "From the dashboard, (optionally) start a new module. Then, click on *Edit Menu* and start a *New Menu* (model). Set your menu name and *Confirm*. Now, on its form, drag & drop the necessary fields." +#: ../../content/applications/productivity/studio/fields.rst:336 +msgid "On the *Sales Order* model, the :guilabel:`Customer` field is a :guilabel:`Many2One` field pointing at the *Contact* model. This allows **many** sales orders to be linked to **one** contact (customer)." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:39 -msgid "**Case scenario 2.a: now, you would like to have a model called 'Regions' to which each property must be linked. And, on 'Regions', you would like to see the properties for each region.**" +#: ../../content/applications/productivity/studio/fields.rst:345 +msgid "To prevent users from creating a new record in the linked model, tick :guilabel:`Disable creation`." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:43 -msgid "Go to *Edit Menu > New Menu* and create your menu, calling it *Regions*. Add the necessary fields on its form by dragging & dropping them." +#: ../../content/applications/productivity/studio/fields.rst:347 +msgid "To prevent users from opening records in a pop-up window, tick :guilabel:`Disable opening`." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:45 -msgid "Now, in the form view of *Properties*, add a *Many2one* field with a relation to your model *Region*." +#: ../../content/applications/productivity/studio/fields.rst:348 +msgid "To help users only select the right record, click on :guilabel:`Domain` to create a filter." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:48 -msgid "The *Existing Fields* are the ones that are on the current model but not yet in the view." +#: ../../content/applications/productivity/studio/fields.rst:350 +msgid ":guilabel:`Badge`: displays the value inside a rounded shape, similar to a tag. The value cannot be edited on the UI." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:60 -msgid "Now, go to the model *Regions*, select the form view, and add a status button selecting *Regions (Properties)* as your relational field." +#: ../../content/applications/productivity/studio/fields.rst:357 +msgid "One2Many (`one2many`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:62 -msgid "*Status buttons* are computed fields, meaning that they count the numbers of records on the related model, and allow you to access them." +#: ../../content/applications/productivity/studio/fields.rst:359 +msgid "The :guilabel:`One2Many` field is used to display the existing relations between a record on the current model and multiple records from another model." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:69 -msgid "When searching for relations, click on *Search more* and filter it by *Custom*. This way you avoid creating duplicates." +#: ../../content/applications/productivity/studio/fields.rst:363 +msgid "You could add a :guilabel:`One2Many` field on the *Contact* model to look at **one** customer's **many** sales orders." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:76 -msgid "**Case scenario 2.b: in the model 'Properties', show all the tags as checkboxes instead of tags.**" +#: ../../content/applications/productivity/studio/fields.rst:371 +msgid "To use a :guilabel:`One2Many` field, the two models must have been linked already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search of existing Many2One relations is performed." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:78 -msgid "Once the field *Tags* is added to the form, select it and, under its *Properties > Widgets*, choose *Checkboxes*." +#: ../../content/applications/productivity/studio/fields.rst:378 +msgid "Lines (`one2many`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:85 -msgid "**Case scenario 3: on the leads’ form, add a selection field with the values:'Tags' & 'List' & 'Checkboxes'. According to the value of the field, show tags as many2many_tags, many2many_radio, or many2many(_list).**" +#: ../../content/applications/productivity/studio/fields.rst:380 +msgid "The :guilabel:`Lines` field is used to create a table with rows and columns (e.g., the lines of products on a sales order)." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:89 -msgid "In your form view, add a *Tags* field and relate it to *Partners Tag*. Under *Properties*, define its *Widget* as *Many2many*. Do the same process another 2 times for *Checkboxes* and *Tags*." +#: ../../content/applications/productivity/studio/fields.rst:384 +msgid "To modify the columns, click on the :guilabel:`Lines` field and then :guilabel:`Edit List View`. To edit the form that pops up when a user clicks on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:96 -msgid "Now, add a *Selection* field and the necessary values." +#: ../../content/applications/productivity/studio/fields.rst:397 +msgid "Many2Many (`many2many`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:99 -msgid "Continue by selecting your *Tags* fields, one by one, to set their *Invisible* options according to their *Widget*. In the example below, the invisibility rule for the *Partner Tags* is set as: *Select Tag type > is not = > Tags.*" +#: ../../content/applications/productivity/studio/fields.rst:399 +msgid "The :guilabel:`Many2Many` field is used to link multiple records from another model to multiple records on the current model. Many2Many fields can use :guilabel:`Disable creation`, :guilabel:`Disable opening`, :guilabel:`Domain`, just like :ref:`Many2One fields `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:105 -msgid "**Case scenario 4: on a quotation’s form, add a selection field called 'Manager Validation' with the values: ‘Accepted’ and ‘Refused’. Only a sales manager can see it, and the field should be set as mandatory if the untaxed amount is higher than 500€.**" +#: ../../content/applications/productivity/studio/fields.rst:405 +msgid "On the *Task* model, the :guilabel:`Assignees` field is a :guilabel:`Many2Many` field pointing at the *Contact* model. This allows a single user to be assigned to **many** tasks and **many** users to be assigned to a single task." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:109 -msgid "On your quotation form, add a *Selection* field with the values *Accepted* and *Refused*. Set its *Required* condition as *Untaxed Amount > 500* and the *Limit visibility to groups* as *Sales / Administrator* or managers." +#: ../../content/applications/productivity/studio/fields.rst:413 +msgid ":guilabel:`Checkboxes`: users can select several values using checkboxes." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:117 -msgid "**Case scenario 5: change the tooltip of a field for all views.**" +#: ../../content/applications/productivity/studio/fields.rst:414 +msgid ":guilabel:`Tags`: users can select several values appearing in rounded shapes, also known as *tags*. This has the same effect as selecting the :ref:`Tags field `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:119 -msgid "Activate the :ref:`developer mode ` and open Studio." +#: ../../content/applications/productivity/studio/fields.rst:421 +msgid "Tags (`many2many`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:122 -msgid "Select the necessary field and, under *Properties*, click on *More* to write your tooltip message on *Field Help*. The tooltip message is the explanatory message shown when the user hovers the field. The message here written is displayed on all views forms where the field is added." +#: ../../content/applications/productivity/studio/fields.rst:423 +msgid "The :guilabel:`Tags` field is used to display several values from another model appearing in rounded shapes, also known as *tags*. This field type is a :ref:`Many2Many field ` with the :guilabel:`Tags` widget selected by default. Consequently, the :guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same effects as described under :ref:`Many2Many `." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:129 -msgid "The *Field Help* message can only be applied to *new* fields. If you would like to change/apply a tooltip for a specific field, use the *Help Tooltip* option under *Properties*." +#: ../../content/applications/productivity/studio/fields.rst:430 +msgid "To display tags with different background colors, tick :guilabel:`Use colors`." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/views.rst:3 -msgid "Advanced Use Cases: Views" +#: ../../content/applications/productivity/studio/fields.rst:441 +msgid "Related Field (`related`)" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/views.rst:5 -msgid "**Case scenario 1: in Sales, show orders in a Kanban View instead of a List View.**" +#: ../../content/applications/productivity/studio/fields.rst:443 +msgid "A :guilabel:`Related Field` is not a relational field per se; no relationship is created between models. It uses an existing relationship to fetch and display information from another record." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/views.rst:7 -msgid "From the Sales page, access Studio and, under *Views*, set the *Kanban* option as the default one." +#: ../../content/applications/productivity/studio/fields.rst:447 +msgid "To display the email address of a customer on the *Sales Order* model, use the :guilabel:`Related Field` `partner_id.email` by selecting :guilabel:`Customer` and then :guilabel:`Email`." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/views.rst:14 -msgid "**Case scenario 2: allow for the list of leads to be edited inline without having to switch to the form view.**" +#: ../../content/applications/productivity/studio/fields.rst:453 +msgid "Properties" msgstr "" -#: ../../content/applications/productivity/studio/use_cases/views.rst:19 -msgid "On the *List View*, under *View* > *Editable*, choose between *New record on top* or *New record at the bottom*. This way, besides defining the order in which new records are displayed in the view, you are able to edit them." +#: ../../content/applications/productivity/studio/fields.rst:455 +msgid ":guilabel:`Invisible`: When it is not necessary for users to view a field on the UI, tick :guilabel:`Invisible`. It helps clear the UI by only showing the essential fields depending on a specific situation." msgstr "" -#: ../../content/applications/productivity/studio/use_cases/views.rst:21 -msgid "If the field is left blank, no editing is possible and records are shown based on your column preferences on the lead's page (front-end)." +#: ../../content/applications/productivity/studio/fields.rst:460 +msgid "On the *Form* view of the *Contact* model, the :guilabel:`Title` field only appears when :guilabel:`Individual` is selected, as that field would not be helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:465 +msgid "The :guilabel:`Invisible` attribute also applies to Studio. To view hidden fields inside Studio, click on a view's :guilabel:`View` tab and tick :guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:469 +msgid ":guilabel:`Required`: If a field should always be completed by the user before being able to proceed, tick :guilabel:`Required`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:471 +msgid ":guilabel:`Read only`: If users should not be able to modify a field, tick :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:474 +msgid "You can choose to apply these three properties only for specific records by clicking on :guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:477 +msgid ":guilabel:`Label`: The :guilabel:`Label` is the field's name on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:480 +msgid "This is not the same name as used in the PostgreSQL database. To view and change the latter, activate the :ref:`Developer mode `, and edit the :guilabel:`Technical Name`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:483 +msgid ":guilabel:`Help Tooltip`: To explain the purpose of a field, write a description under :guilabel:`Help Tooltip`. It is displayed inside a tooltip box when hovering with your mouse over the field's label." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:486 +msgid ":guilabel:`Placeholder`: To provide an example of how a field should be completed, write it under :guilabel:`Placeholder`. It is displayed in light gray in lieu of the field's value." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:488 +msgid ":guilabel:`Widget`: To change the default appearance or functionality of a field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:490 +msgid ":guilabel:`Default value`: To add a default value to a field when a record is created, use :guilabel:`Default value`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:492 +msgid ":guilabel:`Limit visibility to groups`: To limit which users can see the field, select a user access group." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:5 +msgid "Models determine the logical structure of a database and how data is stored, organized, and manipulated. In other words, a model is a table of information that can be linked with other tables. A model usually represents a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:9 +msgid "Modules and apps contain various elements, such as models, views, data files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:13 +msgid "All apps are modules. Larger, standalone modules are typically referred to as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:21 +msgid "When you create a new model or app with Studio, you can choose to add up to 14 features to speed up the creation process. These features bundle fields, default settings, and views that are usually used together to provide some standard functionality. Most of these features can be added later on, but adding them from the start makes the model creation process much easier. Furthermore, these features interact together in some cases to increase their usefulness." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:28 +msgid "Creating a model with the :ref:`studio/models-modules-apps/suggested-features/picture` and :ref:`studio/models-modules-apps/suggested-features/pipeline-stages` features enabled adds the image in the card layout of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:41 +msgid "Selecting :guilabel:`Contact details` adds to the :ref:`Form view ` a :ref:`Many2One field ` linked to the *Contact* model and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The :guilabel:`Contact` field is also added to the :ref:`List view `, and the :ref:`Map view ` is activated." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:59 +msgid "Selecting :guilabel:`User assignment` adds to the :ref:`Form view ` a :ref:`Many2One field ` linked to the *Contact* model, with the following :guilabel:`Domain`: `Share User is not set` to only allow the selection of *Internal Users*. In addition, the :guilabel:`many2one_avatar_user` widget is used to display the user's avatar. The :guilabel:`Responsible` field is also added to the :ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:77 +msgid "Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view ` a :ref:`Date field ` and activates the :ref:`Calendar view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:86 +msgid "Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view ` two :ref:`Date fields ` next to each other: one to set a start date, the other to set an end date, using the :guilabel:`daterange` widget, and activates the :ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:96 +msgid "Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view `, adds several fields such as :ref:`Priority ` and :guilabel:`Kanban State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and :guilabel:`Done`. The :guilabel:`Pipeline status bar` and the :guilabel:`Kanban State` field are added to the :ref:`Form view `. The :guilabel:`Color` field is added to the :ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:112 +msgid "Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Tags field `, creating a *Tag* model with preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:122 +msgid "Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view ` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:133 +msgid "Selecting :guilabel:`Lines`: adds to the :ref:`Form view ` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:141 +msgid "Selecting :guilabel:`Notes` adds to the :ref:`Form view ` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:149 +msgid "Selecting :guilabel:`Monetary value` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and :ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:162 +msgid "Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field ` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:174 +msgid "Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view ` a drag handle icon to manually reorder records." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:188 +msgid "Selecting :guilabel:`Chatter` adds to the :ref:`Form view ` Chatter functionalities (sending messages, logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:205 +msgid "Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive` action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:214 +msgid "When you do any customization with Studio, a new module named :guilabel:`Studio customizations` is added to your database." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:217 +msgid "To export these customizations, go to :menuselection:`Main dashboard --> Studio --> Customizations --> Export` to download a ZIP file containing all customizations." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:220 +msgid "To import and install these customizations in another database, connect to the destination database and go to :menuselection:`Main dashboard --> Studio --> Customizations --> Import`, then upload the exported ZIP file before clicking on the :guilabel:`Import` button." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:225 +msgid "Before importing, make sure the destination database contains the same apps and modules as the source database. Studio does not add the underlying modules as dependencies of the exported module." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:5 +msgid "Views are the interface that allows displaying the data contained in a model. One model can have several views, which are simply different ways to show the same data. In Studio, views are organized into four categories: :ref:`general `, :ref:`multiple records `, :ref:`timeline `, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:12 +msgid "To change the default view of a model, go to :menuselection:`Studio --> Views --> Dropdown menu (⋮) --> Set as Default`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:16 +msgid "You can modify views by using the built-in XML editor. To do so, activate :ref:`Developer mode `, go to the view you want to edit, select the :guilabel:`View` tab and then click on :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:21 +msgid "If you are editing a view using the XML editor, avoid making changes directly to standard views and inherited views, as those would be reset and would not be kept in case of an update or module upgrade. Always make sure you select the right Studio inherited views. Indeed, when you modify a view in Studio by drag-and-dropping a new field, a specific Studio inherited view and its XPath, the latter which defines which part of the view is modified, are automatically generated." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:31 +msgid "General views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:34 +#: ../../content/applications/productivity/studio/views.rst:97 +#: ../../content/applications/productivity/studio/views.rst:195 +#: ../../content/applications/productivity/studio/views.rst:311 +msgid "The settings described below are found under the view's :guilabel:`View` tab unless specified otherwise." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:40 +msgid "Form" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:42 +msgid "The :guilabel:`Form` view is used when creating and editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:45 +msgid "To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:47 +#: ../../content/applications/productivity/studio/views.rst:132 +msgid "To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:59 +msgid "Activity" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:61 +msgid "The :guilabel:`Activity` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:65 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:76 +msgid "Search" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:78 +msgid "The :guilabel:`Search` view is added on top of other views to filter, group, and search records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:80 +msgid "To add custom :guilabel:`Filters` and structure them using :guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:82 +msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion Fields`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:94 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:103 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:105 +msgid "The :guilabel:`Kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:109 +msgid "If the :guilabel:`Kanban` view exists, it is used by default to display data on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:112 +msgid "To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:113 +msgid "To create records directly within the view, in a minimalistic form, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:115 +msgid "To change the way records are grouped by default, select a new group under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:127 +msgid "List" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:129 +msgid "The :guilabel:`List` view is used to overview many records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:134 +msgid "To create and edit records directly within the view, select either :guilabel:`New record on top` or :guilabel:`New record at the bottom` under :guilabel:`Editable`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:138 +msgid "This prevents users from opening records in :ref:`Form view ` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:141 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:142 +msgid "To change the way records are sorted by default, select a field under :guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:145 +msgid "To add a drag handle icon to reorder records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:161 +msgid "Map" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:163 +msgid "The :guilabel:`Map` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:167 +msgid "A :ref:`Many2One field ` linked to the *Contact* model is required to activate the view, as the contact address is used to position records on the map." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:170 +msgid "To select which kind of contact should be used on the map, select it under :guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:172 +msgid "To hide the name or the address of the record, tick :guilabel:`Hide name` or :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:174 +msgid "To add information from other fields, select them under :guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:175 +msgid "To have a route suggested between the different records, tick :guilabel:`Enable Routing` and select which field should be used to sort records for the routing." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:187 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:190 +msgid "When you first activate one of the timeline views, you need to select which :ref:`Date ` or :ref:`Date & Time ` fields on your model should be used to define when the records start and stop in order to display them on the view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:201 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:203 +msgid "The :guilabel:`Calendar` view is used to overview and manage records inside a calendar." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:205 +msgid "To create records directly within the view instead of opening the :ref:`Form view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:209 +msgid "This only works on specific models that can be *quick-created* using only a *name*. However, most models do not support quick creation and open the :guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:213 +msgid "To color records on the calendar, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:217 +msgid "As the number of colors is limited, the same color can end up being assigned to different values." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:220 +msgid "To display events lasting the whole day at the top of the calendar, select a :ref:`Checkbox field ` that specifies if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:223 +msgid "To choose the default time scale used to display events, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:227 +msgid "You can also use :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:242 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:244 +msgid "The :guilabel:`Cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:247 +msgid "To display a measure (i.e., the aggregated value of a given field) by default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:249 +msgid "To choose which time interval is used by default to group results, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:251 +msgid "To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` :dfn:`the percentage of records staying over a period of time, it starts at 100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of records moving out over a period of time - it starts at 0% and increases with time`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:255 +msgid "To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is used." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:268 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:270 +msgid "The :guilabel:`Gantt` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:273 +msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:275 +msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:279 +msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:282 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:283 +msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:284 +msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:286 +msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:288 +msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:292 +msgid "As the number of colors is limited, the same color can be assigned to different values." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:294 +msgid "To specify with which degree of precision each time scale should be divided by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month Precision`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:308 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:317 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:319 +msgid "The :guilabel:`Pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:323 +msgid "To access all records whose data is aggregated under a cell, tick :guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:325 +msgid "To divide the data into different categories, select field(s) under :guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or :guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:327 +msgid "To add different types of data to be measured using the view, select a field under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:329 +msgid "To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:341 +msgid "Graph" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:343 +msgid "The :guilabel:`Graph` view is used to showcase data from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:345 +msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:347 +msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:349 +msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:351 +msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:354 +msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:356 +msgid "*For Bar charts only*: When using two data dimensions (categories), display the two columns on top of each other by default by ticking :guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:368 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:370 +msgid "The :guilabel:`Dashboard` view is used to display multiple reporting views and key performance indicators. Which elements are displayed on the view depends on the configuration of the other reporting views." msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index eafb0f725..8fbca02c0 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-07-22 09:36+0000\n" +"POT-Creation-Date: 2022-09-01 15:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -669,7 +669,7 @@ msgid ":doc:`reinvoice_from_project`" msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:112 -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:102 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:104 msgid ":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`" msgstr "" @@ -678,7 +678,7 @@ msgid "Invoice Time Spent on Tickets (Postpaid Support Services)" msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5 -msgid "The :guilabel:`Timesheet on Ticket` integration provides more control and transparency over how clients are charged, and what they're specifically billed for." +msgid "The :guilabel:`Timesheets` integration provides more control and transparency over how clients are charged, and what they're specifically billed for." msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:8 @@ -690,11 +690,11 @@ msgid "Configuration" msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15 -msgid "To turn on the :guilabel:`Timesheet on Ticket` feature, go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, select a Helpdesk team, and then, click :guilabel:`Edit`. Next, enable the options :guilabel:`Timesheet on Ticket` and :guilabel:`Time Reinvoicing`. Then, click :guilabel:`Save` to apply these changes to the Helpdesk team settings." +msgid "To turn on the :guilabel:`Timesheets` feature, go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, select a Helpdesk team, and then, click :guilabel:`Edit`. Next, enable the options :guilabel:`Timesheets` and :guilabel:`Time Billing`. Then, click :guilabel:`Save` to apply these changes to the Helpdesk team settings." msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:20 -msgid "Once the :guilabel:`Timesheet on Ticket` feature is enabled, a :guilabel:`Project` drop-down option will appear below :guilabel:`Timesheet on Ticket`. The :guilabel:`Project` drop-down option will automatically be set to a Project that Odoo created for the Helpdesk team. The tickets' timesheets will be stored in the selected Project." +msgid "Once the :guilabel:`Timesheets` feature is enabled, a :guilabel:`Project` drop-down option will appear below :guilabel:`Timesheets`. The :guilabel:`Project` drop-down option will automatically be set to a project that Odoo created for the Helpdesk team. The tickets' timesheets will be stored in the selected project." msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:26 @@ -710,7 +710,7 @@ msgid "If creating a new product from the sales order form, first give the produ msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:36 -msgid "First, in the :guilabel:`General Information` tab, set the :guilabel:`Product Type` to :guilabel:`Service` and the :guilabel:`Sales Price` to the Helpdesk agent's service rate. Then, in the :guilabel:`Sales` tab, set the :guilabel:`Service Invoicing Policy` to :guilabel:`Timesheets on tasks`. Finally, click :guilabel:`Save` to create the new product and add it to the quotation." +msgid "First, in the :guilabel:`General Information` tab, set the :guilabel:`Product Type` to :guilabel:`Service` and the :guilabel:`Sales Price` to the Helpdesk agent's service rate. Then, set the :guilabel:`Invoicing Policy` to :guilabel:`Based on Timesheets`. Finally, click :guilabel:`Save` to create the new product and add it to the quotation." msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:41 @@ -722,7 +722,7 @@ msgid "Record a timesheet" msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:50 -msgid "To record a timesheet, jump back to the Helpdesk ticket by going to the Helpdesk dashboard and clicking :guilabel:`Tickets` on the team's card (or by going to the Projects dashboard and clicking :guilabel:`Tickets` on the project card). Then, click :guilabel:`Edit` and use the :guilabel:`Timesheets` tab to record the time spent on the ticket." +msgid "To record a timesheet, jump back to the Helpdesk ticket by going to the :guilabel:`Helpdesk` dashboard, clicking :guilabel:`Tickets` on the team's card, and locating the correct ticket. Then, click :guilabel:`Edit` and use the :guilabel:`Timesheets` tab to record the time spent on the ticket." msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:60 @@ -734,30 +734,34 @@ msgid "Link the Helpdesk ticket to the SO" msgstr "" #: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:66 -msgid "Once a timesheet is recorded, the :guilabel:`Sales Order Item` field will appear on the ticket form. To link the :abbr:`SO (Sales Order)` to the ticket, start on the ticket form and click :guilabel:`Edit`. Next, select the :abbr:`SO (Sales Order)` that was created earlier from the drop-down menu. Odoo will automatically filter the sales orders to only show sales orders that are connected to the ticket's customer. Lastly, click :guilabel:`Save` to connect the ticket and the :abbr:`SO (Sales Order)`." +msgid "To link the :guilabel:`Sales Order` to the ticket, start on the ticket form and click :guilabel:`Edit`. Next, select the :guilabel:`Sales Order` that was created earlier from the :guilabel:`Sales Order Item` drop-down menu. Odoo will automatically filter the options to only show sales orders that are connected to the ticket's customer. Lastly, click :guilabel:`Save` to connect the ticket and the :guilabel:`Sales Order Item`." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:78 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:77 +msgid "The :guilabel:`Sales Order Item` can be connected to the ticket before or after any timesheets are recorded, the order doesn't matter." +msgstr "" + +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:81 msgid "Modify billing rates" msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:80 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:83 msgid "If a timesheet entry is recorded, but the agent does not want to bill the client for that time, go to the :guilabel:`Timesheets` tab and toggle on the visibility of the :guilabel:`Sales Order Item` column. When filling out the information for the timesheet entry, make sure to leave the non-billable timesheet entry's :guilabel:`Sales Order Item` field blank." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:85 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:88 msgid "If the agent wants to charge a different rate for a timesheet entry, first, add a new product to the connected :abbr:`SO (Sales Order)` priced at the new rate. Then, select the new product in the timesheet entry's :guilabel:`Sales Order Item` field." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:90 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:93 msgid "Create the invoice" msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:92 -msgid "When the Helpdesk ticket is completed and the client is ready to be billed for time, begin by clicking the :guilabel:`Sales Order` smart button on the ticket form to navigate to the :abbr:`SO (Sales Order)`. The :guilabel:`Delivered` column should match the number of hours recorded on the ticket's timesheet. After checking and filling out the relevant information, click :guilabel:`Create Invoice` to bill the client for the time spent on the ticket. Odoo will automatically generate an invoice to send to the client and the Helpdesk ticket can officially be closed." +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:95 +msgid "When the Helpdesk ticket is completed and the client is ready to be billed for time, begin by clicking the :guilabel:`Sales Order` smart button on the ticket form to navigate to the sales order. The :guilabel:`Delivered` column should match the number of hours recorded on the ticket's timesheet. After checking and filling out the relevant information, click :guilabel:`Create Invoice` to bill the client for the time spent on the ticket. Odoo will automatically generate an invoice to send to the client and the Helpdesk ticket can officially be closed." msgstr "" -#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:101 +#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:103 msgid ":doc:`invoice_time`" msgstr ""