NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[I18N] *: export latest terms

Browse Source 
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#9587

X-original-commit: f1d8cb8f16
Signed-off-by: Louis Wicket (wil) <wil@odoo.com>
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
This commit is contained in:
Tiffany Chang (tic) 2024-05-31 12:37:14 +02:00
parent 35931b493d
commit 3bfd593757
12 changed files with 13290 additions and 6659 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

380
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-04-30 09:16+0000\n"
"POT-Creation-Date: 2024-05-31 09:59+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -444,59 +444,59 @@ msgstr ""
msgid "To confirm the deletion, enter the :guilabel:`Password` and the :guilabel:`Login` for the account being deleted. Then, click the :guilabel:`Delete Account` button to confirm the deletion."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:34
#: ../../content/administration/odoo_accounts.rst:36
msgid "Odoo.com account password change"
msgstr ""
#: ../../content/administration/odoo_accounts.rst:36
#: ../../content/administration/odoo_accounts.rst:38
msgid "To change an Odoo.com account password, first login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the profile icon. Then, select :guilabel:`My Account`, and a portal dashboard appears."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:41
#: ../../content/administration/odoo_accounts.rst:43
msgid "To change the Odoo.com password, click on the :guilabel:`Edit Security Settings` link, below the :menuselection:`Account Security` section. Next, make the necessary changes by typing in the current :guilabel:`Password`, :guilabel:`New Password`, and verify the new password. Lastly, click on :guilabel:`Change Password` to complete the password change."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:47
#: ../../content/administration/odoo_accounts.rst:49
msgid "If a customer would like to change the login, contact Odoo support `here <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:51
#: ../../content/administration/odoo_accounts.rst:53
msgid "Passwords for Odoo.com users and portal users remain separate, even if the same email address is used."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:55
#: ../../content/administration/odoo_accounts.rst:57
msgid "Add two-factor authentication"
msgstr ""
#: ../../content/administration/odoo_accounts.rst:57
#: ../../content/administration/odoo_accounts.rst:59
msgid "To add two-factor authentication, login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the :guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal dashboard appears."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:62
#: ../../content/administration/odoo_accounts.rst:64
msgid "If the user would like to turn on two-factor authentication (2FA) for Odoo.com access, click on the :guilabel:`Edit Security Settings` link below the :menuselection:`Account Security` section."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:65
#: ../../content/administration/odoo_accounts.rst:67
msgid "Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor authentication)`. Then, confirm the current password in the :guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. Following that, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the :guilabel:`QR code` or entering a :guilabel:`Verification Code`."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:71
#: ../../content/administration/odoo_accounts.rst:73
msgid "Finally, click on :guilabel:`Enable two-factor authentication` to complete the setup."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:74
#: ../../content/administration/odoo_accounts.rst:76
msgid "Under :guilabel:`My Account` Odoo.com users can also access the following:"
msgstr ""
#: ../../content/administration/odoo_accounts.rst:76
#: ../../content/administration/odoo_accounts.rst:78
msgid ":guilabel:`My Partner dashboard`"
msgstr ""
#: ../../content/administration/odoo_accounts.rst:77
#: ../../content/administration/odoo_accounts.rst:79
msgid ":guilabel:`My In-App Services`"
msgstr ""
#: ../../content/administration/odoo_accounts.rst:78
#: ../../content/administration/odoo_accounts.rst:80
msgid ":guilabel:`My Apps Dashboard`"
msgstr ""
@ -3849,54 +3849,230 @@ msgid "It should be stored securely, and should be generated randomly e.g."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:743
msgid "which will generate a 32 characters pseudorandom printable string."
msgid "which generates a 32-character pseudorandom printable string."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:746
msgid "Supported Browsers"
msgid "Reset the master password"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:748
msgid "Odoo supports all the major desktop and mobile browsers available on the market, as long as they are supported by their publishers."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:751
msgid "Here are the supported browsers:"
msgid "There may be instances where the master password is misplaced, or compromised, and needs to be reset. The following process is for system administrators of an Odoo on-premise database detailing how to manually reset and re-encrypt the master password."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:753
msgid "Google Chrome"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:754
msgid "Mozilla Firefox"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:755
msgid "Microsoft Edge"
msgid "For more information about changing an Odoo.com account password, see this documentation: :ref:`odoocom/change_password`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:756
msgid "Apple Safari"
msgid "When creating a new on-premise database, a random master password is generated. Odoo recommends using this password to secure the database. This password is implemented by default, so there is a secure master password for any Odoo on-premise deployment."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:758
msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report."
#: ../../content/administration/on_premise/deploy.rst:761
msgid "When creating an Odoo on-premise database the installation is accessible to anyone on the internet, until this password is set to secure the database."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:763
msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:766
msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software."
#: ../../content/administration/on_premise/deploy.rst:764
msgid "The master password is specified in the Odoo configuration file (`odoo.conf` or `odoorc` (hidden file)). The Odoo master password is needed to modify, create, or delete a database through the graphical user interface (GUI)."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:769
msgid "Locate configuration file"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:771
msgid "First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden file))."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:775
#: ../../content/administration/on_premise/packages.rst:148
#: ../../content/administration/on_premise/source.rst:70
#: ../../content/administration/on_premise/source.rst:133
#: ../../content/administration/on_premise/source.rst:158
#: ../../content/administration/on_premise/source.rst:180
#: ../../content/administration/on_premise/source.rst:208
#: ../../content/administration/on_premise/source.rst:239
#: ../../content/administration/on_premise/source.rst:328
#: ../../content/administration/on_premise/source.rst:397
#: ../../content/administration/on_premise/source.rst:460
msgid "Windows"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:777
msgid "The configuration file is located at: `c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:779
#: ../../content/administration/on_premise/packages.rst:25
#: ../../content/administration/on_premise/source.rst:52
#: ../../content/administration/on_premise/source.rst:129
#: ../../content/administration/on_premise/source.rst:152
#: ../../content/administration/on_premise/source.rst:174
#: ../../content/administration/on_premise/source.rst:199
#: ../../content/administration/on_premise/source.rst:228
#: ../../content/administration/on_premise/source.rst:271
#: ../../content/administration/on_premise/source.rst:388
#: ../../content/administration/on_premise/source.rst:450
msgid "Linux"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:781
msgid "Depending on how Odoo is installed on the Linux machine, the configuration file is located in one of two different places:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:784
msgid "Package installation: `/etc/odoo.conf`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:785
msgid "Source installation: `~/.odoorc`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:788
msgid "Change old password"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:790
msgid "Once the appropriate file has been opened, proceed to modify the old password in the configuration file to a temporary password."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:795
#: ../../content/administration/on_premise/deploy.rst:843
msgid "Graphical user interface"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:797
msgid "After locating the configuration file, open it using a (:abbr:`GUI (graphical user interface)`). This can be achieved by simply double clicking on the file. Then, the device should have a default :abbr:`GUI (graphical user interface)` to open the file with."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:801
msgid "Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`, for example. This password can be anything, as long as it is saved temporarily. Make sure to modify all characters after the `=`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:806
#: ../../content/administration/on_premise/deploy.rst:825
msgid "The line appears like this: `admin_passwd = $pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:810
#: ../../content/administration/on_premise/deploy.rst:829
msgid "The modified line appears like this: `admin_passwd = newpassword1234`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:812
#: ../../content/administration/on_premise/deploy.rst:852
msgid "Command-line interface"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:814
msgid "Modify the master password line using the following Unix command detailed below."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:816
msgid "Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and edit the configuration file. To modify the configuration file, enter the following command: :command:`sudo nano /etc/odoo.conf`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:820
msgid "After opening the configuration file, modify the master password line `admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This password can be anything, as long as it is saved temporarily. Make sure to modify all characters after the `=`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:832
msgid "It is essential that the password is changed to something else, rather than triggering a new password reset by adding a semicolon `;` at the beginning of the line. This ensures the database is secure throughout the entire password reset process."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:837
msgid "Restart Odoo server"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:839
msgid "After setting the temporary password, a restart of the Odoo server is **required**."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:845
msgid "To restart the Odoo server, first, type `services` into the Windows :guilabel:`Search` bar. Then, select the :guilabel:`Services` application, and scroll down to the :guilabel:`Odoo` service."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:849
msgid "Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or :guilabel:`Restart`. This action manually restarts the Odoo server."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:854
msgid "Restart the Odoo server by typing the command: :command:`sudo service odoo15 restart`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:857
msgid "Change the number after `odoo` to fit the specific version the server is running on."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:860
msgid "Use web interface to re-encrypt password"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:862
msgid "First, navigate to `/web/database/manager` or `http://server_ip:port/web/database/manager` in a browser."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:866
msgid "Replace `server_ip` with the IP address of the database. Replace `port` with the numbered port the database is accessible from."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:869
msgid "Next, click :guilabel:`Set Master Password`, and type in the previously-selected temporary password into the :guilabel:`Master Password` field. Following this step, type in a :guilabel:`New Master Password`. The :guilabel:`New Master Password` is hashed (or encrypted), once the :guilabel:`Continue` button is clicked."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:874
msgid "At this point, the password has been successfully reset, and a hashed version of the new password now appears in the configuration file."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:878
msgid "For more information on Odoo database security, see this documentation: :ref:`db_manager_security`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:882
msgid "Supported Browsers"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:884
msgid "Odoo supports all the major desktop and mobile browsers available on the market, as long as they are supported by their publishers."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:887
msgid "Here are the supported browsers:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:889
msgid "Google Chrome"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:890
msgid "Mozilla Firefox"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:891
msgid "Microsoft Edge"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:892
msgid "Apple Safari"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:894
msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:899
msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:902
msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:905
msgid "technically a tool like socat_ can be used to proxy UNIX sockets across networks, but that is mostly for software which can only be used over UNIX sockets"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:773
#: ../../content/administration/on_premise/deploy.rst:909
msgid "or be accessible only over an internal packet-switched network, but that requires secured switches, protections against `ARP spoofing`_ and precludes usage of WiFi. Even over secure packet-switched networks, deployment over HTTPS is recommended, and possible costs are lowered as \"self-signed\" certificates are easier to deploy on a controlled environment than over the internet."
msgstr ""
@ -4065,19 +4241,6 @@ msgstr ""
msgid "It is required to be logged in as a paying on-premise customer or partner to download the Enterprise packages."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:25
#: ../../content/administration/on_premise/source.rst:52
#: ../../content/administration/on_premise/source.rst:129
#: ../../content/administration/on_premise/source.rst:152
#: ../../content/administration/on_premise/source.rst:174
#: ../../content/administration/on_premise/source.rst:199
#: ../../content/administration/on_premise/source.rst:228
#: ../../content/administration/on_premise/source.rst:271
#: ../../content/administration/on_premise/source.rst:384
#: ../../content/administration/on_premise/source.rst:446
msgid "Linux"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:28
#: ../../content/administration/on_premise/source.rst:116
msgid "Prepare"
@ -4109,7 +4272,7 @@ msgid "Make sure that the `sudo` command is available and well configured and, o
msgstr ""
#: ../../content/administration/on_premise/packages.rst:57
#: ../../content/administration/on_premise/source.rst:416
#: ../../content/administration/on_premise/source.rst:420
msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.6 <https://github.com/wkhtmltopdf/packaging/releases/tag/0.12.6.1-3>`_ for it to support headers and footers. Check out the `wkhtmltopdf wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more details on the various versions."
msgstr ""
@ -4161,19 +4324,6 @@ msgstr ""
msgid "Once downloaded, the package can be installed using the 'dnf' package manager:"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:148
#: ../../content/administration/on_premise/source.rst:70
#: ../../content/administration/on_premise/source.rst:133
#: ../../content/administration/on_premise/source.rst:158
#: ../../content/administration/on_premise/source.rst:180
#: ../../content/administration/on_premise/source.rst:208
#: ../../content/administration/on_premise/source.rst:239
#: ../../content/administration/on_premise/source.rst:324
#: ../../content/administration/on_premise/source.rst:393
#: ../../content/administration/on_premise/source.rst:456
msgid "Windows"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:151
msgid "Windows packaging is offered for the convenience of testing or running single-user local instances but production deployment is discouraged due to a number of limitations and risks associated with deploying Odoo on a Windows platform."
msgstr ""
@ -4289,9 +4439,9 @@ msgstr ""
#: ../../content/administration/on_premise/source.rst:186
#: ../../content/administration/on_premise/source.rst:213
#: ../../content/administration/on_premise/source.rst:253
#: ../../content/administration/on_premise/source.rst:347
#: ../../content/administration/on_premise/source.rst:405
#: ../../content/administration/on_premise/source.rst:467
#: ../../content/administration/on_premise/source.rst:351
#: ../../content/administration/on_premise/source.rst:409
#: ../../content/administration/on_premise/source.rst:471
msgid "Mac OS"
msgstr ""
@ -4405,152 +4555,156 @@ msgid "Using **distribution packages** is the preferred way of installing depend
msgstr ""
#: ../../content/administration/on_premise/source.rst:280
msgid "For Debian-based systems, the packages are listed in the `debian/control <https://github.com/odoo/odoo/blob/17.0/debian/control>`_ file of the Odoo sources."
msgid "On Debian/Ubuntu, the following commands should install the required packages:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:283
msgid "On Debian/Ubuntu, the following commands should install the required packages:"
#: ../../content/administration/on_premise/source.rst:287
msgid "The `setup/debinstall.sh` script will parse the `debian/control <https://github.com/odoo/odoo/blob/17.0/debian/control>`_ file and install the found packages."
msgstr ""
#: ../../content/administration/on_premise/source.rst:290
msgid "Install with pip"
msgstr ""
#: ../../content/administration/on_premise/source.rst:292
#: ../../content/administration/on_premise/source.rst:293
msgid "Using pip may lead to security issues and broken dependencies; only do this if you know what you are doing."
msgstr ""
#: ../../content/administration/on_premise/source.rst:296
msgid "As some of the Python packages need a compilation step, they require system libraries to be installed."
msgstr ""
#: ../../content/administration/on_premise/source.rst:295
#: ../../content/administration/on_premise/source.rst:299
msgid "On Debian/Ubuntu, the following command should install these required libraries:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:301
#: ../../content/administration/on_premise/source.rst:305
msgid "Odoo dependencies are listed in the :file:`requirements.txt` file located at the root of the Odoo Community directory."
msgstr ""
#: ../../content/administration/on_premise/source.rst:305
#: ../../content/administration/on_premise/source.rst:309
msgid "The Python packages in :file:`requirements.txt` are based on their stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo release. For example, for Odoo 15.0, the `python3-babel` package version is 2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is then chosen in the :file:`requirements.txt`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:312
#: ../../content/administration/on_premise/source.rst:334
#: ../../content/administration/on_premise/source.rst:353
#: ../../content/administration/on_premise/source.rst:316
#: ../../content/administration/on_premise/source.rst:338
#: ../../content/administration/on_premise/source.rst:357
msgid "It can be preferable not to mix Python module packages between different instances of Odoo or with the system. However, it is possible to use `virtualenv <https://pypi.org/project/virtualenv/>`_ to create isolated Python environments."
msgstr ""
#: ../../content/administration/on_premise/source.rst:316
#: ../../content/administration/on_premise/source.rst:320
msgid "Navigate to the path of the Odoo Community installation (:file:`CommunityPath`) and run **pip** on the requirements file to install the requirements for the current user."
msgstr ""
#: ../../content/administration/on_premise/source.rst:326
#: ../../content/administration/on_premise/source.rst:330
msgid "Before installing the dependencies, download and install the `Build Tools for Visual Studio <https://visualstudio.microsoft.com/downloads/>`_. Select **C++ build tools** in the **Workloads** tab and install them when prompted."
msgstr ""
#: ../../content/administration/on_premise/source.rst:330
#: ../../content/administration/on_premise/source.rst:349
#: ../../content/administration/on_premise/source.rst:334
#: ../../content/administration/on_premise/source.rst:353
msgid "Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo Community directory."
msgstr ""
#: ../../content/administration/on_premise/source.rst:338
#: ../../content/administration/on_premise/source.rst:342
msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file in a terminal **with Administrator privileges**:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:357
#: ../../content/administration/on_premise/source.rst:361
msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:367
#: ../../content/administration/on_premise/source.rst:371
msgid "Non-Python dependencies must be installed with a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
msgstr ""
#: ../../content/administration/on_premise/source.rst:370
#: ../../content/administration/on_premise/source.rst:374
msgid "Download and install the **Command Line Tools**:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:376
#: ../../content/administration/on_premise/source.rst:380
msgid "Use the package manager to install non-Python dependencies."
msgstr ""
#: ../../content/administration/on_premise/source.rst:379
#: ../../content/administration/on_premise/source.rst:383
msgid "For languages using a **right-to-left interface** (such as Arabic or Hebrew), the `rtlcss` package is required."
msgstr ""
#: ../../content/administration/on_premise/source.rst:386
#: ../../content/administration/on_premise/source.rst:390
msgid "Download and install **nodejs** and **npm** with a package manager."
msgstr ""
#: ../../content/administration/on_premise/source.rst:387
#: ../../content/administration/on_premise/source.rst:396
#: ../../content/administration/on_premise/source.rst:409
#: ../../content/administration/on_premise/source.rst:391
#: ../../content/administration/on_premise/source.rst:400
#: ../../content/administration/on_premise/source.rst:413
msgid "Install `rtlcss`:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:395
#: ../../content/administration/on_premise/source.rst:399
msgid "Download and install `nodejs <https://nodejs.org/en/download>`_."
msgstr ""
#: ../../content/administration/on_premise/source.rst:402
#: ../../content/administration/on_premise/source.rst:406
msgid "Edit the system environment's variable `PATH` to add the folder where `rtlcss.cmd` is located (typically: :file:`C:\\\\Users\\\\<user>\\\\AppData\\\\Roaming\\\\npm\\\\`)."
msgstr ""
#: ../../content/administration/on_premise/source.rst:407
#: ../../content/administration/on_premise/source.rst:411
msgid "Download and install **nodejs** with a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
msgstr ""
#: ../../content/administration/on_premise/source.rst:424
#: ../../content/administration/on_premise/source.rst:428
msgid "Running Odoo"
msgstr ""
#: ../../content/administration/on_premise/source.rst:426
#: ../../content/administration/on_premise/source.rst:430
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/on_premise/source.rst:429
#: ../../content/administration/on_premise/source.rst:433
msgid "To configure the server, either specify :ref:`command-line arguments <reference/cmdline/server>` or a :ref:`configuration file <reference/cmdline/config>`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:433
#: ../../content/administration/on_premise/source.rst:437
msgid "For the Enterprise edition, add the path to the `enterprise` add-ons to the `addons-path` argument. Note that it must come before the other paths in `addons-path` for add-ons to be loaded correctly."
msgstr ""
#: ../../content/administration/on_premise/source.rst:437
#: ../../content/administration/on_premise/source.rst:441
msgid "Common necessary configurations are:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:439
#: ../../content/administration/on_premise/source.rst:443
msgid "PostgreSQL user and password."
msgstr ""
#: ../../content/administration/on_premise/source.rst:440
#: ../../content/administration/on_premise/source.rst:444
msgid "Custom addon paths beyond the defaults to load custom modules."
msgstr ""
#: ../../content/administration/on_premise/source.rst:442
#: ../../content/administration/on_premise/source.rst:446
msgid "A typical way to run the server would be:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:453
#: ../../content/administration/on_premise/source.rst:474
#: ../../content/administration/on_premise/source.rst:457
#: ../../content/administration/on_premise/source.rst:478
msgid "Where `CommunityPath` is the path of the Odoo Community installation, and `mydb` is the name of the PostgreSQL database."
msgstr ""
#: ../../content/administration/on_premise/source.rst:463
#: ../../content/administration/on_premise/source.rst:467
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/on_premise/source.rst:477
#: ../../content/administration/on_premise/source.rst:481
msgid "After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open http://localhost:8069 in a web browser and log into the Odoo database with the base administrator account: use `admin` as the email and, again, `admin` as the password."
msgstr ""
#: ../../content/administration/on_premise/source.rst:482
#: ../../content/administration/on_premise/source.rst:486
msgid "From there, create and manage new :doc:`users <../../applications/general/users>`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:483
#: ../../content/administration/on_premise/source.rst:487
msgid "The user account used to log into Odoo's web interface differs from the :option:`--db_user <odoo-bin -r>` CLI argument."
msgstr ""
#: ../../content/administration/on_premise/source.rst:487
#: ../../content/administration/on_premise/source.rst:491
msgid ":doc:`The list of CLI arguments for odoo-bin </developer/reference/cli>`"
msgstr ""

571
locale/sources/essentials.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-04-30 09:16+0000\n"
"POT-Creation-Date: 2024-05-31 09:59+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -25,303 +25,446 @@ msgid "Activities"
msgstr ""
#: ../../content/applications/essentials/activities.rst:5
msgid "*Activities* are follow-up tasks tied to a record in an Odoo database. Activities can be scheduled on any page of the database that contains a chatter thread, kanban view, list view, or activities view of an application."
msgid "*Activities* are follow-up tasks tied to a record in an Odoo database."
msgstr ""
#: ../../content/applications/essentials/activities.rst:10
msgid "Schedule activities"
#: ../../content/applications/essentials/activities.rst:9
msgid "The icon used to display activities varies depending on the :ref:`activity type <activities/types>`:"
msgstr ""
#: ../../content/applications/essentials/activities.rst:11
msgid ":guilabel:`🕘 (clock)`: the default icon, which appears if nothing is scheduled."
msgstr ""
#: ../../content/applications/essentials/activities.rst:12
msgid "One way that activities are created is by clicking the :guilabel:`Schedule Activity` button, located at the top of the *chatter* on any record. On the pop-up window that appears, select an :guilabel:`Activity Type` from the drop-down menu."
msgid ":guilabel:`📞 (phone)`: this icon appears if a phone call is scheduled."
msgstr ""
#: ../../content/applications/essentials/activities.rst:17
msgid "Individual applications have a list of *Activity Types* dedicated to that application. For example, to view and edit the activities available for the *CRM* application, go to :menuselection:`CRM app --> Configuration --> Activity Types`."
#: ../../content/applications/essentials/activities.rst:13
msgid ":guilabel:`✉️ (envelope)`: this icon appears if an email is scheduled."
msgstr ""
#: ../../content/applications/essentials/activities.rst:14
msgid ":guilabel:`✔️ (checkmark)`: this icon appears if a to-do is scheduled."
msgstr ""
#: ../../content/applications/essentials/activities.rst:15
msgid ":guilabel:`(group of people)`: this icon appears if a meeting is scheduled."
msgstr ""
#: ../../content/applications/essentials/activities.rst:16
msgid ":guilabel:`(arrow pointing up above a line)`: this icon appears if a document is scheduled to be uploaded."
msgstr ""
#: ../../content/applications/essentials/activities.rst:18
msgid ":guilabel:`(pencil in a box)`: this icon appears if a signature request is scheduled."
msgstr ""
#: ../../content/applications/essentials/activities.rst:21
msgid "Enter a title for the activity in the :guilabel:`Summary` field, located in the :guilabel:`Schedule Activity` pop-up window."
msgid "Schedule activities"
msgstr ""
#: ../../content/applications/essentials/activities.rst:24
msgid "To assign the activity to a different user, select a name from the :guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the activity is automatically assigned."
msgstr ""
#: ../../content/applications/essentials/activities.rst:27
msgid "Lastly, feel free to add any additional information in the optional :guilabel:`Log a note...` field."
#: ../../content/applications/essentials/activities.rst:23
msgid "Activities can be scheduled on any page of the database that contains a :ref:`chatter <activities/chatter>` thread, :ref:`Kanban view <activities/kanban>`, :ref:`list view <activities/list>`, or :ref:`activities view <activities/activity>` of an application."
msgstr ""
#: ../../content/applications/essentials/activities.rst:30
msgid "The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up window auto-populates based on the configuration settings for the selected :guilabel:`Activity Type`. However, this date can be changed by selecting a day on the calendar in the :guilabel:`Due Date` field."
msgid "Chatter"
msgstr ""
#: ../../content/applications/essentials/activities.rst:32
msgid "Activities can be created from the chatter on any record."
msgstr ""
#: ../../content/applications/essentials/activities.rst:34
msgid "Lastly, click one of the following buttons:"
msgstr ""
#: ../../content/applications/essentials/activities.rst:36
msgid ":guilabel:`Schedule`: adds the activity to the chatter under :guilabel:`Planned activities`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:37
msgid ":guilabel:`Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, it is automatically marked as completed."
msgstr ""
#: ../../content/applications/essentials/activities.rst:39
msgid ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` marked as done, and opens a new activity window."
msgstr ""
#: ../../content/applications/essentials/activities.rst:41
msgid ":guilabel:`Discard`: discards any changes made on the pop-up window."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
#: ../../content/applications/essentials/activities.rst:-1
msgid "View of CRM leads and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:47
msgid "Depending on the activity type, the :guilabel:`Schedule` button may be replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` button."
msgstr ""
#: ../../content/applications/essentials/activities.rst:50
msgid "Scheduled activities are added to the chatter for the record under :guilabel:`Planned activities`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:55
msgid "Activities can also be scheduled from the kanban, list, or activities view of an application."
msgstr ""
#: ../../content/applications/essentials/activities.rst:59
msgid "Kanban view"
msgstr ""
#: ../../content/applications/essentials/activities.rst:61
msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill out the pop-up form."
msgstr ""
#: ../../content/applications/essentials/activities.rst:0
msgid "Kanban view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:67
msgid "List view"
msgstr ""
#: ../../content/applications/essentials/activities.rst:69
msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`. If the record already has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 (phone)` or an :guilabel:`✉️ (envelope)` icon."
msgstr ""
#: ../../content/applications/essentials/activities.rst:0
msgid "List view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:76
msgid "Activity view"
msgstr ""
#: ../../content/applications/essentials/activities.rst:78
msgid "To open the activity view for an application, select the :guilabel:`🕘 (clock)` icon from the menu bar anywhere in the database. Select any application from the drop-down menu, and click the :guilabel:`🕘 (clock)` icon for the desired app."
msgstr ""
#: ../../content/applications/essentials/activities.rst:0
msgid "Activity menu drop down with focus on where to open activity view for CRM."
msgstr ""
#: ../../content/applications/essentials/activities.rst:85
msgid "Select a record on which to schedule an activity. Move across the row to find the desired activity type, then click the :guilabel:`＋ (plus sign)`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:0
msgid "Activity view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:92
msgid "Activity colors, and their relation to an activity's due date, is consistent throughout Odoo, regardless of the activity type, or the view."
msgstr ""
#: ../../content/applications/essentials/activities.rst:95
msgid "Activities that appear in **green** indicate a due date sometime in the future."
msgstr ""
#: ../../content/applications/essentials/activities.rst:96
msgid "**Yellow** indicates that the activity's due date is today."
msgstr ""
#: ../../content/applications/essentials/activities.rst:97
msgid "**Red** indicates that the activity is overdue and the due date has passed."
msgstr ""
#: ../../content/applications/essentials/activities.rst:99
msgid "For example, if an activity is created for a phone call, and the due date passes, the activity appears with a red phone in list view, and a red clock on the kanban view."
msgstr ""
#: ../../content/applications/essentials/activities.rst:103
msgid "View scheduled activities"
msgstr ""
#: ../../content/applications/essentials/activities.rst:105
msgid "To view scheduled activities, open either the :menuselection:`Sales app` or :menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located to the far-right side of the other view options."
msgstr ""
#: ../../content/applications/essentials/activities.rst:108
msgid "Doing so opens the activities menu, showcasing all the scheduled activities for the user, by default. To show all activities for every user, remove the :guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar."
msgstr ""
#: ../../content/applications/essentials/activities.rst:112
msgid "To view a consolidated list of activities separated by the application where they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on the header menu to see the activities for that specific application in a drop-down menu."
msgstr ""
#: ../../content/applications/essentials/activities.rst:116
msgid "The possibility to :guilabel:`Add new note` and :guilabel:`Request a Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘 (clock)` icon on the header menu is clicked."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "View of CRM leads page emphasizing the activities menu."
msgstr ""
#: ../../content/applications/essentials/activities.rst:123
msgid "Configure activity types"
msgstr ""
#: ../../content/applications/essentials/activities.rst:125
msgid "To configure the types of activities in the database, go to :menuselection:`Settings app --> Discuss --> Activities --> Activity Types`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "View of the settings page emphasizing the menu activity types."
msgstr ""
#: ../../content/applications/essentials/activities.rst:131
msgid "Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found."
msgstr ""
#: ../../content/applications/essentials/activities.rst:133
msgid "To edit an existing activity type, select it from the list, then click :guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:136
msgid "At the top of a blank activity type form, start by choosing a :guilabel:`Name` for the new activity type."
msgid "To schedule a new activity, click the :guilabel:`Activities` button, located at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up window that appears, :ref:`fill out the Schedule Activity form <activities/form>`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "New activity type form."
msgstr ""
#: ../../content/applications/essentials/activities.rst:143
msgid "Activity settings"
#: ../../content/applications/essentials/activities.rst:45
msgid "Kanban view"
msgstr ""
#: ../../content/applications/essentials/activities.rst:146
msgid "Action"
#: ../../content/applications/essentials/activities.rst:47
msgid "Another way that activities are created is from the Kanban view in an application."
msgstr ""
#: ../../content/applications/essentials/activities.rst:148
msgid "The *Action* field specifies the intent of the activity. Some actions trigger specific behaviors after an activity is scheduled."
#: ../../content/applications/essentials/activities.rst:-1
msgid "The Kanban icon in the top menu, highlighted."
msgstr ""
#: ../../content/applications/essentials/activities.rst:53
msgid "To do so, click on the :guilabel:`🕘 (clock)` icon located at the bottom of an individual record."
msgstr ""
#: ../../content/applications/essentials/activities.rst:55
msgid "Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the Schedule Activity form <activities/form>`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "Kanban view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:63
#: ../../content/applications/essentials/activities.rst:82
msgid "If a record already has a scheduled activity, the :guilabel:`🕘 (clock)` icon is replaced by the icon that represents the existing scheduled activity. Click on the activity type's icon to schedule another activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:70
msgid "List view"
msgstr ""
#: ../../content/applications/essentials/activities.rst:72
msgid "Activities can also be created from a list view."
msgstr ""
#: ../../content/applications/essentials/activities.rst:74
msgid "If the :guilabel:`Activities` column is hidden, reveal it using the :guilabel:`(additional options toggle)` icon in the far-right of the top row, represented by two horizontal lines with two dots."
msgstr ""
#: ../../content/applications/essentials/activities.rst:77
msgid "Then, click on the :guilabel:`🕘 (clock)` icon for the record the activity is being added to, then click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the Schedule Activity form <activities/form>` that appears."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "List view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:93
msgid "Activity view"
msgstr ""
#: ../../content/applications/essentials/activities.rst:95
msgid "Most applications in Odoo have an *Activity* view available. If available, a :guilabel:`🕘 (clock)` activity icon is visible in the top-right of the main menu bar."
msgstr ""
#: ../../content/applications/essentials/activities.rst:98
msgid "To open the activity view, click the :guilabel:`🕘 (clock)` activity icon."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "Top-right menu with the Activities icon called out."
msgstr ""
#: ../../content/applications/essentials/activities.rst:104
msgid "In this view, all the available activities are listed in the columns, while the horizontal entries represent all the individual records."
msgstr ""
#: ../../content/applications/essentials/activities.rst:107
msgid "Activities that appear green have a due date in the future, activities that appear orange are due today, while activities appearing red are overdue."
msgstr ""
#: ../../content/applications/essentials/activities.rst:110
msgid "Color bars in each column represent records for specific activity types, and display a number indicating how many activities are scheduled for that type."
msgstr ""
#: ../../content/applications/essentials/activities.rst:113
msgid "If multiple activity types are scheduled for a record, a number appears in the box, indicating the total number of scheduled activities."
msgstr ""
#: ../../content/applications/essentials/activities.rst:117
msgid "Activity colors, and their relation to an activity's due date, is consistent throughout Odoo, regardless of the activity type, or the view."
msgstr ""
#: ../../content/applications/essentials/activities.rst:120
msgid "To schedule an activity for a record, hover over the corresponding field, and a :guilabel:`➕ (plus sign)` appears. Click the :guilabel:`➕ (plus sign)`, and then :ref:`fill out the Schedule Activity form <activities/form>`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "Activity view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:131
msgid "Schedule Activity form"
msgstr ""
#: ../../content/applications/essentials/activities.rst:133
msgid "Activities can be scheduled from many different places, such as from the :ref:`chatter <activities/chatter>` of a record, or from one of multiple views in an application, when available: the :ref:`Kanban view <activities/kanban>`, :ref:`list view <activities/list>`, or :ref:`activity view <activities/activity>`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:138
#: ../../content/applications/essentials/activities.rst:220
msgid "Enter the following information on the form:"
msgstr ""
#: ../../content/applications/essentials/activities.rst:140
msgid ":guilabel:`Activity Type`: select the type of activity from the drop-down menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other applications are installed, additional options may be available."
msgstr ""
#: ../../content/applications/essentials/activities.rst:145
msgid "Individual applications have a list of dedicated :ref:`activity types <activities/types>`. For example, installing the *Sales* application makes :guilabel:`Order Upsell` available, while installing the *Sign* application makes :guilabel:`Request Signature` available."
msgstr ""
#: ../../content/applications/essentials/activities.rst:149
msgid ":guilabel:`Summary`: enter a short title for the activity, such as `Discuss Proposal`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:150
msgid ":guilabel:`Due Date`: using the calendar popover, select the activity's deadline."
msgstr ""
#: ../../content/applications/essentials/activities.rst:151
msgid "If :guilabel:`Upload Document` is selected, a link to upload a document is added directly to the planned activity in the chatter."
msgid ":guilabel:`Assigned to`: by default, the current user populates this field. To assign a different user to the activity, select them from the drop-down menu."
msgstr ""
#: ../../content/applications/essentials/activities.rst:153
msgid "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users have the option to open their calendar to schedule a time for this activity."
msgid ":guilabel:`Notes`: add any additional information for the activity in this field."
msgstr ""
#: ../../content/applications/essentials/activities.rst:155
msgid "If :guilabel:`Request Signature` is selected, a link is added to the planned activity in the chatter that opens a signature request pop-up window."
msgid "When the :guilabel:`Schedule Activity` pop-up window is completed, click one of the following buttons:"
msgstr ""
#: ../../content/applications/essentials/activities.rst:159
msgid "The actions available to select on an activity type vary, depending on the applications currently installed in the database."
#: ../../content/applications/essentials/activities.rst:158
msgid ":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:163
msgid "Default user"
#: ../../content/applications/essentials/activities.rst:160
msgid "Click on the desired date and time for the activity, and a :guilabel:`New Event` pop-up window appears. The summary from the *Schedule Activity* pop-up window populates the :guilabel:`Title` field."
msgstr ""
#: ../../content/applications/essentials/activities.rst:165
msgid "To automatically assign this activity to a specific user when this activity type is scheduled, choose a name from the :guilabel:`Default User` drop-down menu. If this field is left blank, the activity is assigned to the user who creates the activity."
#: ../../content/applications/essentials/activities.rst:164
msgid "Enter the information in the :guilabel:`New Event` pop-up window, then click :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is added to the chatter under the :guilabel:`Planned Activities` section."
msgstr ""
#: ../../content/applications/essentials/activities.rst:170
msgid "Default summary"
#: ../../content/applications/essentials/activities.rst:169
msgid "The :guilabel:`Open Calendar` button **only** appears if the :guilabel:`Activity Type` is set to either :guilabel:`Call` or :guilabel:`Meeting`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:172
msgid "To include notes whenever this activity type is created, enter them into the :guilabel:`Default Summary` field."
msgid ":guilabel:`Schedule`: schedules the activity, and adds the activity to the chatter under :guilabel:`Planned Activities`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:174
msgid ":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, and is automatically marked as done."
msgstr ""
#: ../../content/applications/essentials/activities.rst:176
msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved."
msgid ":guilabel:`Done & Schedule Next`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, is automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up window appears."
msgstr ""
#: ../../content/applications/essentials/activities.rst:181
msgid "Next activity"
#: ../../content/applications/essentials/activities.rst:179
msgid ":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule Activity` pop-up window."
msgstr ""
#: ../../content/applications/essentials/activities.rst:183
msgid "To automatically suggest, or trigger, a new activity after an activity has been marked complete, the :guilabel:`Chaining Type` must be set."
#: ../../content/applications/essentials/activities.rst:-1
msgid "View of CRM leads and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:187
msgid "Suggest next activity"
#: ../../content/applications/essentials/activities.rst:188
msgid "All scheduled activities"
msgstr ""
#: ../../content/applications/essentials/activities.rst:189
msgid "In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next Activity`. Upon doing so, the field underneath changes to: :guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to select any activities to recommend as follow-up tasks to this activity type."
#: ../../content/applications/essentials/activities.rst:190
msgid "To view a consolidated list of activities, organized by application, click the :guilabel:`🕘 (clock)` icon in the header menu, located in the top-right."
msgstr ""
#: ../../content/applications/essentials/activities.rst:193
#: ../../content/applications/essentials/activities.rst:220
msgid "In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so, configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity deadline`."
msgid "If any activities are scheduled, the number of activities appear in a red bubble on the :guilabel:`🕘 (clock)` icon."
msgstr ""
#: ../../content/applications/essentials/activities.rst:198
#: ../../content/applications/essentials/activities.rst:225
msgid "This :guilabel:`Schedule` field information can be altered before the activity is scheduled."
#: ../../content/applications/essentials/activities.rst:196
msgid "All activities for each application are further divided into subsections, indicating where in the application the activity is to be completed. Each sub-section lists the number of scheduled activities that are :guilabel:`Late`, due :guilabel:`Today`, and scheduled in the :guilabel:`Future`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:200
#: ../../content/applications/essentials/activities.rst:227
msgid "When all configurations are complete, click :guilabel:`Save`."
#: ../../content/applications/essentials/activities.rst:202
msgid "In the *Time Off* application, one activity is scheduled to be done in the *All Time Off* requests dashboard, and six activities are scheduled to be done in the *Allocations* dashboard."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "Schedule activity popup with emphasis on recommended activities."
#: ../../content/applications/essentials/activities.rst:205
msgid "These requests appear in two separate lists in the all activities drop-down menu: one labeled `Time Off` and one labeled `Time Off Allocation`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:206
msgid "If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest Next Activity`, and has activities listed in the :guilabel:`Suggest` field, users are presented with recommendations for activities as next steps."
#: ../../content/applications/essentials/activities.rst:0
msgid "The list of activities that is accessed from the main menu bar. Two entries for the Time\n"
"Off application are highlighted."
msgstr ""
#: ../../content/applications/essentials/activities.rst:211
msgid "Trigger next activity"
msgstr ""
#: ../../content/applications/essentials/activities.rst:213
msgid "Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` immediately launches the next activity once the previous one is completed."
#: ../../content/applications/essentials/activities.rst:214
msgid "Request a document"
msgstr ""
#: ../../content/applications/essentials/activities.rst:216
msgid "If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining Type` field, the field beneath changes to: :guilabel:`Trigger`. From the :guilabel:`Trigger` field drop-down menu, select the activity that should be launched once this activity is completed."
msgid "The option to :guilabel:`Request a Document` is available at the bottom of the list of :ref:`all scheduled activities <activities/all>`, the option to :guilabel:`Request a Document` appears. Click :guilabel:`Request a Document`, and a :guilabel:`Request a file` pop-up window appears."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "Schedule new activity popup with emphasis on Done and launch next button."
#: ../../content/applications/essentials/activities.rst:222
msgid ":guilabel:`Document Name`: enter a name for the document being requested."
msgstr ""
#: ../../content/applications/essentials/activities.rst:223
msgid ":guilabel:`Request To`: select the user the document is being requested from using the drop-down menu."
msgstr ""
#: ../../content/applications/essentials/activities.rst:225
msgid ":guilabel:`Due Date In`: enter a numerical value indicating when the document is due. Next to this field, a :guilabel:`Days` field is visible. Click :guilabel:`Days`, the default option, to reveal a drop-down menu. Select the desired time-frame option from the list. The options are :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:229
msgid ":guilabel:`Workspace`: using the drop-down menu, select the specific :ref:`Workspace <documents/workspaces>` the document is being uploaded to."
msgstr ""
#: ../../content/applications/essentials/activities.rst:231
msgid ":guilabel:`Tags`: select any desired tags from the drop-down menu. The available tags displayed are based on the tags configured for the selected :guilabel:`Workspace`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:233
msgid "When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger Next Activity`, marking the activity as `Done` immediately launches the next activity listed in the :guilabel:`Trigger` field."
msgid ":guilabel:`Message`: enter a message to clarify the document request in this field."
msgstr ""
#: ../../content/applications/essentials/activities.rst:238
msgid ":doc:`/applications/productivity/discuss`"
#: ../../content/applications/essentials/activities.rst:235
msgid "When all the fields are completed, click :guilabel:`Request` to send the document request."
msgstr ""
#: ../../content/applications/essentials/activities.rst:239
msgid ":doc:`/applications/productivity/discuss/team_communication`"
#: ../../content/applications/essentials/activities.rst:-1
msgid "The Request a file form, with all fields filled out to request a contract."
msgstr ""
#: ../../content/applications/essentials/activities.rst:244
msgid "Activity types"
msgstr ""
#: ../../content/applications/essentials/activities.rst:246
msgid "To view the currently configured types of activities in the database, navigate to :menuselection:`Settings app --> Discuss section --> Activities setting --> Activity Types`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "Activity Types button in the Settings application under the Discuss section."
msgstr ""
#: ../../content/applications/essentials/activities.rst:253
msgid "Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "The list of activity types already configured and available."
msgstr ""
#: ../../content/applications/essentials/activities.rst:260
msgid "Edit activity types"
msgstr ""
#: ../../content/applications/essentials/activities.rst:262
msgid "To edit an existing :ref:`activity type <activities/types>`, click on the activity type, and the activity type form loads."
msgstr ""
#: ../../content/applications/essentials/activities.rst:265
msgid "Make any desired changes to the activity type form. The form automatically saves, but it can be saved manually at any time by clicking the :guilabel:`Save Manually` option, represented by a :guilabel:`(cloud upload)` icon, located in the top-left corner of the page."
msgstr ""
#: ../../content/applications/essentials/activities.rst:270
msgid "Create new activity types"
msgstr ""
#: ../../content/applications/essentials/activities.rst:272
msgid "To create a new :ref:`activity type <activities/types>`, click :guilabel:`New` from the :guilabel:`Activity Types` page, and a blank activity type form loads."
msgstr ""
#: ../../content/applications/essentials/activities.rst:275
msgid "Enter a :guilabel:`Name` for the activity type at the top of the form, then enter the following information on the form."
msgstr ""
#: ../../content/applications/essentials/activities.rst:279
msgid "Activity Settings section"
msgstr ""
#: ../../content/applications/essentials/activities.rst:281
msgid ":guilabel:`Action`: using the drop-down menu, select an action associated with this new activity type. Some actions trigger specific behaviors after an activity is scheduled, such as:"
msgstr ""
#: ../../content/applications/essentials/activities.rst:284
msgid ":guilabel:`Upload Document`: if selected, a link to upload a document is automatically added to the planned activity in the chatter."
msgstr ""
#: ../../content/applications/essentials/activities.rst:286
msgid ":guilabel:`Call` or :guilabel:`Meeting`: if selected, users have the option to open their calendar to select a date and time for the activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:288
msgid ":guilabel:`Request Signature`: if selected, a link to open a signature request pop-up window is automatically added to the planned activity in the chatter. This requires the Odoo *Sign* application to be installed."
msgstr ""
#: ../../content/applications/essentials/activities.rst:293
msgid "Available activity types vary based on the installed applications in the database."
msgstr ""
#: ../../content/applications/essentials/activities.rst:295
msgid ":guilabel:`Folder`: select a specific :ref:`workspace <documents/workspaces>` folder to save a document to. This field **only** appears if :guilabel:`Upload Document` is selected for the :guilabel:`Action`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:299
msgid "Using the drop-down menu, select the :guilabel:`Folder` the document is saved to."
msgstr ""
#: ../../content/applications/essentials/activities.rst:301
msgid ":guilabel:`Default User`: select a user from the drop-down menu to automatically assign this activity to the selected user when this activity type is scheduled. If this field is left blank, the activity is assigned to the user who creates the activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:304
msgid ":guilabel:`Default Summary`: enter a note to include whenever this activity type is created."
msgstr ""
#: ../../content/applications/essentials/activities.rst:307
msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved."
msgstr ""
#: ../../content/applications/essentials/activities.rst:311
msgid ":guilabel:`Keep Done`: tick this checkbox to keep activities that have been marked as `Done` visible in the :ref:`activity view <activities/activity>`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:313
msgid ":guilabel:`Default Note`: enter any notes to appear with the activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:316
msgid "Next Activity section"
msgstr ""
#: ../../content/applications/essentials/activities.rst:318
msgid "It is possible to have another activity either suggested or triggered. To do so, configure the :guilabel:`Next Activity` section."
msgstr ""
#: ../../content/applications/essentials/activities.rst:321
msgid ":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` field is displayed."
msgstr ""
#: ../../content/applications/essentials/activities.rst:326
msgid "The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload Document` is selected for the :guilabel:`Action`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:329
msgid ":guilabel:`Suggest/Trigger`: depending on what is selected for the :guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or :guilabel:`Trigger`. Using the drop-down menu, select the activity to recommend or schedule as a follow-up task to the activity type."
msgstr ""
#: ../../content/applications/essentials/activities.rst:332
msgid ":guilabel:`Schedule`: configure when the next activity is suggested or triggered."
msgstr ""
#: ../../content/applications/essentials/activities.rst:334
msgid "First, enter a numerical value indicating when the activity is suggested or triggered."
msgstr ""
#: ../../content/applications/essentials/activities.rst:336
msgid "Next to this field, a :guilabel:`Days` field is visible. Click :guilabel:`Days`, the default option, to reveal a drop-down menu. Select the desired time-frame option from the list. The options are :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:340
msgid "Lastly, using the drop-down menu, select whether the activity is scheduled or triggered either :guilabel:`after previous activity deadline` or :guilabel:`after completion date`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:-1
msgid "A new Activity form with all the fields filled out."
msgstr ""
#: ../../content/applications/essentials/activities.rst:348
msgid ":doc:`../productivity/discuss`"
msgstr ""
#: ../../content/applications/essentials/activities.rst:349
msgid ":doc:`../productivity/discuss/team_communication`"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:3

3282
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

238
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-04-30 09:16+0000\n"
"POT-Creation-Date: 2024-05-31 09:59+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1241,107 +1241,75 @@ msgid "When editing the translations, the default language set in the database a
msgstr ""
#: ../../content/applications/general/developer_mode.rst:5
msgid "Developer Mode (debug mode)"
msgid "Developer mode (debug mode)"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:7
msgid "The developer mode (or debug mode) unlocks access to extra and advanced tools in Odoo. There are several ways to activate the developer mode: through the :ref:`settings <general/developer_mode/settings>`, the :ref:`browser extension <general/developer_mode/browser-extension>`, through the :ref:`command palette <general/developer_mode/command-palette>` or the :ref:`URL <general/developer_mode/url>`."
msgid "The developer mode, also known as debug mode, unlocks access to advanced :ref:`tools and settings <developer-mode/tools>` in Odoo."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:17
msgid "Activate through the Settings"
#: ../../content/applications/general/developer_mode.rst:11
msgid "Proceed with caution, as some developer tools and technical settings are considered advanced and may have associated risks. Only use them if you understand the implications and are confident in your actions."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:19
msgid "The debug mode can be activated in the Odoo database settings. Go to :menuselection:`Settings --> General Settings --> Developer Tools` and click on :guilabel:`Activate the developer mode`. At least one application needs to be installed for the :guilabel:`Developer Tools` section to appear in the :guilabel:`Settings` module."
#: ../../content/applications/general/developer_mode.rst:16
msgid "The developer mode is also available with :ref:`assets <frontend/framework/assets_debug_mode>`, which are used to debug JavaScript code, and with :ref:`tests assets <frontend/framework/tests_debug_mode>`, which are used to run test tours."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Overview of the debug options under settings in Odoo."
#: ../../content/applications/general/developer_mode.rst:23
msgid "Activation"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:29
msgid ":guilabel:`Activate the developer mode (with assets)` is used by developers; :guilabel:`Activate the developer mode (with tests assets)` is used by developers and testers."
#: ../../content/applications/general/developer_mode.rst:25
msgid "To activate it, open the :guilabel:`Settings` app, scroll down to the :guilabel:`Developer Tools` section, and click :guilabel:`Activate the developer mode`."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:32
#: ../../content/applications/general/developer_mode.rst:28
msgid "Once activated, the :guilabel:`Deactivate the developer mode` option becomes available."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Activating the developer mode in the Settings app"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:33
msgid "To activate the developer mode **from anywhere in the database**, add `?debug=1` to the URL after `/web` (e.g., `https://example.odoo.com/web?debug=1#action=menu&cids=1`). To deactivate it, use `?debug=0` instead."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:37
msgid "Activate through the browser extension"
msgid "Use `?debug=assets` to activate the developer mode with assets and `?debug=tests` to activate it with tests assets."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:39
msgid "Within a web browser, navigate to the browser settings and extensions and search for the `Odoo Debug` extension. Once the extension is installed, a new icon will be shown on the browser's toolbar."
#: ../../content/applications/general/developer_mode.rst:41
msgid "Open the **command palette** by pressing `Ctrl + K` or `Cmd ⌘ + K`, then type `debug` to activate the developer mode with assets or deactivate it."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:43
msgid "For the *Odoo Debug* extension, a single click enables a normal version of the mode, while a double click enables it with assets. To deactivate it, use a single click."
#: ../../content/applications/general/developer_mode.rst:44
msgid "Browser extension"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:46
msgid "The `Odoo Debug <https://github.com/Droggol/OdooDebug>`_ browser extension adds an icon to toggle developer mode on or off from the browser's toolbar. It is available on the `Chrome Web Store <https://chromewebstore.google.com/detail/odoo-debug/hmdmhilocobgohohpdpolmibjklfgkbi>`_ and `Firefox Add-ons <https://addons.mozilla.org/firefox/addon/odoo-debug/>`_."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:54
msgid "Developer tools and technical menu"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:56
msgid "Once the developer mode is activated, the developer tools can be accessed by clicking the :icon:`fa-bug` :guilabel:`(bug)` icon. The menu contains tools useful for understanding or editing technical data, such as a view's field, filters, or actions. The options available depend on where the menu is accessed from."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "View of Odoo's debug icon in a Google Chrome toolbar."
msgid "Accessing the developer tools"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:53
msgid "Activate through the command palette"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:55
msgid "In Odoo, the command palette tool has a command to activate the debug mode. First, open the command palette tool with the keyboard shortcut `ctrl+k` and then type `debug`. A command will show up to activate the debug mode."
#: ../../content/applications/general/developer_mode.rst:64
msgid "Database administrators can access the technical menu from the :guilabel:`Settings` app. It contains advanced database settings, such as ones related to the database structure, security, actions, etc."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Command palette with debug command."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:68
msgid "Activate through the URL"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:70
msgid "The debug mode can also be activated by adding an extra query string to the database's URL. In the URL, add `?debug=1` or `?debug=true` after `/web`. To deactivate the debug mode, change the value to `?debug=0` instead."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Overview of a URL with the debug mode command added."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:79
msgid "Additional modes are available for developers: `?debug=assets` enables the :ref:`assets mode <frontend/framework/assets_debug_mode>`, and `?debug=tests` enables the :ref:`tests mode <frontend/framework/tests_debug_mode>`."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:86
msgid "Locate the developer mode tools"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:88
msgid "Once developer mode is activated, the developer mode tools can be accessed from the :guilabel:`Open Developer Tools` button, the bug icon located in the header of the Odoo database."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Overview of a console page and the debug icon being shown in Odoo."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:95
msgid "This menu contains additional tools that are useful to understand or edit technical data, such as the views or actions of a page. On a page that has filters, actions, and view options, the developer mode tools contain some useful menu items such as:"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:99
msgid ":guilabel:`Edit Action`"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:100
msgid ":guilabel:`Manage Filters`"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:101
msgid "Edit the current view (e.g. Kanban, List, Graph, etc.)"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:102
msgid "See the :guilabel:`Fields View Get`"
msgid "Accessing the technical menu"
msgstr ""
#: ../../content/applications/general/email_communication.rst:5
@ -1803,220 +1771,220 @@ msgstr ""
msgid "Check if the :abbr:`DKIM (DomainKeys Identified Mail)` record is valid with a free tool like `DKIM Core <https://dkimcore.org/tools/>`_. If a selector is asked, enter `odoo`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:100
#: ../../content/applications/general/email_communication/email_domain.rst:102
msgid "Check the DMARC policy"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:102
#: ../../content/applications/general/email_communication/email_domain.rst:104
msgid "The Domain-based Message Authentication, Reporting, & Conformance (DMARC) record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and :abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name tell the destination server what to do with an incoming email that fails the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:110
#: ../../content/applications/general/email_communication/email_domain.rst:112
msgid "DMARC: TXT record"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:112
#: ../../content/applications/general/email_communication/email_domain.rst:114
msgid "`v=DMARC1; p=none;`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:114
#: ../../content/applications/general/email_communication/email_domain.rst:116
msgid "There are three :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policies:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:117
#: ../../content/applications/general/email_communication/email_domain.rst:119
msgid "`p=none`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:118
#: ../../content/applications/general/email_communication/email_domain.rst:171
#: ../../content/applications/general/email_communication/email_domain.rst:120
#: ../../content/applications/general/email_communication/email_domain.rst:173
msgid "`p=quarantine`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:119
#: ../../content/applications/general/email_communication/email_domain.rst:121
msgid "`p=reject`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:121
#: ../../content/applications/general/email_communication/email_domain.rst:123
msgid "`p=quarantine` and `p=reject` instruct the server that receives an email to quarantine that email or ignore it if the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check fails."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:125
#: ../../content/applications/general/email_communication/email_domain.rst:127
msgid "If the domain name uses :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` and has defined one of these policies, the domain must be :abbr:`SPF (Sender Policy Framework)` compliant or enable :abbr:`DKIM (DomainKeys Identified Mail)`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:130
#: ../../content/applications/general/email_communication/email_domain.rst:132
msgid "Yahoo or AOL are examples of email providers with a :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policy set to `p=reject`. Odoo strongly advises against using an *@yahoo.com* or *@aol.com* address for the database users. These emails will never reach their recipient."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:135
#: ../../content/applications/general/email_communication/email_domain.rst:137
msgid "`p=none` is used for the domain owner to receive reports about entities using their domain. It should not impact the deliverability if the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` check fails."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:139
#: ../../content/applications/general/email_communication/email_domain.rst:141
msgid ":abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` records are comprised of tags in the form of :abbr:`DNS (Domain Name System)` records. These tags/parameters allow for reporting, such as :abbr:`RUA (Reporting URI of aggregate reports)` and :abbr:`RUF (Reporting URI for forensic reports)`, along with more precise specification like :abbr:`PCT (Percentage of messages subjected to filtering)`, :abbr:`P (Policy for organizational domain)`, :abbr:`SP (Policy for subdomains of the OD)` :abbr:`ADKIM (Alignment mode for DKIM)` & :abbr:`ASPF (Alignment mode for SPF)`. For best practice, the the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policy should not start out being too restrictive."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:148
#: ../../content/applications/general/email_communication/email_domain.rst:150
msgid "The following chart displays available tags:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:154
#: ../../content/applications/general/email_communication/email_domain.rst:156
msgid "Tag Name"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:155
#: ../../content/applications/general/email_communication/email_domain.rst:157
msgid "Purpose"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:156
#: ../../content/applications/general/email_communication/email_domain.rst:158
msgid "Example"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:157
#: ../../content/applications/general/email_communication/email_domain.rst:159
msgid "v"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:158
#: ../../content/applications/general/email_communication/email_domain.rst:160
msgid "Protocol version"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:159
#: ../../content/applications/general/email_communication/email_domain.rst:161
msgid "`v=DMARC1`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:160
#: ../../content/applications/general/email_communication/email_domain.rst:162
msgid "pct"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:161
#: ../../content/applications/general/email_communication/email_domain.rst:163
msgid "Percentage of messages subjected to filtering"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:162
#: ../../content/applications/general/email_communication/email_domain.rst:164
msgid "`pct=20`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:163
#: ../../content/applications/general/email_communication/email_domain.rst:165
msgid "ruf"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:164
#: ../../content/applications/general/email_communication/email_domain.rst:166
msgid "Reporting URI for forensic reports"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:165
#: ../../content/applications/general/email_communication/email_domain.rst:167
msgid "`ruf=mailto:authfail@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:166
#: ../../content/applications/general/email_communication/email_domain.rst:168
msgid "rua"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:167
#: ../../content/applications/general/email_communication/email_domain.rst:169
msgid "Reporting URI of aggregate reports"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:168
#: ../../content/applications/general/email_communication/email_domain.rst:170
msgid "`rua=mailto:aggrep@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:169
#: ../../content/applications/general/email_communication/email_domain.rst:171
msgid "p"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:170
#: ../../content/applications/general/email_communication/email_domain.rst:172
msgid "Policy for organizational domain"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:172
#: ../../content/applications/general/email_communication/email_domain.rst:174
msgid "sp"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:173
#: ../../content/applications/general/email_communication/email_domain.rst:175
msgid "Policy for subdomains of the OD"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:174
#: ../../content/applications/general/email_communication/email_domain.rst:176
msgid "`sp=reject`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:175
#: ../../content/applications/general/email_communication/email_domain.rst:177
msgid "adkim"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:176
#: ../../content/applications/general/email_communication/email_domain.rst:178
msgid "Alignment mode for DKIM"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:177
#: ../../content/applications/general/email_communication/email_domain.rst:179
msgid "`adkim=s`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:178
#: ../../content/applications/general/email_communication/email_domain.rst:180
msgid "aspf"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:179
#: ../../content/applications/general/email_communication/email_domain.rst:181
msgid "Alignment mode for SPF"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:180
#: ../../content/applications/general/email_communication/email_domain.rst:182
msgid "`aspf=r`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:182
#: ../../content/applications/general/email_communication/email_domain.rst:184
msgid "Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name with a tool like `MXToolbox DMARC <https://mxtoolbox.com/DMARC.aspx>`_."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:186
#: ../../content/applications/general/email_communication/email_domain.rst:188
msgid "`DMARC.org is another great resource to learn about DMARC records. <https://dmarc.org/overview/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:192
#: ../../content/applications/general/email_communication/email_domain.rst:194
msgid "SPF, DKIM & DMARC documentation of common providers"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:194
#: ../../content/applications/general/email_communication/email_domain.rst:196
msgid "`OVH DNS <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:195
#: ../../content/applications/general/email_communication/email_domain.rst:197
msgid "`OVH SPF <https://docs.ovh.com/us/en/domains/web_hosting_the_spf_record/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:196
#: ../../content/applications/general/email_communication/email_domain.rst:198
msgid "`GoDaddy TXT record <https://www.godaddy.com/help/add-a-txt-record-19232>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:197
#: ../../content/applications/general/email_communication/email_domain.rst:199
msgid "`GoDaddy SPF <https://www.godaddy.com/help/add-an-spf-record-19218>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:198
#: ../../content/applications/general/email_communication/email_domain.rst:200
msgid "`GoDaddy DKIM <https://www.godaddy.com/help/add-a-cname-record-19236>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:199
#: ../../content/applications/general/email_communication/email_domain.rst:201
msgid "`NameCheap <https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add- txtspfdkimdmarc-records-for-my-domain/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:201
#: ../../content/applications/general/email_communication/email_domain.rst:203
msgid "`CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:202
#: ../../content/applications/general/email_communication/email_domain.rst:204
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:203
#: ../../content/applications/general/email_communication/email_domain.rst:205
msgid "`Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:205
#: ../../content/applications/general/email_communication/email_domain.rst:207
msgid "To fully test the configuration, use the `Mail-Tester <https://www.mail-tester.com/>`_ tool, which gives a full overview of the content and configuration in one sent email. Mail-Tester can also be used to configure records for other, lesser-known providers."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:210
#: ../../content/applications/general/email_communication/email_domain.rst:212
msgid "`Using Mail-Tester to set SPF Records for specific carriers <https://www.mail-tester.com/spf/>`_"
msgstr ""
@ -5386,7 +5354,7 @@ msgid "Download and initial installation"
msgstr ""
#: ../../content/applications/general/iot/config/windows_iot.rst:41
msgid "To begin the installation, navigate to the Odoo 16 or higher installation package for Enterprise or Community - Windows edition at `Odoo's download page <https://odoo.com/download>`_. Next, install and setup the Odoo :file:`.exe` file. After the instructions screen, click :guilabel:`Next` to start the installation and agree to the :abbr:`TOS (Terms of Service)`."
msgid "To begin the installation, navigate to the Odoo 16 or higher installation package for Community - Windows edition at `Odoo's download page <https://odoo.com/download>`_. Next, install and setup the Odoo :file:`.exe` file. After the instructions screen, click :guilabel:`Next` to start the installation and agree to the :abbr:`TOS (Terms of Service)`."
msgstr ""
#: ../../content/applications/general/iot/config/windows_iot.rst:46
@ -5765,10 +5733,18 @@ msgstr ""
msgid "Confirm the un-installation and follow the steps to uninstall through the Odoo uninstall guide."
msgstr ""
#: ../../content/applications/general/iot/devices.rst:5
#: ../../content/applications/general/iot/devices.rst:7
msgid "Devices"
msgstr ""
#: ../../content/applications/general/iot/devices.rst:21
msgid ":doc:`Worldline payment terminal <../../sales/point_of_sale/payment_methods/terminals/worldline>`"
msgstr ""
#: ../../content/applications/general/iot/devices.rst:23
msgid ":doc:`Ingenico payment terminal <../../sales/point_of_sale/payment_methods/terminals/ingenico>`"
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:3
msgid "Connect a camera"
msgstr ""
@ -6815,7 +6791,7 @@ msgid "The model technical name can also be accessed in :ref:`developer mode <de
msgstr ""
#: ../../content/applications/general/users/access_rights.rst:126
msgid "On a form, navigate to any field, and hover over the field name. A box of backend information reveals itself with the specific Odoo :guilabel:`Object` name in the backend. This is the technical name of the model that should be added."
msgid "On a form, navigate to any field, and hover over the field name. A box of backend information reveals itself with the specific Odoo :guilabel:`Model` name in the backend. This is the technical name of the model that should be added."
msgstr ""
#: ../../content/applications/general/users/access_rights.rst:0

4768
locale/sources/hr.pot
View File

File diff suppressed because it is too large Load Diff

6255
locale/sources/inventory_and_mrp.pot
View File

File diff suppressed because it is too large Load Diff

1351
locale/sources/marketing.pot
View File

File diff suppressed because it is too large Load Diff

206
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-04-30 09:16+0000\n"
"POT-Creation-Date: 2024-05-31 09:59+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1492,67 +1492,83 @@ msgid "Enable the centralization of files attached to your accounting."
msgstr ""
#: ../../content/applications/productivity/documents.rst:36
msgid "If you select a new workspace, existing documents aren't moved. Only newly created documents will be found under the new workspace."
msgstr ""
#: ../../content/applications/productivity/documents.rst:40
msgid "Workspaces"
msgid "If you select a new workspace, existing documents are not moved. Only newly created documents will be found under the new workspace."
msgstr ""
#: ../../content/applications/productivity/documents.rst:42
msgid "Workspaces"
msgstr ""
#: ../../content/applications/productivity/documents.rst:44
msgid "Workspaces are hierarchical folders having their own set of tags and :ref:`actions <documents/workflow-actions>`. Default workspaces exist, but you can create your own by going to :menuselection:`Documents --> Configuration --> Workspaces` and clicking :guilabel:`New`. On the new page, fill in the following information:"
msgstr ""
#: ../../content/applications/productivity/documents.rst:47
#: ../../content/applications/productivity/documents.rst:49
msgid ":guilabel:`Name`"
msgstr ""
#: ../../content/applications/productivity/documents.rst:48
#: ../../content/applications/productivity/documents.rst:50
msgid ":guilabel:`Parent Workspace`: if you want to create a sub-workspace, select its :guilabel:`Parent Workspace`"
msgstr ""
#: ../../content/applications/productivity/documents.rst:52
#: ../../content/applications/productivity/documents.rst:54
#: ../../content/applications/productivity/sign.rst:236
msgid "Tags"
msgstr ""
#: ../../content/applications/productivity/documents.rst:54
#: ../../content/applications/productivity/documents.rst:56
msgid "Tags are used within workspaces to add a level of differentiation between documents. They are organized per category, and filters can be used to sort them."
msgstr ""
#: ../../content/applications/productivity/documents.rst:57
#: ../../content/applications/productivity/documents.rst:59
msgid "Tags can be created from the :guilabel:`Tags` tab. Click :guilabel:`Add a line`, create the :guilabel:`Tag Category`, and :guilabel:`Name` your tags."
msgstr ""
#: ../../content/applications/productivity/documents.rst:61
#: ../../content/applications/productivity/documents.rst:63
msgid "The tags of a parent workspace apply to the child workspaces automatically;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:62
#: ../../content/applications/productivity/documents.rst:64
msgid "Tags can be created and modified by going to :menuselection:`Configuration --> Tags`;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:63
#: ../../content/applications/productivity/documents.rst:65
msgid "Tags can also be created or edited by clicking the gear icon :guilabel:`⚙` on the left menu."
msgstr ""
#: ../../content/applications/productivity/documents.rst:66
#: ../../content/applications/productivity/documents.rst:67
msgid "An **email alias** can be used to automatically send received documents to a specific workspace based on the tag assigned. To create an email alias:"
msgstr ""
#: ../../content/applications/productivity/documents.rst:70
msgid "Select the tag and the corresponding workspace where the document should be directed in the left column of your dashboard."
msgstr ""
#: ../../content/applications/productivity/documents.rst:73
msgid "Next to the :guilabel:`Upload` button, click the down arrow, and then click :guilabel:`Share`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:75
msgid "In the new window, click :guilabel:`Download and Upload` and enter the email alias where documents should be sent."
msgstr ""
#: ../../content/applications/productivity/documents.rst:79
msgid "Access rights"
msgstr ""
#: ../../content/applications/productivity/documents.rst:68
#: ../../content/applications/productivity/documents.rst:81
msgid "To manage your workspace access rights, go to :menuselection:`Documents --> Configuration --> Workspaces`, open the workspace you want to edit, and go to the :guilabel:`Access Rights` tab. You can add :guilabel:`Write Groups` that can view, create, and edit the workspace's documents. You can also add :guilabel:`Read Groups` that can only view the workspace's documents."
msgstr ""
#: ../../content/applications/productivity/documents.rst:74
#: ../../content/applications/productivity/documents.rst:87
msgid "Description"
msgstr ""
#: ../../content/applications/productivity/documents.rst:76
#: ../../content/applications/productivity/documents.rst:89
msgid "You can add descriptive information to your workspace by going to :menuselection:`Documents --> Configuration --> Workspaces`, opening the workspace you want to describe and going to the :guilabel:`Description` tab."
msgstr ""
#: ../../content/applications/productivity/documents.rst:81
#: ../../content/applications/productivity/documents.rst:94
msgid "Workspaces can also be created and edited by clicking the gear icon :guilabel:`⚙` on the left menu."
msgstr ""
@ -1560,43 +1576,43 @@ msgstr ""
msgid "Create sub-workspaces from the left menu"
msgstr ""
#: ../../content/applications/productivity/documents.rst:88
#: ../../content/applications/productivity/documents.rst:101
msgid "Documents management"
msgstr ""
#: ../../content/applications/productivity/documents.rst:90
msgid "When selecting or opening a document, the right panel displays different options. On the top, additional options might be available: :guilabel:`Download`, :guilabel:`Share`, :guilabel:`Replace`, :guilabel:`Lock` or :guilabel:`Split`. It is also possible to :guilabel:`Open chatter` or :guilabel:`Archive` the document."
#: ../../content/applications/productivity/documents.rst:103
msgid "When selecting or opening a document, the right panel displays different options. On the top, additional options might be available: :guilabel:`Download`, :guilabel:`Share`, :guilabel:`Replace`, :guilabel:`Lock` or :guilabel:`Split`. It is also possible to :guilabel:`Open chatter` or use the :guilabel:`Move to trash` option."
msgstr ""
#: ../../content/applications/productivity/documents.rst:-1
msgid "right panel options"
msgstr ""
#: ../../content/applications/productivity/documents.rst:99
msgid "Then, you can modify the name of your file by clicking on :guilabel:`Document`. A :guilabel:`Contact` or an :guilabel:`Owner` can be assigned. The related :guilabel:`Workspace` can be modified and it is possible to access the related :guilabel:`Journal Entry` or add :guilabel:`Tags`."
#: ../../content/applications/productivity/documents.rst:112
msgid "Then, you can modify the name of your file by clicking on :guilabel:`Name`. A :guilabel:`Contact` or an :guilabel:`Owner` can be assigned. The related :guilabel:`Workspace` can be modified and it is possible to access the related :guilabel:`Journal Entry` or add :guilabel:`Tags`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:105
#: ../../content/applications/productivity/documents.rst:117
msgid "The :guilabel:`Contact` is the person related to the document and assigned to it. He can only view the document and not modify it. I.e.: an existing supplier in your database is the contact for their bill."
msgstr ""
#: ../../content/applications/productivity/documents.rst:108
#: ../../content/applications/productivity/documents.rst:120
msgid "The person who creates a document is, by default :guilabel:`Owner` of it and has complete rights to it. It is possible to replace the owner of a document. I.e., an employee must be owner of a document to be able to see it in \"My Profile\"."
msgstr ""
#: ../../content/applications/productivity/documents.rst:112
#: ../../content/applications/productivity/documents.rst:124
msgid "Different :ref:`Actions <documents/workflow-actions>` are available at the bottom of the right panel, depending on the workspace where your document is stored."
msgstr ""
#: ../../content/applications/productivity/documents.rst:116
#: ../../content/applications/productivity/documents.rst:128
msgid "Split PDF documents"
msgstr ""
#: ../../content/applications/productivity/documents.rst:118
#: ../../content/applications/productivity/documents.rst:130
msgid "Select the PDF you want to split, and click the scissors icon. A new view displays all the pages of the document."
msgstr ""
#: ../../content/applications/productivity/documents.rst:121
#: ../../content/applications/productivity/documents.rst:133
msgid "By default, each page of the document will be split when clicking :guilabel:`Split`. To remove a split between two pages, click on the scissors icon."
msgstr ""
@ -1604,43 +1620,43 @@ msgstr ""
msgid "split your documents"
msgstr ""
#: ../../content/applications/productivity/documents.rst:128
#: ../../content/applications/productivity/documents.rst:140
msgid "To merge documents from your dashboard, select them and click the scissors icon. Click on the scissors between the two documents and click :guilabel:`Split` to merge the documents."
msgstr ""
#: ../../content/applications/productivity/documents.rst:132
#: ../../content/applications/productivity/documents.rst:144
msgid "Additional features"
msgstr ""
#: ../../content/applications/productivity/documents.rst:134
#: ../../content/applications/productivity/documents.rst:146
msgid "Select a workspace and click the arrow next to the :guilabel:`Upload` button to access additional features:"
msgstr ""
#: ../../content/applications/productivity/documents.rst:138
#: ../../content/applications/productivity/documents.rst:150
msgid "Request"
msgstr ""
#: ../../content/applications/productivity/documents.rst:140
#: ../../content/applications/productivity/documents.rst:152
msgid "You can create \"missing documents\" and organize them as documents, to remind users to download them."
msgstr ""
#: ../../content/applications/productivity/documents.rst:142
#: ../../content/applications/productivity/documents.rst:154
msgid "Select the workspace where the file should be stored, click :guilabel:`Upload`, then :guilabel:`Request`. Add the :guilabel:`Document Name`, select the person you need it from in the :guilabel:`Request To` field, fill in the :guilabel:`Due Date In`, confirm the :guilabel:`Workspace`, the document should belong to, and add :guilabel:`Tags` and a :guilabel:`Note`, if needed. Then, click :guilabel:`Request`. A placeholder for the missing document is created in the workspace."
msgstr ""
#: ../../content/applications/productivity/documents.rst:149
#: ../../content/applications/productivity/documents.rst:161
msgid "When your document is available, click the placeholder to upload it."
msgstr ""
#: ../../content/applications/productivity/documents.rst:151
#: ../../content/applications/productivity/documents.rst:163
msgid "You can see all missing documents by going to the **Activity** view and to the :guilabel:`Requested Document` column."
msgstr ""
#: ../../content/applications/productivity/documents.rst:155
#: ../../content/applications/productivity/documents.rst:167
msgid "From the :guilabel:`Activity` view, you can send a **reminder email** to users from whom you are expecting a document. Go to the :guilabel:`Requested Document` column, click on ⋮ and :guilabel:`Document Request: Reminder`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:159
#: ../../content/applications/productivity/documents.rst:171
msgid "Click on a date to see the details of a specific request. You can update it by clicking on the pen icon, :guilabel:`Preview` the content of the reminder email, or :guilabel:`Send Now` to send a reminder email."
msgstr ""
@ -1648,83 +1664,83 @@ msgstr ""
msgid "send a reminder email from the Activity view"
msgstr ""
#: ../../content/applications/productivity/documents.rst:167
#: ../../content/applications/productivity/documents.rst:179
msgid "Add a link"
msgstr ""
#: ../../content/applications/productivity/documents.rst:169
#: ../../content/applications/productivity/documents.rst:181
msgid "To add a link to your documents dashboard, click on :guilabel:`Add a Link`, enter the :guilabel:`URL`, and :guilabel:`Name` it."
msgstr ""
#: ../../content/applications/productivity/documents.rst:173
#: ../../content/applications/productivity/documents.rst:185
msgid "Share"
msgstr ""
#: ../../content/applications/productivity/documents.rst:175
#: ../../content/applications/productivity/documents.rst:187
msgid "You can create a share link to a document or all documents of a workspace. It allows anyone to download the file(s) or upload files to a workspace."
msgstr ""
#: ../../content/applications/productivity/documents.rst:178
#: ../../content/applications/productivity/documents.rst:190
msgid "To do so, select the workspace or the document and click the arrow next to the :guilabel:`Upload` button then :guilabel:`Share`. On the pop-up, the share :guilabel:`URL` is displayed. :guilabel:`Copy` it to share it with anyone. :guilabel:`Name` the share link and set a validity date for the URL by filling in the :guilabel:`Valid Until` field. Tick the :guilabel:`Include Sub Folders` box if you also want to share a workspace's sub-folders. To let users upload their own documents, select :guilabel:`Download and Upload`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:186
#: ../../content/applications/productivity/documents.rst:198
msgid "It is possible to only share one or more documents (without their workspace) by selecting them and clicking :guilabel:`Share`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:190
#: ../../content/applications/productivity/documents.rst:202
msgid "New spreadsheet"
msgstr ""
#: ../../content/applications/productivity/documents.rst:192
#: ../../content/applications/productivity/documents.rst:204
msgid "To create a new :doc:`spreadsheet <spreadsheet>`, click :guilabel:`New Spreadsheet`. You can select a :guilabel:`Blank spreadsheet` or an :doc:`existing template <spreadsheet/templates>`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:198
#: ../../content/applications/productivity/documents.rst:210
msgid "Workflow actions"
msgstr ""
#: ../../content/applications/productivity/documents.rst:200
#: ../../content/applications/productivity/documents.rst:212
msgid "Workflow actions help manage documents and overall business operations. These are automated actions that can be created and customized for each workspace. With a single click you can, for example, create, move, sign, and add tags to a document, and process bills."
msgstr ""
#: ../../content/applications/productivity/documents.rst:204
#: ../../content/applications/productivity/documents.rst:216
msgid "These workflow actions appear on the right panel when a document meets the set criteria."
msgstr ""
#: ../../content/applications/productivity/documents.rst:207
#: ../../content/applications/productivity/documents.rst:219
msgid "Create workflow actions"
msgstr ""
#: ../../content/applications/productivity/documents.rst:209
#: ../../content/applications/productivity/documents.rst:221
msgid "To create workflow actions, go to :menuselection:`Documents --> Configuration --> Actions` and click :guilabel:`New`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:213
#: ../../content/applications/productivity/documents.rst:225
msgid "An action applies to all **sub-workspaces** under the :guilabel:`Related Workspace` you selected."
msgstr ""
#: ../../content/applications/productivity/documents.rst:216
#: ../../content/applications/productivity/documents.rst:228
msgid "Set the conditions"
msgstr ""
#: ../../content/applications/productivity/documents.rst:218
#: ../../content/applications/productivity/documents.rst:230
msgid "You can :guilabel:`Create` a new :guilabel:`Action` or edit an existing one. You can define the :guilabel:`Action Name` and then set the conditions that trigger the appearance of the action button (:guilabel:`▶`) on the right-side panel when selecting a file."
msgstr ""
#: ../../content/applications/productivity/documents.rst:222
#: ../../content/applications/productivity/documents.rst:234
msgid "There are three basic types of conditions you can set:"
msgstr ""
#: ../../content/applications/productivity/documents.rst:224
msgid ":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does not contain` conditions, meaning the files *must have* or *mustn't have* the tags set here."
#: ../../content/applications/productivity/documents.rst:236
msgid ":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does not contain` conditions, meaning the files *must have* or *must not have* the tags set here."
msgstr ""
#: ../../content/applications/productivity/documents.rst:227
#: ../../content/applications/productivity/documents.rst:239
msgid ":guilabel:`Contact`: the files must be associated with the contact set here."
msgstr ""
#: ../../content/applications/productivity/documents.rst:229
#: ../../content/applications/productivity/documents.rst:241
msgid ":guilabel:`Owner`: the files must be associated with the owner set here."
msgstr ""
@ -1732,23 +1748,23 @@ msgstr ""
msgid "Example of a workflow action's basic condition in Odoo Documents"
msgstr ""
#: ../../content/applications/productivity/documents.rst:235
msgid "If you don't set any conditions, the action button appears for all files inside the selected workspace."
#: ../../content/applications/productivity/documents.rst:247
msgid "If you do not set any conditions, the action button appears for all files inside the selected workspace."
msgstr ""
#: ../../content/applications/productivity/documents.rst:239
#: ../../content/applications/productivity/documents.rst:251
msgid "Advanced condition type: domain"
msgstr ""
#: ../../content/applications/productivity/documents.rst:242
#: ../../content/applications/productivity/documents.rst:254
msgid "It is recommended to have some knowledge of Odoo development to configure *Domain* filters properly."
msgstr ""
#: ../../content/applications/productivity/documents.rst:245
#: ../../content/applications/productivity/documents.rst:257
msgid "The :ref:`developer mode <developer-mode>` needs to be activated to access the :guilabel:`Domain` condition from the :guilabel:`Actions` tab. Once done, select the :guilabel:`Domain` condition type and click :guilabel:`Add condition`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:249
#: ../../content/applications/productivity/documents.rst:261
msgid "To create a rule, you typically select a :guilabel:`field`, an :guilabel:`operator`, and a :guilabel:`value`. For example, if you want to add a workflow action to all the PDF files inside a workspace, set the :guilabel:`field` to *Mime Type*, the :guilabel:`operator` to *contains*, and the pdf :guilabel:`value`."
msgstr ""
@ -1756,95 +1772,95 @@ msgstr ""
msgid "Example of a workflow action's domain condition in Odoo Documents"
msgstr ""
#: ../../content/applications/productivity/documents.rst:257
#: ../../content/applications/productivity/documents.rst:269
msgid "Click :guilabel:`Add New Rule` (plus icon) and :guilabel:`Add branch` to add conditions and sub-conditions. You can then specify if your rule should match :guilabel:`all` or :guilabel:`any` conditions. You can also edit the rule directly using the :guilabel:`Code editor`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:262
#: ../../content/applications/productivity/documents.rst:274
msgid "Configure the actions"
msgstr ""
#: ../../content/applications/productivity/documents.rst:264
#: ../../content/applications/productivity/documents.rst:276
msgid "Select the :guilabel:`Actions` tab to set up your action. You can simultaneously:"
msgstr ""
#: ../../content/applications/productivity/documents.rst:266
#: ../../content/applications/productivity/documents.rst:278
msgid "**Set Contact**: add a contact to the file, or replace an existing contact with a new one."
msgstr ""
#: ../../content/applications/productivity/documents.rst:267
#: ../../content/applications/productivity/documents.rst:279
msgid "**Set Owner**: add an owner to the file, or replace an existing owner with a new one."
msgstr ""
#: ../../content/applications/productivity/documents.rst:268
#: ../../content/applications/productivity/documents.rst:280
msgid "**Move to Workspace**: move the file to any workspace."
msgstr ""
#: ../../content/applications/productivity/documents.rst:269
#: ../../content/applications/productivity/documents.rst:281
msgid "**Create**: create one of the following items attached to the file in your database:"
msgstr ""
#: ../../content/applications/productivity/documents.rst:271
#: ../../content/applications/productivity/documents.rst:283
msgid "**Link to record**: link the document to a record (i.e. link to a vehicle in Fleet);"
msgstr ""
#: ../../content/applications/productivity/documents.rst:272
#: ../../content/applications/productivity/documents.rst:284
msgid "**Product template**: create a product you can edit directly;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:273
#: ../../content/applications/productivity/documents.rst:285
msgid "**Task**: create a Project task you can edit directly;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:274
#: ../../content/applications/productivity/documents.rst:286
msgid "**Signature PDF template**: create a new Sign template to send out;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:275
#: ../../content/applications/productivity/documents.rst:287
msgid "**PDF to sign**: create a PDF to sign;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:276
#: ../../content/applications/productivity/documents.rst:288
msgid "**Applicant**: create a new HR application you can edit directly;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:277
#: ../../content/applications/productivity/documents.rst:289
msgid "**Vendor bill**: create a vendor bill using OCR and AI to scrape information from the file content;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:279
#: ../../content/applications/productivity/documents.rst:291
msgid "**Customer invoice**: create a customer invoice using OCR and AI to scrape information from the file;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:281
#: ../../content/applications/productivity/documents.rst:293
msgid "**Vendor credit note**: create a vendor credit note using OCR and AI to scrape information from the file;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:283
#: ../../content/applications/productivity/documents.rst:295
msgid "**Credit note**: create a customer credit note using OCR and AI to scrape information from the file;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:285
#: ../../content/applications/productivity/documents.rst:297
msgid "**Miscellaneous Operations**: create a record in :guilabel:`Miscellaneous Operations` in Accounting;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:287
#: ../../content/applications/productivity/documents.rst:299
msgid "**Bank Statement**: create a Bank Statement in Finance;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:288
#: ../../content/applications/productivity/documents.rst:300
msgid "**Expense**: create an expense automatically based on a file's content."
msgstr ""
#: ../../content/applications/productivity/documents.rst:290
msgid "**Set Tags**: add, remove, and replace any number of tags."
#: ../../content/applications/productivity/documents.rst:302
msgid "**Set Tags**: add, remove, and replace any number of tags;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:291
msgid "**Activities - Mark all as Done**: mark all activities linked to the file as done."
#: ../../content/applications/productivity/documents.rst:303
msgid "**Activities - Mark all as Done**: mark all activities linked to the file as done;"
msgstr ""
#: ../../content/applications/productivity/documents.rst:292
#: ../../content/applications/productivity/documents.rst:304
msgid "**Activities - Schedule Activity**: create a new activity linked to the file as configured in the action. You can choose to set the activity on the document owner."
msgstr ""
@ -1852,15 +1868,15 @@ msgstr ""
msgid "Example of a workflow action Odoo Documents"
msgstr ""
#: ../../content/applications/productivity/documents.rst:299
#: ../../content/applications/productivity/documents.rst:311
msgid "Digitize documents with AI and optical character recognition (OCR)"
msgstr ""
#: ../../content/applications/productivity/documents.rst:301
#: ../../content/applications/productivity/documents.rst:313
msgid "Documents available in the Finance workspace can be digitized. Select the document to digitize, click :guilabel:`Create Bill`, :guilabel:`Create Customer Invoice`, or :guilabel:`Create credit note`, and then click :guilabel:`Send for Digitization`."
msgstr ""
#: ../../content/applications/productivity/documents.rst:306
#: ../../content/applications/productivity/documents.rst:318
msgid ":doc:`AI-powered document digitization <../finance/accounting/vendor_bills/invoice_digitization>`"
msgstr ""

1147
locale/sources/sales.pot
View File

File diff suppressed because it is too large Load Diff

925
locale/sources/services.pot
View File

File diff suppressed because it is too large Load Diff

412
locale/sources/studio.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-03-25 16:01+0000\n"
"POT-Creation-Date: 2024-05-31 09:59+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -61,19 +61,31 @@ msgid "`Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:3
msgid "Automated actions (automations)"
msgid "Automation rules"
msgstr ""
#: ../../content/applications/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)."
msgid "Automation rules are used to trigger automatic changes based on user actions (e.g., apply a modification when a field is set to a specific value), email events, time conditions (e.g., archive a record 7 days after its last update), or external events."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:9
msgid "To create an automated action with Studio, go to :guilabel:`Automations` from anywhere within Studio."
msgid "To create an automation rule with Studio, proceed as follows:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:11
msgid "Open Studio and click :guilabel:`Automations`, then :guilabel:`New`."
msgstr ""
#: ../../content/applications/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`."
msgid "Select the :ref:`studio/automated-actions/trigger` and, if necessary, fill in the fields that appear on the screen based on the chosen trigger."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:14
msgid "Click :guilabel:`Add an action`, then select the :guilabel:`Type` of :ref:`action <studio/automated-actions/action>` and fill in the fields that appear on the screen based on your selected action."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:17
msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
@ -81,243 +93,395 @@ msgid "Example of an automated action on the Subscription model"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:25
msgid "Model"
msgid "To modify the :doc:`model <models_modules_apps>` of the automation rule, switch models before clicking :guilabel:`Automations` in Studio, or :ref:`activate the developer mode <developer-mode>`, create or edit an automation rule, and select the :guilabel:`Model` in the :guilabel:`Automation Rules` form."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:27
msgid "Select the model where the automated action should be applied."
#: ../../content/applications/studio/automated_actions.rst:29
msgid "You can also create automation rules from any kanban stage by clicking the gear icon (:guilabel:`⚙` ) next to the kanban stage name, then selecting :guilabel:`Automations`. In this case, the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, but you can change it if necessary."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:30
msgid "The model you are on when you click on :guilabel:`Automations` is pre-selected by default."
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Create automations from a kanban stage"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:35
#: ../../content/applications/studio/automated_actions.rst:40
msgid "Trigger"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:37
msgid "Define when the automated action should be applied. Six triggers are available."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:42
msgid "On Creation"
msgid "The :guilabel:`Trigger` is used to define when the automation rule should be applied. The available triggers depend on the :doc:`model <models_modules_apps>`. Five trigger categories are available overall:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:44
msgid "The action is triggered when a record is created and then saved."
#: ../../content/applications/studio/automated_actions.rst:46
msgid ":ref:`studio/automated-actions/trigger/values-updated`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:47
msgid ":ref:`studio/automated-actions/trigger/email-events`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:48
msgid ":ref:`studio/automated-actions/trigger/values-timing-conditions`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:49
msgid "On Update"
msgid ":ref:`studio/automated-actions/trigger/custom`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:51
msgid "The action is triggered when a previously saved record is edited and then saved."
#: ../../content/applications/studio/automated_actions.rst:50
msgid ":ref:`studio/automated-actions/trigger/external`"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:53
msgid "Use :guilabel:`Trigger Fields` to specify which fields - and only those - trigger the action on their update."
msgid "You can also define a :guilabel:`Before Update Domain` to specify the conditions that must be met *before* the automation rule is triggered. In contrast, the conditions defined using the :ref:`Extra Conditions <studio/automated-actions/trigger/values-timing-conditions>` and :ref:`Apply on <studio/automated-actions/trigger/custom>` filters are checked *during* the execution of the automation rule."
msgstr ""
#: ../../content/applications/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."
#: ../../content/applications/studio/automated_actions.rst:59
msgid "To define a :guilabel:`Before Update Domain`, :ref:`activate the developer mode <developer-mode>`, create or edit an automation rule, click :guilabel:`Edit Domain`, then click :guilabel:`New Rule`."
msgstr ""
#: ../../content/applications/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`."
#: ../../content/applications/studio/automated_actions.rst:63
msgid "For example, if you want the automated action to happen when an email address is set on a contact that did not have an address before (in contrast to modifying their existing address), define the :guilabel:`Before Update Domain` to :guilabel:`Email is not set`, and the :guilabel:`Apply on` domain to :guilabel:`Email is set`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of an On Update trigger"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:72
msgid "On Creation & Update"
msgid "Example of a trigger with a Before Update Domain"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:74
msgid "The action is triggered when a record is created and saved or edited afterward and saved."
msgid "Values Updated"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:79
msgid "On Deletion"
#: ../../content/applications/studio/automated_actions.rst:76
msgid "The triggers available in this category depend on the model and are based on common field changes, such as adding a specific tag (e.g., to a task) or setting the :guilabel:`User` field. Select the trigger, then select a value if required."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:81
msgid "The action is triggered when a record is deleted."
#: ../../content/applications/studio/automated_actions.rst:-1
msgid "Example of a Values Updated trigger"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:84
msgid "This trigger is rarely used, as archiving records is usually preferred to deletion."
#: ../../content/applications/studio/automated_actions.rst:86
msgid "Email Events"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:89
msgid "Based on Form Modification"
#: ../../content/applications/studio/automated_actions.rst:88
msgid "Trigger automated actions upon receiving or sending emails."
msgstr ""
#: ../../content/applications/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 <studio/views/general/form>`, 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."
#: ../../content/applications/studio/automated_actions.rst:93
msgid "Timing Conditions"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:95
msgid "Trigger automated actions based on a date field. The following triggers are available:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:97
msgid "This trigger can only be used with the :ref:`Execute Python Code action <studio/automated-actions/action/python-code>`, so development is required."
msgid ":guilabel:`Based on date field`: Select the field to be used next to the :guilabel:`Delay` field."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:103
msgid "Based on Timed Condition"
#: ../../content/applications/studio/automated_actions.rst:98
msgid ":guilabel:`After creation`: The action is triggered when a record is created and saved."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:105
msgid "The action is triggered when a trigger field's date or date & time value is reached."
#: ../../content/applications/studio/automated_actions.rst:99
msgid ":guilabel:`After last update`: The action is triggered when an existing record is edited and saved."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:102
msgid "You can then define:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:104
msgid "a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. To trigger the action before the trigger date, specify a negative number. If you selected the :guilabel:`Based on date field` trigger, you must also select the date field to be used to determine the delay."
msgstr ""
#: ../../content/applications/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."
msgid ":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify the conditions to be met to trigger the automation rule. Click :guilabel:`New Rule` to add another condition."
msgstr ""
#: ../../content/applications/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`."
#: ../../content/applications/studio/automated_actions.rst:110
msgid "The action is triggered when the delay is reached and the conditions are met."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:113
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` to **-30** :guilabel:`Minutes`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Based on Timed Condition trigger"
msgid "Example of a Based on date field trigger"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:121
msgid "By default, the scheduler checks for trigger dates every 4 hours."
msgid "By default, the scheduler checks for trigger dates every 4 hours, meaning lower granularity in time-based automations may not always be honored."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:126
msgid "Apply on"
#: ../../content/applications/studio/automated_actions.rst:127
msgid "Custom"
msgstr ""
#: ../../content/applications/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."
#: ../../content/applications/studio/automated_actions.rst:129
msgid "Trigger automated actions:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:134
msgid "Action"
#: ../../content/applications/studio/automated_actions.rst:131
msgid ":guilabel:`On save`: When the record is saved;"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:132
msgid ":guilabel:`On deletion`: When a record is deleted;"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:133
msgid ":guilabel:`On UI change`: When a field's value is changed on the :ref:`Form view <studio/views/general/form>`, even before saving the record."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:136
msgid "Determine what the automated action should do (server action). There are eight types of action to choose from."
msgid "For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you **must** then select the field(s) to be used to trigger the automation rule in the :guilabel:`When updating` field."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:142
msgid "Execute Python Code"
#: ../../content/applications/studio/automated_actions.rst:140
msgid "If no field is selected in the :guilabel:`When updating` field, the automated action may be executed multiple times per record."
msgstr ""
#: ../../content/applications/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."
#: ../../content/applications/studio/automated_actions.rst:143
msgid "Optionally, you can also define additional conditions to be met to trigger the automation rule in the :guilabel:`Apply on` field."
msgstr ""
#: ../../content/applications/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/studio/automated_actions.rst:153
msgid "Create a new Record"
msgid "The :guilabel:`On UI change` trigger can only be used with the :ref:`studio/automated-actions/action/python-code` action and only works when a modification is made manually. The action is not executed if the field is changed through another automation rule."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:155
msgid "The action is used to create a new record on any model."
msgid "External"
msgstr ""
#: ../../content/applications/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."
#: ../../content/applications/studio/automated_actions.rst:157
msgid "Trigger automated actions based on an external event using a webhook. A webhook is a method of communication between two systems where the source system sends an HTTP(S) request to a destination system based on a specific event. It usually includes a data payload containing information about the event that occurred."
msgstr ""
#: ../../content/applications/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/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`:"
#: ../../content/applications/studio/automated_actions.rst:162
msgid "To configure the :guilabel:`On webhook` trigger, copy the :guilabel:`URL` generated by Odoo into the destination system (i.e., the system receiving the request). Then, in the :guilabel:`Target Record` field, enter the code to run to define the record(s) to be updated using the automation rule."
msgstr ""
#: ../../content/applications/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/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."
msgid "The URL must be treated as **confidential**; sharing it online or without caution could potentially expose your system to malicious parties. Click the :guilabel:`Rotate Secret` button to change the URL's secret if necessary."
msgstr ""
#: ../../content/applications/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."
msgid "The code defined by default in the :guilabel:`Target Record` field works for webhooks coming from another Odoo database. It is used to determine the record(s) to be updated using the information in the payload."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Create a new Record action"
#: ../../content/applications/studio/automated_actions.rst:175
msgid "If you wish to use the webhook's content for a purpose other than to find the record(s) (e.g., *create* a record), your only option is to use an :ref:`studio/automated-actions/action/python-code` action. In this case, the :guilabel:`Target record` field must contain any valid code, but its result doesn't have any effect on the automated action itself."
msgstr ""
#: ../../content/applications/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."
#: ../../content/applications/studio/automated_actions.rst:179
msgid "The webhook content is available in the server action context as a `payload` variable (i.e., a dictionary that contains the GET parameters or POST JSON body of the incoming request)."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:187
msgid "Update the Record"
#: ../../content/applications/studio/automated_actions.rst:182
msgid "You can also choose to :guilabel:`Log Calls` to record the payloads received, e.g., to make sure the data sent by the source system matches the expected format and content. This also helps identify and diagnose any issues that may arise. To access the logs, click the :guilabel:`Logs` smart button at the top of the :guilabel:`Automation rules` form."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:189
msgid "The action is used to set value(s) for field(s) of any record on the current model."
#: ../../content/applications/studio/automated_actions.rst:190
msgid "Actions"
msgstr ""
#: ../../content/applications/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`."
msgid "Once you have defined the automation rule's :ref:`trigger <studio/automated-actions/trigger>`, click :guilabel:`Add an action` to define the action to be executed."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:198
msgid "Execute several actions"
#: ../../content/applications/studio/automated_actions.rst:196
msgid "You can define multiple actions for the same trigger/automation rule. The actions are executed in the order they are defined. This means, for example, that if you define an :guilabel:`Update record` action and then a :guilabel:`Send email` action, the email uses the updated values. However, if the :guilabel:`Send email` action is defined before the :guilabel:`Update record` action, the email uses the values set *before* the update action is run."
msgstr ""
#: ../../content/applications/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."
#: ../../content/applications/studio/automated_actions.rst:206
msgid "Update Record"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:207
msgid "Send Email"
#: ../../content/applications/studio/automated_actions.rst:208
msgid "This action allows to update one of the record's (related) fields. Click the :guilabel:`Update` field and, in the list that opens, select or search for the field to be updated; click the right arrow next to the field name to access the list of related fields if needed."
msgstr ""
#: ../../content/applications/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/studio/automated_actions.rst:215
msgid "Add Followers"
#: ../../content/applications/studio/automated_actions.rst:212
msgid "If you selected a :ref:`many2many field <studio/fields/relational-fields/many2many>`, choose whether the field must be updated by :guilabel:`Adding`, :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by :guilabel:`Clearing it`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:217
msgid "The action is used to subscribe existing contacts to the record."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:222
msgid "Create Next Activity"
msgstr ""
#: ../../content/applications/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/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`."
msgid "If you want the automated action to remove a tag from the customer record, set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select :guilabel:`By Removing`, then select the tag."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Create Next Activity action"
msgid "Example of an Update Record action"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:243
msgid "Send SMS Text Message"
#: ../../content/applications/studio/automated_actions.rst:225
msgid "Alternatively, you can also set a record's field dynamically using Python code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, then enter the code to be used for computing the field's value. For example, if you want the automation rule to compute a custom :ref:`datetime field <studio/fields/simple-fields/date-time>` when a task's priority is set to `High` (by starring the task), you can define the trigger :guilabel:`Priority is set to` to `High` and define the :guilabel:`Update Record` action as follows:"
msgstr ""
#: ../../content/applications/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`."
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Compute a custom datetime field using a Python expression"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:249
msgid "If you want sent messages to be logged in the Chatter, tick :guilabel:`Log as Note`."
#: ../../content/applications/studio/automated_actions.rst:236
msgid "Create Activity"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:238
msgid "This action is used to schedule a new activity linked to the record. Select an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, then specify when you want the activity to be scheduled in the :guilabel:`Due Date In` field, and select a :guilabel:`User type`:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:242
msgid "To always assign the activity to the same user, select :guilabel:`Specific User` and add the user in the :guilabel:`Responsible` field;"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:244
msgid "To target a user linked to the record dynamically, select :guilabel:`Dynamic User (based on record)` and change the :guilabel:`User Field` if necessary."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:248
msgid "After a lead is turned into an opportunity, you want the automated action to set up a call for the user responsible for the lead. To do so, set the :guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` to :guilabel:`Dynamic User (based on record)`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Create Activity action"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:256
msgid "Send Email and Send SMS"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:258
msgid "These actions are used to send an email or a text message to a contact linked to a specific record. To do so, select or create an :guilabel:`Email Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email As` or :guilabel:`Send SMS As` field, choose how you want to send the email or text message:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:263
msgid ":guilabel:`Email`: to send the message as an email to the recipients of the :guilabel:`Email Template`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:265
msgid ":guilabel:`Message`: to post the message on the record and notify the record's followers."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:266
msgid ":guilabel:`Note`: to send the message as an internal note visible to internal users in the chatter."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:268
msgid ":guilabel:`SMS (without note)`: to send the message as a text message to the recipients of the :guilabel:`SMS template`."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:270
msgid ":guilabel:`SMS (with note)`: to send the message as a text message to the recipients of the :guilabel:`SMS template` and post it as an internal note in the chatter."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:272
msgid ":guilabel:`Note only`: to only post the message as an internal note in the chatter."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:277
msgid "Add Followers and Remove Followers"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:279
msgid "Use these actions to (un)subscribe existing contacts to/from the record."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:282
msgid "Create Record"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:284
msgid "This action is used to create a new record on any model."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:286
msgid "Select the required model in the :guilabel:`Record to Create` field; it contains the current model by default. Specify a :guilabel:`Name` for the record, and then, if you want to create the record on another model, select a field in the :guilabel:`Link Field` field to link the record that triggered the creation of the new record."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:292
msgid "The dropdown list related to the :guilabel:`Link Field` field only contains :ref:`one2many fields <studio/fields/relational-fields/one2many>` existing on the current model that are linked to a :ref:`many2one field <studio/fields/relational-fields/many2one>` on the target model."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:297
msgid "You can create another automation rule with :ref:`studio/automated-actions/action/update-record` actions to update the fields of the new record if necessary. For example, you can use a :guilabel:`Create Record` action to create a new project task and then assign it to a specific user using an :guilabel:`Update Record` action."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:305
msgid "Execute Code"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:307
msgid "This action is used to execute Python code. You can write your code into the :guilabel:`Code` tab using the following variables:"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:310
msgid "`env`: environment on which the action is triggered"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:311
msgid "`model`: model of the record on which the action is triggered; is a void recordset"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:312
msgid "`record`: record on which the action is triggered; may be void"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:313
msgid "`records`: recordset of all records on which the action is triggered in multi-mode; this may be left empty"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:315
msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:316
msgid "`float_compare`: utility function to compare floats based on specific precision"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:317
msgid "`log(message, level='info')`: logging function to record debug information in ir.logging table"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:319
msgid "`_logger.info(message)`: logger to emit messages in server logs"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:320
msgid "`UserError`: exception class for raising user-facing warning messages"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:321
msgid "`Command`: x2many commands namespace"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:322
msgid "`action = {...}`: to return an action"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:325
msgid "The available variables are described both in the :guilabel:`Code` and :guilabel:`Help` tabs."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:328
msgid "Send Webhook Notification"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:330
msgid "This action allows to send a POST request with the values of the :guilabel:`Fields` to the URL specified in the :guilabel:`URL` field."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:333
msgid "The :guilabel:`Sample Payload` provides a preview of the data included in the request using a random record's data or dummy data if no record is available."
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:339
msgid "Execute Existing Actions"
msgstr ""
#: ../../content/applications/studio/automated_actions.rst:341
msgid "The action is used to trigger multiple actions (linked to the current model) at the same time. To do so, click on :guilabel:`Add a line`, then, in the :guilabel:`Add: Child Actions` pop-up, select an existing action or click :guilabel:`New` to create a new one."
msgstr ""
#: ../../content/applications/studio/fields.rst:3

414
locale/sources/websites.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-04-30 09:16+0000\n"
"POT-Creation-Date: 2024-05-31 09:59+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -686,7 +686,7 @@ msgid "eCommerce management"
msgstr ""
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:3
#: ../../content/applications/websites/website/configuration/multi_website.rst:130
#: ../../content/applications/websites/website/configuration/multi_website.rst:124
msgid "Customer accounts"
msgstr ""
@ -1039,7 +1039,7 @@ msgid "Other options include **multiple views (Pivot, etc.), comparison** by per
msgstr ""
#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:31
#: ../../content/applications/websites/website/configuration/multi_website.rst:153
#: ../../content/applications/websites/website/configuration/multi_website.rst:147
msgid "Analytics"
msgstr ""
@ -1729,7 +1729,7 @@ msgid ":guilabel:`Website`: the website on which that file is *available*. If yo
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/products.rst:168
msgid "The file is then available after checkout in the **purchase order** section found on the customer's portal."
msgid "The file is then available after checkout in the :guilabel:`Sales Orders` section, found on the customer's portal."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/products.rst:172
@ -4289,7 +4289,7 @@ msgid ":doc:`/applications/sales/crm/acquire_leads`"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:156
msgid ":doc:`/applications/services/helpdesk/overview/getting_started`"
msgid ":doc:`../../services/helpdesk`"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:161
@ -5039,7 +5039,7 @@ msgid "Odoo allows you to create multiple websites from the same database. This
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:11
msgid "Each website can be designed and configured independently with its own :doc:`domain name <domain_names>`, theme, pages, menus, :doc:`languages <translate>`, :doc:`products <../../ecommerce/managing_products/products>`, assigned sales team, etc. They can also :ref:`share content and pages <multi-website/website_content>`."
msgid "Each website can be designed and configured independently with its own :doc:`domain name <domain_names>`, :doc:`theme <../web_design/themes>`, :doc:`pages <../pages>`, :doc:`menus <../pages/menus>`, :doc:`languages <translate>`, :doc:`products <../../ecommerce/managing_products/products>`, assigned sales team, etc. They can also :ref:`share content and pages <multi-website/website_content>`."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:18
@ -5055,7 +5055,7 @@ msgid "To create a new website, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:26
#: ../../content/applications/websites/website/configuration/multi_website.rst:142
#: ../../content/applications/websites/website/configuration/multi_website.rst:136
msgid "Go to :menuselection:`Website --> Configuration --> Settings`."
msgstr ""
@ -5100,34 +5100,30 @@ msgid "Website selector"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:55
msgid "When you switch websites, you are redirected to the other website, to the same page (URL) as the current one. If the page you are currently viewing does not exist on the other website, you are redirected to a 404 error page. Once redirected, click :guilabel:`Create page` to create the page."
msgid "When you switch websites, you are redirected to the homepage of the other website."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:0
msgid "Create a page from a 404 error page"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:64
#: ../../content/applications/websites/website/configuration/multi_website.rst:58
msgid "Website-specific configuration"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:66
#: ../../content/applications/websites/website/configuration/multi_website.rst:60
msgid "Most website settings are website-specific, which means they can be enabled/disabled per website. To adapt the settings for a website, go to :menuselection:`Website --> Configuration --> Settings`. Select the desired website in the field :guilabel:`Settings of Website` at the top of the :guilabel:`Settings` page, in the **yellow** banner. Then, adapt the options for that specific website."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:73
#: ../../content/applications/websites/website/configuration/multi_website.rst:67
msgid "Websites are created with the default settings; the settings are not copied from one website to the other."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:75
#: ../../content/applications/websites/website/configuration/multi_website.rst:69
msgid "In a :doc:`multi-company environment </applications/general/companies>`, each website can be linked to a specific company in your database so that only company-related data (e.g., products, jobs, events, etc.) is displayed on the website. To display company-specific data, set the desired company in the :guilabel:`Company` field."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:83
#: ../../content/applications/websites/website/configuration/multi_website.rst:77
msgid "Content availability"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:85
#: ../../content/applications/websites/website/configuration/multi_website.rst:79
msgid "By default, pages, products, events, etc. created from the frontend (using the :guilabel:`+New` button) are only available on the website from which it was created. Records created from the backend, however, are made available on all websites by default. The content's availability can be changed in the backend, in the :guilabel:`Website` field. For example, for products, go to :menuselection:`eCommerce --> Products`, then select the product and go to the :guilabel:`Sales` tab. For forums, go to :menuselection:`Configuration --> Forums`, then select the forum."
msgstr ""
@ -5135,35 +5131,35 @@ msgstr ""
msgid "Website field in Forum form"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:98
#: ../../content/applications/websites/website/configuration/multi_website.rst:92
msgid "Records and features can be made available:"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:100
#: ../../content/applications/websites/website/configuration/multi_website.rst:94
msgid "On all websites: leave the :guilabel:`Website` field empty;"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:101
#: ../../content/applications/websites/website/configuration/multi_website.rst:95
msgid "Only on one website: set the :guilabel:`Website` field accordingly;"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:102
#: ../../content/applications/websites/website/configuration/multi_website.rst:96
msgid "On some websites: in this case, you should duplicate the item and set the :guilabel:`Website` field."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:106
#: ../../content/applications/websites/website/configuration/multi_website.rst:100
msgid "Website pages"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:108
#: ../../content/applications/websites/website/configuration/multi_website.rst:102
msgid "To modify the website on which a page is to be published, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:110
#: ../../content/applications/websites/website/configuration/multi_website.rst:104
msgid "Go to :menuselection:`Website --> Site --> Pages`."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:111
#: ../../content/applications/websites/website/configuration/multi_website.rst:105
msgid "Open the search panel and select the website on which the page is currently published."
msgstr ""
@ -5171,56 +5167,56 @@ msgstr ""
msgid "Display pages per website"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:116
#: ../../content/applications/websites/website/configuration/multi_website.rst:110
msgid "Tick the check box next to the page(s) you want to change."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:117
#: ../../content/applications/websites/website/configuration/multi_website.rst:111
msgid "Click the :guilabel:`Website` field and select the website, or empty it to publish the page on all websites."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:121
#: ../../content/applications/websites/website/configuration/multi_website.rst:115
msgid "Each website must have its own homepage; you may not use the same homepage for several websites."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:124
#: ../../content/applications/websites/website/configuration/multi_website.rst:118
msgid "eCommerce features"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:126
#: ../../content/applications/websites/website/configuration/multi_website.rst:120
msgid "eCommerce features such as products, eCommerce categories, pricelists, discounts, payment providers, etc. can be restricted to :ref:`a specific website <website_field>`."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:132
#: ../../content/applications/websites/website/configuration/multi_website.rst:126
msgid "You can :doc:`allow your customers to use the same account <../../ecommerce/ecommerce_management/customer_accounts>` on all of your websites by enabling the :guilabel:`Shared Customer Accounts` check box in the website settings."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:137
#: ../../content/applications/websites/website/configuration/multi_website.rst:131
msgid "Pricing"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:139
#: ../../content/applications/websites/website/configuration/multi_website.rst:133
msgid "Products can be priced differently based on the website using :ref:`pricelists <ecommerce/pricelists>`. The following configuration is required:"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:143
#: ../../content/applications/websites/website/configuration/multi_website.rst:137
msgid "Scroll down to the :guilabel:`Shop - Products` section and select the :guilabel:`Pricelists` option :guilabel:`Multiple prices per product`."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:145
#: ../../content/applications/websites/website/configuration/multi_website.rst:139
msgid "Click :guilabel:`Pricelists` to define new pricelists or edit existing ones."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:146
#: ../../content/applications/websites/website/configuration/multi_website.rst:140
msgid "Select the pricelist or click :guilabel:`New` to create a new one, then select the :guilabel:`Configuration` tab and set the :guilabel:`Website` field."
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:150
#: ../../content/applications/websites/website/configuration/multi_website.rst:144
#: ../../content/applications/websites/website/reporting.rst:5
msgid "Reporting"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:155
#: ../../content/applications/websites/website/configuration/multi_website.rst:149
msgid "Each website has its own :ref:`analytics <analytics/plausible>`. To switch between websites, click the buttons in the upper right corner."
msgstr ""
@ -5228,11 +5224,11 @@ msgstr ""
msgid "Switch websites in analytics"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:162
#: ../../content/applications/websites/website/configuration/multi_website.rst:156
msgid "Other reporting data"
msgstr ""
#: ../../content/applications/websites/website/configuration/multi_website.rst:164
#: ../../content/applications/websites/website/configuration/multi_website.rst:158
msgid "Other reporting data such as eCommerce dashboard data, online sales analyses and visitors can be grouped by website if necessary. Open the search panel and select :guilabel:`Group by --> Website`."
msgstr ""
@ -5245,54 +5241,54 @@ msgid ":ref:`Cloudflare Turnstile <cloudflare-turnstile>` and :ref:`Google reCAP
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:10
msgid "**Cloudflare Turnstile is recommended** as it is possible to add an interactive check if the automated check fails. Also, Google reCAPTCHA v3 is limited to `1 million assessments per month per domain <https://developers.google.com/recaptcha/docs/faq#are-there-any-qps-or-daily-limits-on-my-use-of-recaptcha>`_."
msgid "We recommend using **Cloudflare Turnstile** as reCAPTCHA v3 may not be compliant with local data protection regulations."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:15
#: ../../content/applications/websites/website/configuration/spam_protection.rst:14
msgid "All pages using the :guilabel:`Form`, :guilabel:`Newsletter Block`, :guilabel:`Newsletter Popup` snippets, and the eCommerce :guilabel:`Extra Step During Checkout` form are protected by both tools."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:20
#: ../../content/applications/websites/website/configuration/spam_protection.rst:19
msgid "`Cloudflare Turnstile's documentation <https://developers.cloudflare.com/turnstile/>`_"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:21
#: ../../content/applications/websites/website/configuration/spam_protection.rst:20
msgid "`Google's reCAPTCHA v3 guide <https://developers.google.com/recaptcha/docs/v3>`_"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:26
#: ../../content/applications/websites/website/configuration/spam_protection.rst:25
msgid "Cloudflare Turnstile configuration"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:29
#: ../../content/applications/websites/website/configuration/spam_protection.rst:28
msgid "On Cloudflare"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:31
#: ../../content/applications/websites/website/configuration/spam_protection.rst:30
msgid "`Create <https://dash.cloudflare.com/sign-up>`_ a Cloudflare account or use an existing one and `log in <https://dash.cloudflare.com/login>`_."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:33
#: ../../content/applications/websites/website/configuration/spam_protection.rst:32
msgid "On the dashboard navigation sidebar, click :guilabel:`Turnstile`."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:34
#: ../../content/applications/websites/website/configuration/spam_protection.rst:33
msgid "On the :guilabel:`Turnstile Sites` page, click :guilabel:`Add Site`."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:35
#: ../../content/applications/websites/website/configuration/spam_protection.rst:34
msgid "Add a :guilabel:`Site name` to identify it easily."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:36
#: ../../content/applications/websites/website/configuration/spam_protection.rst:35
msgid "Enter or select the website's :guilabel:`Domain` (e.g., *example.com* or *subdomain.example.com*)."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:37
#: ../../content/applications/websites/website/configuration/spam_protection.rst:36
msgid "Select a :guilabel:`Widget Mode`:"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:39
#: ../../content/applications/websites/website/configuration/spam_protection.rst:38
msgid "The :guilabel:`Managed` mode is **recommended**, as visitors can be prompted to check a box confirming they are human if deemed necessary by Turnstile."
msgstr ""
@ -5300,11 +5296,11 @@ msgstr ""
msgid "Cloudflare Turnstile human verification widget"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:45
#: ../../content/applications/websites/website/configuration/spam_protection.rst:44
msgid "For the :guilabel:`Non-interactive` and :guilabel:`Invisible` modes, visitors are never prompted to interact. In :guilabel:`Non-interactive` mode, a loading widget can be displayed to warn visitors that Turnstile protects the form; however, the widget is not supported by Odoo."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:50
#: ../../content/applications/websites/website/configuration/spam_protection.rst:49
msgid "If the Turnstile check fails, visitors are not able to submit the form, and the following error message is displayed:"
msgstr ""
@ -5312,8 +5308,8 @@ msgstr ""
msgid "Cloudflare Turnstile verification error message"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:56
#: ../../content/applications/websites/website/pages.rst:27
#: ../../content/applications/websites/website/configuration/spam_protection.rst:55
#: ../../content/applications/websites/website/pages.rst:28
msgid "Click :guilabel:`Create`."
msgstr ""
@ -5321,74 +5317,78 @@ msgstr ""
msgid "Adding a website to Cloudflare Turnstile"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:61
#: ../../content/applications/websites/website/configuration/spam_protection.rst:60
msgid "The generated keys are then displayed. Leave the page open for convenience, as copying the keys in Odoo is required next."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:65
#: ../../content/applications/websites/website/configuration/spam_protection.rst:109
#: ../../content/applications/websites/website/configuration/spam_protection.rst:64
#: ../../content/applications/websites/website/configuration/spam_protection.rst:111
msgid "On Odoo"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:67
#: ../../content/applications/websites/website/configuration/spam_protection.rst:66
msgid "From the database dashboard, click :guilabel:`Settings`. Under :guilabel:`Integrations`, enable :guilabel:`Cloudflare Turnstile` and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:69
#: ../../content/applications/websites/website/configuration/spam_protection.rst:68
msgid "Open the Cloudflare Turnstile page, copy the :guilabel:`Site Key`, and paste it into the :guilabel:`CF Site Key` field in Odoo."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:71
#: ../../content/applications/websites/website/configuration/spam_protection.rst:70
msgid "Open the Cloudflare Turnstile page, copy the :guilabel:`Secret Key`, and paste it into the :guilabel:`CF Secret Key` field in Odoo."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:73
#: ../../content/applications/websites/website/configuration/spam_protection.rst:125
#: ../../content/applications/websites/website/configuration/spam_protection.rst:72
#: ../../content/applications/websites/website/configuration/spam_protection.rst:127
#: ../../content/applications/websites/website/configuration/translate.rst:95
msgid "Click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:76
#: ../../content/applications/websites/website/configuration/spam_protection.rst:75
msgid "Navigate to Turnstile on your Cloudflare account to view the solve rates and access more settings."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:82
#: ../../content/applications/websites/website/configuration/spam_protection.rst:81
msgid "reCAPTCHA v3 configuration"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:85
msgid "On Google"
#: ../../content/applications/websites/website/configuration/spam_protection.rst:84
msgid "reCAPTCHA v3 may not be compliant with local data protection regulations."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:87
msgid "On Google"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:89
msgid "Open `the reCAPTCHA website registration page <https://www.google.com/recaptcha/admin/create>`_. Log in or create a Google account if necessary."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:90
#: ../../content/applications/websites/website/configuration/spam_protection.rst:92
msgid "On the website registration page:"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:92
#: ../../content/applications/websites/website/configuration/spam_protection.rst:94
msgid "Give the website a :guilabel:`Label`."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:93
#: ../../content/applications/websites/website/configuration/spam_protection.rst:95
msgid "Leave the :guilabel:`reCAPTCHA type` on :guilabel:`Score based (v3)`."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:94
#: ../../content/applications/websites/website/configuration/spam_protection.rst:96
msgid "Enter one or more :guilabel:`Domains` (e.g., *example.com* or *subdomain.example.com*)."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:95
#: ../../content/applications/websites/website/configuration/spam_protection.rst:97
msgid "Under :guilabel:`Google Cloud Platform`, a project is automatically selected if one was already created with the logged-in Google account. If not, one is automatically created. Click :guilabel:`Google Cloud Platform` to select a project yourself or rename the automatically created project."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:99
#: ../../content/applications/websites/website/configuration/spam_protection.rst:101
msgid "Agree to the terms of service."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:100
#: ../../content/applications/websites/website/configuration/spam_protection.rst:102
msgid "Click :guilabel:`Submit`."
msgstr ""
@ -5396,31 +5396,31 @@ msgstr ""
msgid "reCAPTCHA website registration example"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:105
#: ../../content/applications/websites/website/configuration/spam_protection.rst:107
msgid "A new page with the generated keys is then displayed. Leave it open for convenience, as copying the keys to Odoo is required next."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:111
#: ../../content/applications/websites/website/configuration/spam_protection.rst:113
msgid "From the database dashboard, click :guilabel:`Settings`. Under :guilabel:`Integrations`, enable :guilabel:`reCAPTCHA` if needed."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:115
#: ../../content/applications/websites/website/configuration/spam_protection.rst:117
msgid "Do not disable the :guilabel:`reCAPTCHA` feature or uninstall the :guilabel:`Google reCAPTCHA integration` module, as many other modules would also be removed."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:118
#: ../../content/applications/websites/website/configuration/spam_protection.rst:120
msgid "Open the Google reCAPTCHA page, copy the :guilabel:`Site key`, and paste it into the :guilabel:`Site Key` field in Odoo."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:120
#: ../../content/applications/websites/website/configuration/spam_protection.rst:122
msgid "Open the Google reCAPTCHA page, copy the :guilabel:`Secret key`, and paste it into the :guilabel:`Secret Key` field in Odoo."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:122
#: ../../content/applications/websites/website/configuration/spam_protection.rst:124
msgid "Change the default :guilabel:`Minimum score` (`0.50`) if necessary, using a value between `1.00` and `0.00`. The higher the threshold is, the more difficult it is to pass the reCAPTCHA, and vice versa."
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:127
#: ../../content/applications/websites/website/configuration/spam_protection.rst:129
msgid "You can notify visitors that reCAPTCHA protects a form. To do so, open the website editor and navigate to the form. Then, click somewhere on the form, and on the right sidebar's :guilabel:`Customize` tab, toggle :guilabel:`Show reCAPTCHA Policy` found under the :guilabel:`Form` section."
msgstr ""
@ -5428,7 +5428,7 @@ msgstr ""
msgid "reCAPTCHA policy message displayed on a form"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:136
#: ../../content/applications/websites/website/configuration/spam_protection.rst:138
msgid "If the reCAPTCHA check fails, the following error message is displayed:"
msgstr ""
@ -5436,7 +5436,7 @@ msgstr ""
msgid "Google reCAPTCHA verification error message"
msgstr ""
#: ../../content/applications/websites/website/configuration/spam_protection.rst:142
#: ../../content/applications/websites/website/configuration/spam_protection.rst:144
msgid "Analytics and additional settings are available on `Google's reCAPTCHA administration page <https://www.google.com/recaptcha/admin/>`_. For example, you can receive email alerts if Google detects suspicious traffic on your website or view the percentage of suspicious requests, which could help you determine the right minimum score."
msgstr ""
@ -5740,107 +5740,107 @@ msgstr ""
msgid "Odoo allows you to create pages for your website and customize their content and appearance to your needs."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:11
msgid "*Static* pages are pages that have stable content, such as the homepage. You can manually create new ones, define their URL, adapt their :ref:`properties <website/page_properties>`, etc. *Dynamic* pages, on the other hand, are generated dynamically. All pages generated automatically by Odoo, for example when you install an app or module (e.g., `/shop` or `/blog`) or publish a new product or blog post, are dynamic pages and are therefore managed differently."
#: ../../content/applications/websites/website/pages.rst:12
msgid "**Static** pages have stable content, such as the homepage. You can manually create new ones, define their URLs, adapt their :ref:`properties <website/page_properties>`, etc. **Dynamic** pages, on the other hand, are generated dynamically. All pages generated automatically by Odoo, for example, when you install an app or module (e.g., `/shop` or `/blog`) or publish a new product or blog post, are dynamic pages and are therefore managed differently."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:18
#: ../../content/applications/websites/website/pages.rst:19
msgid "Page creation"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:20
#: ../../content/applications/websites/website/pages.rst:21
msgid "Website pages can be created from the **frontend** and the **backend**. To create a new website page, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:23
#: ../../content/applications/websites/website/pages.rst:24
msgid "Either open the **Website** app, click :guilabel:`+ New` in the top-right corner, then select :guilabel:`Page`;"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:25
#: ../../content/applications/websites/website/pages.rst:26
msgid "Or go to :menuselection:`Website --> Site --> Pages` and click :guilabel:`New`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:26
msgid "Enter a :guilabel:`Page Title`; this title is used in the menu, as well as in the page's URL."
#: ../../content/applications/websites/website/pages.rst:27
msgid "Enter a :guilabel:`Page Title`; this title is used in the menu and the page's URL."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:28
#: ../../content/applications/websites/website/pages.rst:29
msgid "Customize the page's content and appearance using the website builder, then click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:30
#: ../../content/applications/websites/website/pages.rst:31
msgid ":ref:`Publish <website/un-publish-page>` the page."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:33
#: ../../content/applications/websites/website/pages.rst:34
msgid "Disable :guilabel:`Add to menu` if the page should not appear in the menu."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:36
#: ../../content/applications/websites/website/pages.rst:37
msgid "Page management"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:41
#: ../../content/applications/websites/website/pages.rst:42
msgid "Publishing/unpublishing pages"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:43
msgid "Pages need to be published to make them accessible to website visitors. To publish or unpublish a page, access it, then toggle the switch in the upper-right corner from :guilabel:`Unpublished` to :guilabel:`Published`, or vice versa."
#: ../../content/applications/websites/website/pages.rst:44
msgid "Pages need to be published to make them accessible to website visitors. To publish or unpublish a page, access it and toggle the switch in the upper-right corner from :guilabel:`Unpublished` to :guilabel:`Published`, or vice versa."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:-1
msgid "Unpublished/Published toggle"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:51
#: ../../content/applications/websites/website/pages.rst:52
msgid "It is also possible to:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:53
#: ../../content/applications/websites/website/pages.rst:54
msgid "publish/unpublish a page from the :ref:`page properties <website/page_properties>`, where you can define a publishing date and/or restrict the page's visibility if needed;"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:55
msgid "publish/unpublish several pages at once: go to :menuselection:`Website --> Site --> Pages`, select the pages, then, click :guilabel:`Action` and select :guilabel:`Publish` or :guilabel:`Unpublish`."
#: ../../content/applications/websites/website/pages.rst:56
msgid "publish/unpublish several pages at once: go to :menuselection:`Website --> Site --> Pages`, select the pages, then click :guilabel:`Action` and select :guilabel:`Publish` or :guilabel:`Unpublish`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:60
#: ../../content/applications/websites/website/pages.rst:61
msgid "Homepage"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:62
msgid "By default, when you create a website, Odoo creates a dedicated :guilabel:`Home` page, but you can define any website page as your homepage. To do so, go to :menuselection:`Website --> Configuration --> Settings`, then, in the :guilabel:`Website info` section, define the URL of the desired page in the field :guilabel:`Homepage URL` (e.g., `/shop`)."
#: ../../content/applications/websites/website/pages.rst:63
msgid "When you create a website, Odoo creates a dedicated :guilabel:`Home` page by default, but you can define any website page as your homepage. To do so, go to :menuselection:`Website --> Configuration --> Settings`, then, in the :guilabel:`Website info` section, define the URL of the desired page in the field :guilabel:`Homepage URL` (e.g., `/shop`)."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:67
msgid "Alternatively, you can define any static page as your homepage by going to :menuselection:`Website --> Site --> Properties`. Select the :guilabel:`Publish` tab and enable :guilabel:`Use as Homepage`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:73
msgid "Page properties"
#: ../../content/applications/websites/website/pages.rst:68
msgid "Alternatively, you can define any :ref:`static page <website/page_type>` as your homepage by going to :menuselection:`Website --> Site --> Properties`. Select the :guilabel:`Publish` tab and enable :guilabel:`Use as Homepage`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:75
msgid "To modify a static page's properties, access the page you wish to modify, then go to :menuselection:`Site --> Properties`."
msgid "Page properties"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:78
msgid "The :guilabel:`Name` tab allows you to:"
#: ../../content/applications/websites/website/pages.rst:77
msgid "To modify a :ref:`static page's <website/page_type>` properties, access the page you wish to modify, then go to :menuselection:`Site --> Properties`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:80
msgid "The :guilabel:`Name` tab allows you to:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:82
msgid "rename the page using the :guilabel:`Page Name` field;"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:81
#: ../../content/applications/websites/website/pages.rst:83
msgid "modify the :guilabel:`Page URL`. In this case, you can redirect the old URL to the new one if needed. To do so, enable :guilabel:`Redirect Old URL`, then select the :guilabel:`Type` of :ref:`redirection <website/URL-redirection>`:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:85
#: ../../content/applications/websites/website/pages.rst:87
msgid ":guilabel:`301 Moved permanently`: to redirect the page permanently;"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:86
#: ../../content/applications/websites/website/pages.rst:88
msgid ":guilabel:`302 Moved temporarily`: to redirect the page temporarily."
msgstr ""
@ -5848,159 +5848,159 @@ msgstr ""
msgid "Redirect old URL"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:91
#: ../../content/applications/websites/website/pages.rst:93
msgid "You can further adapt the page's properties in the :guilabel:`Publish` tab:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:93
#: ../../content/applications/websites/website/pages.rst:95
msgid ":guilabel:`Show in Top Menu`: Disable if you don't want the page to appear in the menu;"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:94
#: ../../content/applications/websites/website/pages.rst:96
msgid ":guilabel:`Use as Homepage`: Enable if you want the page to be the homepage of your website;"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:95
#: ../../content/applications/websites/website/pages.rst:97
msgid ":guilabel:`Indexed`: Disable if you don't want the page to be shown in search engine results;"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:96
#: ../../content/applications/websites/website/pages.rst:98
msgid ":guilabel:`Published`: Enable to publish the page;"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:97
#: ../../content/applications/websites/website/pages.rst:99
msgid ":guilabel:`Publishing Date`: To publish the page at a specific moment, select the date, click the clock icon to set the time, then click the green check mark to validate your selection."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:99
#: ../../content/applications/websites/website/pages.rst:101
msgid ":guilabel:`Visibility`: Select who can access the page:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:101
#: ../../content/applications/websites/website/pages.rst:103
msgid ":guilabel:`All`"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:102
#: ../../content/applications/websites/website/pages.rst:104
msgid ":guilabel:`Signed In`"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:103
#: ../../content/applications/websites/website/pages.rst:105
msgid ":guilabel:`Restricted Group`: Select the :doc:`user access group(s) </applications/general/users/access_rights>` in the :guilabel:`Authorized group` field."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:105
#: ../../content/applications/websites/website/pages.rst:107
msgid ":guilabel:`With Password`: Enter the password in the :guilabel:`Password` field."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:108
#: ../../content/applications/websites/website/pages.rst:110
msgid "*Some* of these properties can also be modified from :menuselection:`Website --> Site --> Pages`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:111
#: ../../content/applications/websites/website/pages.rst:113
msgid "Duplicating pages"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:113
#: ../../content/applications/websites/website/pages.rst:115
msgid "To duplicate a page, access the page, then go to :menuselection:`Site --> Properties` and click :guilabel:`Duplicate Page`. Enter a :guilabel:`Page Name`, then click :guilabel:`OK`. By default, the new page is added after the duplicated page in the menu, but you can remove it from the menu or change its position using the :doc:`menu editor <pages/menus>`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:121
#: ../../content/applications/websites/website/pages.rst:123
msgid "Deleting pages"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:123
#: ../../content/applications/websites/website/pages.rst:125
msgid "To delete a page, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:125
#: ../../content/applications/websites/website/pages.rst:127
msgid "Access the page, then go to :menuselection:`Site --> Properties` and click :guilabel:`Delete Page`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:127
#: ../../content/applications/websites/website/pages.rst:129
msgid "A pop-up window appears on the screen with all links referring to the page you want to delete, organized by category. To ensure website visitors don't land on a 404 error page, you must update all the links on your website referring to the page. To do so, expand a category, then click on a link to open it in a new window. Alternatively, you can set up a :ref:`redirection <website/URL-redirection>` for the deleted page."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:132
#: ../../content/applications/websites/website/pages.rst:134
msgid "Once you have updated the links (or set up a :ref:`redirection <website/URL-redirection>`), select the :guilabel:`I am sure about this` check box, then click :guilabel:`OK`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:138
msgid "URL redirects"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:140
msgid "Redirecting URLs consists in sending visitors and search engines to a URL that is different from the one they originally requested. This technique is used, for example, to prevent broken links when you :ref:`delete a page <website/delete-page>`, :ref:`modify its URL <website/page_properties>`, or move your site to a new :doc:`domain <configuration/domain_names>`. It can also be used to improve :doc:`pages/seo`."
msgid "URL redirect mapping"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:146
#: ../../content/applications/websites/website/pages.rst:142
msgid "URL redirect mapping consists in sending visitors and search engines to a URL different from the one they initially requested. This technique is used, for example, to prevent broken links when you :ref:`delete a page <website/delete-page>`, :ref:`modify its URL <website/page_properties>`, or migrate your site from another platform to an Odoo :doc:`domain <configuration/domain_names>`. It can also be used to improve :doc:`pages/seo`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:148
msgid "To access existing URL redirections and create new ones, :doc:`activate the developer mode </applications/general/developer_mode>` and go to :menuselection:`Website --> Configuration --> Redirects`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:151
msgid "A record is added automatically every time you :ref:`modify a page's URL <website/page_properties>` and enable :guilabel:`Redirect Old URL`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:153
msgid "You can set up redirections for static and dynamic pages."
msgid "A redirect record is added automatically every time you :ref:`modify a page's URL <website/page_properties>` and enable :guilabel:`Redirect Old URL`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:155
msgid "To create a new redirection, click the :guilabel:`New` button, then fill in the fields:"
msgid "You can set up redirections for :ref:`static and dynamic pages <website/page_type>`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:157
msgid "To create a new redirection, click the :guilabel:`New` button, then fill in the fields:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:159
msgid ":guilabel:`Name`: Enter a name to identify the redirect."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:158
#: ../../content/applications/websites/website/pages.rst:160
msgid ":guilabel:`Action`: Select the type of redirection:"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:160
msgid ":guilabel:`404 Not found`: visitors are redirected to a 404 error page when they try to access the page."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:162
msgid ":guilabel:`301 Moved Permanently`: for permanent redirections of static pages; the new URL is shown in search engine results and the redirect is cached by browsers."
msgid ":guilabel:`404 Not found`: visitors are redirected to a 404 error page when they try to access an unpublished or deleted page."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:164
msgid ":guilabel:`302 Moved Temporarily`: for short-term redirections, for example, if you are redesigning or updating the page. The new URL is neither cached by browsers, nor shown in search engine results."
msgid ":guilabel:`301 Moved Permanently`: for permanent redirections of unpublished or deleted :ref:`static pages <website/page_type>`. The new URL is shown in search engine results, and the redirect is cached by browsers."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:167
msgid ":guilabel:`308 Redirect / Rewrite`: for permanent redirections of dynamic pages; the new URL is shown in search engine results and the redirect is cached by browsers. Use this redirect type to rename a dynamic page, for example, if you wish to rename `/shop` into `/market`."
msgid ":guilabel:`302 Moved Temporarily`: for short-term redirections, for example, if you are redesigning or updating a page. The new URL is neither cached by browsers nor shown in search engine results."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:171
msgid ":guilabel:`URL from`: Enter the URL to be redirected (e.g., `/about-the-company`) or search for the desired dynamic page and select it from the list."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:173
msgid ":guilabel:`URL to`: For 301, 302 and 308 redirects, enter the URL to be redirected to. If you want to redirect to an external URL, make sure to include the protocol (e.g., `https://`)."
#: ../../content/applications/websites/website/pages.rst:170
msgid ":guilabel:`308 Redirect/Rewrite`: for permanent redirections of existing :ref:`dynamic pages <website/page_type>`. The URL is renamed; the new name is shown in search engine results and is cached by browsers. Use this redirect type to rename a dynamic page, for example, if you wish to rename `/shop` into `/market`."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:175
msgid ":guilabel:`URL from`: Enter the URL to be redirected (e.g., `/about-the-company`) or search for the desired :ref:`dynamic page <website/page_type>` and select it from the list."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:177
msgid ":guilabel:`URL to`: For 301, 302, and 308 redirects, enter the URL to be redirected to. If you want to redirect to an external URL, include the protocol (e.g., `https://`)."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:179
msgid ":guilabel:`Website`: Select a specific website."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:176
msgid ":guilabel:`Sequence`: to define the order in which redirections are performed, e.g., in the case of redirect chains (i.e., a series of redirects where one URL is redirected to another one, which is itself further redirected to another URL)."
#: ../../content/applications/websites/website/pages.rst:180
msgid ":guilabel:`Sequence`: To define the order in which redirections are performed, e.g., in the case of redirect chains (i.e., a series of redirects where one URL is redirected to another one, which is itself further redirected to another URL)."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:180
#: ../../content/applications/websites/website/pages.rst:184
msgid "Toggle the :guilabel:`Activate` switch to deactivate the redirection."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:183
msgid "404, 301 and 302 redirections only work if the original page has been :ref:`unpublished <website/un-publish-page>` or :ref:`deleted <website/delete-page>`."
#: ../../content/applications/websites/website/pages.rst:187
msgid "404, 301, and 302 redirections are meant to migrate traffic from :ref:`unpublished <website/un-publish-page>` or :ref:`deleted <website/delete-page>` pages to *new* pages, while the 308 redirect is used for *permanent* redirections of *existing* pages."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:187
#: ../../content/applications/websites/website/pages.rst:192
msgid "`Google documentation on redirects and search <https://developers.google.com/search/docs/crawling-indexing/301-redirects>`_"
msgstr ""
#: ../../content/applications/websites/website/pages.rst:188
#: ../../content/applications/websites/website/pages.rst:193
msgid ":doc:`pages/seo`"
msgstr ""
@ -6499,30 +6499,38 @@ msgid "Google Tag Manager"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:135
msgid ":abbr:`GTM (Google Tag Manager)` is a tag management system that allows you to easily update measurement codes and related code fragments, collectively known as tags on your website or mobile app, directly through the code injector. To use GTM, proceed as follows:"
msgid ":abbr:`GTM (Google Tag Manager)` is a tag management system that allows you to easily update measurement codes and related code fragments, collectively known as tags on your website or mobile app, directly through the code injector."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:139
#: ../../content/applications/websites/website/reporting/analytics.rst:140
msgid "Google Tag Manager may not be compliant with local data protection regulations."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:142
msgid "To use GTM, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:144
msgid "Create or sign in to a Google account by going to https://tagmanager.google.com/."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:141
#: ../../content/applications/websites/website/reporting/analytics.rst:146
msgid "In the :guilabel:`Accounts` tab, click :guilabel:`Create account`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:143
#: ../../content/applications/websites/website/reporting/analytics.rst:148
msgid "Enter an :guilabel:`Account Name` and select the account's :guilabel:`Country`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:145
#: ../../content/applications/websites/website/reporting/analytics.rst:150
msgid "Enter your website's URL in the :guilabel:`Container name` field and select the :guilabel:`Target platform`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:148
#: ../../content/applications/websites/website/reporting/analytics.rst:153
msgid "Click :guilabel:`Create` and agree to the Terms of Service."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:150
#: ../../content/applications/websites/website/reporting/analytics.rst:155
msgid "Copy the `<head>` and `<body>` codes from the popup window. Then, go to your website, click :guilabel:`Edit`, go to the :guilabel:`Themes` tab, scroll down to the :guilabel:`Website Settings` section, then click :guilabel:`<head>` and :guilabel:`</body>` to paste the codes."
msgstr ""
@ -6530,7 +6538,7 @@ msgstr ""
msgid "Install Google Tag Manager"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:159
#: ../../content/applications/websites/website/reporting/analytics.rst:164
msgid "The data is collected in the marketing tools used to monitor the website (e.g., Google Analytics, Plausible, Facebook Pixel), not in Odoo."
msgstr ""
@ -6808,6 +6816,7 @@ msgid "The :guilabel:`Dynamic Content` building blocks, such as :ref:`Form <dyna
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:11
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:12
#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:10
#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:12
msgid "To add a building block, click :guilabel:`Edit`, select the desired building block under the :guilabel:`Blocks` tab, and drag and drop it onto the page. To access its settings, click it and go to the :guilabel:`Customize` tab, where the available options depend on the type of block selected."
@ -6925,6 +6934,47 @@ msgstr ""
msgid "After adding the block to a page, click the :guilabel:`Edit` button found under the :guilabel:`Customize` tab's :guilabel:`Embed Code` section and enter the code, replacing the code used to show the block's instructions."
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:3
msgid "Features"
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:5
msgid "The :guilabel:`Features` :doc:`building blocks <../building_blocks>` allow you to list multiple items next to each other."
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:8
msgid "The :ref:`Table of Content <features/table_of_content>` and the :ref:`Call to Action <features/call_to_action>` blocks are presented below."
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:20
msgid "Table of content"
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:22
msgid "The :guilabel:`Table of Content` block is used to list many different items grouped under several headings. A clickable index is available to navigate quickly between the different categories."
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:-1
msgid "The default Table of Content block"
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:31
#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:29
msgid "Call to action"
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:33
msgid "The :guilabel:`Call to Action` block is used to prompt visitors to take a specific action, such as signing up for a newsletter or contacting you."
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:-1
msgid "The default Call to Action block"
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/features.rst:39
msgid "To change the button's link, select it, go to the :guilabel:`Customize` tab's :guilabel:`Inline Text` section and replace `/contactus` with another URL."
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:3
msgid "Inner content"
msgstr ""
@ -6973,10 +7023,6 @@ msgstr ""
msgid "The default banner block"
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:29
msgid "Call to action"
msgstr ""
#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:31
msgid "The call to action button encourages visitors to take a specific action, for example, consulting your shop, downloading a file, or making an appointment."
msgstr ""