diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 76d776e98..19908ffee 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -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 \n" "Language-Team: LANGUAGE \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 `_." 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 `_ for it to support headers and footers. Check out the `wkhtmltopdf wiki `_ 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 `_ 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 `_ 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 `_ 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 `_. 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 `_, `MacPorts `_)." 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 `_." 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\\\\\\\\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 `_, `MacPorts `_)." 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 ` or a :ref:`configuration file `." 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 ` 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 `" msgstr "" diff --git a/locale/sources/essentials.pot b/locale/sources/essentials.pot index da9d1d6dc..13fb727a4 100644 --- a/locale/sources/essentials.pot +++ b/locale/sources/essentials.pot @@ -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 \n" "Language-Team: LANGUAGE \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 `:" +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 ` thread, :ref:`Kanban view `, :ref:`list view `, or :ref:`activities view ` 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 `." 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 `." +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 ` 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 `." +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 ` of a record, or from one of multiple views in an application, when available: the :ref:`Kanban view `, :ref:`list view `, or :ref:`activity view `." +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 `. 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 `, 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 ` 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 `, 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 `, 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 ` 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 `." +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 diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index e59cbf543..8754fa2d4 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -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 \n" "Language-Team: LANGUAGE \n" @@ -416,7 +416,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:46 #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:12 #: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:15 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:36 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:38 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:15 #: ../../content/applications/finance/accounting/get_started/vat_units.rst:22 #: ../../content/applications/finance/accounting/payments/batch.rst:11 @@ -457,6 +457,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:583 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:701 #: ../../content/applications/finance/fiscal_localizations/germany.rst:58 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:6 #: ../../content/applications/finance/fiscal_localizations/italy.rst:8 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:8 #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:6 @@ -1398,6 +1399,7 @@ msgstr "" #: ../../content/applications/finance/accounting/bank/reconciliation.rst:43 #: ../../content/applications/finance/accounting/bank/transactions.rst:3 +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:32 msgid "Transactions" msgstr "" @@ -1761,7 +1763,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:5 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:90 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:352 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:432 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:363 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 msgid "Customer invoices" @@ -1945,7 +1947,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:169 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:32 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:180 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:242 #: ../../content/applications/finance/fiscal_localizations/chile.rst:366 #: ../../content/applications/finance/fiscal_localizations/chile.rst:376 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 @@ -2996,6 +2998,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:58 #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:123 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:125 #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:38 msgid ":doc:`../../fiscal_localizations`" msgstr "" @@ -4303,264 +4306,267 @@ msgid "Thus, when shipments are returned to their supplier, Odoo automatically g msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:27 -msgid "This document addresses a specific use case for theoretical purposes. Navigate :ref:`here ` for instructions on how to set up and use |AVCO| in Odoo." -msgstr "" - -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:32 -msgid ":ref:`Using inventory valuation `" +msgid "This document addresses a specific use case for theoretical purposes. For instructions on how to set up and use |AVCO|, refer to the :doc:`inventory valuation configuration <../../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config>` doc." msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:33 +msgid ":doc:`Using inventory valuation <../../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation>`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:35 msgid ":ref:`Other inventory valuation methods `" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:38 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:40 msgid "To use average cost inventory valuation on a product, navigate to :menuselection:`Inventory --> Configuration --> Product Categories` and select the category that will be using |AVCO|. On the product category page, set :guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory Valuation` to `Automated`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:44 -msgid ":ref:`Inventory valuation configuration `" +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:46 +msgid ":doc:`Inventory valuation configuration <../../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config>`" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:47 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:50 msgid "Using average cost valuation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:49 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:52 msgid "The average cost method adjusts the inventory valuation when products are received in the warehouse. This section explains how it works, but if the explanation is unnecessary, skip to the :ref:`return to supplier use case ` section." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:59 msgid "Formula" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:58 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:61 msgid "When new products arrive, the new average cost for each product is recomputed using the formula:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:60 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:63 msgid "Avg~Cost = \\frac{(Old~Qty \\times Old~Avg~Cost) + (Incoming~Qty \\times Purchase~Price)}{Final~Qty}\n" "\n" "" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:63 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:66 msgid "**Old Qty**: product count in stock before receiving the new shipment;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:64 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:67 msgid "**Old Avg Cost**: calculated average cost for a single product from the previous inventory valuation;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:66 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:69 msgid "**Incoming Qty**: count of products arriving in the new shipment;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:67 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:70 msgid "**Purchase Price**: estimated price of products at the reception of products (since vendor bills may arrive later). The amount includes not only the price for the products, but also added costs, such as shipping, taxes, and :ref:`landed costs `. At reception of the vendor bill, this price is adjusted;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:71 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:74 msgid "**Final Qty**: quantity of on-hand stock after the stock move." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:76 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:79 msgid "When products leave the warehouse, the average cost **does not** change. Read about why the average cost valuation is **not** adjusted :ref:`here `." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:85 msgid "Compute average cost" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:87 msgid "To understand how the average cost of a product changes with each shipment, consider the following table of warehouse operations and stock moves. Each is a different example of how the average cost valuation is affected." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:92 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:198 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:239 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:276 msgid "Operation" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:92 msgid "Incoming Value" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:92 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:198 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:239 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:276 msgid "Inventory Value" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:92 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:198 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:239 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:276 msgid "Qty On Hand" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:92 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:198 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:239 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:276 msgid "Avg Cost" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:94 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:94 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:278 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:278 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:282 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:286 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:288 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:292 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:403 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:417 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:424 msgid "$0" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:94 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:278 #: ../../content/applications/finance/fiscal_localizations/france.rst:240 #: ../../content/applications/finance/fiscal_localizations/france.rst:240 msgid "0" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:96 msgid "Receive 8 tables at $10/unit" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:96 msgid "8 * $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:96 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:280 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:282 msgid "$80" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:96 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:280 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:282 msgid "8" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:96 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:280 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:282 msgid "$10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:98 msgid "Receive 4 tables at $16/unit" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:98 msgid "4 * $16" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:98 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:284 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:286 msgid "$144" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:98 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:284 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:286 #: ../../content/applications/finance/fiscal_localizations/france.rst:88 #: ../../content/applications/finance/fiscal_localizations/france.rst:111 msgid "12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:98 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:100 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:200 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:241 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:243 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:243 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:284 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:286 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:288 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:290 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:292 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:292 msgid "$12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:100 msgid "Deliver 10 tables" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:100 msgid "-10 * $12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:100 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:200 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:241 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:288 msgid "$24" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:100 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:200 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:241 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:288 msgid "2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:106 msgid "Ensure comprehension of the above computations by reviewing the \"Receive 8 tables at $10/unit\" example." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:106 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:109 msgid "Initially, the product stock is 0, so all values are $0." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:108 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:111 msgid "In the first warehouse operation, `8` tables are received at `$10` each. The average cost is calculated using the :ref:`formula `:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:111 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:114 msgid "Avg~Cost = \\frac{0 + 8 \\times $10}{8} = \\frac{$80}{8} = $10\n" "\n" "" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:114 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 msgid "Since the *incoming quantity* of tables is `8` and the *purchase price* for each is `$10`," msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:115 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:118 msgid "The inventory value in the numerator is evaluated to `$80`;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:116 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 msgid "`$80` is divided by the total amount of tables to store, `8`;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:120 msgid "`$10` is the average cost of a single table from the first shipment." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:122 msgid "To verify this in Odoo, in the *Purchase* app, order `8` quantities of a new product, `Table`, with no previous stock moves, for `$10` each." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:122 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:125 msgid "In the table's :guilabel:`Product Category` field in the :guilabel:`General Information` tab of the product form, click the :guilabel:`➡️ (arrow)` icon, to open an :guilabel:`External Link` to edit the product category. Set the :guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory Valuation` to `Automated`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:127 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 msgid "Then, return to the purchase order. Click :guilabel:`Confirm Order`, and click :guilabel:`Receive Products` to confirm receipt." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:133 msgid "Next, check the inventory valuation record generated by the product reception by navigating to :menuselection:`Inventory --> Reporting --> Inventory Valuation`. Select the drop-down for `Table`, and view the :guilabel:`Total Value` column for the *valuation layer* (:dfn:`inventory valuation at a specific point in time = on-hand quantity * unit price`). The 8 tables in-stock are worth $80." msgstr "" @@ -4568,53 +4574,53 @@ msgstr "" msgid "Show inventory valuation of 8 tables in Odoo." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:141 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:144 msgid "When the product category's :guilabel:`Costing Method` is set to :guilabel:`AVCO`, then the average cost of a product is also displayed on the :guilabel:`Cost` field, under the :guilabel:`General Information` tab, on the product page itself." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:149 msgid "Product delivery (use case)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:151 msgid "For outgoing shipments, :ref:`outbound products have no effect on the average cost valuation `. Although the average cost valuation is not recalculated, the inventory value still decreases because the product is removed from stock and delivered to the customer location." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:157 msgid "To demonstrate that the average cost valuation is not recalculated, examine the \"Deliver 10 tables\" example." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:157 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 msgid "Avg~Cost = \\frac{12 \\times $12 + (-10) \\times $12}{12-10} = \\frac{24}{2} = $12\n" "\n" "" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:163 msgid "Because 10 tables are being sent out to customers, the *incoming quantity* is `-10`. The previous average cost (`$12`) is used in lieu of a vendor's *purchase price*;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:162 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:165 msgid "The *incoming inventory value* is `-10 * $12 = -$120`;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:163 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:166 msgid "The old *inventory value* (`$144`) is added to the *incoming inventory value* (`-$120`), so `$144 + -$120 = $24`;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:165 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:168 msgid "Only `2` tables remain after shipping out `10` tables from `12`. So the current *inventory value* (`$24`) is divided by the on-hand quantity (`2`);" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:167 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:170 msgid "`$24 / 2 = $12`, which is the same average cost as the previous operation." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:169 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:172 msgid "To verify this in Odoo, sell `10` tables in the *Sales* app, validate the delivery, and then review the inventory valuation record by going to in :menuselection:`Inventory --> Reporting --> Inventory Valuation`. In the topmost valuation layer, delivering `10` tables reduces the product's value by `-$120`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:174 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:177 msgid "**Note**: What is not represented in this stock valuation record is the revenue made from this sale, so this decrease is not a loss to the company." msgstr "" @@ -4622,59 +4628,59 @@ msgstr "" msgid "Show how deliveries decrease inventory valuation." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:184 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:187 msgid "Return items to supplier (use case)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:186 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:189 msgid "Because the price paid to suppliers can differ from the price the product is valued at with the |AVCO| method, Odoo handles returned items in a specific way." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:189 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:192 msgid "Products are returned to suppliers at the original purchase price, but;" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:190 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:193 msgid "The internal cost valuation remains unchanged." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:192 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 msgid "The above :ref:`example table ` is updated as follows:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:198 msgid "Qty*Avg Cost" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 msgid "Return 1 table bought at $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 msgid "-1 * $12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:243 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:290 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:292 #: ../../content/applications/finance/fiscal_localizations/france.rst:242 msgid "1" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:205 msgid "In other words, returns to vendors are perceived by Odoo as another form of a product exiting the warehouse. To Odoo, because the table is valued at $12 per unit, the inventory value is reduced by `$12` when the product is returned; the initial purchase price of `$10` is unrelated to the table's average cost." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:208 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:211 msgid "To return a single table that was purchased for `$10`, navigate to the receipt in the *Inventory* app for the :ref:`8 tables purchased in Exercise 1 ` by going to the :guilabel:`Inventory Overview`, clicking on :guilabel:`Receipts`, and selecting the desired receipt." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:213 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:216 msgid "Then, click :guilabel:`Return` on the validated delivery order, and modify the quantity to `1` in the reverse transfer window. This creates an outgoing shipment for the table. Select :guilabel:`Validate` to confirm the outgoing shipment." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:217 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:220 msgid "Return to :menuselection:`Inventory --> Reporting --> Inventory Valuation` to see how the outgoing shipment decreases the inventory value by $12." msgstr "" @@ -4682,181 +4688,181 @@ msgstr "" msgid "Inventory valuation for return." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:227 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:230 msgid "Eliminate stock valuation errors in outgoing products" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:229 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:232 msgid "Inconsistencies can occur in a company's inventory when the average cost valuation is recalculated on outgoing shipments." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:232 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:235 msgid "To demonstrate this error, the table below displays a scenario in which 1 table is shipped to a customer and another is returned to a supplier at the purchased price." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:239 msgid "Qty*Price" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:243 msgid "Ship 1 product to customer" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:243 msgid "-1 \\* $12" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 msgid "Return 1 product initially bought at $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 msgid "-1 \\* $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:290 msgid "**$2**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 msgid "**0**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:248 msgid "In the final operation above, the final inventory valuation for the table is `$2` even though there are `0` tables left in stock." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:248 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:251 msgid "Correct method" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:250 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:253 msgid "Use the average cost to value the return. This does not mean the company gets $12 back for a $10 purchase; the item returned for $10 is valued internally at $12. The inventory value change represents a product worth $12 no longer being accounted for in company assets." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:255 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:258 msgid "Anglo-Saxon accounting" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:257 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:260 msgid "In addition to using |AVCO|, companies that use **Anglo-Saxon accounting** also keep a holding account that tracks the amount to be paid to vendors. Once a vendor delivers an order, **inventory value** increases based on the vendor price of the products that have entered the stock. The holding account (called **stock input**) is credited and only reconciled once the vendor bill is received." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:263 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:266 msgid ":ref:`Anglo-Saxon vs. Continental `" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:265 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:268 msgid "The table below reflects journal entries and accounts. The *stock input* account stores the money intended to pay vendors when the vendor bill has not yet been received. To balance accounts when returning products that have a price difference between the price the product is **valued at** and the price it was bought for, a *price difference* account is created." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:276 msgid "Stock Input" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:276 msgid "Price Diff" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:280 msgid "Receive 8 tables at $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:280 msgid "($80)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:282 msgid "Receive vendor bill $80" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:284 msgid "Receive 4 tables at $16" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:284 msgid "($64)" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:286 msgid "Receive vendor bill $64" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:288 msgid "Deliver 10 tables to customer" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:290 msgid "Return 1 table initially bought at $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:290 msgid "**$10**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:290 msgid "**$12**" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:292 msgid "Receive vendor refund $10" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:292 msgid "$2" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:293 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:296 msgid "Product reception" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:296 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:299 msgid "Summary" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:298 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:301 msgid "At product reception, Odoo ensures companies can pay for goods that were purchased by preemptively moving an amount matching the price of received goods into the :doc:`liability account `, **Stock Input**. Then, once the bill has been received, the amount in the holding account is transferred to *Accounts Payable*. Transfers into this account means the bill has been paid. **Stock Input** is reconciled once the vendor bill is received." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:305 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:308 msgid "Inventory valuation is a method of calculating how much each in-stock product is worth internally. Since there is a difference between the price the product is **valuated at** and the price the product was actually **purchased for**, the **Inventory Valuation** account is unrelated to the crediting and debiting operations of the **Stock Input** account." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:310 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:313 msgid "To conceptualize all this, follow the breakdown below." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:313 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:316 msgid "Accounts balanced at received products" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:315 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:318 msgid "In this example, a company starts with zero units of a product, `table`, in stock. Then, 8 tables are received from the vendor:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:318 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:321 msgid "The **Stock Input** account stores `$80` of credit owed to the vendor. The amount in this account is unrelated to the inventory value." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:320 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:323 msgid "`$80` worth of tables came **in** (**debit** the *Inventory Value* account `$80`), and" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:321 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:324 msgid "`$80` must be paid **out** for received goods (**credit** the *Stock Input* account `$80`)." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:324 -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:367 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:327 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:370 msgid "In Odoo" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:326 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:329 msgid "Odoo generates an accounting journal entry when shipments that use |AVCO| costing method are received. Configure a :guilabel:`Price Difference Account` by selecting the :guilabel:`➡️ (arrow)` icon next to the :guilabel:`Product Category` field on the product page." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:330 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:333 msgid "Under :guilabel:`Account Properties`, create a new :guilabel:`Price Difference Account` by typing in the name of the account and clicking :guilabel:`Create and Edit`. Then set the account :guilabel:`Type` as `Expenses`, and click :guilabel:`Save`." msgstr "" @@ -4864,7 +4870,7 @@ msgstr "" msgid "Create price difference account." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:338 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:341 msgid "Then, receive the shipment in the *Purchase* app or *Inventory* app, and navigate to the :menuselection:`Accounting app --> Accounting --> Journal Entries`. In the list, find the :guilabel:`Reference` that matches the warehouse reception operation for the relevant product." msgstr "" @@ -4872,7 +4878,7 @@ msgstr "" msgid "Show accounting entry of 8 tables from the list." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:346 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:349 msgid "Click on the line for 8 tables. This accounting journal entry shows that when the 8 tables were received, the `Stock Valuation` account increased by `$80`. Conversely, the **Stock Input** account (set as `Stock Interim (Received)` account by default) is credited `$80`." msgstr "" @@ -4880,31 +4886,31 @@ msgstr "" msgid "Debit stock valuation and credit stock input 80 dollars." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:355 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:358 msgid "Accounts balanced at received vendor bill" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:357 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:360 msgid "In this example, a company starts with zero units of a product, table, in stock. Then, 8 tables are received from the vendor. When the bill is received from vendor for 8 tables:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:360 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:363 msgid "Use `$80` in the **Stock Input** account to pay the bill. This cancels out and the account now holds `$0`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:362 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:365 msgid "Debit **Stock Input** `$80` (to reconcile this account)." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:363 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:366 msgid "Credit **Accounts payable** `$80`. This account stores the amount the company owes others, so accountants use the amount to write checks to vendors." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:369 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:372 msgid "Once the vendor requests payment, navigate to the :menuselection:`Purchase app --> Orders --> Purchase` and select the :abbr:`PO (Purchase Order)` for 8 tables. Inside the :abbr:`PO (Purchase Order)`, select :guilabel:`Create Bill`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:373 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:376 msgid "Switch to the :guilabel:`Journal Items` tab to view how `$80` is transferred from the holding account, `Stock Interim (Received)` to `Accounts Payable`. :guilabel:`Confirm` the bill to record the payment to the vendor." msgstr "" @@ -4912,19 +4918,19 @@ msgstr "" msgid "Show bill linked to the purchase order for 8 tables." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:382 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:385 msgid "On product delivery" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:384 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:387 msgid "In the :ref:`above example table `, when 10 products are delivered to a customer, the **Stock Input** account is untouched because there are no new products coming in. To put it simply:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:388 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:391 msgid "**Inventory valuation** is credited `$120`. Subtracting from inventory valuation represents `$120` worth of products exiting the company." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:390 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:393 msgid "Debit **Accounts Receivable** to record revenue from the sale." msgstr "" @@ -4932,39 +4938,39 @@ msgstr "" msgid "Show journal items linked to sale order." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:398 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:401 msgid "In the accounting journal entry invoicing a customer for 10 tables, the accounts **Product Sales**, **Tax Received**, and **Accounts Receivable** all pertain to the sale of the product. **Accounts Receivable** is the account where the customer payment will be received." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:402 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:405 msgid "Anglo-Saxon accounting recognizes the cost of goods sold (COGS) once the sale is made. So, up until the product is sold, scrapped, or returned, costs of keeping the product in stock are not accounted for. The **Expense** account is debited `$120` to log the costs of storing 10 tables during this period of time." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:408 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:411 msgid "On product return" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:410 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:413 msgid "In the :ref:`above example table `, when returning 1 product to a vendor purchased at `$10`, a company expects `$10` in the **Accounts Payable** account from the vendor. However, **Stock Input** account must be debited `$12` because the average cost is `$12` at the time of the return. The missing `$2` is accounted for in the :guilabel:`Price Difference Account`, which is set up in the product's :guilabel:`Product Category`." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:417 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:420 msgid "Behavior of *price difference accounts* varies from localization. In this case, the account is intended to store differences between vendor price and *automated* inventory valuation methods." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:420 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:423 msgid "Summary:" msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:422 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:425 msgid "Debit **Stock Input** account `$10` to move the table from stock to stock input. This move is to indicate that the table is to be processed for an outgoing shipment." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:424 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:427 msgid "Debit **Stock Input** an additional `$2` to account for the **Price Difference**." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:425 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:428 msgid "Credit **Stock Valuation** `$12` because the item is leaving the stock." msgstr "" @@ -4972,15 +4978,15 @@ msgstr "" msgid "2 dollar difference expensed in Price Difference account." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:431 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:434 msgid "Once the vendor's refund is received," msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:433 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:436 msgid "Credit **Stock Input** account `$10` to reconcile the price of the table." msgstr "" -#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:434 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:437 msgid "Debit **Accounts Payable** `$10` to have the accountants collect and register the payment in their journal." msgstr "" @@ -4992,7 +4998,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:79 #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:17 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:146 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:208 #: ../../content/applications/finance/fiscal_localizations/chile.rst:361 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:258 @@ -5523,6 +5529,7 @@ msgid "Partial payment 2/2" msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:422 msgid "30" msgstr "" @@ -5701,7 +5708,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:99 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:254 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:159 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:221 #: ../../content/applications/finance/fiscal_localizations/chile.rst:278 #: ../../content/applications/finance/fiscal_localizations/france.rst:194 #: ../../content/applications/finance/fiscal_localizations/india.rst:101 @@ -5811,6 +5818,7 @@ msgid "VAT units tab" msgstr "" #: ../../content/applications/finance/accounting/get_started/vat_units.rst:45 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:339 msgid "Fiscal position" msgstr "" @@ -8418,6 +8426,7 @@ msgid "You can find additional information about VAT and its mechanism on this p msgstr "" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:20 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:233 #: ../../content/applications/finance/accounting/vendor_bills/assets.rst:32 msgid "Prerequisites" msgstr "" @@ -8522,6 +8531,7 @@ msgid ":doc:`../taxes`" msgstr "" #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:122 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:150 msgid ":doc:`../get_started`" msgstr "" @@ -8678,10 +8688,10 @@ msgid "To allocate the current year's earnings, create a miscellaneous entry to msgstr "" #: ../../content/applications/finance/accounting/reporting/year_end.rst:105 -msgid "Setting an :guilabel:`All Users Lock Date` is **irreversible** and cannot be removed." +msgid "Install the :guilabel:`Irreversible Lock Date` (`account_lock`) module to make the :guilabel:`All Users Lock Date` *irreversible* once set." msgstr "" -#: ../../content/applications/finance/accounting/reporting/year_end.rst:108 +#: ../../content/applications/finance/accounting/reporting/year_end.rst:109 msgid "A specific year-end closing entry is **optional** in order to close out the **profit and loss statement**. The reports are created in real-time, meaning that the profit and loss statement corresponds directly with the year-end date specified in Odoo. Therefore, any time the **income statement** is generated, the beginning date corresponds with the beginning of the **fiscal year** and all account balances should equal zero." msgstr "" @@ -8742,7 +8752,7 @@ msgid "The **tax name** is displayed for backend users in the :guilabel:`Taxes` msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:73 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:306 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:386 msgid "Tax computation" msgstr "" @@ -8796,6 +8806,7 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:109 #: ../../content/applications/finance/accounting/taxes.rst:124 #: ../../content/applications/finance/accounting/taxes.rst:268 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:397 msgid "Total" msgstr "" @@ -9312,90 +9323,1182 @@ msgstr "" msgid "Note that this is error prone: if you set a fiscal position with tax included in prices but use a pricelist that is not included, you might have wrong prices calculated for you. That's why we usually recommend companies to only work with one price reference." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:3 -msgid "Avatax integration" -msgstr "" - #: ../../content/applications/finance/accounting/taxes/avatax.rst:5 -msgid "Avatax is a tax calculation provider that can be integrated in Odoo." +msgid "AvaTax integration" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:10 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:98 -msgid "Credential configuration" +#: ../../content/applications/finance/accounting/taxes/avatax.rst:7 +msgid "Avalara's *AvaTax* is a cloud-based tax software. Integrating *AvaTax* with Odoo provides real-time and region-specific tax calculations when users sell, purchase, and invoice items in Odoo. *AvaTax* tax calculation is supported with every United Nations charted country, including inter-border transactions." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:12 -msgid "To integrate Avatax with Odoo, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes` and add your Avatax credentials in the :guilabel:`Avatax` section." +#: ../../content/applications/finance/accounting/taxes/avatax.rst:13 +msgid "*AvaTax* is only available for integration with databases/companies that have locations in the United States, Canada, and Brazil. This means the fiscal position/country of a database can only be set to the United States, Canada, or Brazil. For more information, reference this documentation: :ref:`avatax/fiscal_country`." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:16 -msgid "If you do not yet have credentials, click on :guilabel:`How to Get Credentials`." -msgstr "" - -#: ../../content/applications/finance/accounting/taxes/avatax.rst:-1 -msgid "Configure Avatax settings" +#: ../../content/applications/finance/accounting/taxes/avatax.rst:18 +msgid "*AvaTax* accounts for location-based tax rates for each state, county, and city. It improves remittance accuracy by paying close attention to laws, rules, jurisdiction boundaries, and special circumstances (like, tax holidays, and product exemptions). Companies who integrate with *AvaTax* can maintain control of tax-calculations in-house with this simple :abbr:`API (application programming interface)` integration." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:25 -msgid "Tax mapping" +msgid "Some limitations exist in Odoo while using *AvaTax* for tax calculation:" msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:27 -msgid "The Avatax integration is available on Sale Orders and Invoices with the included Avatax fiscal position." +msgid "*AvaTax* is **not** supported in Odoo's *Point of Sale* app, because a dynamic tax calculation model is excessive for transactions within a single delivery address, such as stores or restaurants." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:30 -msgid "Before using the integration, specify an :guilabel:`Avatax Category` on the product categories." +msgid "*AvaTax* and Odoo use the company address and **not** the warehouse address." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:31 +msgid "Exercise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other specific industries." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:35 +msgid "Avalara's support documents: `About AvaTax `_" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:39 +msgid "Set up on AvaTax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:41 +msgid "To use *AvaTax*, an account with Avalara is required for the setup. If one has not been set up yet, connect with Avalara to purchase a license: `Avalara: Let's Talk `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:46 +msgid "Upon account setup, take note of the *AvaTax* :guilabel:`Account ID`. This will be needed in the :ref:`Odoo setup `. In Odoo, this number is the :guilabel:`API ID`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:49 +msgid "Then, `create a basic company profile `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:53 +msgid "Create basic company profile" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:55 +msgid "Collect essential business details for the next step: locations where tax is collected, products/services sold (and their sales locations), and customer tax exemptions, if applicable. Follow the Avalara documentation for creating a basic company profile:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:59 +msgid "`Add company information `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:61 +msgid "`Tell us where the company collects and pays tax `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:63 +msgid "`Verify jurisdictions and activate the company `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:65 +msgid "`Add other company locations for location-based filing `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:67 +msgid "`Add a marketplace to the company profile `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:73 +msgid "Connect to AvaTax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:75 +msgid "After creating the basic company profile in Avalara, connect to *AvaTax*. This step links Odoo and *AvaTax* bidirectionally." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:78 +msgid "Navigate to either Avalara's `sandbox `_ or `production `_ environment. This will depend on which type of Avalara account the company would like to integrate." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:83 +msgid "`Sandbox vs production environments in Avalara `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:86 +msgid "Log in to create the :guilabel:`License Key`. Go to :menuselection:`Settings --> License and API Keys`. Click :guilabel:`Generate License Key`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:90 +msgid "A warning appears stating: `If your business app is connected to Avalara solutions, the connection will be broken until you update the app with the new license key. This action cannot be undone.`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:94 +msgid "Generating a new license key breaks the connection with existing business apps using the *AvaTax* integration. Make sure to update these apps with the new license key." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:97 +msgid "If this will be the first :abbr:`API (application programming interface)` integration being made with *AvaTax* and Odoo, then click :guilabel:`Generate license key`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:100 +msgid "If this is an additional license key, ensure the previous connection can be broken. There is **only** one license key associated with each of the Avalara sandbox and production accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:104 +msgid "Copy this key to a safe place. It is **strongly encouraged** to backup the license key for future reference. This key cannot be retrieved after leaving this screen." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:108 +msgid "Odoo configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:110 +msgid "Before using *AvaTax*, there are some additional configurations in Odoo to ensure tax calculations are made accurately." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:113 +msgid "Verify that the Odoo database contains necessary data. The country initially set up in the database determines the fiscal position, and aids *AvaTax* in calculating accurate tax rates." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:119 +msgid "Fiscal country" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:121 +msgid "To set the :guilabel:`Fiscal Country`, navigate to :menuselection:`Accounting app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:127 +msgid "Under the :guilabel:`Taxes` section, set the :guilabel:`Fiscal Country` feature to :guilabel:`United States`, :guilabel:`Canada`, or :guilabel:`Brazil`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:131 +msgid "Company settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:133 +msgid "All companies operating under the Odoo database should have a full and complete address listed in the settings. Navigate to the :menuselection:`Settings app`, and under the :guilabel:`Companies` section, ensure there is only one company operating the Odoo database. Click :guilabel:`Update Info` to open a separate page to update company details." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:138 +msgid "If there are multiple companies operating in the database, click :guilabel:`Manage Companies` to load a list of companies to select from. Update company information by clicking into the specific company." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:142 +msgid "Database administrators should ensure that the :guilabel:`Street...`, :guilabel:`Street2...`, :guilabel:`City`, :guilabel:`State`, :guilabel:`ZIP`, and :guilabel:`Country` are all updated for the companies." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:146 +msgid "This ensures accurate tax calculations and smooth end-of-year accounting operations." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:149 +msgid ":doc:`../../../general/companies`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:153 +msgid "Module installation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:155 +msgid "Next, ensure that the Odoo *AvaTax* module is installed. To do so, navigate to the :menuselection:`Apps application`. In the :guilabel:`Search...` bar, type in `avatax`, and press :kbd:`Enter`. The following results populate:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:163 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:29 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:14 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:40 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:30 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:46 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:14 +#: ../../content/applications/finance/fiscal_localizations/india.rst:16 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:17 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:14 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:15 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:14 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 +msgid "Name" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:164 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:30 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:15 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:41 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:31 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:47 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:15 +#: ../../content/applications/finance/fiscal_localizations/india.rst:17 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:72 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:116 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:15 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:16 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:15 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:165 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:16 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:100 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:16 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:42 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:32 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:16 +#: ../../content/applications/finance/fiscal_localizations/india.rst:18 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:19 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:16 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 +msgid "Description" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:166 +msgid ":guilabel:`Avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:167 +msgid "`account_avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:168 +msgid "Default *AvaTax* module. This module adds the base *AvaTax* features for tax calculation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:169 +msgid ":guilabel:`Avatax for geo localization`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:170 +msgid "`account_avatax_geolocalize`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:171 +msgid "This module includes the features required for integration of *AvaTax* into geo-localization in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:173 +msgid ":guilabel:`Avatax for SO`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:174 +msgid "`account_avatax_sale`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:175 +msgid "Includes the information needed for tax calculation on sales orders in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:176 +msgid ":guilabel:`Avatax for Inventory`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:177 +msgid "`account_avatax_stock`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:178 +msgid "Includes tax calculation in Odoo Inventory." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:179 +msgid ":guilabel:`Amazon/Avatax Bridge`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:180 +msgid "`sale_amazon_avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:181 +msgid "Includes tax calculation features between the *Amazon Connector* and Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:182 +msgid ":guilabel:`Avatax Brazil`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:183 +msgid "`l10n_br_avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:184 +msgid "Includes information for tax calculation in the Brazil localization." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:185 +msgid ":guilabel:`Avatax Brazil for Services`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:186 +msgid "`l10n_br_avatax_services`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:187 +msgid "This module includes the required features for tax calculation for services in the Brazil localization." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:189 +msgid ":guilabel:`Avatax Brazil Sale for Services`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:190 +msgid "`l10n_br_edi_sale_services`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:191 +msgid "This module includes the required features for tax calculation for the sale of services in the Brazil localization. This includes electronic data interchange (EDI)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:193 +msgid ":guilabel:`Test SOs for the Brazilian AvaTax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:194 +msgid "`l10n_br_test_avatax_sale`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:195 +msgid "This module includes the required features for test sales orders in the Brazil localization." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:197 +msgid "Click the :guilabel:`Install` button on the module labeled, :guilabel:`Avatax`: `account_avatax`. Doing so installs the following modules:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:200 +msgid ":guilabel:`Avatax`: `account_avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:201 +msgid ":guilabel:`Avatax for SO`: `account_avatax_sale`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:202 +msgid ":guilabel:`Avatax for Inventory`: `account_avatax_stock`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:204 +msgid "Should *AvaTax* be needed for geo-localization, or with the *Amazon Connector*, then install those modules individually by clicking on :guilabel:`Install` on :guilabel:`Avatax for geo localization` and :guilabel:`Amazon/Avatax Bridge`, respectively." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:209 +msgid "For localization specific *AvaTax* instructions, view the following :doc:`fiscal localization <../../fiscal_localizations>` documentation:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:212 +msgid ":doc:`../../fiscal_localizations/brazil`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:217 +msgid "Odoo AvaTax settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:219 +msgid "To integrate the *AvaTax* :abbr:`API (application programming interface)` with Odoo, go to :menuselection:`Accounting app --> Configuration --> Settings` section. The :guilabel:`AvaTax` fields in the :guilabel:`Taxes` section is where the *AvaTax* configurations are made, and the credentials are entered in." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:224 +msgid "First, tick the checkbox to the left of the :guilabel:`AvaTax` settings, to activate *AvaTax* on the database. This is a quick, convenient way to activate and deactivate *AvaTax* tax calculation on the Odoo database." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:-1 -msgid "Specify Avatax Category on products" +msgid "Configure AvaTax settings" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:36 -msgid "Avatax Categories may be overridden or set on individual products as well." +#: ../../content/applications/finance/accounting/taxes/avatax.rst:235 +msgid "First, select the :guilabel:`Environment` in which the company wishes to use *AvaTax* in. It can either be :guilabel:`Sandbox` or :guilabel:`Production`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:239 +msgid "For help determining which *AvaTax* environment to use (either :guilabel:`Production` or :guilabel:`Sandbox`), visit: `Sandbox vs Production environments `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:244 +msgid "Credentials" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:246 +msgid "Now, the credentials can be entered in. The *AvaTax* :guilabel:`Account ID` should be entered in the :guilabel:`API ID` field, and the :guilabel:`License Key` should be entered in the :guilabel:`API Key` field." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:251 +msgid "The :guilabel:`Account ID` can be found by logging into the *AvaTax* portal (`sandbox `_ or `production `_). In the upper-right corner, click on the initials of the user and :guilabel:`Account`. The :guilabel:`Account ID` is listed first." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:256 +msgid "To access the :guilabel:`License Key` see this documentation: :ref:`avatax/create_avalara_credentials`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:259 +msgid "For the :guilabel:`Company Code` field, enter the Avalara company code for the company being configured. Avalara interprets this as `DEFAULT`, if it is not set. The :guilabel:`Company Code` can be accessed in the Avalara management portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:263 +msgid "First, log into the *AvaTax* portal (`sandbox `_ or `production `_). Then, navigate to :menuselection:`Settings --> Manage Companies`. The :guilabel:`Company Code` value is located in the row of the :guilabel:`Company` in the :guilabel:`Company Code` column." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:-1 -msgid "Override product categories as needed" +msgid "AvaTax company code highlighted on the company details page." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:45 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:273 +msgid "Transaction options" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:275 +msgid "There are two transactional settings in the Odoo *AvaTax* settings that can be configured: :guilabel:`Use UPC` and :guilabel:`Commit Transactions`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:278 +msgid "If the checkbox next to :guilabel:`Use UPC` is ticked, the transactions will use Universal Product Codes (UPC), instead of custom defined codes in Avalara. Consult a certified public accountant (CPA) for specific guidance." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:282 +msgid "Should the :guilabel:`Commit Transactions` checkbox be ticked, then, the transactions in the Odoo database will be committed for reporting in *AvaTax*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:286 msgid "Address validation" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:47 -msgid "Manually validate customer addresses by clicking the :guilabel:`Validate address` link in the customer form view." +#: ../../content/applications/finance/accounting/taxes/avatax.rst:288 +msgid "The *Address Validation* feature ensures that the most up-to-date address by postal standards is set on a contact in Odoo. This is important to provide accurate tax calculations for customers." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:292 +msgid "The :guilabel:`Address Validation` feature only works with partners/customers in North America." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:294 +msgid "Additionally, tick the checkbox next to the :guilabel:`Address validation` field." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:297 +msgid "For accurate tax calculations, it is best practice to enter a complete address for the contacts saved in the database. However, *AvaTax* can still function by implementing a best effort attempt using only the :guilabel:`Country`, :guilabel:`State`, and :guilabel:`Zip code`. These are the three minimum required fields." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:302 +msgid ":guilabel:`Save` the settings to implement the configuration." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:305 +msgid "Manually :guilabel:`Validate` the address by navigating to the :menuselection:`Contacts app`, and selecting a contact. Now that the *AvaTax* module has been configured on the database, a :guilabel:`Validate` button appears directly below the :guilabel:`Address`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:309 +msgid "Click :guilabel:`Validate`, and a pop-up window appears with a :guilabel:`Validated Address` and :guilabel:`Original Address` listed. If the :guilabel:`Validated Address` is the correct mailing address for tax purposes, click :guilabel:`Save Validated`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:0 +msgid "Validate address pop-up window in Odoo with \"Save Validated\" button and \"Validated\n" +"Address\" highlighted." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:319 +msgid "All previously-entered addresses for contacts in the Odoo database will need to be validated using the manually validate process outlined above. Addresses are not automatically validated if they were entered previously. This only occurs upon tax calculation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:324 +msgid "Test connection" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:326 +msgid "After entering all the above information into the *AvaTax* setup on Odoo, click :guilabel:`Test connection`. This ensures the :guilabel:`API ID` and :guilabel:`API KEY` are correct, and a connection is made between Odoo and the *AvaTax* application programming interface (API)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:331 +msgid "Sync parameters" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:333 +msgid "Upon finishing the configuration and settings of the *AvaTax* section, click the :guilabel:`Sync Parameters` button. This action synchronizes the exemption codes from *AvaTax*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:341 +msgid "Next, navigate to :menuselection:`Accounting app --> Configuration --> Accounting: Fiscal Positions`. A :guilabel:`Fiscal Position` is listed named, :guilabel:`Automatic Tax Mapping (AvaTax)`. Click it to open *AvaTax's* fiscal position configuration page." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:345 +msgid "Here, ensure that the :guilabel:`Use AvaTax API` checkbox is ticked." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:347 +msgid "Optionally, tick the checkbox next to the field labeled: :guilabel:`Detect Automatically`. Should this option be ticked, then, Odoo will automatically apply this :guilabel:`Fiscal Position` for transactions in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:351 +msgid "Enabling :guilabel:`Detect Automatically` also makes specific parameters, such as :guilabel:`VAT required`, :guilabel:`Foreign Tax ID`, :guilabel:`Country Group`, :guilabel:`Country`, :guilabel:`Federal States`, or :guilabel:`Zip Range` appear. Filling these parameters filters the :guilabel:`Fiscal Position` usage. Leaving them blank ensures all calculations are made using this :guilabel:`Fiscal Position`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:358 +msgid "Should the :guilabel:`Detect Automatically` checkbox not be ticked, each customer will need to have the :guilabel:`Fiscal Position` set on their :guilabel:`Sales and Purchase` tab of the contact record. To do so, navigate to :menuselection:`Sales app --> Order --> Customers`, or :menuselection:`Contacts app --> Contacts`. Then, select a customer or contact to set the fiscal position on." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:364 +msgid "Navigate to the :guilabel:`Sales and Purchase` tab, and down to the section labeled, :guilabel:`Fiscal Position`. Set the :guilabel:`Fiscal Position` field to the fiscal position for the customer." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:369 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:430 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:39 +msgid ":doc:`fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:372 +msgid "AvaTax accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:374 +msgid "Upon selecting the checkbox option for :guilabel:`Use AvaTax API` a new :guilabel:`AvaTax` tab appears. Click into this tab to reveal two different settings." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:377 +msgid "The first setting is the :guilabel:`AvaTax Invoice Account`, while the second is, :guilabel:`AvaTax Refund Account`. Ensure both accounts are set for smooth end-of-year record keeping. Consult a certified public accountant (CPA) for specific guidance on setting both accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:381 +msgid "Click :guilabel:`Save` to implement the changes." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:384 +msgid "Tax mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:386 +msgid "The *AvaTax* integration is available on sale orders and invoices with the included *AvaTax* fiscal position." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:390 +msgid "Additionally, there is a :guilabel:`Tax Mapping` tab and :guilabel:`Account Mapping` tab in the :guilabel:`Automatic Tax Mapping (AvaTax)` fiscal position, where mapping for products can also be configured. To access :guilabel:`Fiscal Positions` navigate to :menuselection:`Accounting app --> Configuration --> Accounting: Fiscal Positions`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:396 +msgid "Product category mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:398 +msgid "Before using the integration, specify an :guilabel:`Avatax Category` on the product categories. Navigate to :menuselection:`Inventory app --> Configuration --> Product Categories`. Select the product category to add the :guilabel:`AvaTax Category` to. In the :guilabel:`AvaTax Category` field, select a category from the drop-down menu, or :guilabel:`Search More...` to open the complete list of options." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:-1 -msgid "Validate customer addresses" +msgid "Specify AvaTax Category on products." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:54 -msgid "If preferred, choose to keep the newly validated address or the original address in the wizard that pops up." +#: ../../content/applications/finance/accounting/taxes/avatax.rst:409 +msgid "Product mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:411 +msgid "*AvaTax* Categories may be set on individual products, as well. To set the :guilabel:`Avatax Category` navigate to :menuselection:`Inventory app --> Products --> Products`. Select the product to add the :guilabel:`Avatax Category` to. Under the :guilabel:`General Information` tab, on the far-right, is a selector field labeled: :guilabel:`Avatax Category`. Finally, click the drop-down menu, and select a category, or :guilabel:`Search More...` to find one that is not listed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:418 +msgid "If both the product, and its category, have an :guilabel:`AvaTax Category` set, the product's :guilabel:`AvaTax Category` takes precedence." msgstr "" #: ../../content/applications/finance/accounting/taxes/avatax.rst:-1 -msgid "Address validation wizard" +msgid "Override product categories as needed." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:64 +#: ../../content/applications/finance/accounting/taxes/avatax.rst:426 +msgid "Mapping an :guilabel:`AvaTax Category` on either the *Product* or *Product Category* should be completed for every *Product* or *Product Category*, depending the route that is chosen." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:431 +msgid ":doc:`avatax/avatax_use`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:432 +msgid ":doc:`avatax/avalara_portal`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:433 +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:258 +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:163 +msgid "`US Tax Compliance: Avatax elearning video `_" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:6 +msgid "Avalara (Avatax) portal" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:8 +msgid "Avalara's (*AvaTax*) management console offers account management options including: viewing/editing the transactions sent from Odoo to *AvaTax*, details on how the taxes are calculated, tax reporting, tax exemption management, and tax return resources." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:13 +msgid "Avalara is the software developer of the tax software, *AvaTax*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:15 +msgid "To access the console, first, navigate to either Avalara's `sandbox `_ or `production `_ environment. This will depend on which type of account was set in the :doc:`integration <../avatax>`. Log in to the management console." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:-1 +msgid "Avalara dashboard after logging into management portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:25 +msgid "For more information see Avalara's documentation: `Activate your Communications Customer Portal account `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:34 +msgid "To access transactions, click in the :guilabel:`Transactions` link on the main dashboard upon logging into the :ref:`avatax/portal`. To manually access the *Transactions* page, while logged into the Avalara console, navigate to :menuselection:`Transactions --> Transactions`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:-1 +msgid "Avalara portal with the transactions shortcut highlighted." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:43 +msgid "Edit transaction" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:45 +msgid "Click into a transaction to reveal more details about the transaction. These details include sections on :guilabel:`Invoice detail`, :guilabel:`Additional info`, and :guilabel:`Customer info`. Click :icon:`fa-pencil` :guilabel:`Edit document details` to make changes to the transaction." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:49 +msgid "A :guilabel:`Discount` can be added to adjust the invoice. This is especially useful in cases where the transaction has already synced with Avalara / *AvaTax*, and changes need to be made afterward." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:55 +msgid "Filter" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:57 +msgid "Filter transactions on the :guilabel:`Transactions` page, by setting the :guilabel:`From` and :guilabel:`To` fields, and configuring other fields to filter by, including:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:60 +msgid ":guilabel:`Document Status`: any of the following options, :guilabel:`All`, :guilabel:`Voided`, :guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:62 +msgid ":guilabel:`Document Code`: any of the following options, :guilabel:`Exactly match`, :guilabel:`Starts with`, or :guilabel:`Contains`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:64 +msgid ":guilabel:`Customer/Vendor Code`: the customer/vendor code in Odoo (e.g. `Contact18`)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:65 +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:108 +msgid ":guilabel:`Country`: the country this tax was calculated in; this is a text field." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:66 +msgid ":guilabel:`Region`: the region of the country, which varies based on the :guilabel:`Country` selection." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:69 +msgid "Click :icon:`fa-plus` :guilabel:`Filters` to access the following filter conditions:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:71 +msgid ":guilabel:`Document Type`: any of the following selections, :guilabel:`All`, :guilabel:`Sales Invoice`, :guilabel:`Purchase Invoice`, :guilabel:`Return Invoice`, :guilabel:`Inventory Transfer Inbound Invoice`, :guilabel:`Inventory Transfer Outbound Invoice`, or :guilabel:`Customs Invoice`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:75 +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:118 +msgid ":guilabel:`Import ID`: represents the import ID of the document." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:78 +msgid "Sort by" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:80 +msgid "On the :guilabel:`Transactions` page, transactions will be listed below, according to the set :ref:`avalara/portal-filter`, located in the top half of the page. The following columns are available by default, to sort by ascending or descending order:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:84 +msgid ":guilabel:`Doc Code`: either of the following options, :guilabel:`Exactly match`, :guilabel:`Starts with`, or :guilabel:`Contains`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:86 +msgid ":guilabel:`Doc Status`: either of the following options, :guilabel:`All`, :guilabel:`Voided`, :guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:88 +msgid ":guilabel:`Cust/Vendor Code` : this is the customer/vendor code in Odoo (e.g. Contact18)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:89 +msgid ":guilabel:`Region`: this is the region of the country, this will vary based on the :guilabel:`Country` selection." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:91 +msgid ":guilabel:`Amount`: the numeric amount of the total amount on the Odoo document." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:92 +msgid ":guilabel:`Tax`: the numeric amount of the tax applied to the total." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:-1 +msgid "Transactions page on the Avalara portal with the filter and sort-by options highlighted." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:99 +msgid "Customize columns" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:101 +msgid "Additional columns can be added by clicking the :icon:`fa-cog` :guilabel:`Customize columns`. On the resulting popover window, click the drop-down menu for the :guilabel:`column` that should be changed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:105 +msgid "The following columns can be added for additional transactional information:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:107 +msgid ":guilabel:`AvaTax calculated`: the amount of tax calculated by *AvaTax*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:109 +msgid ":guilabel:`Cust/vendor code`: the customer/vendor code in Odoo (e.g. `Contact18`)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:110 +msgid ":guilabel:`Currency`: the standardized abbreviation for the currency the amount total is in." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:111 +msgid ":guilabel:`Doc date`: the document's date of creation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:112 +msgid ":guilabel:`Doc status`: any of the following options, :guilabel:`All`, :guilabel:`Voided`, :guilabel:`Committed`, :guilabel:`Uncommitted`, or :guilabel:`Locked`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:114 +msgid ":guilabel:`Doc type`: any of the following selections, :guilabel:`All`, :guilabel:`Sales Invoice`, :guilabel:`Purchase Invoice`, :guilabel:`Return Invoice`, :guilabel:`Inventory Transfer Inbound Invoice`, :guilabel:`Inventory Transfer Outbound Invoice`, or :guilabel:`Customs Invoice`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:119 +msgid ":guilabel:`Last modified`: timestamp of the last time the document was modified." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:120 +msgid ":guilabel:`Location code`: the location code used to calculate the tax, based on the delivery address." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:122 +msgid ":guilabel:`PO number`: the purchase order number." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:123 +msgid ":guilabel:`Reference code`: the Odoo reference code (e.g. NV/2024/00003)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:124 +msgid ":guilabel:`Region`: the region of the country,which varies based on the :guilabel:`Country` selection." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:126 +msgid ":guilabel:`Salesperson code`: the numeric ID of the user assigned to the sales order in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:127 +msgid ":guilabel:`Tax date`: the month/day/year of the tax calculation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:128 +msgid ":guilabel:`Tax override type`: where an exemption would appear, should there be none, the field populates with :guilabel:`None`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:131 +msgid "To add a new column click the :icon:`fa-plus` :guilabel:`Column`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:134 +msgid "For more information on *AvaTax* transactions, refer to this Avalara documentation: `Transactions `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:138 +msgid "Import-export" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:140 +msgid "While on the :ref:`avalara/portal-transactions`, click :icon:`fa-download` :guilabel:`Import transactions` or :icon:`fa-upload` :guilabel:`Export transactions` to import or export transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:144 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:52 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1019 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:85 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:42 +msgid "Reports" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:146 +msgid "To access reporting, navigate to the :menuselection:`Reports` link in the top menu of the Avalara management console. Next, select from one of the available reporting tabs: :guilabel:`Transactions reports`, :guilabel:`Liability & tax return reports`, or :guilabel:`Exemption reports`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:151 +msgid "Additionally, there is a :guilabel:`Favorites` tab and :guilabel:`Downloads` tab. The :guilabel:`Favorites` tab contains any favorited report configurations for the Avalara user. The :guilabel:`Downloads` tab contains a list view where the user can download the high-volume transaction reports created in the last 30 days." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:156 +msgid "Make a selection for the :guilabel:`Report Category`, and the :guilabel:`Report Name`, under the :guilabel:`Select a report` section." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:159 +msgid "Next, fill out the :guilabel:`Select report details` section. These options will vary based on the tab selected above." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:162 +msgid "Depending on the report size, the following two options are available in the section labeled, :guilabel:`Select the approximate number of transactions for your report`: :guilabel:`Create and download the report instantly` (for small reports) and :guilabel:`Create and download the report in the background` (for larger reports). Select one or the other depending on the volume of transactions in this report." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:168 +msgid "Finally, under the section labeled, :guilabel:`Report preview and export` make a selection of the file type to download. Either a :guilabel:`.PDF` or :guilabel:`.XLS` can be chosen. Alternatively, the file can be previewed by selecting the :guilabel:`Preview` option." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:172 +msgid "After making all the configurations, click :guilabel:`Create report` to download the report. Click :icon:`fa-star-o` :guilabel:`Make this report a favorite` to save the report configuration to the user's favorites." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:176 +msgid "After the report is created, click :icon:`fa-download` :guilabel:`Download` to download the file to the device." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:180 +msgid "Select a pre-configured report from the :guilabel:`Frequently used reports` section of the reporting dashboard." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:183 +msgid "Access this list by clicking on the :guilabel:`Reports` option in the top menu of the Avalara management console, and scroll to the bottom of the page." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:187 +msgid "`See Avalara's documentation: Reports in AvaTax `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:191 +msgid "Add more jurisdictions" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:193 +msgid "Additional jurisdictions (tax locations) can be added in the Avalara management console. Navigate to either Avalara's `sandbox `_ or `production `_ environment. This will depend on which type of account was set in the :doc:`integration <../avatax>`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:198 +msgid "Next, navigate to :menuselection:`Settings --> Where you collect tax`. Choose between the three different tabs, depending on the business need. The first tab is :guilabel:`Sales and use tax`, where tax can be collected for the United States. Click the :icon:`fa-plus` :guilabel:`Add to where you collect sales and use tax` to add another location where the company collects sales and use tax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:203 +msgid "The second option, is the :guilabel:`VAT/GST` tab where the :icon:`fa-plus` :guilabel:`Add a country or territory where you collect VAT/GST` can be selected to add another country or territory where the company collects VAT/GST." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:207 +msgid "Finally, on the far-right, is the :guilabel:`Customs duty` tab, where a country can be added where the company collects customs duty. Simply click on the :icon:`fa-plus` :guilabel:`Add a country where you calculate customs duty` icon below the tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:-1 +msgid "AvaTax management console, on the Where you collect tax page, with the add button and\n" +"sales and use tax tab highlighted." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:217 +msgid "`See Avalara's documentation: Add local jurisdiction taxes `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:221 +msgid "Tax exemption certificate" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:223 +msgid "Tax exemption certificates for customers can be added into the Avalara management console, so that *AvaTax* is aware of which customers may be exempt from paying certain taxes. To add an *exception certificate* navigate to :menuselection:`Exemptions --> Customer certificates`. From there, click on the :icon:`fa-plus` :guilabel:`Add a certificate` to configure an exemption." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:229 +msgid "An Avalara subscription to Exemption Certificate Management (ECM) is required in order to attach certificate images, and to be ready for an audit. For more on subscribing to this add-on, visit `Avalara `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:235 +msgid "End-of-year operations" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:237 +msgid "Avalara's services include tax return services, for when it is time to file taxes at the end of the year. To access Avalara's tax services log, into the `management portal `_. Then, from the main dashboard, click :guilabel:`Returns`. Avalara will prompt the Avalara user to log in for security purposes, and redirect the user to the *Returns* portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:-1 +msgid "Avalara portal with the returns shortcut highlighted." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:247 +msgid "Click :guilabel:`Get started` to begin the tax return process. For more information, refer to this Avalara documentation: `About Managed Returns `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:252 +msgid "Alternatively, click on the :menuselection:`Returns` button in the top menu of the Avalara management console." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:256 +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:161 +msgid ":doc:`../avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avalara_portal.rst:257 +msgid ":doc:`avatax_use`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:3 +msgid "AvaTax use" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:5 +msgid "AvaTax is a tax calculation software that can be integrated with Odoo in the United States and Canada. Once the :doc:`integration setup <../avatax>` is complete, the calculated tax is simple and automatic." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:10 msgid "Tax calculation" msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:66 -msgid "Automatically calculate taxes on Odoo quotations and invoices with Avatax by confirming the documents. Alternatively, calculate the taxes manually by clicking the :guilabel:`Compute taxes using Avatax` button while these documents are in draft mode." +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:12 +msgid "Automatically calculate taxes on Odoo quotations and invoices with AvaTax by confirming the documents during the sales flow. Alternatively, calculate the taxes manually by clicking the :guilabel:`Compute Taxes` button, while these documents are in draft stage." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:70 -msgid "Use the :guilabel:`Avalara Code` field that's available on customers, quotations, and invoices to cross-reference data in Odoo and Avatax." +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:17 +msgid "Clicking the :guilabel:`Compute Taxes` button recalculates taxes, if any product lines are edited on the invoice." msgstr "" -#: ../../content/applications/finance/accounting/taxes/avatax.rst:74 -#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:39 -msgid ":doc:`fiscal_positions`" +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:-1 +msgid "Sales quotation with the confirm and compute taxes button highlighted." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:24 +msgid "The tax calculation is triggered during the following :ref:`automatic trigger ` and :ref:`manual trigger ` circumstances." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:30 +msgid "Automatic triggers" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:32 +msgid "When the sales rep sends the quote by email with :guilabel:`Send by email` button (pop-up)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:33 +msgid "When the customer views the online quote on the portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:34 +msgid "When a quote is confirmed and becomes a sales order." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:35 +msgid "When the customer views the invoice on the portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:36 +msgid "When a draft invoice is validated." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:37 +msgid "When the customer views the subscription in the portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:38 +msgid "When a subscription generates an invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:39 +msgid "When the customer gets to the last screen of the eCommerce checkout." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:44 +msgid "Manual triggers" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:46 +msgid ":guilabel:`Compute Taxes` button at the bottom of the quote." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:47 +msgid ":guilabel:`Compute Taxes` button at the top of the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:49 +msgid "Use each of these buttons to manually re-calculate the sales tax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:52 +msgid "Use the :guilabel:`Avalara Partner Code` field that is available on customer records, quotations, and invoices to cross-reference data in Odoo and AvaTax. This field is located under the :menuselection:`Other info` tab of the sales order or quotation in the :guilabel:`Sales` section." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:56 +msgid "On the customer record, navigate to *Contacts app* and select a contact. Then open the :guilabel:`Sales & Purchase` tab and the :guilabel:`Avalara Partner Code` under the :guilabel:`Sales` section." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:61 +msgid "The :guilabel:`Automatic Tax Mapping (AvaTax)` fiscal position is also applied on those Odoo documents, like subscriptions." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:65 +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:165 +msgid ":doc:`../fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:68 +msgid "AvaTax synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:70 +msgid "Synchronization occurs with AvaTax, when the *invoice* is created in Odoo. This means the sales tax is recorded with Avalara (AvaTax software developer)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:73 +msgid "To do so, navigate to :menuselection:`Sales app --> Orders --> Quotations`. Select a quotation from the list." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:76 +msgid "After confirming a quotation and validating the delivery, click :guilabel:`Create Invoice`. Indicate whether it is a :guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)`, or :guilabel:`Down payment (fixed amount)`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:80 +msgid "Then click :guilabel:`Create and view invoice`. The recorded taxes can be seen in the :guilabel:`Journal Items` tab of the invoice. There will be different taxes depending on the location of the :guilabel:`Delivery Address`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:-1 +msgid "Journal items highlighted on a invoice in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:88 +msgid "Finally, press the :guilabel:`Confirm` button to complete the invoice and synchronize with the AvaTax portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:92 +msgid "An invoice cannot be :guilabel:`Reset to draft` because this causes de-synchronization with the AvaTax Portal. Instead, click :guilabel:`Add credit note` and state: `Sync with AvaTax Portal`. See this documentation: :doc:`../../../accounting/customer_invoices/credit_notes`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:97 +msgid "Fixed price discounts" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:99 +msgid "Add a fixed price discount to a valuable customer, by clicking :guilabel:`Add a line` on the customer's invoice. Add the product discount, and set the :guilabel:`Price` to either a positive or negative value. To recalculate the taxes, click :guilabel:`Compute Taxes`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:104 +msgid "Tax calculation can even be done on negative subtotals and credit notes." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:107 +msgid "Logging" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:109 +msgid "It is possible to log Avalara/*AvaTax* actions in Odoo for further analysis, or verification of functionality. Logging is accessible through the *AvaTax* settings." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:112 +msgid "To start logging *AvaTax* actions, first, navigate to the :menuselection:`Accounting app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:115 +msgid "Then, in the :guilabel:`Taxes` section, under the :guilabel:`AvaTax` settings, click :guilabel:`Start logging for 30 minutes`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:118 +msgid "Upon starting the log process, Odoo will log all Avalara/*AvaTax* actions performed in the database." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:120 +msgid "To view the logs, click on :guilabel:`Show logs` to the right of the :guilabel:`Start logging for 30 minutes`. This reveals a detailed list of Avalara/*AvaTax* actions. This list is sortable by the following columns:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:124 +msgid ":guilabel:`Created on`: timestamp of the *AvaTax* calculation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:125 +msgid ":guilabel:`Created by`: numeric value of the user in the database." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:126 +msgid ":guilabel:`Database name`: name of the database." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:127 +msgid ":guilabel:`Type`: two values can be chosen for this field, :guilabel:`Server` or :guilabel:`Client`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:129 +msgid ":guilabel:`Name`: Avalara service name. In this case, it will be *AvaTax*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:130 +msgid ":guilabel:`Level`: by default, this will be `INFO`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:131 +msgid ":guilabel:`Path`: indicates the path taken to make the calculation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:132 +msgid ":guilabel:`Line`: indicates the line the calculation is made on." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:133 +msgid ":guilabel:`Function`: indicates the calculation taken on the line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:-1 +msgid "Avalara logging page with top row of list highlighted." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:139 +msgid "Click into the log line to reveal another field, called :guilabel:`Message`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:141 +msgid "This field populates a raw transcription of the transaction, which involves the creation (or adjustment) of a sales invoice using the Avalara *AvaTax* API." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:144 +msgid "The transaction includes details, such as addresses for shipping from and to, line items describing the products or services, tax codes, tax amounts, and other relevant information." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:147 +msgid "The :guilabel:`Message` contains the calculated taxes for different jurisdictions and confirms the creation (or adjustment) of the transaction." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:151 +msgid "Custom fields can be made using Odoo *Studio*. Click the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` menu to the far-right of the header row. Then click :icon:`fa-plus` :guilabel:`Add custom field`. This action opens Odoo *Studio*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:156 +msgid "Odoo *Studio* requires a *custom* pricing plan. Consult the database's customer success manager for more information on switching plans. Or to see if Odoo *Studio* is included in the database's current pricing plan. See this documentation: :doc:`../../../../studio`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax/avatax_use.rst:162 +msgid ":doc:`avalara_portal`" msgstr "" #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:3 @@ -9559,13 +10662,6 @@ msgstr "" msgid "The :abbr:`OSS (One-Stop Shop)` system introduced by the European Union simplifies VAT collection for **cross-border** sales of goods and services. It primarily applies to business-to-consumer **(B2C)** cases. With the OSS, businesses can register for VAT in their home country and use a single online portal to handle VAT obligations for their sales within the EU. There are **two primary schemes**: the **Union OSS** scheme for cross-border services and the **Import OSS** scheme for goods valued at or below €150." msgstr "" -#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:52 -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1019 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:85 -#: ../../content/applications/finance/fiscal_localizations/spain.rst:42 -msgid "Reports" -msgstr "" - #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:54 msgid "To generate **OSS sales** or **OSS imports** reports and submit them onto the OSS portal, go to :menuselection:`Accounting --> Reporting --> Tax Report`, click :guilabel:`Report: Generic Tax report`, and select either :guilabel:`OSS Sales` or :guilabel:`OSS Imports`. Once selected, click on :guilabel:`PDF`, :guilabel:`XLSX`, or :guilabel:`XML` in the top-left corner. This generates the currently-opened report in the selected format. Once generated, log into the platform of your competent federal authority to submit it onto the OSS portal." msgstr "" @@ -9804,7 +10900,7 @@ msgstr "" #: ../../content/applications/finance/accounting/vendor_bills.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:592 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:463 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:570 #: ../../content/applications/finance/fiscal_localizations/chile.rst:700 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:710 #: ../../content/applications/finance/fiscal_localizations/italy.rst:119 @@ -11492,6 +12588,7 @@ msgid "`Smart Tutorial - Localización de Argentina ` the following modules to get all the features of the Argentinean localization:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:29 -#: ../../content/applications/finance/fiscal_localizations/austria.rst:14 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:30 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:46 -#: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 -#: ../../content/applications/finance/fiscal_localizations/france.rst:182 -#: ../../content/applications/finance/fiscal_localizations/india.rst:16 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:17 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 -#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 -#: ../../content/applications/finance/fiscal_localizations/romania.rst:14 -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:15 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:14 -#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 -msgid "Name" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:30 -#: ../../content/applications/finance/fiscal_localizations/austria.rst:15 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:31 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:47 -#: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 -#: ../../content/applications/finance/fiscal_localizations/india.rst:17 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:18 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 -#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:72 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:116 -#: ../../content/applications/finance/fiscal_localizations/romania.rst:15 -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:16 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:15 -#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 -msgid "Technical name" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 -#: ../../content/applications/finance/fiscal_localizations/australia.rst:16 -#: ../../content/applications/finance/fiscal_localizations/australia.rst:100 -#: ../../content/applications/finance/fiscal_localizations/austria.rst:16 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:32 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 -#: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 -#: ../../content/applications/finance/fiscal_localizations/france.rst:59 -#: ../../content/applications/finance/fiscal_localizations/india.rst:18 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:19 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 -#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 -#: ../../content/applications/finance/fiscal_localizations/romania.rst:16 -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 -#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 -msgid "Description" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/argentina.rst:32 msgid ":guilabel:`Argentina - Accounting`" msgstr "" @@ -11618,7 +12648,7 @@ msgid "(optional) Allows the user to see Identification Type and AFIP Responsibi msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:52 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:37 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:64 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:87 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 #: ../../content/applications/finance/fiscal_localizations/peru.rst:52 @@ -11659,7 +12689,7 @@ msgid "Select Fiscal Localization Package." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:79 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:143 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:205 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:255 msgid "Configure master data" msgstr "" @@ -12745,7 +13775,7 @@ msgid "Since an online payment needs to be confirmed for the :guilabel:`Automati msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:923 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:212 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:267 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:181 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:270 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 @@ -13742,6 +14772,7 @@ msgid "`Stripe Terminal `_" msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:540 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:93 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 msgid "Payroll" msgstr "" @@ -14063,6 +15094,7 @@ msgid "When satisfied with the payslip, click :guilabel:`Create Draft entry` to msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:781 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:308 msgid "Pay employees" msgstr "" @@ -14207,11 +15239,15 @@ msgstr "" msgid "You can choose any Odoo journal to post the payslip entries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:908 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:906 +msgid "Configure the tax by going to :menuselection:`Accounting --> Configuration --> Taxes`. Create the necessary taxes for the Employment Hero payslip entries. Fill in the tax code from **Employment Hero** in the :guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:911 msgid "How does the API work?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:910 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:913 msgid "The API syncs the journal entries from Employment Hero to Odoo and leaves them in draft mode. The reference includes the Employment Hero payslip entry ID in brackets for the user to easily retrieve the same record in Employment Hero and Odoo." msgstr "" @@ -14219,15 +15255,15 @@ msgstr "" msgid "Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:917 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:920 msgid "By default, the synchronisation happens once per week. You can fetch the records manually by going to :menuselection:`Accounting --> Configuration --> Settings` and, in the :guilabel:`Enable Employment Hero Integration` option, click on :guilabel:`Fetch Payruns Manually`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:921 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:924 msgid "Employment Hero payslip entries also work based on double-entry bookkeeping." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:923 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:926 msgid "The accounts used by Employment Hero are defined in the section :guilabel:`Payroll settings`." msgstr "" @@ -14235,7 +15271,7 @@ msgstr "" msgid "Chart of Accounts menu in Employment Hero" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/australia.rst:928 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:931 msgid "For the API to work, you need to create the same accounts as the default accounts of your Employment Hero business (**same name and same code**) in Odoo. You also need to choose the correct account types in Odoo to generate accurate financial reports." msgstr "" @@ -14348,6 +15384,8 @@ msgid ":guilabel:`Country`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/austria.rst:64 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:85 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:325 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:99 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:292 msgid ":guilabel:`Phone`" @@ -15160,11 +16198,11 @@ msgid "Brazil" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:12 -msgid "With the Brazilian localization, sales taxes can be automatically computed and electronic invoices (NF-e) for goods can be sent using AvaTax (Avalara) through |API| calls. Moreover, taxes for services can be configured." +msgid "With the Brazilian localization, sales taxes can be automatically computed and electronic invoices for goods (NF-e) and services (NFS-e) can be sent using AvaTax (Avalara) through |API| calls. Moreover, taxes for services can be configured." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:16 -msgid "For the goods tax computation and electronic invoicing process, you need to configure the :ref:`contacts `, :ref:`company `, :ref:`products `, and :ref:`create an account in Avatax ` need to be configured in the general settings." +msgid "For the goods and services tax computation and electronic invoicing process, you need to configure the :ref:`contacts `, :ref:`company `, :ref:`products `, and :ref:`create an account in AvaTax ` which needs to be configured in the general settings." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:21 @@ -15175,191 +16213,313 @@ msgstr "" msgid "The localization also includes taxes and a chart of accounts template that can be modified if needed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:30 -msgid "Install the :guilabel:`🇧🇷 Brazil` :ref:`fiscal localization package ` to get all the default accounting features of the Brazilian localization, following the :abbr:`IFRS (International Financial Reporting Standards)` rules." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:33 +msgid ":ref:`Install ` the following modules to get all the features of the Brazilian localization:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:39 -msgid "To configure your company information, go to the :menuselection:`Contacts` app and search the name given to your company." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:43 +msgid ":guilabel:`Brazilian - Accounting`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:42 -msgid "Select the :guilabel:`Company` option at the top of the page. Then, configure the following fields:" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:44 +msgid "`l10n_br`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:45 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:245 -msgid ":guilabel:`Name`." +msgid "Default :ref:`fiscal localization package `, which represents having the Generic Brazilian chart of accounts and Taxes, together with document types and identification types." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:46 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:246 -msgid ":guilabel:`Address` (add :guilabel:`City`, :guilabel:`State`, :guilabel:`Zip Code`, :guilabel:`Country`)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:48 +msgid ":guilabel:`Brazil - Accounting Reports`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:49 -msgid "In the :guilabel:`Street` field, enter the street name, number, and any additional address information." +msgid "`l10n_br_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:50 +msgid "Accounting reports for Brazil." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:51 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:250 -msgid "In the :guilabel:`Street 2` field, enter the neighborhood." +msgid ":guilabel:`AvaTax Brazil` & :guilabel:`AvaTax Brazil for Services`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:52 +msgid "`l10n_br_avatax` & `l10n_br_avatax_services`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:53 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:252 -msgid ":guilabel:`Identification Number` (:guilabel:`CNPJ`, :guilabel:`CPF`)." +msgid "Goods and Services tax computation through Avalara." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:54 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:253 -msgid ":guilabel:`Tax ID` (associated with the identification type)." +msgid ":guilabel:`Brazilian Accounting EDI` & :guilabel:`Brazilian Accounting EDI for services`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:55 -msgid ":guilabel:`IE` (State registration)." +msgid "`l10n_br_edi` & `l10n_br_edi_services`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:56 -msgid ":guilabel:`IM` (Municipal registration)." +msgid "Provides electronic invoicing for goods and services for Brazil through AvaTax." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:57 -msgid ":guilabel:`SUFRAMA code` (Superintendence of the Manaus Free Trade Zone - add if applicable)." +msgid ":guilabel:`Brazil Pix QR codes`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:58 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:257 -msgid ":guilabel:`Phone`." +msgid "`l10n_br_pix`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:59 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:258 -msgid ":guilabel:`Email`." +msgid "Implements Pix QR codes for Brazil." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:66 +msgid "To configure your company information, go to the :menuselection:`Contacts` app and search the name given to your company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:69 +msgid "Select the :guilabel:`Company` option at the top of the page. Then, configure the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:72 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:313 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1096 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:95 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:288 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:73 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:314 +msgid ":guilabel:`Address`: add :guilabel:`City`, :guilabel:`State`, :guilabel:`Zip Code`, :guilabel:`Country`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:76 +msgid "In the :guilabel:`Street` field, enter the street name, number, and any additional address information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:78 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:318 +msgid "In the :guilabel:`Street 2` field, enter the neighborhood." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:80 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:320 +msgid ":guilabel:`Identification Number`: :guilabel:`CNPJ` or :guilabel:`CPF`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:81 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:321 +msgid ":guilabel:`Tax ID`: associated with the identification type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:82 +msgid ":guilabel:`IE`: State registration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:83 +msgid ":guilabel:`IM`: Municipal registration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:84 +msgid ":guilabel:`SUFRAMA code`: Superintendence of the Manaus Free Trade Zone - add if applicable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:86 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:326 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:233 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:100 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:293 +msgid ":guilabel:`Email`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 msgid "Company configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:64 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:91 msgid "Configure the :guilabel:`Fiscal Information` within the :guilabel:`Sales and Purchase` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:66 -msgid "Add the :guilabel:`Fiscal Position` for :ref:`Avatax Brazil `." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:93 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:104 +msgid "Add the :guilabel:`Fiscal Position` for :ref:`AvaTax Brazil `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:67 -msgid ":guilabel:`Tax Regime` (Federal Tax Regime)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:94 +msgid ":guilabel:`Tax Regime`: Federal Tax Regime" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:68 -msgid ":guilabel:`ICMS Taxpayer Type` (indicates ICMS regime, Exempt status, or Non-Taxpayer)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:95 +msgid ":guilabel:`ICMS Taxpayer Type`: indicates :guilabel:`ICMS regime`, :guilabel:`Exempt status`, or :guilabel:`Non-Taxpayer`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:69 -msgid ":guilabel:`Main Activity Sector`." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:97 +msgid ":guilabel:`Main Activity Sector`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 msgid "Company fiscal configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:74 -msgid "Finally, upload a company logo and save the contact" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:102 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:347 +msgid "Configure the following extra :guilabel:`Fiscal Information` if you are going to issue NFS-e:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:77 -msgid "If you are a simplified regime, you need to configure the ICMS rate under :menuselection:`Accounting --> Configuration --> Settings --> Taxes --> Avatax Brazil`." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:105 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:350 +msgid ":guilabel:`COFINS Details`: :guilabel:`Taxable, Not Taxable, Taxable with rate 0%, Exempt, Suspended`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:83 -msgid "Configure AvaTax integration" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:107 +msgid ":guilabel:`PIS Details` :guilabel:`Taxable, Not Taxable, Taxable with rate 0%, Exempt, Suspended`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:85 -msgid "Avalara AvaTax is a tax calculation and electronic invoicing provider that can be integrated in Odoo to automatically compute taxes by taking into account the company, contact (customer), product, and transaction information to retrieve the correct tax to be used and process the e-invoice afterward with the government." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:109 +msgid ":guilabel:`CSLL Taxable` If the company is subject to CSLL or not" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:90 -msgid "Using this integration requires :doc:`In-App-Purchases (IAPs) <../../essentials/in_app_purchase>` to compute the taxes and to send the electronic invoices. Whenever you compute taxes, an |API| call is made using credits from your |IAP| credits balance." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:95 -msgid "Odoo is a certified partner of Avalara Brazil." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:100 -msgid "To activate AvaTax in Odoo, you need to create an account. To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, and in the :guilabel:`AvaTax Brazil` section, add the administration email address to be used for the AvaTax portal in the :guilabel:`Avatax Portal Email`, and then click on :guilabel:`Create account`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:106 -msgid "When **testing** an :guilabel:`Avatax Portal Email` integration in a testing or sandbox database, use an alternate email address. It is **not** possible to re-use the same email address on the production database." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:110 -msgid "After you create the account from Odoo, you need to go to the Avalara Portal to set up your password:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:113 -msgid "Access the `Avalara portal `_." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Company fiscal configuration for NFSe." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:114 -msgid "Click on :guilabel:`Meu primeiro acesso`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:115 -msgid "Add the email address you used in Odoo to create the Avalara/Avatax account, and then click :guilabel:`Solicitar Senha`." +msgid "Finally, upload a company logo and save the contact." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:117 +msgid "If you are a simplified regime, you need to configure the ICMS rate under :menuselection:`Accounting --> Configuration --> Settings --> Taxes --> AvaTax Brazil`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:123 +msgid "Configure AvaTax integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:125 +msgid "Avalara AvaTax is a tax calculation and electronic invoicing provider that can be integrated in Odoo to automatically compute taxes by taking into account the company, contact (customer), product, and transaction information to retrieve the correct tax to be used and process the e-invoice afterward with the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:130 +msgid "Using this integration requires :doc:`In-App-Purchases (IAPs) <../../essentials/in_app_purchase>` to compute the taxes and to send the electronic invoices. Whenever you compute taxes, send an electronic document (NF-e, NFS-e, etc), or perform any electronic flow (NF-e Cancellation, Correction letter, Invalidate invoice number range), an API call is made using credits from your `IAP credits balance `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:137 +msgid "Odoo is a certified partner of Avalara Brazil." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:138 +msgid "You can `buy IAP credit on odoo.com `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:141 +msgid "Credential configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:143 +msgid "To activate AvaTax in Odoo, you need to create an account. To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, and in the :guilabel:`AvaTax Brazil` section, add the administration email address to be used for the AvaTax portal in the :guilabel:`AvaTax Portal Email`, and then click on :guilabel:`Create account`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:149 +msgid "When **testing** or **creating a production** :guilabel:`AvaTax Portal Email` integration in a sandbox or production database, use a real email address, as it is needed to log in to the Avalara Portal and set up the certificates, whether you want to test or use it on production." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:153 +msgid "There are two different Avalara Portals, one for testing and one for production:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:155 +msgid "Sandbox: https://portal.sandbox.avalarabrasil.com.br/" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:156 +msgid "Production: https://portal.avalarabrasil.com.br/" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:158 +msgid "When you create the account from Odoo, be sure to select the right environment. Moreover, the email used to open the account cannot be used to open another account. Save your :guilabel:`API ID` and :guilabel:`API Key` when you create the account from Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Transfer API Credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:165 +msgid "After you create the account from Odoo, you need to go to the Avalara Portal to set up your password:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:168 +msgid "Access the `Avalara portal `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:169 +msgid "Click on :guilabel:`Meu primeiro acesso`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:170 +msgid "Add the email address you used in Odoo to create the Avalara/AvaTax account, and then click :guilabel:`Solicitar Senha`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:172 msgid "You will receive an email with a token and a link to create your password. Click on this link and copy-paste the token to allocate your desired password." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:121 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:176 msgid "You can start using AvaTax in Odoo for tax computation **only** without creating a password and accessing the Avalara portal in the Odoo database. However, in order to use the electronic invoice service, you **must** access the AvaTax portal and upload your certificate there." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:-1 -msgid "Avatax account configuration." +msgid "AvaTax account configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:129 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:184 msgid "You can transfer |API| credentials. Use this only when you have already created an account in another Odoo instance and wish to reuse it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:133 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:188 msgid "A1 certificate upload" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:135 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:190 msgid "In order to issue electronic invoices, a certificate needs to be uploaded to the `AvaTax portal `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:138 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:193 msgid "The certificate will be synchronized with Odoo, as long as the external identifier number in the AvaTax portal matches - without special characters - with the CNPJ number, and the identification number (CNPJ) in Odoo matches with the CNPJ in AvaTax." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:148 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:198 +msgid "To issue NFS-e, some cities require that you link the certificate within the City Portal system before issuing NFS-e from Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:201 +msgid "If you receive an error message from the city that says :guilabel:`Your certificate is not linked to the user`, that means this process needs to be done in the city portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:210 msgid "The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` is installed by default as part of the data set included in the localization module. The accounts are mapped automatically in their corresponding taxes, and the default account payable and account receivable fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:153 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:215 msgid "The chart of accounts for Brazil is based on the SPED CoA, which gives a baseline of the accounts needed in Brazil." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:156 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:218 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:267 msgid "You can add or delete accounts according to the company's needs." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:161 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:223 msgid "In Brazil, a *series* number is linked to a sequence number range for electronic invoices. The series number can be configured in Odoo on a sales journal from the :guilabel:`Series` field. If more than one series is needed, then a new sales journal will need to be created and a new series number assigned to it for each series needed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:166 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:228 msgid "The :guilabel:`Use Documents` field needs to be selected. When issuing electronic and non-electronic invoices, the :guilabel:`Type` field selects the document type used when creating the invoice. The :guilabel:`Type` field will only be displayed if the :guilabel:`Use Documents` field is selected on the journal." msgstr "" @@ -15367,71 +16527,85 @@ msgstr "" msgid "Journal configuration with the Use Documents? field checked." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:175 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:237 msgid "When creating the journal, ensure the field :guilabel:`Dedicated Credit Note Sequence` is unchecked, as in Brazil, sequences between invoices, credit notes, and debit notes are shared per series number, which means per journal." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:182 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:244 msgid "Taxes are automatically created when installing the Brazilian localization. Taxes are already configured, and some of them are used by Avalara when computing taxes on the sales order or invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:185 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:247 msgid "Taxes can be edited, or more taxes can be added. For example, some taxes used for services need to be manually added and configured, as the rate may differ depending on the city where you are offering the service." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:190 -msgid "Taxes attached to services are not computed by AvaTax. Only goods taxes are computed." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:252 +msgid "If you decide to do service taxes manually, you won't be able to issue an NFS-e. To electronically send an NFS-e, you need to compute taxes using Avalara." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:192 -msgid "When configuring a tax used for a service that is included in the final price (when the tax is not added or subtracted on top of the product price), set the :guilabel:`Tax Computation` to :guilabel:`Percentage of Price Tax Included`, and, on the :guilabel:`Advanced Options` tab, check the :guilabel:`Included in Price` option." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:-1 -msgid "Tax configuration." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:201 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:256 msgid "Do not delete taxes, as they are used for the AvaTax tax computation. If deleted, Odoo creates them again when used in an |SO| or invoice and computing taxes with AvaTax, but the account used to register the tax needs to be re-configured in the tax's :guilabel:`Definition` tab, under the :guilabel:`Distribution for invoices` and :guilabel:`Distribution for refunds` sections." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:207 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:262 msgid ":doc:`Taxes functional documentation <../accounting/taxes>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:214 -msgid "To use the AvaTax integration on sale orders and invoices, first specify the following information on the product:" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:269 +msgid "To use the AvaTax integration on sale orders and invoices, first specify the following information on the product depending on its intended use:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:217 -msgid ":guilabel:`CEST Code` (Code for products subject to ICMS tax substitution)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:273 +msgid "E-Invoice for goods (NF-e)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:218 -msgid ":guilabel:`Mercosul NCM Code` (Mercosur Common Nomenclature Product Code)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:275 +msgid ":guilabel:`CEST Code`: Code for products subject to ICMS tax substitution" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:219 -msgid ":guilabel:`Source of Origin` (Indicates the origin of the product, which can be foreign or domestic, among other possible options depending on the specific use case)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:276 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:295 +msgid ":guilabel:`Mercosul NCM Code`: Mercosur Common Nomenclature Product Code" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:221 -msgid ":guilabel:`SPED Fiscal Product Type` (Fiscal product type according to SPED list table)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:277 +msgid ":guilabel:`Source of Origin`: Indicates the origin of the product, which can be foreign or domestic, among other possible options depending on the specific use case" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:222 -msgid ":guilabel:`Purpose of Use` (Specify the intended purpose of use for this product)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:279 +msgid ":guilabel:`SPED Fiscal Product Type`: Fiscal product type according to SPED list table" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:280 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:296 +msgid ":guilabel:`Purpose of Use`: Specify the intended purpose of use for this product" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:-1 msgid "Product configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:228 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:286 msgid "Odoo automatically creates three products to be used for transportation costs associated with sales. These are named `Freight`, `Insurance`, and `Other Costs`. They are already configured, if more need to be created, duplicate and use the same configuration (configuration needed: :guilabel:`Product Type` `Service`, :guilabel:`Transportation Cost Type` `Insurance`, `Freight`, or `Other Costs`)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:237 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:293 +msgid "E-Invoice for services (NFS-e)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:297 +msgid ":guilabel:`Service Code Origin`: City Service Code where the provider is registered" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:298 +msgid ":guilabel:`Service Codes`: City Service Code where the service will be provided, if no code is added, the Origin City Code will be used" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:300 +msgid ":guilabel:`Labor Assignment`: Defines if your services includes labor" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:305 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:282 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:174 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:656 @@ -15439,59 +16613,59 @@ msgstr "" msgid "Contacts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:239 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:307 msgid "Before using the integration, specify the following information on the contact:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:241 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:309 msgid "General information about the contact:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:243 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:311 msgid "Select the :guilabel:`Company` option for a contact with a tax ID (CNPJ), or check :guilabel:`Individual` for a contact with a CPF." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:249 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:317 msgid "In the :guilabel:`Street` field, enter the street, number, and any extra address information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:254 -msgid ":guilabel:`IE`: state tax identification number." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:322 +msgid ":guilabel:`IE`: state tax identification number" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:255 -msgid ":guilabel:`IM`: municipal tax identification number." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:323 +msgid ":guilabel:`IM`: municipal tax identification number" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:256 -msgid ":guilabel:`SUFRAMA code`: SUFRAMA registration number." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:324 +msgid ":guilabel:`SUFRAMA code`: SUFRAMA registration number" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 msgid "Contact configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:264 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:332 msgid "The :guilabel:`CPF`, :guilabel:`IE`, :guilabel:`IM`, and :guilabel:`SUFRAMA code` fields are are hidden until the :guilabel:`Country` is set to `Brazil`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:267 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:335 msgid "Fiscal information about the contact under the :guilabel:`Sales \\& Purchase` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:269 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 msgid ":guilabel:`Fiscal Position`: add the AvaTax fiscal position to automatically compute taxes on sale orders and invoices automatically" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:271 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:339 msgid ":guilabel:`Tax Regime`: federal tax regime" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:272 -msgid ":guilabel:`ICMS Taxpayer Type`: taxpayer type determines if the contact is within the ICMS regime, if it is exempt, or if it is a non-taxpayer" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:340 +msgid ":guilabel:`ICMS Taxpayer Type`: taxpayer type determines if the contact is within the :guilabel:`ICMS regime`, :guilabel:`Exempt status`, or :guilabel:`Non-taxpayer`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:274 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:342 msgid ":guilabel:`Main Activity Sector`: list of main activity sectors of the contact" msgstr "" @@ -15499,157 +16673,167 @@ msgstr "" msgid "Contact fiscal configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:282 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:349 +msgid "Add the :guilabel:`Fiscal Position` for :ref:`AvaTax Brazil `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:352 +msgid ":guilabel:`PIS Details`: :guilabel:`Taxable, Not Taxable, Taxable with rate 0%, Exempt, Suspended`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:354 +msgid ":guilabel:`CSLL Taxable`: If the company is subject to CSLL or not" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Contact fiscal configuration for NFSe." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:362 msgid "Fiscal positions" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:284 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:364 msgid "To compute taxes and send electronic invoices on sale orders and invoices, both the :guilabel:`Detect Automatically` and the :guilabel:`Use AvaTax API` options need to be enabled in the :guilabel:`Fiscal Position`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:288 -msgid "The :guilabel:`Fiscal Position` can be configured on the contact or selected when creating a sales order or an invoice." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:368 +msgid "The :guilabel:`Fiscal Position` can be configured on the :ref:`contact ` or selected when creating a sales order or an invoice." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:-1 msgid "Fiscal position configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:295 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:375 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:355 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:311 msgid "Workflows" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:297 -msgid "This section provides an overview of the actions that trigger `API calls `_ for tax computation, and how to send an electronic invoice for goods (NF-e) for government validation." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:377 +msgid "This section provides an overview of the actions that trigger `API calls `_ for tax computation, along with instructions on how to send electronic invoices for goods (NF-e) and services (NFS-e) for government validation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:302 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:382 msgid "Please note that each |API| call incurs a cost. Be mindful of the actions that trigger these calls to manage costs effectively." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:309 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:389 msgid "Tax calculations on quotations and sales orders" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:311 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:391 msgid "Trigger an |API| call to calculate taxes on a quotation or sales order automatically with AvaTax in any of the following ways:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:314 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:394 msgid "**Quotation confirmation**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:315 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:395 msgid "Confirm a quotation into a sales order." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:316 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:332 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:396 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:412 msgid "**Manual trigger**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:317 -msgid "Click on :guilabel:`Compute Taxes Using Avatax`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:318 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:334 -msgid "**Preview**" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:319 -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:335 -msgid "Click on the :guilabel:`Preview` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:320 -msgid "**Email a quotation / sales order**" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:321 -msgid "Send a quotation or sales order to a customer via email." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:324 -msgid "**Online quotation access**" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:323 -msgid "When a customer accesses the quotation online (via the portal view), the |API| call is triggered." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:327 -msgid "Tax calculations on invoices" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:329 -msgid "Trigger an |API| call to calculate taxes on a customer invoice automatically with AvaTax any of the following ways:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:333 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:397 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:413 msgid "Click on :guilabel:`Compute Taxes Using AvaTax`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:398 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:414 +msgid "**Preview**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:399 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:415 +msgid "Click on the :guilabel:`Preview` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:400 +msgid "**Email a quotation / sales order**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:401 +msgid "Send a quotation or sales order to a customer via email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:404 +msgid "**Online quotation access**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:403 +msgid "When a customer accesses the quotation online (via the portal view), the |API| call is triggered." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:407 +msgid "Tax calculations on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:409 +msgid "Trigger an |API| call to calculate taxes on a customer invoice automatically with AvaTax in any of the following ways:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:417 msgid "**Online invoice access**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:417 msgid "When a customer accesses the invoice online (via the portal view), the |API| call is triggered." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:340 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:420 msgid "The :guilabel:`Fiscal Position` must be set to `Automatic Tax Mapping (Avalara Brazil)` for any of these actions to compute taxes automatically." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:344 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:424 msgid ":doc:`Fiscal positions (tax and account mapping) <../accounting/taxes/fiscal_positions>`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:349 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:429 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:109 msgid "Electronic documents" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:354 -msgid "To process an electronic invoice for goods (NF-e), the invoice needs to be confirmed and taxes need to be computed by Avalara. Once that step is done, click on the :guilabel:`Send \\& Print` button in the upper left corner, and a pop-up will appear. Then click on :guilabel:`Process e-invoice` and any of the other options - :guilabel:`Download` or :guilabel:`Email`. Finally, click on :guilabel:`Send \\& Print` to process the invoice against the government." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:434 +msgid "To process an electronic invoice for goods (NF-e) or services (NFS-e), the invoice needs to be confirmed and taxes need to be computed by Avalara. Once that step is done, click on the :guilabel:`Send & Print` button in the upper left corner. In the pop-up that appears, click on :guilabel:`Process e-invoice` and any of the other options - :guilabel:`Download` or :guilabel:`Email`. Finally, click on :guilabel:`Send & Print` to process the invoice with the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:360 -msgid "Before sending the electronic invoice for goods (NF-e) some fields need to be filled out on the invoice:" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:441 +msgid "Before sending the electronic invoice for goods (NF-e) or services (NFS-e), some fields need to be filled out on the invoice:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:363 -msgid ":guilabel:`Customer` with all the customer information" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:444 +msgid ":guilabel:`Customer`, with all the customer information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:364 -msgid ":guilabel:`Payment Method: Brazil` (how the invoice is planned to be paid)" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:445 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:578 +msgid ":guilabel:`Payment Method: Brazil`: how the invoice is planned to be paid" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:365 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:446 msgid ":guilabel:`Fiscal Position` set as the :guilabel:`Automatic Tax Mapping (Avalara Brazil)`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:368 -msgid ":guilabel:`Document Type` set as :guilabel:`(55) Electronic Invoice (NF-e)`. This is the only" +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:447 +msgid ":guilabel:`Document Type` set as :guilabel:`(55) Electronic Invoice (NF-e)` or :guilabel:`(SE) Electronic Service Invoice (NFS-e)`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:367 -msgid "electronic document supported at the moment. Non-electronic invoices can be registered, and other document types can be activated if needed" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:370 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:450 msgid "There are some other optional fields that depend on the nature of the transaction. These fields are not required, so no errors will appear from the government if these optional fields are not populated for most cases:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:374 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:454 msgid ":guilabel:`Freight Model` determines how the goods are planned to be transported - domestic" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:375 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:455 msgid ":guilabel:`Transporter Brazil` determines who is doing the transportation" msgstr "" @@ -15661,71 +16845,95 @@ msgstr "" msgid "Process electronic invoice pop-up in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:384 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:464 msgid "All of the fields available on the invoice used to issue an electronic invoice are also available on the sales order, if needed. When creating the first invoice, the field :guilabel:`Document Number` is displayed, allocated as the first number to be used sequentially for subsequent invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:390 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:470 #: ../../content/applications/finance/fiscal_localizations/chile.rst:595 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 msgid "Credit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:392 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:472 msgid "If a sales return needs to be registered, then a credit note can be created in Odoo to be sent to the government for validation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:396 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:476 +msgid "Credit notes are only available for electronic invoices for goods (NF-e)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:479 msgid ":ref:`Issue a credit note `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:399 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:482 #: ../../content/applications/finance/fiscal_localizations/peru.rst:594 msgid "Debit Notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:401 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:484 msgid "If additional information needs to be included, or values need to be corrected that were not accurately provided in the original invoice, a debit note can be issued." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:405 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:488 +msgid "Debit notes are only available for electronic invoices for goods (NF-e)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:490 msgid "Only the products included in the original invoice can be part of the debit note. While changes can be made to the product's unit price or quantity, products **cannot** be added to the debit note. The purpose of this document is only to declare the amount that you want to add to the original invoice for the same or fewer products." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:411 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:496 msgid ":ref:`Issue a debit note `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:414 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:499 msgid "Invoice cancellation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:416 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:501 msgid "It is possible to cancel an electronic invoice that was validated by the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:419 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:504 msgid "Check whether the electronic invoice is still within the cancellation deadline, which may vary according to the legislation of each state." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:422 -msgid "This can be done in Odoo by clicking :guilabel:`Request Cancel` and adding a cancellation :guilabel:`Reason` on the pop-up that appears. If you want to send this cancellation reason to the customer via email, activate the :guilabel:`E-mail` checkbox." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:508 +msgid "E-invoices for goods (NF-e)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:510 +msgid "Cancel an e-invoice for goods (NF-e) in Odoo by clicking :guilabel:`Request Cancel` and adding a cancellation :guilabel:`Reason` on the pop-up that appears. If you want to send this cancellation reason to the customer via email, activate the :guilabel:`E-mail` checkbox." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:-1 msgid "Invoice cancellation reason in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:430 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:518 +msgid "This is an electronic cancellation, which means that Odoo will send a request to the government to cancel the NF-e, and it will then consume one |IAP| credit, as an |API| call occurs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:522 +msgid "E-invoices for services (NFS-e)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:524 +msgid "Cancel an e-invoice for services (NFS-e) in Odoo by clicking :guilabel:`Request Cancel`. In this case, there is no electronic cancellation process, as not every city has this service available. The user needs to manually cancel this NFS-e on the city portal. Once that step is completed, they can request the cancellation in Odoo, which will cancel the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:530 msgid "Correction letter" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:432 -msgid "A correction letter can be created and linked to an electronic invoice that was validated by the government." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:532 +msgid "A correction letter can be created and linked to an electronic invoice for goods (NF-e) that was validated by the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:435 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:535 msgid "This can be done in Odoo by clicking :guilabel:`Correction Letter` and adding a correction :guilabel:`Reason` on the pop-up that appears. To send this correction reason to a customer via email, activate the :guilabel:`E-mail` checkbox." msgstr "" @@ -15733,11 +16941,15 @@ msgstr "" msgid "Correction letter reason in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:443 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:543 +msgid "Correction letters are only available for electronic invoices for goods (NF-e)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:546 msgid "Invalidate invoice number range" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:445 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:548 msgid "A range of sequences that are assigned to sales journals can be invalidated with the government if they are not currently used, **and** will not be used in the future. To do so, navigate to the journal, and click the :menuselection:`⚙️ (gear) icon --> Invalidate Number Range (BR)`. On the :guilabel:`Invalidate Number Range (BR)` wizard, add the :guilabel:`Initial Number` and :guilabel:`End Number` of the range that should be canceled, and enter an invalidation :guilabel:`Reason`." msgstr "" @@ -15749,36 +16961,36 @@ msgstr "" msgid "Number range invalidation wizard in Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:459 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:562 +msgid "Invalidate invoice number range documents are only available for electronic invoices for goods (NF-e)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:566 msgid "The log of the canceled numbers along with the XML file are recorded in the chatter of the journal." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:465 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:572 msgid "On the vendor bills side, when receiving an invoice from a supplier, you can encode the bill in Odoo by adding all the commercial information together with the same Brazilian specific information that is recorded on the :ref:`customer invoices `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:469 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:576 msgid "These Brazilian specific fields are:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:471 -msgid ":guilabel:`Payment Method: Brazil` (how the invoice is planned to be paid)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:579 +msgid ":guilabel:`Document Type`: used by your vendor" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:472 -msgid ":guilabel:`Document Type` used by your vendor." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:580 +msgid ":guilabel:`Document Number`: the invoice number from your supplier" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:473 -msgid ":guilabel:`Document Number` (the invoice number from your supplier)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:581 +msgid ":guilabel:`Freight Model`: **NF-e specific** how goods are planned to be transported - domestic" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:474 -msgid ":guilabel:`Freight Model` (how goods are planned to be transported - domestic)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/brazil.rst:475 -msgid ":guilabel:`Transporter Brazil` (who is doing the transportation)." +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:582 +msgid ":guilabel:`Transporter Brazil`: **NF-e specific** who is doing the transportation." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:3 @@ -16142,20 +17354,6 @@ msgstr "" msgid "Configuring partner contacts is also required to send :abbr:`SII (Servicio de Impuestos Internos)` electronic invoices. Open the :menuselection:`Contacts` app to do so and fill in the following fields on a new or existing contact form." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1096 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:95 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:288 -msgid ":guilabel:`Name`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:233 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:100 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:293 -msgid ":guilabel:`Email`" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/chile.rst:234 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:97 msgid ":guilabel:`Identification Number`" @@ -20701,93 +21899,886 @@ msgstr "" msgid "Hong Kong" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:6 -msgid "Add FPS QR codes to invoices" +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:8 +msgid ":ref:`Install ` the following modules to get the latest features of the Hong Kong localization:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:8 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:17 +msgid ":guilabel:`Hong Kong - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:18 +msgid "`l10n_hk`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:19 +msgid "The base module to manage chart of accounting and localization for Hong Kong." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:20 +msgid ":guilabel:`Hong Kong - Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:21 +msgid "`l10n_hk_hr_payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:22 +msgid "Enables :ref:`payroll ` specific localization features for Odoo *Payroll* app. This module also installs :guilabel:`Hong Kong - Payroll with Accounting` and :guilabel:`Documents - Hong Kong Payroll`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:25 +msgid ":guilabel:`Hong Kong - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:26 +msgid "`l10n_hk_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:27 +msgid "Installs the link between Hong Kong payroll and accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:28 +msgid ":guilabel:`Documents - Hong Kong Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:29 +msgid "`documents_l10n_hk_hr_payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:30 +msgid "Integrates employee ir56 forms in the Odoo *Documents* app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:33 +msgid "FPS QR codes on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:35 msgid ":abbr:`FPS (Faster Payment System)` is a payment service platform that allows customers to make instant domestic payments to individuals and merchants in Hong Kong dollars or Renminbi via online and mobile banking." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:13 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:40 #: ../../content/applications/finance/fiscal_localizations/singapore.rst:12 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:125 #: ../../content/applications/finance/fiscal_localizations/vietnam.rst:12 msgid "Activate QR codes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:15 -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:14 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:127 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:14 -msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Customer Payments` section, activate the :guilabel:`QR Codes` feature." +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:42 +msgid "Go to :menuselection:`Accounting app --> Configuration --> Settings`. Under the :guilabel:`Customer Payments` section, tick the checkbox beside the :guilabel:`QR Codes` feature. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:19 -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:47 msgid "FPS bank account configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:21 -msgid "Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and select the bank account for which you want to activate FPS. Set the :guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field depending on the type you chose." +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:49 +msgid "Go to :menuselection:`Contacts app --> Configuration --> Bank Accounts section --> Bank Accounts`. Then select the bank account for FPS activation. Proceed to set the :guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field, depending on the type chosen." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:26 -msgid "The account holder's country must be set to Hong Kong on its contact form." +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:53 +msgid "Remember to include the invoice number in the QR code, by ticking the :guilabel:`Include Reference` checkbox." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:27 -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:26 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:27 -msgid "You could also include the invoice number in the QR code by checking the :guilabel:`Include Reference` checkbox." +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "FPS bank account configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:34 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:61 +msgid "The account holder's country **must** be set to `Hong Kong` on their contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:64 #: ../../content/applications/finance/fiscal_localizations/singapore.rst:33 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:144 #: ../../content/applications/finance/fiscal_localizations/vietnam.rst:34 msgid ":doc:`../accounting/bank`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:37 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:67 #: ../../content/applications/finance/fiscal_localizations/singapore.rst:36 #: ../../content/applications/finance/fiscal_localizations/thailand.rst:147 #: ../../content/applications/finance/fiscal_localizations/vietnam.rst:37 msgid "Bank journal configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:39 -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:38 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:39 -msgid "Go to :menuselection:`Accounting --> Configuration --> Journals`, open the bank journal, then fill out the :guilabel:`Account Number` and :guilabel:`Bank` under the :guilabel:`Journal Entries` tab." +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:69 +msgid "Go to :menuselection:`Accounting app --> Configuration --> Journals` and open the bank journal. Then, fill out the :guilabel:`Account Number` and :guilabel:`Bank` fields, located in the :guilabel:`Journal Entries` tab." msgstr "" #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:-1 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:-1 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:-1 -msgid "Bank Account's journal configuration" +msgid "Bank Account's journal configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:46 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:78 msgid "Issue invoices with FPS QR codes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:48 -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:47 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:48 -msgid "When creating a new invoice, open the :guilabel:`Other Info` tab and set the :guilabel:`Payment QR-code` option to *EMV Merchant-Presented QR-code*." +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:80 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:158 +msgid "When creating a new invoice, open the :guilabel:`Other Info` tab and set the :guilabel:`Payment QR-code` option to :guilabel:`EMV Merchant-Presented QR-code`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:-1 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:-1 -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:-1 -msgid "Select EMV Merchant-Presented QR-code option" +msgid "Select EMV Merchant-Presented QR-code option." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:54 -msgid "Ensure that the :guilabel:`Recipient Bank` is the one you configured, as Odoo uses this field to generate the FPS QR code." +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:87 +msgid "Ensure that the :guilabel:`Recipient Bank` is configured, as Odoo uses this field to generate the FPS QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:96 +msgid "Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is installed before proceeding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:100 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:102 +msgid "Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, configure the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:105 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:107 +msgid ":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option **must** be selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:109 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:111 +msgid ":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:112 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:113 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:114 +msgid ":guilabel:`Current Rental`: employee's rental records (if rental allowance is applicable)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:115 +msgid ":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, :guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:116 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:117 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:118 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:121 +msgid "For the :guilabel:`Bank Account Number`, this account should be set as :guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:124 +msgid "To achieve this, click on the right-arrow button next to :guilabel:`Bank Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted` by clicking on the toggle." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:128 +msgid "To populate the :guilabel:`Current Rental`, click on the :guilabel:`History` button. Then, click on :guilabel:`New`. Fill in the relevant details and save the rental record. Upon saving the record, the rental contract :guilabel:`state` will be visible (at the top-right corner) and can be set to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:133 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:135 +msgid ":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% VC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:137 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:142 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:144 +msgid "Once the new employee has been created, click the :guilabel:`Contracts` smart button on the employee record, or navigate to :menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:148 +msgid "Only **one** contract can be active simultaneously per employee, but an employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:151 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:153 +msgid ":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong Employee`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:154 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:155 +msgid ":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` (from employee record)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:156 +msgid ":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, :guilabel:`Attendances` or :guilabel:`Planning`. This field determines how the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:160 +msgid ":guilabel:`Working Schedule`: the work entries are generated automatically based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:162 +msgid ":guilabel:`Attendances`: the work entries are generated based on the check-in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:164 +msgid ":guilabel:`Planning`: the work entries are generated from planning shifts only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:166 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:168 +msgid ":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-time employees, or :guilabel:`Hourly Wage` for employees who are paid hourly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:170 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:171 +msgid ":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:173 +msgid ":guilabel:`Internet Subscription`: this is an **optional** field to provide additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:177 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:179 +msgid "Once all information has been setup, set the contract status to :guilabel:`Running` by clicking the :guilabel:`Running` button in the top-right of the page." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:189 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:191 +msgid "Once the employees, and their contracts, are configured, payslips can be generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:194 +msgid "Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:196 +msgid ":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee salary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:197 +msgid ":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:199 +msgid ":guilabel:`CAP57: Long Service Payment`: applicable to employees with more than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:201 +msgid ":guilabel:`CAP57: Severance Payment`: applicable to employees with more than two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:204 +msgid "Before running the payslips, the accounts used in the salary rule can be adjusted by navigating to :menuselection:`Payroll app --> Configuration --> Rules`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:211 +msgid "Odoo can create pay runs in two ways: via :ref:`batch ` or :ref:`individual ` payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:217 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:219 +msgid "This method of payslip generation is used for recurring payments, since multiple employee payslips can be managed at once. Go to :menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:222 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:246 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:494 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:514 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:223 +msgid "Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` (e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:225 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:226 +msgid "Choose which :guilabel:`Salary Structure` to use for this batch. The department filter allows the batch to only apply to a specific group of employees." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:228 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:229 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:231 +msgid "Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry found in the :guilabel:`Other Info` tab of each payslip. A :guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you sure you want to proceed?`. Click :guilabel:`Ok` to create the journal entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:238 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:240 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:242 +msgid "This method of payslip generation is commonly used to handle non-recurring payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, :guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance Payment`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:247 +msgid "Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is filled out automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:249 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:250 +msgid "Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees Monthly Pay`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:251 +msgid "The :guilabel:`Worked Days & Inputs` tab automatically compute the worked days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:253 +msgid "Additional payslip items can be added at this time (e.g. :guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other Inputs` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:255 +msgid "Click on :guilabel:`Compute Sheet` button to generate the payslip lines. This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:259 +msgid "If the work entry for an employee was amended, click the :icon:`fa-cog` :guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:263 +msgid "The :guilabel:`Salary Computation` tab shows the detailed breakdown of the computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:266 +msgid ":guilabel:`Rent Allowance`: amount derived from the employee's active rental record." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:267 +msgid ":guilabel:`Basic Salary`: amount of base salary provided (after rent allowance deduction)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:268 +msgid ":guilabel:`713 Gross`: net payable amount considering *Commission*, *Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:270 +msgid ":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:272 +msgid ":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:273 +msgid ":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:274 +msgid ":guilabel:`Gross`: net payable amount from MPF gross after consideration of MPF deductions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:275 +msgid ":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:278 +msgid "There are no MPF contributions for the first month. Both employee and employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:285 +msgid "Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:288 +msgid ":guilabel:`Back Pay`: additional salary payout can be included under this category." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:289 +msgid ":guilabel:`Commission`: the commission earned during the period can be manually entered here." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:290 +msgid ":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:291 +msgid ":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:292 +msgid ":guilabel:`Referral Fee`: the additional bonus offered for any form of business-related referral." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:293 +msgid ":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:295 +msgid ":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded from the current payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:297 +msgid ":guilabel:`Custom Average Monthly Salary`: to override the average monthly salary used for end-of-year payment (rule is only applicable to payslips generated in December)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:299 +msgid ":guilabel:`Lieu of Notice Period (Months)`: only applicable to :guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, the final payout is set as 1-month. Use the :guilabel:`Count` field under the :guilabel:`Other Inputs` section to set a different notice period duration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:304 +msgid "Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by :guilabel:`Create Draft entry` to generate a draft journal entry found in the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:310 +msgid "Once the draft journal entries have been posted, the company can now pay the employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:313 +msgid "From the employee's payslip (:menuselection:`Payroll app --> Payslips --> All Payslips`), once the payslip's journal entry has been posted, click :guilabel:`Register Payment`. The process is the same as :doc:`paying vendor bills <../accounting/payments>`. Select the desired bank journal and payment method, then later reconcile the payment with the corresponding bank statement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:317 +msgid "For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), once all draft journal entries from the batch are confirmed, click :guilabel:`Mark as Paid` to post the payment journal entry. Then :doc:`create a payment <../accounting/payments>` in the *Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:323 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:325 +msgid "To configure the contract for an employee paid hourly using the *Attendances* app for hours tracking, navigate to :menuselection:`Payroll app --> Contracts --> Contracts`. Create a new :ref:`contract `. It is important to remember to set the :guilabel:`Work Entry Source` as :guilabel:`Attendances`, and :guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:331 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:333 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:334 +msgid "The employee can check-in/out, via the kiosk mode and the time will be logged automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:335 +msgid "In the :menuselection:`Payroll app`, review the attendance work entries generated from :menuselection:`Payroll app --> Work Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:337 +msgid "Next, generate the :ref:`payslips ` and process the payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:348 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:350 +msgid "The work entry types and time off types are fully integrated between the *Time Off* and *Payroll* apps. There are several default time off types and work entry types specific to Hong Kong which are installed automatically along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:354 +msgid "Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:356 +msgid "There are two checkboxes to be considered when setting up the work entry type:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:358 +msgid ":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:359 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:366 +msgid ":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:369 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:371 +msgid "The *Hong Kong - Payroll* module is compliant with 713 Ordinance which relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair compensation for employees." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:374 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:379 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:379 +msgid ":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period, minus the wages of non-full pay, divided by the total days in a 12-month period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:383 +msgid "For 418 compliance, there is no automated allocation of the *Statutory Holiday* entitlement to the employees. As soon as 418 requirements are met, manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:388 +msgid "Before generating payslips, ensure the statuses are :guilabel:`Done` to validate the outcome." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:393 +msgid "Period" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:394 +msgid "Days" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:395 +msgid "Wage" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:396 +msgid "Commission" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:398 +msgid "ADW" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:399 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:400 +msgid "Jan" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:401 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:415 +msgid "31" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:402 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:404 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:409 +msgid "$20200" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:405 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:406 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:413 +msgid "N/A" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:407 +msgid "Feb" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:408 +msgid "28" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:410 +msgid "$5000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:411 +msgid "$25200" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:412 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:414 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:416 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:418 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:419 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:420 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:421 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:423 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:427 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:430 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:432 +msgid "**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW (Average Daily Wage)` is always computed on a cumulative basis of the trailing 12-months." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:434 +msgid "**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type` for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:436 +msgid "**Mar**: Apply for **one** full-paid annual leave in March. The salary compensation for the leave taken is based on :abbr:`ADW (Average Daily Wage)` thus far." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:443 +msgid "**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed accordingly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:451 +msgid "The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, and not be visible to the user." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:455 +msgid "`HK 713 Ordinance `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:456 +msgid "`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:459 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:461 +msgid "Before generating the below reports, setup the following in :menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:464 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:466 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:468 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:469 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:471 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:473 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:474 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:475 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:482 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:484 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:486 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:487 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:488 +msgid ":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in HK)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:489 +msgid ":guilabel:`IR56G`: notification of Ceasation of Employment (departing from HK permanently)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:491 +msgid "Go to :menuselection:`Payroll app --> Reporting`, and select one of the :guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:495 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:496 +msgid "Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart button appears." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:497 +msgid "The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:499 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:506 +msgid "The scheduled action called *Payroll: Generate pdfs* can be manually triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:510 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:512 +msgid "Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:515 +msgid "Select the relevant :guilabel:`Year`, :guilabel:`Month`, and :guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:516 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:517 +msgid "The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:524 +msgid "Odoo will not be developing further reports for other MPF trustee as there will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:528 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:531 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:533 +msgid "If *HSBC Autopay* is selected as the batch payment method, click on :guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:540 +msgid "This creates an :file:`.apc` file format which can be uploaded to the HSCB portal for processing." msgstr "" #: ../../content/applications/finance/fiscal_localizations/india.rst:3 @@ -25509,6 +27500,12 @@ msgstr "" msgid "PayNow is a payment service platform that allows customers to make instant domestic payments to individuals and merchants in Singapore dollars via online and mobile banking." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:14 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:127 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:14 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Customer Payments` section, activate the :guilabel:`QR Codes` feature." +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/singapore.rst:18 #: ../../content/applications/finance/fiscal_localizations/singapore.rst:-1 msgid "PayNow bank account configuration" @@ -25522,10 +27519,37 @@ msgstr "" msgid "The account holder's country must be set to Singapore on its contact form." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:26 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:27 +msgid "You could also include the invoice number in the QR code by checking the :guilabel:`Include Reference` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:38 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:39 +msgid "Go to :menuselection:`Accounting --> Configuration --> Journals`, open the bank journal, then fill out the :guilabel:`Account Number` and :guilabel:`Bank` under the :guilabel:`Journal Entries` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:-1 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:-1 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:-1 +msgid "Bank Account's journal configuration" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/singapore.rst:45 msgid "Issue invoices with PayNow QR codes" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:47 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:48 +msgid "When creating a new invoice, open the :guilabel:`Other Info` tab and set the :guilabel:`Payment QR-code` option to *EMV Merchant-Presented QR-code*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:-1 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:-1 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:-1 +msgid "Select EMV Merchant-Presented QR-code option" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/singapore.rst:53 msgid "Ensure that the :guilabel:`Recipient Bank` is the one you configured, as Odoo uses this field to generate the PayNow QR code." msgstr "" @@ -26204,10 +28228,6 @@ msgstr "" msgid "Issue invoices with PromptPay QR code" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:158 -msgid "When creating a new invoice, open the :guilabel:`Other Info` tab and set the :guilabel:`Payment QR-code` option to :guilabel:`EMV Merchant-Presented QR-code`." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/thailand.rst:164 msgid "Ensure that the :guilabel:`Recipient Bank` is the one you configured, as Odoo uses this field to generate the PromptPay QR code." msgstr "" @@ -28680,7 +30700,7 @@ msgid "Under :guilabel:`Webhook verification token`, click :guilabel:`View Webho msgstr "" #: ../../content/applications/finance/payment_providers/xendit.rst:33 -msgid "In the :guilabel:`Webhook URL` section, enter your Odoo database URL (e.g., `https://example.odoo.com`) in the field :guilabel:`Invoices paid` and click the :guilabel:`Test and save` button next to it." +msgid "In the :guilabel:`Webhook URL` section, enter your Odoo database's URL, followed by `/payment/xendit/webhook` (e.g., `https://example.odoo.com/payment/xendit/webhook`) in the field :guilabel:`Invoices paid` and click the :guilabel:`Test and save` button next to it." msgstr "" #: ../../content/applications/finance/payment_providers/xendit.rst:40 diff --git a/locale/sources/general.pot b/locale/sources/general.pot index fcdf1d862..ade57eb15 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -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 \n" "Language-Team: LANGUAGE \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 `, the :ref:`browser extension `, through the :ref:`command palette ` or the :ref:`URL `." +msgid "The developer mode, also known as debug mode, unlocks access to advanced :ref:`tools and settings ` 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 `, which are used to debug JavaScript code, and with :ref:`tests assets `, 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 `_ 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 `_ and `Firefox Add-ons `_." +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 `, and `?debug=tests` enables the :ref:`tests 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 `_. 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 `_." 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. `_" 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 `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:195 +#: ../../content/applications/general/email_communication/email_domain.rst:197 msgid "`OVH SPF `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:196 +#: ../../content/applications/general/email_communication/email_domain.rst:198 msgid "`GoDaddy TXT record `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:197 +#: ../../content/applications/general/email_communication/email_domain.rst:199 msgid "`GoDaddy SPF `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:198 +#: ../../content/applications/general/email_communication/email_domain.rst:200 msgid "`GoDaddy DKIM `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:199 +#: ../../content/applications/general/email_communication/email_domain.rst:201 msgid "`NameCheap `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:201 +#: ../../content/applications/general/email_communication/email_domain.rst:203 msgid "`CloudFlare DNS `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:202 +#: ../../content/applications/general/email_communication/email_domain.rst:204 msgid "`Google Domains `_" msgstr "" -#: ../../content/applications/general/email_communication/email_domain.rst:203 +#: ../../content/applications/general/email_communication/email_domain.rst:205 msgid "`Azure DNS `_" 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 `_ 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 `_" 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 `_. 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 `_. 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 \n" "Language-Team: LANGUAGE \n" @@ -20,71 +20,72 @@ msgstr "" msgid "Human resources" msgstr "" -#: ../../content/applications/hr/appraisals.rst:3 -#: ../../content/applications/hr/appraisals.rst:50 -#: ../../content/applications/hr/appraisals.rst:195 +#: ../../content/applications/hr/appraisals.rst:5 +#: ../../content/applications/hr/appraisals.rst:52 +#: ../../content/applications/hr/appraisals.rst:174 msgid "Appraisals" msgstr "" -#: ../../content/applications/hr/appraisals.rst:5 +#: ../../content/applications/hr/appraisals.rst:7 msgid "In Odoo, the *Appraisals* application can be used to evaluate employee performance on a recurring basis. Managers can evaluate the performance of their employees, and also allow employees to do a self-assessment of their own. Appraisals are customizable, and can be set for any kind of schedule desired." msgstr "" -#: ../../content/applications/hr/appraisals.rst:10 +#: ../../content/applications/hr/appraisals.rst:12 msgid "Appraisals give employees valuable feedback, including actionable goals to work toward, and measurable skills to improve upon. Additionally, appraisals may form the basis for raises, promotions, and other benefits." msgstr "" -#: ../../content/applications/hr/appraisals.rst:14 +#: ../../content/applications/hr/appraisals.rst:16 msgid "Regular appraisals are good for both the employees and the company, since they can accurately measure performance based on company goals, and show employees where they need to improve." msgstr "" -#: ../../content/applications/hr/appraisals.rst:18 -#: ../../content/applications/hr/attendances.rst:66 -#: ../../content/applications/hr/frontdesk.rst:13 -#: ../../content/applications/hr/time_off.rst:28 +#: ../../content/applications/hr/appraisals.rst:20 +#: ../../content/applications/hr/attendances.rst:59 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/time_off.rst:31 msgid "Configuration" msgstr "" -#: ../../content/applications/hr/appraisals.rst:20 +#: ../../content/applications/hr/appraisals.rst:22 msgid "The :guilabel:`Configuration` menu in the *Appraisals* application is where the settings can be configured, feedback templates can be edited, frequencies can be set, evaluation scales can be managed, data for 360 feedback can be stored, and goal tags can be viewed/created." msgstr "" -#: ../../content/applications/hr/appraisals.rst:25 +#: ../../content/applications/hr/appraisals.rst:27 #: ../../content/applications/hr/fleet.rst:14 #: ../../content/applications/hr/lunch.rst:15 #: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:35 msgid "Settings" msgstr "" -#: ../../content/applications/hr/appraisals.rst:27 +#: ../../content/applications/hr/appraisals.rst:29 msgid "To access the *Settings* menu, navigate to :menuselection:`Appraisals application --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:31 +#: ../../content/applications/hr/appraisals.rst:33 msgid "Feedback templates" msgstr "" -#: ../../content/applications/hr/appraisals.rst:33 +#: ../../content/applications/hr/appraisals.rst:35 msgid "Feedback templates are form outlines used during an employee appraisal. Any edits made to a template are, ultimately, reflected in the appraisals sent to employees." msgstr "" -#: ../../content/applications/hr/appraisals.rst:36 +#: ../../content/applications/hr/appraisals.rst:38 msgid "There are two default templates pre-configured in Odoo *Appraisals*: one for employee feedback, and one for manager feedback. Each contains several sections, along with questions, and brief explanations for how to respond to the questions." msgstr "" -#: ../../content/applications/hr/appraisals.rst:40 +#: ../../content/applications/hr/appraisals.rst:42 msgid "The :guilabel:`Employee Feedback Template` has the following sections: :guilabel:`My work`, :guilabel:`My future`, and :guilabel:`My feelings`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:43 +#: ../../content/applications/hr/appraisals.rst:45 msgid "The :guilabel:`Manager Feedback Template` has the following sections: :guilabel:`Feedback`, :guilabel:`Evaluation`, and :guilabel:`Improvements`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:46 +#: ../../content/applications/hr/appraisals.rst:48 msgid "Any desired changes to the default feedback templates can be made by making changes directly in each template." msgstr "" -#: ../../content/applications/hr/appraisals.rst:52 +#: ../../content/applications/hr/appraisals.rst:54 msgid "The :guilabel:`Appraisals` section of the settings menu determines the frequency that appraisals are performed, and if it is possible to request additional feedback." msgstr "" @@ -92,68 +93,68 @@ msgstr "" msgid "The appraisals sections with the timeline filled in and 360 feedback enabled." msgstr "" -#: ../../content/applications/hr/appraisals.rst:62 +#: ../../content/applications/hr/appraisals.rst:64 msgid "Appraisals plans" msgstr "" -#: ../../content/applications/hr/appraisals.rst:64 +#: ../../content/applications/hr/appraisals.rst:66 msgid "By default, appraisals are pre-configured to be automatically created six months after an employee is hired, with a second appraisal exactly six months after that." msgstr "" -#: ../../content/applications/hr/appraisals.rst:67 +#: ../../content/applications/hr/appraisals.rst:69 msgid "Once those two initial appraisals have been completed in the employee's first year, following appraisals are only created once a year (every twelve months)." msgstr "" -#: ../../content/applications/hr/appraisals.rst:70 +#: ../../content/applications/hr/appraisals.rst:72 msgid "To modify this schedule, change the number of months in the blank fields under the :guilabel:`Appraisals Plans` section." msgstr "" -#: ../../content/applications/hr/appraisals.rst:74 +#: ../../content/applications/hr/appraisals.rst:76 msgid "If the :guilabel:`Appraisals Plans` section is modified, **all** empty :guilabel:`Next Appraisal Dates` are modified for **all** employees." msgstr "" -#: ../../content/applications/hr/appraisals.rst:78 -#: ../../content/applications/hr/appraisals.rst:120 +#: ../../content/applications/hr/appraisals.rst:80 +#: ../../content/applications/hr/appraisals.rst:122 msgid "360 feedback" msgstr "" -#: ../../content/applications/hr/appraisals.rst:80 +#: ../../content/applications/hr/appraisals.rst:82 msgid "The :guilabel:`360 Feedback` option can be enabled to allow managers to request feedback from other employees using a different survey form, at any time, independent of the appraisal schedule." msgstr "" -#: ../../content/applications/hr/appraisals.rst:83 +#: ../../content/applications/hr/appraisals.rst:85 msgid "Typically, managers ask for feedback from other people who work with an employee they manage. This includes the employee's various managers, peers, and direct reports." msgstr "" -#: ../../content/applications/hr/appraisals.rst:86 +#: ../../content/applications/hr/appraisals.rst:88 msgid "To view the :guilabel:`360 Feedback` survey, click the :guilabel:`→ Internal link` icon at the end of the :guilabel:`Default Template` field. The :guilabel:`360 Feedback` survey loads, and any desired changes to the survey can be made." msgstr "" -#: ../../content/applications/hr/appraisals.rst:90 +#: ../../content/applications/hr/appraisals.rst:92 msgid "For more information on how to edit a survey, refer to the :doc:`../marketing/surveys/create` document." msgstr "" -#: ../../content/applications/hr/appraisals.rst:94 +#: ../../content/applications/hr/appraisals.rst:96 msgid "The :guilabel:`360 Feedback` form is a pre-configured survey within the *Surveys* application. In order to use the :guilabel:`360 Feedback` option, including the ability to edit the survey, the *Surveys* application **must** be installed." msgstr "" -#: ../../content/applications/hr/appraisals.rst:99 +#: ../../content/applications/hr/appraisals.rst:101 msgid "Evaluation scale" msgstr "" -#: ../../content/applications/hr/appraisals.rst:101 +#: ../../content/applications/hr/appraisals.rst:103 msgid "On each employee appraisal form, final rating options appear by default. To view and edit these options, navigate to :menuselection:`Appraisals application --> Configuration --> Evaluation Scale`. This presents the ratings in a list view." msgstr "" -#: ../../content/applications/hr/appraisals.rst:105 +#: ../../content/applications/hr/appraisals.rst:107 msgid "The pre-configured ratings are :guilabel:`Needs Improvement`, :guilabel:`Meets Expectations`, :guilabel:`Exceeds Expectations`, and :guilabel:`Strongly Exceeds Expectations`. To add another rating, click the :guilabel:`New` button." msgstr "" -#: ../../content/applications/hr/appraisals.rst:109 +#: ../../content/applications/hr/appraisals.rst:111 msgid "When the :guilabel:`New` button is clicked on the :guilabel:`Evaluation Scale` page, a blank line appears at the bottom of the list. Enter the name of the rating in the field." msgstr "" -#: ../../content/applications/hr/appraisals.rst:112 +#: ../../content/applications/hr/appraisals.rst:114 msgid "To rearrange the order of the ratings, click the :guilabel:`(six small gray boxes)` icon to the left of a rating, and drag the rating to the desired position on the list." msgstr "" @@ -161,7 +162,7 @@ msgstr "" msgid "The evaluation scale, with the new button and click and drag icons highlighted." msgstr "" -#: ../../content/applications/hr/appraisals.rst:122 +#: ../../content/applications/hr/appraisals.rst:124 msgid "The :guilabel:`360 Feedback` section displays information for all the surveys currently configured in the *Appraisals* application. To view the surveys, and their statistics, navigate to :menuselection:`Appraisals application --> Configuration --> 360 Feedback`." msgstr "" @@ -169,155 +170,123 @@ msgstr "" msgid "A list view of all available surveys in the Appraisals application." msgstr "" -#: ../../content/applications/hr/appraisals.rst:130 +#: ../../content/applications/hr/appraisals.rst:132 msgid "Each appraisal (or survey) is presented in its own line on the :guilabel:`360 Feedback` page, along with various information related to that particular appraisal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:133 +#: ../../content/applications/hr/appraisals.rst:135 msgid "Each appraisal includes the following information:" msgstr "" -#: ../../content/applications/hr/appraisals.rst:135 +#: ../../content/applications/hr/appraisals.rst:137 msgid ":guilabel:`Survey Name`: the name of the specific survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:136 +#: ../../content/applications/hr/appraisals.rst:138 msgid ":guilabel:`Responsible`: the employee responsible for the survey, including the month and year they were given that designation." msgstr "" -#: ../../content/applications/hr/appraisals.rst:138 +#: ../../content/applications/hr/appraisals.rst:140 msgid ":guilabel:`Questions`: the number of questions in that particular survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:139 +#: ../../content/applications/hr/appraisals.rst:141 msgid ":guilabel:`Average Duration`: the average time a user spends completing the survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:140 +#: ../../content/applications/hr/appraisals.rst:142 msgid ":guilabel:`Registered`: the number of people who have been sent the survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:141 +#: ../../content/applications/hr/appraisals.rst:143 msgid ":guilabel:`Completed`: the number of people who have completed the survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:143 +#: ../../content/applications/hr/appraisals.rst:145 msgid "Each appraisal also has two buttons at the end of each line: a :guilabel:`Test` button and a :guilabel:`See Results` button." msgstr "" -#: ../../content/applications/hr/appraisals.rst:146 +#: ../../content/applications/hr/appraisals.rst:148 msgid "To see what an appraisal looks like for the end user (i.e. an employee), click the :guilabel:`Test` button, and the appraisal loads in a new browser tab. The entire appraisal loads, and can be clicked through without having to enter any answers." msgstr "" -#: ../../content/applications/hr/appraisals.rst:150 +#: ../../content/applications/hr/appraisals.rst:152 msgid "To exit, close the tab. Or, click :guilabel:`This is a Test Survey. → Edit Survey` at the top of the page to be taken to the detail form for that particular survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:153 +#: ../../content/applications/hr/appraisals.rst:155 msgid "To view the results from everyone who completed an appraisal, click the :guilabel:`See Results` button. This presents all the answers for the survey in a new tab. Each question provides information on how many people responded to a question, and how many people skipped it. All answers for each question are visible." msgstr "" -#: ../../content/applications/hr/appraisals.rst:158 +#: ../../content/applications/hr/appraisals.rst:160 msgid "To exit, close the tab. Or, click :guilabel:`→ Edit Survey` at the top of the page to be taken to the detail form for that particular survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:161 +#: ../../content/applications/hr/appraisals.rst:163 msgid "In addition to viewing the responses from past appraisals and surveys, new surveys can also be created from the :guilabel:`360 Feedback` page. Simply click the :guilabel:`New` button in the top-left of the page to create a new survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:165 +#: ../../content/applications/hr/appraisals.rst:167 msgid "For more information on how to create a survey, refer to the :doc:`../marketing/surveys/create` document." msgstr "" -#: ../../content/applications/hr/appraisals.rst:169 +#: ../../content/applications/hr/appraisals.rst:171 msgid "In previous versions of Odoo, this section was referred to as :guilabel:`Surveys`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:172 -msgid "Tags" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:174 -msgid "An additional feature of the *Appraisals* application is the ability to set :ref:`goals ` for employees. On each goal form, there is a field to add tags. The available tags are pulled from a list that is configured from the settings." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:178 -msgid "To view a list of all existing goal tags, and to create new tags, go to the :guilabel:`Goal Tags` page, by navigating to :menuselection:`Appraisals application --> Configuration --> Tags`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:181 -msgid "All currently configured tags are presented in a list view." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:183 -msgid "The *Appraisals* application does **not** have any pre-configured tags, so all tags need to be added from this list, or directly from the goal form." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:186 -msgid "To create a new tag from the :guilabel:`Goal Tags` page, click the :guilabel:`New` button, and a blank line appears." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:189 -msgid "Enter the name of the tag on the line. Then, press the enter key to save the tag, and create a new blank line. Repeat this for all tags that need to be added." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:192 -msgid "The list of tags is automatically arranged in alphabetical order." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:197 +#: ../../content/applications/hr/appraisals.rst:176 msgid "Navigate to the main *Appraisals* dashboard by opening the :guilabel:`Appraisals` application. The :guilabel:`Appraisals` dashboard is the default view." msgstr "" -#: ../../content/applications/hr/appraisals.rst:200 +#: ../../content/applications/hr/appraisals.rst:179 msgid "To view the dashboard at any point in the application, navigate to :menuselection:`Appraisals application --> Appraisals`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:203 +#: ../../content/applications/hr/appraisals.rst:182 msgid "All appraisals are displayed on the dashboard in a Kanban view, by default, with a list of groupings on the left side of the dashboard, including :guilabel:`Company`, :guilabel:`Department`, and :guilabel:`Status`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:207 +#: ../../content/applications/hr/appraisals.rst:186 msgid "Click any grouping option to view appraisals for **only** the chosen selection." msgstr "" -#: ../../content/applications/hr/appraisals.rst:210 +#: ../../content/applications/hr/appraisals.rst:189 msgid "Only groupings with multiple selections appear in the list. For example, if a database only has one company, the :guilabel:`Company` grouping does **not** appear, since there is no other company to select." msgstr "" -#: ../../content/applications/hr/appraisals.rst:214 +#: ../../content/applications/hr/appraisals.rst:193 msgid "Each appraisal card displays the following information:" msgstr "" -#: ../../content/applications/hr/appraisals.rst:216 +#: ../../content/applications/hr/appraisals.rst:195 msgid ":guilabel:`Name`: the employee's name." msgstr "" -#: ../../content/applications/hr/appraisals.rst:217 +#: ../../content/applications/hr/appraisals.rst:196 msgid ":guilabel:`Department`: the department the employee is associated with." msgstr "" -#: ../../content/applications/hr/appraisals.rst:218 +#: ../../content/applications/hr/appraisals.rst:197 msgid ":guilabel:`Company`: the company the employee works for. This only appears in a multi-company database." msgstr "" -#: ../../content/applications/hr/appraisals.rst:220 +#: ../../content/applications/hr/appraisals.rst:199 msgid ":guilabel:`Date`: the date the appraisal was requested, or is scheduled for in the future." msgstr "" -#: ../../content/applications/hr/appraisals.rst:221 +#: ../../content/applications/hr/appraisals.rst:200 msgid ":guilabel:`Activities`: any activities that are scheduled for the appraisal, such as :guilabel:`Meetings` or :guilabel:`Phone Calls.` If no activities are scheduled, an activity can be scheduled from the :guilabel:`🕘 (clock)` icon, located in the bottom-left corner of an appraisal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:225 +#: ../../content/applications/hr/appraisals.rst:204 msgid ":guilabel:`Manager`: the employee's manager, indicated by the profile icon in the bottom-right corner of an appraisal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:227 +#: ../../content/applications/hr/appraisals.rst:206 msgid ":guilabel:`Status banner`: the status of the appraisal. A banner appears if an appraisal is marked as either :guilabel:`Canceled` or :guilabel:`Done`. If no banner is present, that means the appraisal has not happened, or has not been scheduled yet." msgstr "" -#: ../../content/applications/hr/appraisals.rst:231 +#: ../../content/applications/hr/appraisals.rst:210 msgid "To view the details of any appraisal, click on the card to open the appraisal form." msgstr "" @@ -325,87 +294,87 @@ msgstr "" msgid "The Appraisals dashboard with each appraisal in its own box." msgstr "" -#: ../../content/applications/hr/appraisals.rst:238 +#: ../../content/applications/hr/appraisals.rst:217 msgid "New appraisal" msgstr "" -#: ../../content/applications/hr/appraisals.rst:240 +#: ../../content/applications/hr/appraisals.rst:219 msgid "To create a new appraisal, click the :guilabel:`New` button at the top of the :guilabel:`Appraisals` dashboard to load a blank appraisal form. Then, enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/appraisals.rst:243 +#: ../../content/applications/hr/appraisals.rst:222 msgid ":guilabel:`Name`: enter the employee's name." msgstr "" -#: ../../content/applications/hr/appraisals.rst:244 +#: ../../content/applications/hr/appraisals.rst:223 msgid ":guilabel:`Manager`: select the employee's manager from the drop-down menu. The manager is responsible for completing the :guilabel:`Manager's Feedback` section of the appraisal. This field auto-populates after the employee is selected, if they have a manager set on their employee profile." msgstr "" -#: ../../content/applications/hr/appraisals.rst:248 +#: ../../content/applications/hr/appraisals.rst:227 msgid ":guilabel:`Appraisal Date`: the current date is automatically entered in this field. This field is automatically updated once the appraisal is completed or canceled, with the corresponding date of completion or cancellation." msgstr "" -#: ../../content/applications/hr/appraisals.rst:251 +#: ../../content/applications/hr/appraisals.rst:230 msgid ":guilabel:`Department`: select the employee's department from the drop-down menu. This field auto-populates after the employee is selected, if they have a department set on their employee profile." msgstr "" -#: ../../content/applications/hr/appraisals.rst:254 +#: ../../content/applications/hr/appraisals.rst:233 msgid ":guilabel:`Company`: select the employee's company from the drop-down menu. This field auto-populates after the employee is selected, if they have a company set on their employee profile." msgstr "" -#: ../../content/applications/hr/appraisals.rst:259 +#: ../../content/applications/hr/appraisals.rst:238 msgid "The only required fields for the appraisal form are the employee's :guilabel:`Name`, the :guilabel:`Manager`, and the :guilabel:`Company`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:262 +#: ../../content/applications/hr/appraisals.rst:241 msgid "Once the form is complete, click the :guilabel:`Confirm` button to confirm the appraisal request." msgstr "" -#: ../../content/applications/hr/appraisals.rst:264 +#: ../../content/applications/hr/appraisals.rst:243 msgid "Once confirmed, the employee receives an email stating that an appraisal was requested, and is then prompted to schedule an appraisal date." msgstr "" -#: ../../content/applications/hr/appraisals.rst:267 +#: ../../content/applications/hr/appraisals.rst:246 msgid "The status changes to :guilabel:`Confirmed`, and the :guilabel:`Employee's Feedback` section of the :guilabel:`Appraisal` tab is grayed out. The information in that section only appears after the self-assessment is published by the employee. The :guilabel:`Final Rating` field also appears once the appraisal request is confirmed." msgstr "" -#: ../../content/applications/hr/appraisals.rst:272 +#: ../../content/applications/hr/appraisals.rst:251 msgid "If there are any existing appraisals for the employee, an :guilabel:`Appraisal` smart button appears at the top of the page, listing the total number of appraisals there are for the employee." msgstr "" -#: ../../content/applications/hr/appraisals.rst:276 +#: ../../content/applications/hr/appraisals.rst:255 msgid "Ask for feedback" msgstr "" -#: ../../content/applications/hr/appraisals.rst:278 +#: ../../content/applications/hr/appraisals.rst:257 msgid "As part of the appraisal process, the manager can request feedback on an employee from anyone in the company. Feedback is usually requested from co-workers and other people who interact with, or work with, the employee. This is to get a more well-rounded view of the employee, and aid in the manager's overall assessment." msgstr "" -#: ../../content/applications/hr/appraisals.rst:283 +#: ../../content/applications/hr/appraisals.rst:262 msgid "To request feedback, the appraisal **must** be confirmed. Once confirmed, an :guilabel:`Ask Feedback` button appears at the top of the form." msgstr "" -#: ../../content/applications/hr/appraisals.rst:286 +#: ../../content/applications/hr/appraisals.rst:265 msgid "When the :guilabel:`Ask Feedback` button is clicked, an :guilabel:`Ask Feedback` email pop-up form appears, using the :guilabel:`Appraisal: Ask Feedback` email template, which sends the :guilabel:`360 Feedback` survey." msgstr "" -#: ../../content/applications/hr/appraisals.rst:290 +#: ../../content/applications/hr/appraisals.rst:269 msgid "Enter the employees being asked to complete the survey in the :guilabel:`Recipients` field. Multiple employees may be selected." msgstr "" -#: ../../content/applications/hr/appraisals.rst:293 +#: ../../content/applications/hr/appraisals.rst:272 msgid "The email template has dynamic placeholders to personalize the message. Add any additional text to the email, if desired." msgstr "" -#: ../../content/applications/hr/appraisals.rst:296 +#: ../../content/applications/hr/appraisals.rst:275 msgid "If required, an :guilabel:`Answer Deadline` can be added, as well." msgstr "" -#: ../../content/applications/hr/appraisals.rst:298 +#: ../../content/applications/hr/appraisals.rst:277 msgid "If any attachments are needed, click the :guilabel:`Attachments` button, and a file explorer window appears. Navigate to the file(s), select them, then click :guilabel:`Open`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:301 +#: ../../content/applications/hr/appraisals.rst:280 msgid "When the email is ready to send, click :guilabel:`Send.`" msgstr "" @@ -413,27 +382,27 @@ msgstr "" msgid "The email pop-up when requesting feedback from other employees." msgstr "" -#: ../../content/applications/hr/appraisals.rst:308 +#: ../../content/applications/hr/appraisals.rst:287 msgid "Appraisal form" msgstr "" -#: ../../content/applications/hr/appraisals.rst:310 +#: ../../content/applications/hr/appraisals.rst:289 msgid "Once an appraisal is confirmed, the next steps are for the employee to fill out the self-assessment, after which the manager completes their assessment." msgstr "" -#: ../../content/applications/hr/appraisals.rst:316 +#: ../../content/applications/hr/appraisals.rst:295 msgid "Employee's feedback" msgstr "" -#: ../../content/applications/hr/appraisals.rst:318 +#: ../../content/applications/hr/appraisals.rst:297 msgid "To complete their portion of feedback, employees should navigate to the main :menuselection:`Appraisals application` dashboard, where the only entries visible are appraisals for the employee, themselves, and/or anyone they manage and have to provide manager feedback for." msgstr "" -#: ../../content/applications/hr/appraisals.rst:322 +#: ../../content/applications/hr/appraisals.rst:301 msgid "Click on the appraisal to open the appraisal form. Enter responses in the :guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` tab." msgstr "" -#: ../../content/applications/hr/appraisals.rst:325 +#: ../../content/applications/hr/appraisals.rst:304 msgid "When completed, click the :guilabel:`Not Visible to Manager` toggle (the default setting once an appraisal is confirmed). When clicked, the toggle changes to :guilabel:`Visible to Manager`." msgstr "" @@ -441,19 +410,19 @@ msgstr "" msgid "The feedback section for the employee with the toggle button highlighted." msgstr "" -#: ../../content/applications/hr/appraisals.rst:335 +#: ../../content/applications/hr/appraisals.rst:314 msgid "Manager's feedback" msgstr "" -#: ../../content/applications/hr/appraisals.rst:337 +#: ../../content/applications/hr/appraisals.rst:316 msgid "After the employee has completed the :guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` tab, it is time for the manager to fill out the :guilabel:`Manager's Feedback` section." msgstr "" -#: ../../content/applications/hr/appraisals.rst:341 +#: ../../content/applications/hr/appraisals.rst:320 msgid "The manager enters their responses in the fields in the :ref:`same manner as the employee `." msgstr "" -#: ../../content/applications/hr/appraisals.rst:344 +#: ../../content/applications/hr/appraisals.rst:323 msgid "When the feedback section is completed, click the :guilabel:`Not Visible to Employee` toggle (the default setting once an appraisal is confirmed). When clicked, the toggle changes to :guilabel:`Visible to Employee`." msgstr "" @@ -461,31 +430,32 @@ msgstr "" msgid "The feedback section for both employees and managers. The toggle buttons are highlighted." msgstr "" -#: ../../content/applications/hr/appraisals.rst:353 +#: ../../content/applications/hr/appraisals.rst:332 +#: ../../content/applications/hr/recruitment.rst:748 msgid "Skills tab" msgstr "" -#: ../../content/applications/hr/appraisals.rst:355 +#: ../../content/applications/hr/appraisals.rst:334 msgid "Part of an appraisal is evaluating an employee's skills, and tracking their progress over time. The :guilabel:`Skills` tab of the appraisal form auto-populates with the skills from the :doc:`employee form <../hr/employees/new_employee>`, once an appraisal is confirmed." msgstr "" -#: ../../content/applications/hr/appraisals.rst:359 +#: ../../content/applications/hr/appraisals.rst:338 msgid "Each skill is grouped with like skills, and the :guilabel:`Skill Level`, :guilabel:`Progress`, and :guilabel:`Justification` are displayed for each skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:362 +#: ../../content/applications/hr/appraisals.rst:341 msgid "Update any skills, or add any new skills to the :guilabel:`Skills` tab." msgstr "" -#: ../../content/applications/hr/appraisals.rst:364 +#: ../../content/applications/hr/appraisals.rst:343 msgid "If a skill level has increased, a reason for the improved rating can be entered into the :guilabel:`Justification` field, such as `took a fluency language test` or `received Javascript certification`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:368 +#: ../../content/applications/hr/appraisals.rst:347 msgid "Refer to the :ref:`Create a new employee ` document for detailed instructions on adding or updating a skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:371 +#: ../../content/applications/hr/appraisals.rst:350 msgid "After an appraisal is completed, and the skills have been updated, the next time an appraisal is confirmed, the updated skills populate the :guilabel:`Skills` tab." msgstr "" @@ -493,60 +463,60 @@ msgstr "" msgid "The skills tab of an appraisal form, all filled out." msgstr "" -#: ../../content/applications/hr/appraisals.rst:379 +#: ../../content/applications/hr/appraisals.rst:358 msgid "Private note tab" msgstr "" -#: ../../content/applications/hr/appraisals.rst:381 +#: ../../content/applications/hr/appraisals.rst:360 msgid "If managers want to leave notes that are only visible to other managers, they can be entered in the :guilabel:`Private Note` tab. The employee being evaluated does **not** have access to this tab, and the tab does **not** appear on their appraisal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:386 -#: ../../content/applications/hr/recruitment.rst:520 +#: ../../content/applications/hr/appraisals.rst:365 +#: ../../content/applications/hr/recruitment.rst:797 msgid "Schedule a meeting" msgstr "" -#: ../../content/applications/hr/appraisals.rst:388 +#: ../../content/applications/hr/appraisals.rst:367 msgid "Once both portions of an appraisal are completed (the :ref:`employee ` and :ref:`manager ` feedback sections), it is time for the employee and manager to meet and discuss the appraisal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:392 +#: ../../content/applications/hr/appraisals.rst:371 msgid "A meeting can be scheduled in one of two ways: either from the *Appraisals* application dashboard, or from an individual appraisal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:395 +#: ../../content/applications/hr/appraisals.rst:374 msgid "To schedule an appraisal from the dashboard of the *Appraisals* application, first navigate to :menuselection:`Appraisals application --> Appraisals`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:398 +#: ../../content/applications/hr/appraisals.rst:377 msgid "Click the :guilabel:`🕘 (clock)` icon, beneath the appraisal date on the desired appraisal card, and a :guilabel:`Schedule Activity` pop-up window appears. Then, click :guilabel:`+ Schedule an activity` to create a blank activity form." msgstr "" -#: ../../content/applications/hr/appraisals.rst:402 +#: ../../content/applications/hr/appraisals.rst:381 msgid "Select :guilabel:`Meeting` for the :guilabel:`Activity Type` from the drop-down menu. Doing so causes the form to change, so only the :guilabel:`Activity Type` and :guilabel:`Summary` fields appear." msgstr "" -#: ../../content/applications/hr/appraisals.rst:406 +#: ../../content/applications/hr/appraisals.rst:385 msgid "If scheduling an activity other than a meeting, such as a :guilabel:`Call` or a :guilabel:`To-Do`, the fields that appear on the :guilabel:`Schedule Activity` pop-up form change, accordingly." msgstr "" -#: ../../content/applications/hr/appraisals.rst:410 +#: ../../content/applications/hr/appraisals.rst:389 msgid "The :guilabel:`🕘 (clock)` icon may appear as a number of different icons, depending on what, if any, scheduled activities are in place, and the color represents their corresponding due dates." msgstr "" -#: ../../content/applications/hr/appraisals.rst:413 +#: ../../content/applications/hr/appraisals.rst:392 msgid "If no activities are scheduled, that is represented by a gray :guilabel:`🕘 (clock)` icon." msgstr "" -#: ../../content/applications/hr/appraisals.rst:415 +#: ../../content/applications/hr/appraisals.rst:394 msgid "However, if a specific activity is scheduled, the icon may appear as a :guilabel:`📞 (phone)` icon for a phone call, a :guilabel:`👥 (group of people)` icon for a meeting, and so on." msgstr "" -#: ../../content/applications/hr/appraisals.rst:418 +#: ../../content/applications/hr/appraisals.rst:397 msgid "The color of the icon indicates the status; a green icon means an activity is scheduled in the future, and a red icon means the activity is past due." msgstr "" -#: ../../content/applications/hr/appraisals.rst:421 +#: ../../content/applications/hr/appraisals.rst:400 msgid "For more details on activities, refer to the :doc:`../essentials/activities` document." msgstr "" @@ -554,31 +524,31 @@ msgstr "" msgid "The appraisal cards with the various activity icons highlighted." msgstr "" -#: ../../content/applications/hr/appraisals.rst:427 +#: ../../content/applications/hr/appraisals.rst:406 msgid "Enter a brief description in the :guilabel:`Summary` field of the :guilabel:`Schedule Activity` pop-up window, such as `Annual Appraisal for (Employee)`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:430 +#: ../../content/applications/hr/appraisals.rst:409 msgid "Next, click the :guilabel:`Open Calendar` button. From the calendar page that appears, navigate to, and double-click on, the desired date and time for the meeting." msgstr "" -#: ../../content/applications/hr/appraisals.rst:433 +#: ../../content/applications/hr/appraisals.rst:412 msgid "Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, make any desired modifications, such as designating a :guilabel:`Start` time, or giving a :guilabel:`Name` to the meeting." msgstr "" -#: ../../content/applications/hr/appraisals.rst:437 +#: ../../content/applications/hr/appraisals.rst:416 msgid "Add the appraisee in the :guilabel:`Attendees` section, and include anyone else who should be in the meeting, if necessary." msgstr "" -#: ../../content/applications/hr/appraisals.rst:440 +#: ../../content/applications/hr/appraisals.rst:419 msgid "To make the meeting a video call, instead of an in-person meeting, click :guilabel:`+ Odoo meeting`, and a :guilabel:`Videocall URL` link appears in the field." msgstr "" -#: ../../content/applications/hr/appraisals.rst:443 +#: ../../content/applications/hr/appraisals.rst:422 msgid "Once all the desired changes are complete, click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:445 +#: ../../content/applications/hr/appraisals.rst:424 msgid "The meeting now appears on the calendar, and the invited parties are informed, via email." msgstr "" @@ -586,152 +556,56 @@ msgstr "" msgid "The meeting form with all information entered for Ronnie Hart's annual appraisal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:451 +#: ../../content/applications/hr/appraisals.rst:430 msgid "The other way to schedule a meeting is from the individual appraisal form. To do this, navigate to the :menuselection:`Appraisal application` dashboard, then click on an appraisal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:454 +#: ../../content/applications/hr/appraisals.rst:433 msgid "Next, click on the :guilabel:`Meeting` smart button, and the calendar loads. Follow the same directions above to create the meeting." msgstr "" -#: ../../content/applications/hr/appraisals.rst:458 -msgid "If no meetings are scheduled, the :guilabel:`Meeting` smart button says :guilabel:`No Meeting`." +#: ../../content/applications/hr/appraisals.rst:437 +msgid "If no meetings are scheduled, the :guilabel:`Meeting` smart button reads :guilabel:`No Meeting`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:463 -msgid "Goals" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:465 -msgid "The ability to set goals for employees to work toward is an important feature of Odoo *Appraisals*. Goals are typically set during an appraisal, so the employee knows what they need to work toward before their next appraisal." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:469 -msgid "To view all goals, navigate to :menuselection:`Appraisals application --> Goals`. This presents all the goals for every employee, in a default Kanban view." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:472 -msgid "Each goal card contains the following information:" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:474 -msgid ":guilabel:`Skill`: the name of the goal." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:475 -msgid ":guilabel:`Name`: the employee the goal is assigned to." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:476 -msgid ":guilabel:`Deadline`: the due date for the goal." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:477 -msgid ":guilabel:`Progress`: the percentage of competency set for the goal." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:478 -msgid ":guilabel:`Employee`: the profile icon of the employee the goal is assigned to." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:480 -msgid "If a goal is completed, a :guilabel:`Done` banner appears in the top-right corner of the goal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "The goals Kanban view, with nine goal cards." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:487 -msgid "Every individual goal requires its own entry for each employee. If employees have the same goal, a goal card for each employee appears on the list. For example, if both Bob and Sara have the same goal of `Typing`, two cards appear in the Kanban view: one `Typing` goal for Bob, and another `Typing` goal for Sara." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:493 -msgid "New goal" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:495 -msgid "To create a new goal, navigate to :menuselection:`Appraisals application --> Goals`, and click :guilabel:`New` to open a blank goal form." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:498 -msgid "Enter the information on the card. The information requested is all the same information that appears on the :ref:`goal card ` in the Kanban view, with the addition of a :guilabel:`Tags` field and a :guilabel:`Description` tab." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:502 -msgid "The current user populates the :guilabel:`Employee` field by default, and the :guilabel:`Manager` field populates with the manager set on the employee profile." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:505 -msgid "Make any necessary changes to the form, and add any notes that might be useful to clarify the goal in the :guilabel:`Description` tab." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "A goal form filled out for a Python skill, set to 50% proficiency." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:513 -msgid "Completed goals" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:515 -msgid "When a goal has been met, it is important to update the record. A goal can be marked as `Done` in one of two ways: from the main :guilabel:`Goals` dashboard, or from the individual goal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:518 -msgid "To mark a goal as `Done` from the main :guilabel:`Goals` dashboard, click on the :guilabel:`⋮ (three dots)` icon in the top-right of a goal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:522 -msgid "The :guilabel:`⋮ (three dots)` icon **only** appears when the mouse hovers over the corner of a goal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:525 -msgid "Then, click :guilabel:`Mark as Done` from the resulting drop-down menu. A green :guilabel:`Done` banner appears in the top-right corner of the goal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:528 -msgid "To mark a goal as `Done` from the goal card itself, click on a goal card to open that goal's form. Then, click the :guilabel:`Mark as Done` button in the top-left of the form. When clicked, a green :guilabel:`Done` banner appears in the top-right corner of the goal form." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:533 -#: ../../content/applications/hr/attendances.rst:526 -#: ../../content/applications/hr/frontdesk.rst:351 +#: ../../content/applications/hr/appraisals.rst:440 +#: ../../content/applications/hr/attendances.rst:433 +#: ../../content/applications/hr/frontdesk.rst:210 #: ../../content/applications/hr/payroll/reporting.rst:3 -#: ../../content/applications/hr/referrals.rst:753 -#: ../../content/applications/hr/time_off.rst:893 +#: ../../content/applications/hr/referrals.rst:444 +#: ../../content/applications/hr/time_off.rst:830 msgid "Reporting" msgstr "" -#: ../../content/applications/hr/appraisals.rst:535 +#: ../../content/applications/hr/appraisals.rst:442 msgid "The *Appraisals* application tracks two metrics across two different reports: an :ref:`appraisal analysis `, and a :ref:`skills evolution `." msgstr "" -#: ../../content/applications/hr/appraisals.rst:541 +#: ../../content/applications/hr/appraisals.rst:448 msgid "Appraisal analysis" msgstr "" -#: ../../content/applications/hr/appraisals.rst:543 +#: ../../content/applications/hr/appraisals.rst:450 msgid "To access the *Appraisal Analysis* report, navigate to :menuselection:`Appraisals application --> Reporting --> Appraisal Analysis`. This displays a report of all the appraisals in the database, highlighted in different colors to represent their status." msgstr "" -#: ../../content/applications/hr/appraisals.rst:547 +#: ../../content/applications/hr/appraisals.rst:454 msgid "Appraisals in yellow are completed, appraisals in orange are in-progress (the appraisal is confirmed, but not completed), and appraisals in gray are scheduled (according to the :ref:`appraisals/appraisal-plan`), but have not been confirmed yet." msgstr "" -#: ../../content/applications/hr/appraisals.rst:551 +#: ../../content/applications/hr/appraisals.rst:458 msgid "The report displays the whole current year, by default, grouped by department." msgstr "" -#: ../../content/applications/hr/appraisals.rst:553 +#: ../../content/applications/hr/appraisals.rst:460 msgid "To change the calendar view presented, change the date settings in the top-left of the report. The options to display are :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, and :guilabel:`Year`. Use the arrows to move forward or backward in time." msgstr "" -#: ../../content/applications/hr/appraisals.rst:557 +#: ../../content/applications/hr/appraisals.rst:464 msgid "At any point, click the :guilabel:`Today` button to present the calendar to include today's date in the view." msgstr "" -#: ../../content/applications/hr/appraisals.rst:560 +#: ../../content/applications/hr/appraisals.rst:467 msgid "The report can have other filters and groupings set in the :guilabel:`Search...` bar at the top." msgstr "" @@ -739,51 +613,51 @@ msgstr "" msgid "A report showing all the appraisals for the Appraisal Analysis report." msgstr "" -#: ../../content/applications/hr/appraisals.rst:569 +#: ../../content/applications/hr/appraisals.rst:476 msgid "Skills evolution" msgstr "" -#: ../../content/applications/hr/appraisals.rst:571 +#: ../../content/applications/hr/appraisals.rst:478 msgid "To access the *Skills Evolution* report, navigate to :menuselection:`Appraisals application --> Reporting --> Skills Evolution`. This displays a report of all skills, grouped by employee." msgstr "" -#: ../../content/applications/hr/appraisals.rst:574 +#: ../../content/applications/hr/appraisals.rst:481 msgid "All the lines of the report are collapsed, by default. To view the details of a line, click on a line to expand the data." msgstr "" -#: ../../content/applications/hr/appraisals.rst:577 +#: ../../content/applications/hr/appraisals.rst:484 msgid "Each skill has the following information listed:" msgstr "" -#: ../../content/applications/hr/appraisals.rst:579 +#: ../../content/applications/hr/appraisals.rst:486 msgid ":guilabel:`Employee`: name of the employee." msgstr "" -#: ../../content/applications/hr/appraisals.rst:580 +#: ../../content/applications/hr/appraisals.rst:487 msgid ":guilabel:`Skill Type`: the category the skill falls under." msgstr "" -#: ../../content/applications/hr/appraisals.rst:581 +#: ../../content/applications/hr/appraisals.rst:488 msgid ":guilabel:`Skill`: the specific, individual skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:582 +#: ../../content/applications/hr/appraisals.rst:489 msgid ":guilabel:`Previous Skill Level`: the level the employee had previously achieved for the skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:583 +#: ../../content/applications/hr/appraisals.rst:490 msgid ":guilabel:`Previous Skill Progress`: the previous percentage of competency achieved for the skill (based on the :guilabel:`Skill Level`)." msgstr "" -#: ../../content/applications/hr/appraisals.rst:585 +#: ../../content/applications/hr/appraisals.rst:492 msgid ":guilabel:`Current Skill Level`: the current level the employee has achieved for the skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:586 +#: ../../content/applications/hr/appraisals.rst:493 msgid ":guilabel:`Current Skill Progress`: the current percentage of competency achieved for the skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:587 +#: ../../content/applications/hr/appraisals.rst:494 msgid ":guilabel:`Justification`: any notes entered on the skill explaining the progress." msgstr "" @@ -791,248 +665,287 @@ msgstr "" msgid "A report showing all the skills grouped by employee." msgstr "" +#: ../../content/applications/hr/appraisals.rst:501 +msgid ":doc:`appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "The Odoo *Appraisals* application allows managers to set goals for their employees. That way, employees know what to work toward before their next review." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:8 +msgid "To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. This presents all the goals for every employee, in a default Kanban view." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:13 +msgid "Each goal card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid ":guilabel:`Goal`: the name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:16 +msgid ":guilabel:`Employee`: the employee the goal is assigned to." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":icon:`fa-clock-o` :guilabel:`(clock)` icon: displays the corresponding :doc:`activity icon <../../essentials/activities>` for the record. If no activities are scheduled, the default icon is the :icon:`fa-clock-o` :guilabel:`(clock)`. If any activities have been scheduled, the icon represents the activity scheduled soonest." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:21 +msgid ":guilabel:`Deadline`: the due date for the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:22 +msgid ":guilabel:`Progress`: the percentage of competency set for the goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, :guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:24 +msgid ":guilabel:`Employee Icon`: the profile icon of the employee the goal is assigned to." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:26 +msgid "If a goal is completed, a :guilabel:`Done` banner appears in the top-right corner of the goal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "The goals Kanban view, with nine goal cards." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "Every individual goal requires its own record for each employee. If multiple employees have the same goal, a goal card for each employee appears on the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:36 +msgid "For example, if Bob and Sara have the same goal of `Typing`, two cards appear in the Kanban view: one `Typing` goal for Bob, and another `Typing` goal for Sara." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "New goal" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "To create a new goal, navigate to :menuselection:`Appraisals app --> Goals`, and click :guilabel:`New` top-left corner to open a blank goal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "Input the :guilabel:`Goal`, :guilabel:`Employee`, :guilabel:`Progress`, and :guilabel:`Deadline`, information on the goal card, as discussed in the :ref:`goal card ` section of this document." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:49 +msgid "The information requested is all the same information that appears on the goal card in the Kanban view, with the addition of a :guilabel:`Tags` field and a :guilabel:`Description` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:53 +msgid "The *Appraisals* application does **not** have any pre-configured tags, so all tags need to be added. To add a tag, enter the name of the tag on the line, then click :guilabel:`Create \"(tag)\"`. Repeat this for all tags that need to be added." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:57 +msgid "The current user populates the :guilabel:`Employee` field, by default, and the :guilabel:`Manager` field populates with the manager set on the employee profile." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:60 +msgid "Make any necessary changes to the form, and add any notes that might be useful to clarify the goal in the :guilabel:`Description` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A goal form filled out for a Python skill, set to 50% proficiency." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:68 +msgid "Completed goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:70 +msgid "When a goal has been met, it is important to update the record. A goal can be marked as `Done` in one of two ways: from the main :guilabel:`Goals` dashboard, or from the individual goal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "To mark a goal as `Done` from the main :guilabel:`Goals` dashboard, click on the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in the top-right of a goal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:77 +msgid "The :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon **only** appears when the mouse hovers over the top-right corner of a goal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:80 +msgid "Then, click :guilabel:`Mark as Done` from the resulting drop-down menu. A green :guilabel:`Done` banner appears in the top-right corner of the goal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:83 +msgid "To mark a goal as `Done` from the goal card itself, click on a goal card to open that goal's form. Then, click the :guilabel:`Mark as Done` button in the top-left of the form. When clicked, a green :guilabel:`Done` banner appears in the top-right corner of the goal form." +msgstr "" + #: ../../content/applications/hr/attendances.rst:5 msgid "Attendances" msgstr "" -#: ../../content/applications/hr/attendances.rst:12 +#: ../../content/applications/hr/attendances.rst:7 msgid "Odoo's *Attendances* application functions as a time clock. Employees are able to check in and out of work using a dedicated device in kiosk mode, while users are also able to check in and out of work directly from the database. Managers can quickly see who is available at any given time, create reports to see everyone's hours, and gain insights on which employees are working overtime, or checking out of work earlier than expected." msgstr "" -#: ../../content/applications/hr/attendances.rst:21 +#: ../../content/applications/hr/attendances.rst:16 msgid "Access rights" msgstr "" -#: ../../content/applications/hr/attendances.rst:23 -msgid "It is important to understand how the different access rights affect what users can access in the *Attendances* application." +#: ../../content/applications/hr/attendances.rst:18 +msgid "It is important to understand how the different access rights affect what options and features users can access in the *Attendances* application." msgstr "" -#: ../../content/applications/hr/attendances.rst:26 -msgid "Every user in the database is always able to access their own information on the dashboard and can check in and out directly from the database. Access to all the other features is determined by access rights." +#: ../../content/applications/hr/attendances.rst:21 +msgid "Every user in the database is able to check in and out directly from the database, without needing access to the *Attendances* application. Additionally, all users can access their own attendance records from their employee form in the *Employees* app." msgstr "" -#: ../../content/applications/hr/attendances.rst:30 -msgid "To see what access rights a user has, navigate to the :menuselection:`Settings application --> Users & Companies: Users`, and click on an individual user. The :guilabel:`Access Rights` tab is visible by default. Scroll down to the :guilabel:`Human Resources` section to see the setting. For the :guilabel:`Attendances` field, the options are either to leave the field blank or select :guilabel:`Administrator`." +#: ../../content/applications/hr/attendances.rst:25 +msgid "Access to both the *Attendances* application, and the various features within the application is determined by access rights." msgstr "" -#: ../../content/applications/hr/attendances.rst:36 -msgid "If the :guilabel:`Administrator` option is selected, the user has full access to the entire *Attendances* application, with no restrictions. They can view all employee attendance records, enter kiosk mode from the application, access all reporting metrics, and make modifications to the settings." +#: ../../content/applications/hr/attendances.rst:28 +msgid "To see what access rights a user has, navigate to the :menuselection:`Settings app --> Users & Companies: Users`, and click on an individual user. The :guilabel:`Access Rights` tab is visible by default. Scroll down to the :guilabel:`Human Resources` section to see the setting. For the :guilabel:`Attendances` field, the options are either to leave the field blank or select :guilabel:`Administrator`." msgstr "" -#: ../../content/applications/hr/attendances.rst:41 -msgid "If left blank, the user can only view their own information on the *Attendances* application dashboard and can view their own personal attendance records under the reporting feature. All other attendance records are hidden from view on the report. There is no access to either the kiosk mode or the configuration menu." +#: ../../content/applications/hr/attendances.rst:34 +msgid "If the :guilabel:`Administrator` option is selected, the user has full access to the entire *Attendances* application, with no restrictions. They can view all employee attendance records, enter *Kiosk mMode* from the application, access all reporting metrics, and make modifications to the settings. If left blank, the user does **not** have access to the *Attendances* application." msgstr "" -#: ../../content/applications/hr/attendances.rst:49 +#: ../../content/applications/hr/attendances.rst:42 msgid "Approvers" msgstr "" -#: ../../content/applications/hr/attendances.rst:51 +#: ../../content/applications/hr/attendances.rst:44 msgid "The **only** other scenario where different information may be accessible in the *Attendances* application is for approvers. If a user does *not* have administrative rights for the *Attendances* application, but they are set as an employee's approver for the *Attendances* application, that user is able to view the attendance records for that specific employee, as well as make modifications to that employee's attendance records, if necessary. This applies to all employees for whom the user is listed as the *Attendances* application approver. Approvers are typically managers, though this is not required." msgstr "" -#: ../../content/applications/hr/attendances.rst:59 +#: ../../content/applications/hr/attendances.rst:52 msgid "To see who the attendance approver is for an employee, navigate to the :menuselection:`Employees application` and click on the specific employee. Click on the :guilabel:`Work Information` tab, scroll to the :guilabel:`Approvers` section, and check the :guilabel:`Attendance` field. The person selected is able to view that employees' attendance records, both on the *Attendances* application dashboard as well as in the attendance reports, and make modifications to their records." msgstr "" -#: ../../content/applications/hr/attendances.rst:68 +#: ../../content/applications/hr/attendances.rst:61 msgid "Few configurations are needed in the *Attendances* application. Determining how employees check in and out, defining how the kiosks function, and determining how extra hours are computed are all set in the Configuration menu. Navigate to the :menuselection:`Attendances application --> Configuration` to access the configuration menu." msgstr "" -#: ../../content/applications/hr/attendances.rst:74 +#: ../../content/applications/hr/attendances.rst:67 msgid "Modes" msgstr "" -#: ../../content/applications/hr/attendances.rst:78 +#: ../../content/applications/hr/attendances.rst:71 msgid ":guilabel:`Kiosk Mode`: using the drop-down menu, select how an employee checks in when using a kiosk. Options are :guilabel:`Barcode/RFID`, :guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual Selection`." msgstr "" -#: ../../content/applications/hr/attendances.rst:83 +#: ../../content/applications/hr/attendances.rst:76 msgid "The *Barcode* application **does not** need to be installed to use one of the Barcode/RFID settings." msgstr "" -#: ../../content/applications/hr/attendances.rst:86 +#: ../../content/applications/hr/attendances.rst:79 msgid ":guilabel:`Attendances from Backend`: activate this selection to allow users to check in and out directly from the Odoo database. If this is not activated, users must use a kiosk to check in and out of work." msgstr "" -#: ../../content/applications/hr/attendances.rst:93 +#: ../../content/applications/hr/attendances.rst:86 msgid "Kiosk settings" msgstr "" -#: ../../content/applications/hr/attendances.rst:95 +#: ../../content/applications/hr/attendances.rst:88 msgid "This section only needs to be configured if employees use kiosks for checking in and out. If kiosks are **not** being used, modifying any of these fields does **not** adversely affect the *Attendances* application." msgstr "" -#: ../../content/applications/hr/attendances.rst:99 +#: ../../content/applications/hr/attendances.rst:92 msgid ":guilabel:`Barcode Source`: this setting appears **only** if either of the two Barcode/RFID selections were configured for the :ref:`Kiosk Mode ` setting. Select how barcodes are scanned at the kiosk, either with a dedicated barcode :guilabel:`Scanner`, or the device's :guilabel:`Front Camera`, or :guilabel:`Back Camera`." msgstr "" -#: ../../content/applications/hr/attendances.rst:103 +#: ../../content/applications/hr/attendances.rst:96 msgid ":guilabel:`Employee PIN Identification`: activate this option if employees should use a unique PIN to check in. PINs are configured on each individual employee record. Refer to the :doc:`../hr/employees/new_employee` documentation for more information on setting up PINs." msgstr "" -#: ../../content/applications/hr/attendances.rst:106 +#: ../../content/applications/hr/attendances.rst:99 msgid ":guilabel:`Display Time`: set the duration (in seconds) the check in and check out confirmation screen remains on the kiosk before going back to the main check in screen." msgstr "" -#: ../../content/applications/hr/attendances.rst:108 +#: ../../content/applications/hr/attendances.rst:101 msgid ":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) to use a device as a kiosk without having to sign in to the Odoo database. When setting up a kiosk device, navigate to this unique web address in a web browser to present the Attendances application kiosk." msgstr "" -#: ../../content/applications/hr/attendances.rst:113 +#: ../../content/applications/hr/attendances.rst:106 msgid "These kiosk URLs are **not** secured with any type of access code. Anyone who has the URL can access the Attendances application kiosk. If the URL is compromised for any reason, such as in the event of a security breach, click :guilabel:`Generate a new Kiosk Mode URL`, located beneath the link, to generate a new URL and update the kiosk accordingly." msgstr "" -#: ../../content/applications/hr/attendances.rst:119 +#: ../../content/applications/hr/attendances.rst:112 msgid "Extra hours" msgstr "" -#: ../../content/applications/hr/attendances.rst:121 +#: ../../content/applications/hr/attendances.rst:114 msgid "This section specifies how extra time is calculated, including when extra time is counted and what time is not logged." msgstr "" -#: ../../content/applications/hr/attendances.rst:124 +#: ../../content/applications/hr/attendances.rst:117 msgid ":guilabel:`Count of Extra Hours`: enable this box to allow employees to log extra hours beyond their set working hours (sometimes referred to as *overtime*). Activating this selection displays the following settings as well. If this is not activated, no other configurations appear." msgstr "" -#: ../../content/applications/hr/attendances.rst:128 +#: ../../content/applications/hr/attendances.rst:121 msgid ":guilabel:`Start From`: the current date is automatically entered in this field. If desired, click on this field and use the calendar selector to modify the start date on which extra hours are logged." msgstr "" -#: ../../content/applications/hr/attendances.rst:131 +#: ../../content/applications/hr/attendances.rst:124 msgid ":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in minutes, that is **not** counted towards an employee's overtime. When an employee checks out, and the extra time logged is below the specified minutes, the extra time is **not** counted as overtime for the employee." msgstr "" -#: ../../content/applications/hr/attendances.rst:135 +#: ../../content/applications/hr/attendances.rst:128 msgid ":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, in minutes, that an employee is given, that does **not** adversely affect their attendance if they log less time than their working hours. When an employee checks out, and the total time logged for the day is less than their specified working hours and less than this specified grace period, they are **not** penalized for their reduced hours." msgstr "" -#: ../../content/applications/hr/attendances.rst:142 +#: ../../content/applications/hr/attendances.rst:135 msgid "A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and the working hours for the entire company are set from 9:00 AM to 5:00 PM." msgstr "" -#: ../../content/applications/hr/attendances.rst:145 +#: ../../content/applications/hr/attendances.rst:138 msgid "If an employee checks in at 9:00 AM, and checks out at 5:14 PM, the extra 14 minutes are **not** counted towards their overtime." msgstr "" -#: ../../content/applications/hr/attendances.rst:148 +#: ../../content/applications/hr/attendances.rst:141 msgid "If an employee checks in at 9:05 AM, and checks out at 4:55 PM, even though they logged a total of 10 minutes less than their full working hours, they are **not** penalized for this discrepancy." msgstr "" -#: ../../content/applications/hr/attendances.rst:152 +#: ../../content/applications/hr/attendances.rst:145 msgid ":guilabel:`Display Extra Hours`: activate this box to display the extra hours logged by an employee when they check out with a kiosk, or when a user checks out in the database." msgstr "" -#: ../../content/applications/hr/attendances.rst:156 +#: ../../content/applications/hr/attendances.rst:149 msgid "Employees are still able to log overtime hours even if the :guilabel:`Count of Extra Hours` option is not activated. The difference is that when :guilabel:`Count of Extra Hours` is activated, the extra hours can be :ref:`deducted from an approved time off request `." msgstr "" -#: ../../content/applications/hr/attendances.rst:164 -msgid "Check in and out via the database" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:166 -msgid "Odoo's *Attendances* application allows users who are logged into the database to check in and out, without needing to go into the *Attendances* application, or use a kiosk. For some smaller companies, where every employee is also a user, this feature may be useful." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:170 -msgid "A user can check in and out on the main database dashboard, as well as in any application. In the upper right corner of the top main menu, which is always visible regardless of what application the user is in, a :guilabel:`🔴 (red circle)` or :guilabel:`🟢 (green circle)` is visible. Click on the colored circle to reveal the attendance widget, enabling the user to check in and/or out." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:-1 -#: ../../content/applications/hr/attendances.rst:-1 -msgid "Top right main menu with check in button highlighted." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:180 -msgid "Check in" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:182 -msgid "If the attendance widget circle is red, this indicates the user is not currently checked in. Click the :guilabel:`🔴 (red circle)` and the attendance widget appears, displaying a green :guilabel:`Check in ➡️` button." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:190 -msgid "When the user checks in from the database, the *Attendances* app logs the location details for the user, including the IP Address and GPS coordinates." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:194 -msgid "For the *Attendances* app to log the location details, the user must allow their computer to access their location information." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:197 -msgid "If the user has not checked in and out already during the current work day, this button is the only visible item in the widget. If the user has previously checked in and out, a :guilabel:`Total today` field appears above the button, and the total amount of time that has been logged for the day appears beneath that field, in an :guilabel:`HH:MM` (hours:minutes) format." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:202 -msgid "Click the :guilabel:`Check in ➡️` button to check in. The :guilabel:`🔴 (red circle)` in the top menu changes to green, and the widget changes appearance as well. The widget updates to reflect that the user has checked in, by changing the green :guilabel:`Check in ➡️` button to a yellow :guilabel:`Check out ➡️` button." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:207 -msgid "Click anywhere on the screen to close the attendance widget." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:210 -msgid "Check out" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:212 -msgid "If the user is checking out for the first time, :guilabel:`Since HH:MM (AM/PM)` appears at the top of the widget, with the time the user checked in populating the time field. Beneath that line, :guilabel:`HH:MM` is displayed, indicating the hours and minutes that have elapsed since checking in. As time passes, this value is updated to reflect the hours and minutes that have passed since the user checked in." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:218 -msgid "If the user has previously checked in and out, additional fields are presented. A :guilabel:`Before HH:MM (AM/PM)` field appears in addition to the :guilabel:`Since HH:MM (AM/PM)` field. The time displayed in both of these fields are populated with the most recent check in time, and will match. Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged hours are displayed, in an :guilabel:`HH:MM` (hours:minutes) format." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:224 -msgid "In addition, beneath both of these fields, a :guilabel:`Total today` field appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that will be logged for the user, if they were to log out at that moment." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:228 -msgid "As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and :guilabel:`Total today` fields are updated live. To check out, click the yellow :guilabel:`Check out ➡️` button. The attendance widget updates again, displaying the :guilabel:`Total today` field with the logged time, and the yellow :guilabel:`Check out ➡️` button changes to a green :guilabel:`Check in ➡️` button." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:233 -msgid "When the user checks out from the database, the *Attendances* app logs the location details for the user. This information is **only** logged if the user allows their computer to access this information." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:-1 -msgid "The pop-up that appears when an employee checks in inside the database." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:242 -msgid "There is no limit to the amount of times a user can check in and check out. Users are able to check in and out without any time elapsing (a value of 00:00). Each time an employee logs in and out, the information is stored and appears on the dashboard, including check ins and check outs with no time value." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:250 +#: ../../content/applications/hr/attendances.rst:157 msgid "Kiosk mode" msgstr "" -#: ../../content/applications/hr/attendances.rst:252 +#: ../../content/applications/hr/attendances.rst:159 msgid "Some companies may opt to use a dedicated device (a laptop or desktop PC, a tablet, or a mobile phone) for employees to check in and check out from. Kiosk mode is used for these scenarios." msgstr "" -#: ../../content/applications/hr/attendances.rst:256 +#: ../../content/applications/hr/attendances.rst:163 msgid "If users check in and out using either a badge or an RFID, then an accessible device in kiosk mode **must** be available to check in and check out using these two methods." msgstr "" -#: ../../content/applications/hr/attendances.rst:259 +#: ../../content/applications/hr/attendances.rst:166 msgid "Entering kiosk mode is only available for users with specific :ref:`access rights `." msgstr "" -#: ../../content/applications/hr/attendances.rst:262 +#: ../../content/applications/hr/attendances.rst:169 msgid "Kiosk mode can be activated in three different ways:" msgstr "" -#: ../../content/applications/hr/attendances.rst:264 +#: ../../content/applications/hr/attendances.rst:171 msgid "Navigate to the :guilabel:`Attendances` application, and click :guilabel:`Kiosk Mode` in the top menu. The device then enters kiosk mode." msgstr "" -#: ../../content/applications/hr/attendances.rst:266 +#: ../../content/applications/hr/attendances.rst:173 msgid "Navigate to the :menuselection:`Attendances application --> Configuration`. In the :guilabel:`Kiosk Settings` section, click on the link in the :guilabel:`Attendance Kiosk Url` field. A new tab opens in kiosk mode. It is recommended to close the database tab to keep the database secure." msgstr "" -#: ../../content/applications/hr/attendances.rst:270 +#: ../../content/applications/hr/attendances.rst:177 msgid "Navigate to the :menuselection:`Attendances application --> Configuration`. In the :guilabel:`Kiosk Settings` section, click :guilabel:`Copy` next to the link beneath the :guilabel:`Attendance Kiosk Url` field. Paste this URL into a web browser on the kiosk device and navigate to it." msgstr "" @@ -1040,15 +953,15 @@ msgstr "" msgid "The Attendances Kiosk URL field in the settings section of the Attendances application." msgstr "" -#: ../../content/applications/hr/attendances.rst:279 +#: ../../content/applications/hr/attendances.rst:186 msgid "As a security measure, once a device is in kiosk mode, it is not possible to exit kiosk mode and go back into the database without signing back in. To exit kiosk mode, click the back button in the web browser. This logs the user out of the database, and returns to the main log in screen. This adds an extra layer of security, preventing anyone from accessing the database." msgstr "" -#: ../../content/applications/hr/attendances.rst:285 +#: ../../content/applications/hr/attendances.rst:192 msgid "Badge" msgstr "" -#: ../../content/applications/hr/attendances.rst:287 +#: ../../content/applications/hr/attendances.rst:194 msgid "To check in or out using a badge, tap the :guilabel:`📷 (camera) Tap to scan` image in the center of the kiosk. Then, scan the barcode on the badge using the method configured in the :ref:`kiosk settings ` section of the configuration menu. Options are a dedicated barcode scanning device, or the kiosk's front or back camera. Once the barcode is scanned, the employee is checked in or out, and a :ref:`confirmation message ` appears with all the check in or check out information." msgstr "" @@ -1056,47 +969,47 @@ msgstr "" msgid "The Attendances Kiosk view displaying the scan badge image." msgstr "" -#: ../../content/applications/hr/attendances.rst:299 +#: ../../content/applications/hr/attendances.rst:206 msgid "RFID" msgstr "" -#: ../../content/applications/hr/attendances.rst:301 +#: ../../content/applications/hr/attendances.rst:208 msgid "To check in or out using an RFID key fob, simply scan the fob with an RFID reader. Once scanned, the employee is then either checked in or checked out, and a :ref:`confirmation message ` appears with all the check in or check out information." msgstr "" -#: ../../content/applications/hr/attendances.rst:306 +#: ../../content/applications/hr/attendances.rst:213 msgid "Manually" msgstr "" -#: ../../content/applications/hr/attendances.rst:308 +#: ../../content/applications/hr/attendances.rst:215 msgid "Users who do not have a scannable badge or an RFID fob can manually check in and out at a kiosk. Tap the :guilabel:`Identify Manually` button on the kiosk, and a screen with all the employees that can be checked in or out appears. This is the same view as in the *Employees* application dashboard. Tap on the person, and they are either checked in or checked out, and a :ref:`confirmation message ` appears." msgstr "" -#: ../../content/applications/hr/attendances.rst:314 +#: ../../content/applications/hr/attendances.rst:221 msgid "When a large number of employees appear in the list, making scrolling inefficient, there are two ways to quickly find a specific person:" msgstr "" -#: ../../content/applications/hr/attendances.rst:317 +#: ../../content/applications/hr/attendances.rst:224 msgid ":guilabel:`Search...`: tap on the :guilabel:`Search...` field and enter the person's name. As the name is typed in, the matching results are displayed on the screen." msgstr "" -#: ../../content/applications/hr/attendances.rst:319 +#: ../../content/applications/hr/attendances.rst:226 msgid ":guilabel:`Department`: to quickly filter the presented employees, tap on a department to display only those employees that are part of that department. The :guilabel:`Departments` are listed on the left side of the screen, and the number at the end of each department indicates how many employees are part of the department, and is displayed when selected." msgstr "" -#: ../../content/applications/hr/attendances.rst:325 +#: ../../content/applications/hr/attendances.rst:232 msgid "PIN" msgstr "" -#: ../../content/applications/hr/attendances.rst:327 +#: ../../content/applications/hr/attendances.rst:234 msgid "If the :guilabel:`Employee PIN Identification` option was activated in the :ref:`kiosk settings ` section of the configuration menu, the employee is prompted to enter a PIN when manually checking in or out." msgstr "" -#: ../../content/applications/hr/attendances.rst:331 +#: ../../content/applications/hr/attendances.rst:238 msgid "After the employee is selected, a number pad appears with a message. When checking in, :guilabel:`(Employee) Welcome! Please enter your PIN to check in` appears above the numbers. When checking out, :guilabel:`(Employee) Want to check out? Please enter your PIN to check out` appears above the numbers." msgstr "" -#: ../../content/applications/hr/attendances.rst:336 +#: ../../content/applications/hr/attendances.rst:243 msgid "Tap in the PIN using the number pad, then tap :guilabel:`OK` when done. The employee is then checked in or out, and a :ref:`confirmation message ` appears." msgstr "" @@ -1104,15 +1017,15 @@ msgstr "" msgid "The pop-up that appears when prompted to enter a pin." msgstr "" -#: ../../content/applications/hr/attendances.rst:346 +#: ../../content/applications/hr/attendances.rst:253 msgid "Confirmation message" msgstr "" -#: ../../content/applications/hr/attendances.rst:348 +#: ../../content/applications/hr/attendances.rst:255 msgid "When an employee checks in or out, a confirmation message appears with all the check in or check out information. When checking in, a welcome message appears, as well as the date and time of check in. An :guilabel:`Hours Previously Today: HH:MM` field also appears, displaying any time already logged for that employee for the day. If no time has already been logged, the value displayed is `00:00`. Beneath the message is an :guilabel:`OK` button. To exit the screen before the preset time in the kiosk, tap the :guilabel:`OK` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:355 +#: ../../content/applications/hr/attendances.rst:262 msgid "When checking out, the screen displays a goodbye message, with the date and time of check out, and the total hours logged for the day. Beneath the message is a :guilabel:`Goodbye` button. To exit the screen before the preset time, tap the :guilabel:`Goodbye` button." msgstr "" @@ -1120,28 +1033,28 @@ msgstr "" msgid "The goodbye message with all the employee's check out information." msgstr "" -#: ../../content/applications/hr/attendances.rst:364 -#: ../../content/applications/hr/time_off.rst:745 +#: ../../content/applications/hr/attendances.rst:271 +#: ../../content/applications/hr/time_off.rst:681 msgid "Overview" msgstr "" -#: ../../content/applications/hr/attendances.rst:366 +#: ../../content/applications/hr/attendances.rst:273 msgid "When entering the *Attendances* application, the :guilabel:`Overview` dashboard is presented, containing all the check in and check out information for the signed in user. If the user has specific :ref:`access rights ` and/or are :ref:`approvers ` for specific employees, then those additional employee's check in and check out information is also visible on the :guilabel:`Overview` dashboard." msgstr "" -#: ../../content/applications/hr/attendances.rst:373 +#: ../../content/applications/hr/attendances.rst:280 msgid "Views" msgstr "" -#: ../../content/applications/hr/attendances.rst:375 +#: ../../content/applications/hr/attendances.rst:282 msgid "To change the view from the default Gantt chart to a list view, click the :guilabel:`List` icon in the top right of the dashboard, beneath the user's photo. To switch back to the Gantt chart, click the :guilabel:`Gantt` button, located next to the :guilabel:`List` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:379 +#: ../../content/applications/hr/attendances.rst:286 msgid "The default view presents the current day's information. To present the information for the :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year`, click on the :guilabel:`Day` button to reveal a drop-down, displaying those other options. Select the desired view, and the dashboard updates, presenting the selected information. To change the :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` presented, click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` buttons on either side of the drop-down menu. To jump back to a view containing the current day, click the :guilabel:`Today` button. This refreshes the dashboard, presenting information containing the current day's information." msgstr "" -#: ../../content/applications/hr/attendances.rst:388 +#: ../../content/applications/hr/attendances.rst:295 msgid "In the :guilabel:`Day` view, the column for the current hour is highlighted in yellow. If the :guilabel:`Week` or :guilabel:`Month` view is selected, the column for the current day is highlighted. If the :guilabel:`Year` view is selected, the current month is highlighted." msgstr "" @@ -1150,148 +1063,148 @@ msgid "The overview dashboard presenting the information for the week, with the "highlighted." msgstr "" -#: ../../content/applications/hr/attendances.rst:397 +#: ../../content/applications/hr/attendances.rst:304 msgid "Any entries that have errors appear in red, indicating they need to be resolved by a user with the proper :ref:`access rights ` and/or are :ref:`approvers ` for the employee(s) with the errors." msgstr "" -#: ../../content/applications/hr/attendances.rst:404 +#: ../../content/applications/hr/attendances.rst:311 msgid "Filters and groups" msgstr "" -#: ../../content/applications/hr/attendances.rst:406 +#: ../../content/applications/hr/attendances.rst:313 msgid "To filter the results in the overview dashboard, or to present different groups of information, click the :guilabel:`🔻 (triangle drop down)` button in the right side of the :guilabel:`Search` bar above the dashboard, and select one of the available :guilabel:`Filters` or :guilabel:`Group By` options. There are several pre-configured filters and groups to choose from, as well as an option to create custom ones." msgstr "" -#: ../../content/applications/hr/attendances.rst:413 +#: ../../content/applications/hr/attendances.rst:320 #: ../../content/applications/hr/payroll/reporting.rst:276 msgid "Filters" msgstr "" -#: ../../content/applications/hr/attendances.rst:415 +#: ../../content/applications/hr/attendances.rst:322 msgid "The default filters that can be selected are:" msgstr "" -#: ../../content/applications/hr/attendances.rst:417 +#: ../../content/applications/hr/attendances.rst:324 msgid ":guilabel:`My Attendances`: this filter only presents the user's attendance data." msgstr "" -#: ../../content/applications/hr/attendances.rst:418 +#: ../../content/applications/hr/attendances.rst:325 msgid ":guilabel:`My Team`: this filter presents the attendance data for the user's team." msgstr "" -#: ../../content/applications/hr/attendances.rst:419 +#: ../../content/applications/hr/attendances.rst:326 msgid ":guilabel:`At Work`: this filter displays the attendance data for everyone currently checked in." msgstr "" -#: ../../content/applications/hr/attendances.rst:420 +#: ../../content/applications/hr/attendances.rst:327 msgid ":guilabel:`Errors`: this filter displays any entries with :ref:`errors ` that need to be resolved." msgstr "" -#: ../../content/applications/hr/attendances.rst:422 +#: ../../content/applications/hr/attendances.rst:329 msgid ":guilabel:`Check In`: this filter has a drop-down to further select a specific time period. Select the desired time period from the options presented, a specific month, quarter, or year." msgstr "" -#: ../../content/applications/hr/attendances.rst:424 +#: ../../content/applications/hr/attendances.rst:331 msgid ":guilabel:`Last 7 days`: this filter presents the attendance data for the last seven days." msgstr "" -#: ../../content/applications/hr/attendances.rst:425 +#: ../../content/applications/hr/attendances.rst:332 msgid ":guilabel:`Add Custom Filter`: create a custom filter using the pop-up that appears when this is selected." msgstr "" -#: ../../content/applications/hr/attendances.rst:429 +#: ../../content/applications/hr/attendances.rst:336 msgid "Groups" msgstr "" -#: ../../content/applications/hr/attendances.rst:431 +#: ../../content/applications/hr/attendances.rst:338 msgid "The default groups that can be selected are:" msgstr "" -#: ../../content/applications/hr/attendances.rst:433 +#: ../../content/applications/hr/attendances.rst:340 msgid ":guilabel:`Check In`: this grouping presents a drop-down menu containing the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time period to display all the check-in information, grouped by the selected time period." msgstr "" -#: ../../content/applications/hr/attendances.rst:437 +#: ../../content/applications/hr/attendances.rst:344 msgid ":guilabel:`Employee`: this group presents the attendance data organized by employee." msgstr "" -#: ../../content/applications/hr/attendances.rst:438 +#: ../../content/applications/hr/attendances.rst:345 msgid ":guilabel:`Check Out`: this grouping presents a drop-down menu containing the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time period to display all the check-out information, grouped by the selected time period." msgstr "" -#: ../../content/applications/hr/attendances.rst:442 +#: ../../content/applications/hr/attendances.rst:349 msgid ":guilabel:`Add Custom Group`: this option displays a drop-down menu with a variety of options to group the attendance data by, including :guilabel:`City`, :guilabel:`Country`, :guilabel:`Mode`, and :guilabel:`IP Address`." msgstr "" -#: ../../content/applications/hr/attendances.rst:449 +#: ../../content/applications/hr/attendances.rst:356 msgid "Attendance log details" msgstr "" -#: ../../content/applications/hr/attendances.rst:451 +#: ../../content/applications/hr/attendances.rst:358 msgid "Odoo captures various time and location details when a user checks in and out. The specific details provided are determined by the method the user checked in and out." msgstr "" -#: ../../content/applications/hr/attendances.rst:454 +#: ../../content/applications/hr/attendances.rst:361 msgid "To view the specific check in and/or check out details for an employee, click on an individual entry in the overview dashboard." msgstr "" -#: ../../content/applications/hr/attendances.rst:457 +#: ../../content/applications/hr/attendances.rst:364 msgid "A detailed attendance log for the user appears in a pop-up window. To close the detailed attendance log, click the :guilabel:`Save & Close` button in the bottom-left corner of the form." msgstr "" -#: ../../content/applications/hr/attendances.rst:460 +#: ../../content/applications/hr/attendances.rst:367 msgid "The detailed attendance log contains the following information:" msgstr "" -#: ../../content/applications/hr/attendances.rst:463 +#: ../../content/applications/hr/attendances.rst:370 msgid "Main details" msgstr "" -#: ../../content/applications/hr/attendances.rst:465 +#: ../../content/applications/hr/attendances.rst:372 msgid ":guilabel:`Employee`: the name of the employee." msgstr "" -#: ../../content/applications/hr/attendances.rst:466 +#: ../../content/applications/hr/attendances.rst:373 msgid ":guilabel:`Check In`: the date and time the employee checked in." msgstr "" -#: ../../content/applications/hr/attendances.rst:467 +#: ../../content/applications/hr/attendances.rst:374 msgid ":guilabel:`Check Out`: the date and time the employee checked out. This only appears if the employee has checked out." msgstr "" -#: ../../content/applications/hr/attendances.rst:469 +#: ../../content/applications/hr/attendances.rst:376 msgid ":guilabel:`Worked Hours`: the total amount of time the employee logged for the day, in an hour and minute format (HH:MM). This value calculates all the checks in and check outs for the day, if the employee checked in and out multiple times." msgstr "" -#: ../../content/applications/hr/attendances.rst:472 +#: ../../content/applications/hr/attendances.rst:379 msgid ":guilabel:`Extra Hours`: any extra hours the employee logged that is beyond their expected working hours." msgstr "" -#: ../../content/applications/hr/attendances.rst:476 +#: ../../content/applications/hr/attendances.rst:383 msgid "Check in/check out details" msgstr "" -#: ../../content/applications/hr/attendances.rst:478 +#: ../../content/applications/hr/attendances.rst:385 msgid "The following information appears for both the :guilabel:`Check In` and :guilabel:`Check Out` sections." msgstr "" -#: ../../content/applications/hr/attendances.rst:481 +#: ../../content/applications/hr/attendances.rst:388 msgid ":guilabel:`Mode`: the method with which the attendance information was gathered. :guilabel:`Systray` is displayed if the employee logged in and out :ref:`directly from the database `, :guilabel:`Manual` is displayed if the employee logged in and out :ref:`using an attendance kiosk `." msgstr "" -#: ../../content/applications/hr/attendances.rst:485 +#: ../../content/applications/hr/attendances.rst:392 msgid ":guilabel:`IP Address`: the IP address for the computer the employee used to log in or out." msgstr "" -#: ../../content/applications/hr/attendances.rst:486 +#: ../../content/applications/hr/attendances.rst:393 msgid ":guilabel:`Browser`: the web browser the employee used to log in or out." msgstr "" -#: ../../content/applications/hr/attendances.rst:487 +#: ../../content/applications/hr/attendances.rst:394 msgid ":guilabel:`Localization`: the city and country associated with the computer's IP address." msgstr "" -#: ../../content/applications/hr/attendances.rst:488 +#: ../../content/applications/hr/attendances.rst:395 msgid ":guilabel:`GPS Coordinates`: the specific coordinates when the user logged in or out. To view the specific coordinates on a map, click the :guilabel:`→ View on Maps` button beneath the :guilabel:`GPS Coordinates`. This opens a map in a new browser tab, with the specific location pointed out." msgstr "" @@ -1299,20 +1212,20 @@ msgstr "" msgid "The detailed information for an attendance entry." msgstr "" -#: ../../content/applications/hr/attendances.rst:498 +#: ../../content/applications/hr/attendances.rst:405 #: ../../content/applications/hr/lunch/orders.rst:84 msgid "Errors" msgstr "" -#: ../../content/applications/hr/attendances.rst:500 +#: ../../content/applications/hr/attendances.rst:407 msgid "Entries that contain an error appear on the overview dashboard in red. In the :guilabel:`Gantt view`, the entry appears with a red background. If in the :guilabel:`List view`, the entry text appears in red." msgstr "" -#: ../../content/applications/hr/attendances.rst:504 +#: ../../content/applications/hr/attendances.rst:411 msgid "An error typically occurs when an employee has checked in but has not checked out within the last 24 hours, or when an employee has a check in and check out period spanning over 16 hours." msgstr "" -#: ../../content/applications/hr/attendances.rst:507 +#: ../../content/applications/hr/attendances.rst:414 msgid "To fix the error, the attendance entry must be modified or deleted. Click on the entry to reveal a pop-up containing the details for that particular entry. To modify the :guilabel:`Check In` and/or :guilabel:`Check Out` information, click on the :guilabel:`Check In` or :guilabel:`Check Out` field and a calendar selector appears. Click on the desired date, then use the time selector beneath the calendar to select the specific time for the entry. When the information is correct, click :guilabel:`Apply.`" msgstr "" @@ -1321,35 +1234,35 @@ msgid "The pop-up that allows for modifications to an attendance entry with an e "selector is shown, and the time selector is highlighted." msgstr "" -#: ../../content/applications/hr/attendances.rst:519 +#: ../../content/applications/hr/attendances.rst:426 msgid "When all the information on the pop-up is correct, click :guilabel:`Save & Close`. When the entry no longer has an error, the entry appears in gray instead of red." msgstr "" -#: ../../content/applications/hr/attendances.rst:522 +#: ../../content/applications/hr/attendances.rst:429 msgid "To delete an entry, click :guilabel:`Remove` on the pop-up instead of making modifications to the entry." msgstr "" -#: ../../content/applications/hr/attendances.rst:528 +#: ../../content/applications/hr/attendances.rst:435 msgid "To view attendance reports, click :guilabel:`Reporting` in the top menu. The default report displays each employee's attendance information for the past 3 months, in a :guilabel:`Line Chart`." msgstr "" -#: ../../content/applications/hr/attendances.rst:531 +#: ../../content/applications/hr/attendances.rst:438 msgid "The default view is a :guilabel:`Graph`. To view the data in a pivot table, click the :guilabel:`Pivot Table` button on the top right of the report. To switch back to the graph view, click the :guilabel:`Graph` button, located next to the :guilabel:`Pivot Table` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:535 +#: ../../content/applications/hr/attendances.rst:442 msgid "To present different information, adjust the :ref:`filters and groups ` in the same way as in the :guilabel:`Overview` dashboard." msgstr "" -#: ../../content/applications/hr/attendances.rst:538 +#: ../../content/applications/hr/attendances.rst:445 msgid "The data can be presented in either a :guilabel:`Bar Chart`, :guilabel:`Line Chart`, :guilabel:`Pie Chart`, :guilabel:`Stacked` chart, or in :guilabel:`Descending` or :guilabel:`Ascending` order. To change the view to any of these charts, click the corresponding button above the displayed chart." msgstr "" -#: ../../content/applications/hr/attendances.rst:542 +#: ../../content/applications/hr/attendances.rst:449 msgid "To change the :guilabel:`Measures`, click the :guilabel:`Measures` button and select the desired measure from the drop-down menu." msgstr "" -#: ../../content/applications/hr/attendances.rst:545 +#: ../../content/applications/hr/attendances.rst:452 msgid "The report can also be inserted into a spreadsheet. Click the :guilabel:`Insert in Spreadsheet` button and a pop-up appears. Select the desired spreadsheet, and click :guilabel:`Confirm`." msgstr "" @@ -1357,6 +1270,92 @@ msgstr "" msgid "The default report view, with all the optional view buttons highlighted." msgstr "" +#: ../../content/applications/hr/attendances.rst:460 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:461 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +msgid "Odoo's *Attendances* application allows users, who are logged into the database, to check in and out, without needing to go into the *Attendances* application, or use a kiosk. For smaller companies, where every employee is also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "A user can check in and/or out on the main database Odoo dashboard, or while inside any application. To do so, in the upper-right corner of the top main header menu, which is always visible regardless of what application the user is in, a :guilabel:`🔴 (red circle)` or :guilabel:`🟢 (green circle)` is visible. Click on the colored circle to reveal the attendance widget, enabling the user to check in and/or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:22 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:24 +msgid "If the attendance widget circle is red, this indicates the user is not currently checked in. Click the :guilabel:`🔴 (red circle)`, and the attendance widget appears, displaying a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:32 +msgid "When the user checks in from the database, the *Attendances* app logs the location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:36 +msgid "For the *Attendances* app to log the location details, the user must allow their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "If the user has not already checked in and out during the current work day, this button is the only visible item in the widget. If the user has previously checked in and out, a :guilabel:`Total today` field appears above the button, and the total amount of time that has been logged for the day appears in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:44 +msgid "Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The :guilabel:`🔴 (red circle)` in the top menu changes to green, and the widget changes appearance, as well. The widget updates to reflect that the user has checked in, by changing the green :guilabel:`Check in` :icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:49 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:52 +#: ../../content/applications/hr/frontdesk/visitors.rst:148 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:54 +msgid "If the user is checking out for the first time, :guilabel:`Since HH:MM (AM/PM)` appears at the top of the widget, with the time the user checked in populating the time field. Beneath that line, the hours and minutes that have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. As time passes, this value is updated to reflect the hours and minutes that have passed since the user checked in." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:60 +msgid "If the user has previously checked in and out, additional fields are presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of these fields match, and are populated with the most recent check in time. Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "In addition, beneath both of these fields, a :guilabel:`Total today` field appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:70 +msgid "As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and :guilabel:`Total today` fields are updated live. To check out, click the yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance widget updates again, displaying the :guilabel:`Total today` field with the logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:76 +msgid "When the user checks out from the database, the *Attendances* app logs the location details for the user. This information is **only** logged if the user allows their computer to access this information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:85 +msgid "There is no limit to the amount of times a user can check in and check out. Users are able to check in and out without any time elapsing (a value of 00:00). Each time an employee logs in and out, the information is stored and appears on the main *Attendances* dashboard, including check ins and check outs with no time value." +msgstr "" + #: ../../content/applications/hr/attendances/hardware.rst:3 msgid "Hardware" msgstr "" @@ -1434,6 +1433,198 @@ msgstr "" msgid "Odoo *Employees* organizes a company's employee records, contracts, and departments." msgstr "" +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "All employees in the *Employees* app fall under specific departments within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:8 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "To make a new department, navigate to :menuselection:`Employees app --> Departments`, then click :guilabel:`New` in the top-left to reveal a blank department form. Fill out the following information on the department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:19 +msgid ":guilabel:`Manager`: using the drop-down menu, select the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid ":guilabel:`Parent Department`: if the new department is housed within another department (has a parent department), select the parent department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid ":guilabel:`Custom Appraisal Templates`: if employees in this department require a specific appraisal form that is different from the default appraisal form, tick the checkbox. If this option is activated, an :guilabel:`Appraisal Templates` tab appears below the form. This field **only** appears if the *Appraisals* app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:26 +msgid ":guilabel:`Company`: using the drop-down menu, select the company the department is part of." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:27 +msgid ":guilabel:`Appraisal Survey`: using the drop-down menu, select the default survey to use for the department when requesting feedback from employees. This field **only** appears if the *Appraisals* app is installed, **and** the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:30 +msgid ":guilabel:`Color`: select a color for the department. Click the default white color box to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:32 +msgid ":guilabel:`Appraisal Templates` tab: this tab **only** appears if the :guilabel:`Custom Appraisal Templates` options is activated on the form. Make any desired edits to the appraisal form. The appraisal form is used for appraisals for all employees within this department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:36 +msgid "After the form is completed, click the :icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon to manually save the changes. When saved, a :guilabel:`Department Organization` chart appears in the top-right of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:41 +msgid "The form auto-saves while data is entered, however the :guilabel:`Department Organization` chart does **not** appear until the form is manually saved. If the form is not saved, the :guilabel:`Department Organization` chart is visible upon opening the department card from the :guilabel:`Departments` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:47 +msgid "Refer to the :doc:`../appraisals` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:50 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:52 +msgid "To view the currently configured departments, navigate to :menuselection:`Employees app --> Departments`. All departments appear in a Kanban view, by default, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments dashboard view with all the department cards in a Kanban view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:61 +#: ../../content/applications/hr/fleet/service.rst:329 +#: ../../content/applications/hr/recruitment.rst:175 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:63 +msgid "Each department has its own Kanban card on the main :guilabel:`Departments` :icon:`oi-view-kanban` :guilabel:`(Kanban)` dashboard view, that can display the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:66 +msgid "Department name: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +msgid "Company: the company the department is part of." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:68 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid ":guilabel:`Appraisals`: the number of appraisals scheduled for employees in the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:70 +msgid ":guilabel:`Time Off Requests`: the number of unapproved time off requests for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Allocation Requests`: the number of unapproved allocation requests for employees in the department :ref:`awaiting approval `. This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid ":guilabel:`New Applicants`: the number of :ref:`new applicants ` for a position in this department. This **only** appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:78 +msgid ":guilabel:`Expense Reports`: the number of employees in the department with :ref:`open expense reports to approve `. This **only** appears if there are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:81 +msgid ":guilabel:`Absence`: the number of absences for the current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:82 +msgid "Color bar: the selected color for the department appears as a vertical bar on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:86 +msgid "Click on an alert in a department card, such as :guilabel:`Time Off Requests`, to reveal a list view of the requests to approve. This list includes **all** open requests to approve, not just from the specific department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:90 +msgid "The default view for the :guilabel:`Departments` dashboard is a Kanban view. It is possible to view the departments in two other forms: a list view and a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:94 +#: ../../content/applications/hr/fleet/service.rst:302 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:96 +msgid "To view the departments in a list view, click the :icon:`fa-align-justify` :guilabel:`(list)` icon in the top-right corner. The departments appear in a list view, which displays the :guilabel:`Department Name`, :guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, :guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "The departments are sorted alphabetically by :guilabel:`Department Name`, by default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:108 +msgid "When in list view, departments can be managed in batch by selecting one or multiple record's checkbox, then select the :icon:`fa-cog` :guilabel:`Actions` button to reveal a drop-down menu of actions." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:113 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:115 +msgid "To view the departments in a hierarchy view, click the :icon:`fa-share-alt fa-rotate-90` :guilabel:`(hierarchy)` icon in the top-right corner. The departments appear in an organizational chart format, with the highest-level department at the top (typically :guilabel:`Management`), and all other departments beneath it. All child departments of the first-level child departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:121 +msgid "Each department card displays the :guilabel:`Department Name`, the :guilabel:`Manager` (and their profile image), the :guilabel:`Number of Employees` in the department, and the ability to expand the department (:guilabel:`Unfold`) if there are child departments beneath it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:125 +msgid "Click the :guilabel:`Unfold` button on a department card to expand it. Once expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` button. To collapse the department, click the :guilabel:`Fold` button. Only **one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:129 +msgid "Click anywhere on a department card to open the department form. Click the :guilabel:`(#) Employees` smart button to view a list of all the employees in that department, including all employees in the child departments beneath it, organized by individual department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:134 +msgid "In the hierarchy view, if the :guilabel:`(2) Employees` button on the :guilabel:`Management` card is clicked (the highest-level department card), **all** employees appear in a list view, grouped by department. This is because **all** departments are children of the :guilabel:`Management` department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:139 +msgid "If the :guilabel:`(3) Employees` button in the :guilabel:`Sales` department card is clicked, the employees from the :guilabel:`Sales` department, as well as its two child departments (:guilabel:`East Coast Territory` and :guilabel:`West Coat Territory`), appear in the list." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:0 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:0 +msgid "The list view of employees for the department that was clicked, including all child\n" +"departments." +msgstr "" + #: ../../content/applications/hr/employees/new_employee.rst:3 msgid "New employees" msgstr "" @@ -1485,7 +1676,6 @@ msgid "A new employee form with the required fields highlighted." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:47 -#: ../../content/applications/hr/recruitment.rst:736 msgid "Optional fields" msgstr "" @@ -1558,7 +1748,8 @@ msgid "Resumé tab" msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:110 -#: ../../content/applications/hr/payroll.rst:869 +#: ../../content/applications/hr/payroll.rst:874 +#: ../../content/applications/hr/recruitment.rst:419 msgid "Resumé" msgstr "" @@ -2374,7 +2565,7 @@ msgid ":guilabel:`Trailer Hitch`: check this box if the vehicle has a trailer hi msgstr "" #: ../../content/applications/hr/fleet.rst:172 -#: ../../content/applications/hr/payroll.rst:394 +#: ../../content/applications/hr/payroll.rst:398 msgid "Salary" msgstr "" @@ -3273,10 +3464,6 @@ msgid "The icons in the top right corner than can be clicked to present the info "different ways." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:302 -msgid "List view" -msgstr "" - #: ../../content/applications/hr/fleet/service.rst:304 msgid "The default view of the service records is a list view. This presents all the services, first grouped alphabetically by type of service, then grouped by status." msgstr "" @@ -3306,11 +3493,6 @@ msgstr "" msgid "The form automatically saves as data is entered." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:329 -#: ../../content/applications/hr/recruitment.rst:33 -msgid "Kanban view" -msgstr "" - #: ../../content/applications/hr/fleet/service.rst:331 msgid "To view services by their stage, click the :guilabel:`Kanban` button, which is the second icon in the top-right corner, and appears as two different length bars beneath a line." msgstr "" @@ -3360,11 +3542,11 @@ msgid "Depending on what kind of activity, if any, is scheduled, the activity ic msgstr "" #: ../../content/applications/hr/fleet/service.rst:380 -#: ../../content/applications/hr/frontdesk.rst:31 +#: ../../content/applications/hr/frontdesk.rst:33 #: ../../content/applications/hr/lunch.rst:230 -#: ../../content/applications/hr/payroll.rst:889 +#: ../../content/applications/hr/payroll.rst:894 #: ../../content/applications/hr/payroll/work_entries.rst:54 -#: ../../content/applications/hr/time_off.rst:219 +#: ../../content/applications/hr/time_off.rst:222 msgid "Enter the following information on the form:" msgstr "" @@ -3532,154 +3714,153 @@ msgstr "" msgid "When the form is complete, click the :guilabel:`Schedule` button. Then, both pop-up windows close, and the activity now appears on the activity view." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:3 +#: ../../content/applications/hr/frontdesk.rst:5 msgid "Frontdesk" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:5 +#: ../../content/applications/hr/frontdesk.rst:7 msgid "The Odoo *Frontdesk* application provides a way for visitors to check in to a building or location, and alert the person they are meeting about their arrival. Additionally, they can request a pre-configured beverage to be brought to them, while they wait." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:9 +#: ../../content/applications/hr/frontdesk.rst:11 msgid "This application is ideal for businesses that do **not** have someone working at a reception desk, locations **without** a designated waiting area available to guests and visitors." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/frontdesk.rst:17 msgid "The first item to configure with the *Frontdesk* application is the station, followed by any drink selections that might optionally be offered." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:19 +#: ../../content/applications/hr/frontdesk.rst:21 msgid "Stations" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:21 +#: ../../content/applications/hr/frontdesk.rst:23 msgid "In Odoo's *Frontdesk* application, a *Station* can be thought of as any location where someone can sign in and wait for an employee. This is typically some form of waiting room, such as a lobby. Each station has a kiosk where visitors check in." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:25 +#: ../../content/applications/hr/frontdesk.rst:27 msgid "When setting up the *Frontdesk* application, a minimum of one station **must** be configured, but there is no limit to how many stations can be created and configured." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:28 +#: ../../content/applications/hr/frontdesk.rst:30 msgid "To create a station, navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, and click :guilabel:`New`. When clicked, a blank frontdesk form appears." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:33 +#: ../../content/applications/hr/frontdesk.rst:35 msgid ":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk location. This should be short and easily identifiable, such as `Reception Desk` or `Main Lobby`. This field is required in order to create a station." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:36 +#: ../../content/applications/hr/frontdesk.rst:38 msgid ":guilabel:`Responsibles`: select the person (or persons) who are alerted when a visitor checks in using this specific frontdesk. Multiple selections can be entered. This field is required in order to create a station." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:39 +#: ../../content/applications/hr/frontdesk.rst:41 msgid ":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is saved, with at least the :guilabel:`Frontdesk Name` and :guilabel:`Responsibles` fields filled. To save manually, click the :guilabel:`(cloud with upward arrow)` icon, located at the top of the form." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:43 +#: ../../content/applications/hr/frontdesk.rst:45 msgid "Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL is one way the frontdesk kiosk is accessed." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:46 +#: ../../content/applications/hr/frontdesk.rst:48 msgid "To access the kiosk, click the :guilabel:`Copy` button at the end of the URL, and navigate to that URL in a web browser. This URL opens that specific station's frontdesk sign-in page." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:50 +#: ../../content/applications/hr/frontdesk.rst:52 msgid "To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera with a '+' sign)` icon in the top-right of the form to reveal a :guilabel:`✏️ (pencil)` icon." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:53 -#: ../../content/applications/hr/frontdesk.rst:166 -#: ../../content/applications/hr/frontdesk.rst:182 +#: ../../content/applications/hr/frontdesk.rst:55 +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:184 msgid "Click on the :guilabel:`✏️ (pencil)` icon to open a file explorer, navigate to the desired image/photo file, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:56 +#: ../../content/applications/hr/frontdesk.rst:58 msgid "The image selected for the station photo appears as the background image for the station kiosk." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:59 -#: ../../content/applications/hr/recruitment.rst:608 +#: ../../content/applications/hr/frontdesk.rst:61 msgid "Options tab" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:63 +#: ../../content/applications/hr/frontdesk.rst:65 msgid ":guilabel:`Host Selection`: if the visitor is attending a meeting, this option allows the visitor to select the meeting host from a presented list, and notify that individual. When enabled, additional fields appear, as detailed below." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:66 +#: ../../content/applications/hr/frontdesk.rst:68 msgid ":guilabel:`Authenticate Guest`: if additional information is required when a guest checks in, enable this option, and select which of the following are required:" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:69 +#: ../../content/applications/hr/frontdesk.rst:71 msgid ":guilabel:`Email`: select whether the guest's email address is :guilabel:`Required`, :guilabel:`Optional`, or if the information is not requested at all (:guilabel:`None`)." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:71 +#: ../../content/applications/hr/frontdesk.rst:73 msgid ":guilabel:`Phone`: select whether the guest's phone number is :guilabel:`Required`, :guilabel:`Optional`, or if the information is not requested at all (:guilabel:`None`)." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:73 +#: ../../content/applications/hr/frontdesk.rst:75 msgid ":guilabel:`Organization`: select whether the guest's organization is :guilabel:`Required`, :guilabel:`Optional`, or if the information is not requested at all (:guilabel:`None`)." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:76 +#: ../../content/applications/hr/frontdesk.rst:78 msgid ":guilabel:`Theme`: select the color mode of the kiosk. Choose either :guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` selection displays a dark gray and black background." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:79 +#: ../../content/applications/hr/frontdesk.rst:81 msgid ":guilabel:`Self Check-In`: enable this option to present a check-in QR code on the kiosk. The QR code allows guests to check in using their mobile device, instead of using the kiosk. This option is recommended for a busy kiosk with multiple guests checking in at any time." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:82 +#: ../../content/applications/hr/frontdesk.rst:84 msgid ":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon check in. If this option is enabled, it is necessary to :ref:`configure the drinks being offered `, via the :guilabel:`Configure Drinks` link that appears when the option is enabled. Once all drink options are configured, select each drink to be offered using the drop-down menu." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:88 +#: ../../content/applications/hr/frontdesk.rst:90 msgid "The following options are only visible in the :guilabel:`Options` tab if the :ref:`Host Selection ` option is enabled." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:91 +#: ../../content/applications/hr/frontdesk.rst:93 msgid ":guilabel:`Notify by email`: enable this option to have an email sent to the person the guest is visiting upon check in. When enabled, an :guilabel:`Email Template` field appears beneath, with the default :guilabel:`Frontdesk Email Template` selected." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:95 +#: ../../content/applications/hr/frontdesk.rst:97 msgid "To change the default email template, click the drop-down menu in the :guilabel:`Email Template` field, then select another email template." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:98 +#: ../../content/applications/hr/frontdesk.rst:100 msgid "To modify the currently selected template, click the :guilabel:`Internal link (arrow)` icon at the end of the line, and make any edits to the template." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:100 +#: ../../content/applications/hr/frontdesk.rst:102 msgid ":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message sent to the person the guest is visiting upon check in. When enabled, an :guilabel:`SMS Template` field appears beneath, with the default :guilabel:`Frontdesk SMS Template` selected." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:104 +#: ../../content/applications/hr/frontdesk.rst:106 msgid "To change the default SMS template, click the drop-down menu in the :guilabel:`SMS Template` field, and select another SMS template." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:107 +#: ../../content/applications/hr/frontdesk.rst:109 msgid "To modify the currently selected template, click the :guilabel:`Internal link (arrow)` icon at the end of the line, and make any desired edits to the content of the template. The SMS message may have a maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:110 +#: ../../content/applications/hr/frontdesk.rst:112 msgid ":guilabel:`Notify by Discuss`: this option is enabled by default when the :guilabel:`Host Selection` option is enabled. This option opens a *Discuss* application message window with the person the guest is visiting upon check in." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:114 +#: ../../content/applications/hr/frontdesk.rst:116 msgid "When enabled, a default message appears for the person the guest is visiting. The *Discuss* application **must** be installed in order for this option to work." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:118 +#: ../../content/applications/hr/frontdesk.rst:120 msgid "*Discuss* is installed by default when creating an Odoo database, and does not count towards billing. As long as the *Discuss* application is not intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:123 +#: ../../content/applications/hr/frontdesk.rst:125 msgid "The default message format for the :guilabel:`Notify by Discuss` option is: `(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) (Organization) to meet (Name of employee).`" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:126 +#: ../../content/applications/hr/frontdesk.rst:128 msgid "An example of how that might appear in a *Discuss* message is: `Main Lobby Check-In: John Doe (123-555-1234) (Odoo, Inc.) to meet Marc Demo.`" msgstr "" @@ -3687,49 +3868,50 @@ msgstr "" msgid "Frontdesk station form with all the information filled out." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:134 +#: ../../content/applications/hr/frontdesk.rst:136 msgid "Side Message tab" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:136 +#: ../../content/applications/hr/frontdesk.rst:138 msgid "Enter any desired text to appear on the station kiosk after a guest has checked in, such as a welcome greeting or any necessary instructions. The text appears on the confirmation page, on the right side of the screen after a guest has completed the check-in process." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:143 +#: ../../content/applications/hr/frontdesk.rst:145 +#: ../../content/applications/hr/frontdesk/visitors.rst:112 msgid "Drinks" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:145 +#: ../../content/applications/hr/frontdesk.rst:147 msgid "After a station is created, the next step is to configure the drinks to offer visitors, if desired. This step is **not** necessary or required for the *Frontdesk* application to work, and only needs to be configured if drinks are offered to guests." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:149 +#: ../../content/applications/hr/frontdesk.rst:151 msgid "To add a drink option, navigate to :menuselection:`Frontdesk app --> Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a blank drink form to configure." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:152 +#: ../../content/applications/hr/frontdesk.rst:154 msgid "Enter the following information on the drink form:" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:154 +#: ../../content/applications/hr/frontdesk.rst:156 msgid ":guilabel:`Drink Name`: type the name of the drink option in this field. This field is required." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:155 +#: ../../content/applications/hr/frontdesk.rst:157 msgid ":guilabel:`People to Notify`: use the drop-down menu in this field to select who is notified when the drink is selected. Multiple people can be entered in this field. This field is required." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:157 +#: ../../content/applications/hr/frontdesk.rst:159 msgid ":guilabel:`Sequence`: enter a numerical value in this field to indicate where in the list of drink options this specific option appears. The lower the number, the higher on the list the drink appears. For example, entering the number one would place that drink at the top of the list, and appear first in the sequence." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:163 -#: ../../content/applications/hr/frontdesk.rst:179 +#: ../../content/applications/hr/frontdesk.rst:165 +#: ../../content/applications/hr/frontdesk.rst:181 msgid "To add an image/photo to a drink form, hover over the :guilabel:`(camera with a '+' sign)` icon in the top-right of the form to reveal a :guilabel:`✏️ (pencil)` icon." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:169 -#: ../../content/applications/hr/frontdesk.rst:185 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:187 msgid "The image selected now appears in the picture field, and is set as the image for the drink." msgstr "" @@ -3737,242 +3919,262 @@ msgstr "" msgid "Drink form with the information filled out for an espresso." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:176 +#: ../../content/applications/hr/frontdesk.rst:178 msgid "Station dashboard" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:191 -msgid "Visitors" +#: ../../content/applications/hr/frontdesk.rst:192 +msgid "Kiosk setup" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:193 -msgid "To access a complete list of visitors that are currently checked in, navigate to :menuselection:`Frontdesk app --> Visitors`." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:196 -msgid "The visitors are listed in a list view, with the following details that were entered when they checked in:" -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:200 -msgid "By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` filters appear in the :guilabel:`Search...` bar." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:203 -msgid ":guilabel:`Name`: the guest's name." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:204 -msgid ":guilabel:`Visitor Company`: the company the guest represents." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:205 -msgid ":guilabel:`Phone`: the guest's phone number." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:206 -msgid ":guilabel:`Drinks`: the drink the guest requested." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:207 -msgid ":guilabel:`Host`: who the guest is waiting to see." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:208 -msgid ":guilabel:`CheckIn`: the date and time the guest checked in." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:209 -msgid ":guilabel:`Checkout`: the date and time the guest checked out. As mentioned, in the default view, only guests with a :guilabel:`Checked-In` or :guilabel:`Planned` status are visible. Guests with check-out times are only visible if the :guilabel:`Today` filter is not active." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:212 -msgid ":guilabel:`Duration`: the amount of time the guest has been checked in for." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:213 -msgid ":guilabel:`Station`: the location of where the guest checked in." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:214 -msgid ":guilabel:`Status`: the status of the guest. The options are :guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or :guilabel:`Canceled`. In the default view, only guests with a :guilabel:`Checked-In` or :guilabel:`Planned` status are visible." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:217 -msgid ":guilabel:`Email`: the guest's email address." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:219 -msgid "To the far right of the titled columns on the :guilabel:`Visitors` page is an untitled column, where a guest's status can be updated." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:222 -msgid "When a guest leaves, click the available :guilabel:`Check out` button to update the guest's record, and log the date and time they left." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:225 -msgid "If a scheduled guest arrives, and they did not check in using the *Frontdesk* kiosk, they can be checked in here, by clicking the available :guilabel:`Check in` button to log the date and time they arrived." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:229 -msgid "Beside the untitled status column a :guilabel:`Drink Served` button appears, but only if that particular visitor requested a drink." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:232 -msgid "When their drink has been served, click the :guilabel:`Drink Served` button to indicate the drink has been delivered to the guest. Once clicked, that button disappears." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:-1 -msgid "The full list of currently checked in visitors, with the drinks to be served highlighted." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:239 -msgid "If any column is not visible, or if a visible column is preferred to be hidden, click the :guilabel:`Additional Options (two horizontal lines with dots)` icon, located at the end of the column name list." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:243 -msgid "Clicking that reveals a drop-down menu of column options to enable or disable. A :guilabel:`✅ (checkmark)` icon indicates the column is visible." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:247 -msgid "Planned visitors" -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:249 -msgid "If a guest is expected to arrive at a future date and time, it is possible to enter their information into the *Frontdesk* application in advance." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:252 -msgid "To create a planned guest, navigate to :menuselection:`Frontdesk app --> Visitors --> New`. Then, enter the same information as any other :ref:`visitor `. The only required fields are the visitor's :guilabel:`Name` and the :guilabel:`Station` at which they are expected to arrive." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:258 -msgid "If a guest is planned in advance, they must be checked in from the list on the :guilabel:`Visitors` page in the *Frontdesk* application (:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in using a kiosk, they will be checked in separately, and their planned visitor entry remains listed as :guilabel:`Planned`." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:263 -msgid "Only when a planned guest is checked in inside the application's visitor list, their :guilabel:`Planned` status changes to :guilabel:`Checked-In`." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:266 -msgid "If a guest does check in using a kiosk, ensure all records are current, and the list of currently on-site guests is correct. Be sure to check in and/or check out the correct entries, so the visitors list correctly reflects who is currently on the premises." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:270 -msgid "Ensure planned guests are informed that they should **not** check in using the kiosk if they are listed as a planned guest in advance." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:274 -msgid "Frontdesk flow" -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:276 +#: ../../content/applications/hr/frontdesk.rst:194 msgid "Set up each kiosk for use after configuring the various stations. It is recommended to use a dedicated device for each frontdesk kiosk, such as a tablet." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:279 +#: ../../content/applications/hr/frontdesk.rst:197 msgid "Navigate to the kiosk in one of two ways:" msgstr "" -#: ../../content/applications/hr/frontdesk.rst:281 +#: ../../content/applications/hr/frontdesk.rst:199 msgid "Navigate to the main *Frontdesk* application dashboard, and click the :guilabel:`Open Desk` button on the desired station card. The kiosk loads in a new browser tab." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:283 +#: ../../content/applications/hr/frontdesk.rst:201 msgid "Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, and click on the desired station. Then, click the :guilabel:`Copy` button at the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new browser tab or window." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:288 +#: ../../content/applications/hr/frontdesk.rst:206 msgid "It is recommended to log out of the database, and close the tab, after navigating to the kiosk. That way, there is no possibility of a visitor accessing the database when checking-in." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:292 -msgid "Visitor flow" -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:294 -msgid "When a visitor arrives at a facility, they approach a frontdesk kiosk, and enter their information. The information requested is what was configured for that specific frontdesk station. If any information is required, the field displays a red asterisk (*). The visitor must enter the required information in order to check in." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:299 -msgid "Once all the information is entered, the visitor taps the :guilabel:`Check In` button." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:301 -msgid "If drinks were configured for the station, after tapping :guilabel:`Check In`, a registration confirmation screen loads, along with the question: `Do you want something to drink?`" -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:304 -msgid "The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank you`." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:306 -msgid "If they select :guilabel:`Yes, please`, a drink selection screen appears, and the pre-configured options are listed. The visitor then taps the desired selection, or, if they do not want anything, they can tap the :guilabel:`Nothing, thanks` button at the bottom of the screen." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:310 -msgid "If a drink selection was made, a `Thank you for registering! Your drink is on the way.` message appears." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:313 -msgid "At any point in the check-in process, if ten seconds pass with no selection, the kiosk returns to the main welcome screen." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:316 -msgid "Once the visitor has checked in, the person they are visiting, and any other users who were configured to be notified when checks ins occur at the kiosk, are notified. The notification is either by email, SMS message, a *Discuss* chat, or any combination of those three options." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:320 -msgid "If the visitor requested a drink, the user(s) configured as the :guilabel:`People to Notify` on the drink form, are notified via the *Discuss* application. The message that appears is: `(Visitor Name) just checked-in. They requested (Drink Name).`" -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:324 -msgid "Once the drink has been delivered to the guest, the person who delivered the drink is responsible for marking the drink as delivered." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:327 -msgid "To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> Stations --> (#) Drinks to serve` on the desired station card." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:330 -msgid "This opens a list of all the visitors checked in at that station, and are waiting for a drink. Click the :guilabel:`Drink Served` button at the end of the line for the visitor who was served. Once they are marked as having their drink served, the visitor disappears from the list." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:334 -msgid "Once the visitor has completed their business, and has left the premises, it is important to check them out for accurate record keeping." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:337 -msgid "To check visitors out properly, navigate to :menuselection:`Frontdesk app --> Stations --> (#) On Site`. Doing so opens a list of all the visitors who are currently checked-in at that station." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:340 -msgid "Click the :guilabel:`Check Out` button near the end of the line for the visitor who left. Once they are marked as checked-out, the visitor disappears from the list." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:344 -msgid "Visitors do **not** check themselves out when they leave. It is important to check out visitors for accurate record keeping." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:347 -msgid "Always have an accurate list of who is on the premises at any given time. This is important for security purposes, and in the case of an emergency." -msgstr "" - -#: ../../content/applications/hr/frontdesk.rst:353 +#: ../../content/applications/hr/frontdesk.rst:212 msgid "The *Frontdesk* application has two reports available: :guilabel:`Visitors` and :guilabel:`Drinks`." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:355 +#: ../../content/applications/hr/frontdesk.rst:214 msgid "To access either of these reports, navigate to :menuselection:`Frontdesk app --> Reporting` to reveal a drop-down menu containing the options: :guilabel:`Visitors` and :guilabel:`Drinks`." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:358 +#: ../../content/applications/hr/frontdesk.rst:217 msgid "The :guilabel:`Visitors` report displays the number of visitors by month, for the current year. The :guilabel:`Drinks` report shows how many total requests were made for each drink." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:361 +#: ../../content/applications/hr/frontdesk.rst:220 msgid "As with all reports in Odoo, the filters and groups can be modified to show other metrics, as well." msgstr "" +#: ../../content/applications/hr/frontdesk.rst:223 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "In the Odoo *Frontdesk* application, a *visitor* is defined as any non-employee (e.g., repair person, job candidate, etc.). These visitors can be logged upon arrival and departure for security purposes. This ensures an accurate list of people on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "To access a complete list of checked-in visitors, navigate to :menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "All visitors are presented in a list view, with the following details that were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid ":guilabel:`Checkout`\\*: the date and time the guest checked out. In the default view, only guests with a :guilabel:`Checked-In` or :guilabel:`Planned` status are visible. Guests with check-out times are only visible if the :guilabel:`Today` filter is not active." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid ":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid ":guilabel:`Status`: the status of the guest. The options are :guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or :guilabel:`Canceled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:39 +msgid "\\* These fields are not visible in the default :guilabel:`Visitor` list. These must be enabled using the :icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the top-right of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:43 +msgid "To the far-right of the titled columns on the :guilabel:`Visitors` page, there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:46 +msgid "When a guest leaves, click the available :guilabel:`Check out` button to update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:49 +msgid "If a scheduled guest arrives, and they did not check in using the *Frontdesk* kiosk, they can be checked in here, by clicking the available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:53 +msgid "Beside the untitled status column, a :guilabel:`Drink Served` button appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:56 +msgid "When their drink has been served, click the :guilabel:`Drink Served` button to indicate the drink has been delivered to the guest. Once clicked, that button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "The full list of currently checked in visitors, with the drinks to be served highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:63 +msgid "If any column is not visible, or if a visible column is preferred to be hidden, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` icon, located at the end of the column name list. Doing so, reveals a reveals a drop-down menu of column options to enable or disable. A :icon:`fa-check` :guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:69 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:71 +msgid "Enter expected guest information in advance by creating a planned guest in the *Frontdesk* app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "To create a planned guest, navigate to :menuselection:`Frontdesk app --> Visitors`, and click :guilabel:`New`. Then, enter the same information as any other :ref:`visitor ` on the guest form that appears. The only required fields are the visitor's :guilabel:`Name` and the :guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:79 +msgid "If a guest is planned in advance, they must be checked in from the list on the :guilabel:`Visitors` page in the *Frontdesk* application (:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in using a kiosk, they will be checked in separately, and their planned visitor entry remains listed as :guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:84 +msgid "The :guilabel:`Planned` status of a planned guest **only** changes to :guilabel:`Checked-In` when they are checked in *inside* the application's :guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:87 +msgid "If a guest does check in using a kiosk, ensure all records are current, and the list of guests that are currently on-site is correct. Be sure to check in and/or check out the correct entries, so the visitors list correctly reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:91 +msgid "Ensure planned guests are informed that they should **not** check in using the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:95 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:98 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:100 +msgid "When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk `, and click :guilabel:`Check in`. The information requested from the visitor is what was configured for that specific *Frontdesk* station. If any information is required, the field displays a red asterisk (\\*). The visitor **must** enter the required information in order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:105 +msgid "Once all the information is entered, the visitor taps the :guilabel:`Check In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "At any point in the check-in process, if ten seconds pass with no selection, the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:114 +msgid "If drinks were configured for the station, after tapping :guilabel:`Check In`, a registration confirmation screen loads, along with the question: :guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:119 +msgid "If they select :guilabel:`Yes, please`, a drink selection screen appears, and the pre-configured options are listed. The visitor then taps the desired selection, or, if they do not want anything, they can tap the :guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:123 +msgid "If a drink selection was made, a :guilabel:`Thank you for registering! Your drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:127 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Once the visitor has checked in, the person they are visiting, and any other users who were configured to be notified when check-ins occur at the kiosk, are notified. The notification is either by email, SMS message, a *Discuss* chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:133 +msgid "If the visitor requested a drink, the user(s) configured as the :guilabel:`People to Notify` on the drink form, are notified, via the *Discuss* application. The message that appears is: :guilabel:`(Visitor Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:137 +msgid "Once the drink has been delivered to the guest, the person who delivered the drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:140 +msgid "To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> Stations`, and choose the desired station card displaying :guilabel:`(#) Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:143 +msgid "This opens a list of all the visitors checked in at that station, and are waiting for a drink. Click the :guilabel:`Drink Served` button at the end of the line for the visitor who was served. Once they are marked as having their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "Once the visitor has completed their business, and has left the premises, it is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:153 +msgid "To check visitors out properly, navigate to :menuselection:`Frontdesk app --> Stations`, and choose the desired station card displaying :guilabel:`(#) Drinks to serve`. Doing so opens a list of all the visitors who are currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:157 +msgid "Click the :guilabel:`Check out` button near the end of the line for the visitor who left. Once they are marked as checked-out, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:161 +msgid "Visitors do **not** check themselves out when they leave. It is important for *Frontdesk* users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "Always have an accurate list of who is on the premises at any given time. This is important for security purposes, and in the case of an emergency." +msgstr "" + #: ../../content/applications/hr/lunch.rst:5 msgid "Lunch" msgstr "" @@ -4308,7 +4510,7 @@ msgid "The category form, with the fields filled out for a Soup category." msgstr "" #: ../../content/applications/hr/lunch.rst:280 -#: ../../content/applications/hr/referrals.rst:701 +#: ../../content/applications/hr/referrals.rst:392 msgid "Alerts" msgstr "" @@ -5094,71 +5296,75 @@ msgstr "" msgid "Contract templates are used with the *Recruitment* application when sending an offer to a candidate. The contract template forms the basis of an offer, and can be modified for specific candidates or employees, when necessary. If a contract template is created or modified in the *Payroll* application, the changes are also reflected in the *Recruitment* application." msgstr "" -#: ../../content/applications/hr/payroll.rst:111 +#: ../../content/applications/hr/payroll.rst:112 +msgid "To access contract templates, the *Salary Configurator* (`hr_contract_salary`) module **must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:115 msgid "To view all the current contract templates in the database, navigate to :menuselection:`Payroll app --> Configuration --> Contracts: Templates`." msgstr "" -#: ../../content/applications/hr/payroll.rst:114 +#: ../../content/applications/hr/payroll.rst:118 msgid "On the :guilabel:`Contract Templates` page, all current contract templates appear in a list view. To view the details of a contract template, click anywhere on the line to open the contract form. The contract template can be modified from this form. Proceed to make any desired changes to the contract." msgstr "" -#: ../../content/applications/hr/payroll.rst:119 +#: ../../content/applications/hr/payroll.rst:123 msgid "To create a new contract template, click the :guilabel:`New` button. Then, enter the following information on the blank contract template form that appears:" msgstr "" -#: ../../content/applications/hr/payroll.rst:122 +#: ../../content/applications/hr/payroll.rst:126 msgid ":guilabel:`Contract Reference`: enter a brief description for the template. This should be clear and easily understood, as this name appears in the *Recruitment* application, as well." msgstr "" -#: ../../content/applications/hr/payroll.rst:124 +#: ../../content/applications/hr/payroll.rst:128 msgid ":guilabel:`Working Schedule`: select the desired working schedule the contract applies to from the drop-down menu. If a new working schedule is needed, create a :ref:`new working schedule `." msgstr "" -#: ../../content/applications/hr/payroll.rst:127 +#: ../../content/applications/hr/payroll.rst:131 msgid ":guilabel:`Work Entry Source`: select how the work entries are generated. Choices are either:" msgstr "" -#: ../../content/applications/hr/payroll.rst:129 +#: ../../content/applications/hr/payroll.rst:133 msgid ":guilabel:`Working Schedule`: work entries are generated based on the selected working schedule." msgstr "" -#: ../../content/applications/hr/payroll.rst:130 +#: ../../content/applications/hr/payroll.rst:134 msgid ":guilabel:`Attendances`: work entries are generated based on the employee's attendance, as they are logged in the *Attendances* application. Refer to the :ref:`Attendances ` documentation for information on checking in and out." msgstr "" -#: ../../content/applications/hr/payroll.rst:133 +#: ../../content/applications/hr/payroll.rst:137 msgid ":guilabel:`Planning`: work entries are generated based on the employee's planning in the *Planning* application." msgstr "" -#: ../../content/applications/hr/payroll.rst:136 +#: ../../content/applications/hr/payroll.rst:140 msgid ":guilabel:`Salary Structure Type`: select the :ref:`salary structure type ` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:138 +#: ../../content/applications/hr/payroll.rst:142 msgid ":guilabel:`Department`: select the department the contract template applies to from the drop-down menu. If blank, the template applies to all departments." msgstr "" -#: ../../content/applications/hr/payroll.rst:140 +#: ../../content/applications/hr/payroll.rst:144 msgid ":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If blank, the template applies to all job positions." msgstr "" -#: ../../content/applications/hr/payroll.rst:142 +#: ../../content/applications/hr/payroll.rst:146 msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." msgstr "" -#: ../../content/applications/hr/payroll.rst:143 +#: ../../content/applications/hr/payroll.rst:147 msgid ":guilabel:`Contract Type`: select the type of contract from the drop-down menu. This list is the same as the :ref:`Employment Types `." msgstr "" -#: ../../content/applications/hr/payroll.rst:145 +#: ../../content/applications/hr/payroll.rst:149 msgid ":guilabel:`HR Responsible`: select the employee responsible for validating contracts, using this template, from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:147 +#: ../../content/applications/hr/payroll.rst:151 msgid ":guilabel:`New Contract Document Template`: select a default document that a new employee has to sign to accept an offer." msgstr "" -#: ../../content/applications/hr/payroll.rst:149 +#: ../../content/applications/hr/payroll.rst:153 msgid ":guilabel:`Contract Update Document Template`: select a default document that a current employee has to sign to update their contract." msgstr "" @@ -5166,32 +5372,32 @@ msgstr "" msgid "A new contract template form, with the fields filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:157 +#: ../../content/applications/hr/payroll.rst:161 msgid "Salary information tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:159 +#: ../../content/applications/hr/payroll.rst:163 #: ../../content/applications/hr/payroll/contracts.rst:104 msgid ":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:161 +#: ../../content/applications/hr/payroll.rst:165 msgid ":guilabel:`Schedule Pay`: using the drop-down menu, select how often the employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, :guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, :guilabel:`Weekly`, or :guilabel:`Daily`." msgstr "" -#: ../../content/applications/hr/payroll.rst:165 +#: ../../content/applications/hr/payroll.rst:169 msgid ":guilabel:`Wage`: enter the gross wage. The time period presented in this field is based on what is selected for the :guilabel:`Scheduled Pay` field. It is recommended to populate the :guilabel:`Yearly Cost (Real)` field *first*, since that entry updates this field automatically." msgstr "" -#: ../../content/applications/hr/payroll.rst:168 +#: ../../content/applications/hr/payroll.rst:172 msgid ":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee costs the employer. When this value is entered, the :guilabel:`Monthly Cost (Real)` is automatically updated." msgstr "" -#: ../../content/applications/hr/payroll.rst:170 +#: ../../content/applications/hr/payroll.rst:174 msgid ":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value is automatically populated after the :guilabel:`Yearly Cost (Real)` is entered." msgstr "" -#: ../../content/applications/hr/payroll.rst:174 +#: ../../content/applications/hr/payroll.rst:178 msgid "The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost (Real)` fields are all linked. If any of these fields are updated, the other two fields automatically update to reflect the change. It is best practice to check these three fields if any modifications have been made, to ensure they are accurate." msgstr "" @@ -5199,47 +5405,47 @@ msgstr "" msgid "The salary information tab, with the fields filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:184 +#: ../../content/applications/hr/payroll.rst:188 msgid "Pre-tax benefits and post-tax deductions" msgstr "" -#: ../../content/applications/hr/payroll.rst:186 +#: ../../content/applications/hr/payroll.rst:190 msgid "Depending on the localization settings set for the company, the entries presented in this section either vary, or may not appear at all." msgstr "" -#: ../../content/applications/hr/payroll.rst:189 +#: ../../content/applications/hr/payroll.rst:193 msgid "For example, some entries may pertain to retirement accounts, health insurance benefits, and commuter benefits." msgstr "" -#: ../../content/applications/hr/payroll.rst:192 +#: ../../content/applications/hr/payroll.rst:196 msgid "Enter the monetary amounts or percentages to specify how much of the employee's salary goes to the various benefits and/or deductions." msgstr "" -#: ../../content/applications/hr/payroll.rst:198 +#: ../../content/applications/hr/payroll.rst:202 msgid "Employment types" msgstr "" -#: ../../content/applications/hr/payroll.rst:200 +#: ../../content/applications/hr/payroll.rst:204 msgid "To view all the pre-configured employment types, navigate to :menuselection:`Payroll application --> Configuration --> Contracts: Employment Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll.rst:207 msgid "The employment types are presented in a list view on the :guilabel:`Employment Types` page." msgstr "" -#: ../../content/applications/hr/payroll.rst:205 +#: ../../content/applications/hr/payroll.rst:209 msgid "The default employment types are :guilabel:`Permanent`, :guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, :guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." msgstr "" -#: ../../content/applications/hr/payroll.rst:208 +#: ../../content/applications/hr/payroll.rst:212 msgid "To make a new employment type, click the :guilabel:`New` button in the upper-left corner, and a blank line appears at the bottom of the :guilabel:`Employment Types` page." msgstr "" -#: ../../content/applications/hr/payroll.rst:211 +#: ../../content/applications/hr/payroll.rst:215 msgid "On this new blank line, enter the name of the employment type in the :guilabel:`Name` column. If the employment type is country-specific, select the country using the drop-down menu in the :guilabel:`Country` column. If a country is selected, then the employment type is *only* applicable for that specific country." msgstr "" -#: ../../content/applications/hr/payroll.rst:216 +#: ../../content/applications/hr/payroll.rst:220 msgid "To rearrange the order of the employment types, click the :guilabel:`six small gray boxes` icon to the left of the employment type :guilabel:`Name`, and drag the line to the desired position on the list." msgstr "" @@ -5247,32 +5453,32 @@ msgstr "" msgid "The employment types in the database by default, in a list view." msgstr "" -#: ../../content/applications/hr/payroll.rst:227 +#: ../../content/applications/hr/payroll.rst:231 #: ../../content/applications/hr/payroll/work_entries.rst:3 msgid "Work entries" msgstr "" -#: ../../content/applications/hr/payroll.rst:229 +#: ../../content/applications/hr/payroll.rst:233 msgid "A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`." msgstr "" -#: ../../content/applications/hr/payroll.rst:234 +#: ../../content/applications/hr/payroll.rst:238 msgid ":doc:`Manage work entries `" msgstr "" -#: ../../content/applications/hr/payroll.rst:237 +#: ../../content/applications/hr/payroll.rst:241 msgid "Work entry types" msgstr "" -#: ../../content/applications/hr/payroll.rst:239 +#: ../../content/applications/hr/payroll.rst:243 msgid "When creating a work entry in the *Payroll* application, or when an employee enters information in the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of :guilabel:`Work Entry Types` is automatically created based on localization settings set in the database." msgstr "" -#: ../../content/applications/hr/payroll.rst:244 +#: ../../content/applications/hr/payroll.rst:248 msgid "To view the current work entry types available, go to :menuselection:`Payroll app --> Configuration --> Work Entries --> Work Entry Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:247 +#: ../../content/applications/hr/payroll.rst:251 msgid "Each work entry type has a code to aid in the creation of payslips, and to ensure all taxes and fees are correctly entered." msgstr "" @@ -5280,117 +5486,117 @@ msgstr "" msgid "List of all work entry types currently available for use, with the payroll code and color." msgstr "" -#: ../../content/applications/hr/payroll.rst:255 +#: ../../content/applications/hr/payroll.rst:259 msgid "New work entry type" msgstr "" -#: ../../content/applications/hr/payroll.rst:257 +#: ../../content/applications/hr/payroll.rst:261 msgid "To create a new :guilabel:`Work Entry Type`, click the :guilabel:`New` button, and enter the information for the following sections on the form." msgstr "" -#: ../../content/applications/hr/payroll.rst:261 -#: ../../content/applications/hr/payroll.rst:725 +#: ../../content/applications/hr/payroll.rst:265 +#: ../../content/applications/hr/payroll.rst:730 #: ../../content/applications/hr/payroll/contracts.rst:43 msgid "General information section" msgstr "" -#: ../../content/applications/hr/payroll.rst:263 +#: ../../content/applications/hr/payroll.rst:267 msgid ":guilabel:`Work Entry Type Name`: the name should be short and descriptive, such as `Sick Time` or `Public Holiday`." msgstr "" -#: ../../content/applications/hr/payroll.rst:265 +#: ../../content/applications/hr/payroll.rst:269 msgid ":guilabel:`Payroll Code`: this code appears with the work entry type on timesheets and payslips. Since the code is used in conjunction with the *Accounting* application, it is advised to check with the accounting department for a code to use." msgstr "" -#: ../../content/applications/hr/payroll.rst:268 +#: ../../content/applications/hr/payroll.rst:272 msgid ":guilabel:`DMFA code`: this code is used to identify :abbr:`DMFA (De Multifunctionele Aangifte)` entries on a corresponding :abbr:`DMFA (De Multifunctionele Aangifte)` report. The :abbr:`DMFA (De Multifunctionele Aangifte)` report is a quarterly report that Belgian-based companies are required to submit for social security reporting purposes. This report states the work done by the employees during the quarter, as well as the salaries paid to those employees." msgstr "" -#: ../../content/applications/hr/payroll.rst:273 +#: ../../content/applications/hr/payroll.rst:277 msgid ":guilabel:`External Code`: this code is used for exporting data to a third-party payroll service. Check with the third-party being used to determine the :guilabel:`External Code` to enter for the new work entry type." msgstr "" -#: ../../content/applications/hr/payroll.rst:276 +#: ../../content/applications/hr/payroll.rst:280 msgid ":guilabel:`SDWorx code`: this code is only for companies that use SDWorx, a payroll service provider." msgstr "" -#: ../../content/applications/hr/payroll.rst:278 +#: ../../content/applications/hr/payroll.rst:282 msgid ":guilabel:`Color`: select a color for the particular work entry type." msgstr "" -#: ../../content/applications/hr/payroll.rst:281 +#: ../../content/applications/hr/payroll.rst:285 msgid "Display in payslip section" msgstr "" -#: ../../content/applications/hr/payroll.rst:283 +#: ../../content/applications/hr/payroll.rst:287 msgid ":guilabel:`Rounding`: the rounding method selected determines how quantities on timesheet entries are displayed on the payslip." msgstr "" -#: ../../content/applications/hr/payroll.rst:286 +#: ../../content/applications/hr/payroll.rst:290 msgid ":guilabel:`No Rounding`: a timesheet entry is not modified." msgstr "" -#: ../../content/applications/hr/payroll.rst:287 +#: ../../content/applications/hr/payroll.rst:291 msgid ":guilabel:`Half Day`: a timesheet entry is rounded to the closest half day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:288 +#: ../../content/applications/hr/payroll.rst:292 msgid ":guilabel:`Day`: a timesheet entry is rounded to the closest full day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:291 +#: ../../content/applications/hr/payroll.rst:295 msgid "If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours." msgstr "" -#: ../../content/applications/hr/payroll.rst:297 +#: ../../content/applications/hr/payroll.rst:301 msgid "Unpaid section" msgstr "" -#: ../../content/applications/hr/payroll.rst:299 +#: ../../content/applications/hr/payroll.rst:303 msgid ":guilabel:`Unpaid in Structures Types`: if the work entry is for work that is not paid, specify which pay structure the unpaid work entry applies to from the drop-down menu. Some situations where work is logged on a timesheet, but no compensation given would be for unpaid internships, unpaid training, or volunteer work." msgstr "" -#: ../../content/applications/hr/payroll.rst:305 +#: ../../content/applications/hr/payroll.rst:309 msgid "Valid for advantages section" msgstr "" -#: ../../content/applications/hr/payroll.rst:307 +#: ../../content/applications/hr/payroll.rst:311 msgid ":guilabel:`Meal Voucher`: if the work entry should count towards a meal voucher, check the box." msgstr "" -#: ../../content/applications/hr/payroll.rst:308 +#: ../../content/applications/hr/payroll.rst:312 msgid ":guilabel:`Representation Fees`: if the work entry should count towards representation fees, check the box." msgstr "" -#: ../../content/applications/hr/payroll.rst:310 +#: ../../content/applications/hr/payroll.rst:314 msgid ":guilabel:`Private Car Reimbursement`: if the work entry should count towards a private car reimbursement, check the box." msgstr "" -#: ../../content/applications/hr/payroll.rst:314 +#: ../../content/applications/hr/payroll.rst:318 msgid "Time off options section" msgstr "" -#: ../../content/applications/hr/payroll.rst:316 +#: ../../content/applications/hr/payroll.rst:320 msgid ":guilabel:`Time Off`: check this box if the work entry type can be selected for a time off request, or entry, in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/payroll.rst:319 +#: ../../content/applications/hr/payroll.rst:323 msgid "If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for example." msgstr "" -#: ../../content/applications/hr/payroll.rst:323 +#: ../../content/applications/hr/payroll.rst:327 msgid "A new type of time off can be entered in the field, if the listed types of time off in the drop-down menu do **not** display the type of time off needed." msgstr "" -#: ../../content/applications/hr/payroll.rst:325 +#: ../../content/applications/hr/payroll.rst:329 msgid ":guilabel:`Keep Time Off Right`: this is for Belgian-specific companies **only**, and does **not** appear for other localizations. Check this box if the work entry is for time off that affects the time off benefits for the following year. Workers are given time off each year, according to the government, and in some cases, time off taken during a specific time period can affect how much time off the employee receives or accrues the following year." msgstr "" -#: ../../content/applications/hr/payroll.rst:332 +#: ../../content/applications/hr/payroll.rst:336 msgid "Reporting section" msgstr "" -#: ../../content/applications/hr/payroll.rst:334 +#: ../../content/applications/hr/payroll.rst:338 msgid ":guilabel:`Unforeseen Absence`: if the work entry should be visible on the unforeseen absences report, check this box." msgstr "" @@ -5398,23 +5604,23 @@ msgstr "" msgid "New work entry type form with all fields to be filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:344 +#: ../../content/applications/hr/payroll.rst:348 msgid "Working schedules" msgstr "" -#: ../../content/applications/hr/payroll.rst:346 +#: ../../content/applications/hr/payroll.rst:350 msgid "To view the currently configured working schedules, go to :menuselection:`Payroll app --> Configuration --> Work Entries --> Working Schedules`. The working schedules that are available for an employee's contracts and work entries are found in this list." msgstr "" -#: ../../content/applications/hr/payroll.rst:350 +#: ../../content/applications/hr/payroll.rst:354 msgid "Working schedules are company-specific. Each company **must** identify each type of working schedule they use. If the database is created for only one company, the company column is not available." msgstr "" -#: ../../content/applications/hr/payroll.rst:354 +#: ../../content/applications/hr/payroll.rst:358 msgid "An Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working schedule entry for each company that uses the 40-hour standard work week." msgstr "" -#: ../../content/applications/hr/payroll.rst:357 +#: ../../content/applications/hr/payroll.rst:361 msgid "A database with five companies that all use a standard 40-hour work week needs to have five separate 40-hour working schedules configured." msgstr "" @@ -5422,111 +5628,115 @@ msgstr "" msgid "All working schedules available to use currently set up in the database for the company." msgstr "" -#: ../../content/applications/hr/payroll.rst:367 +#: ../../content/applications/hr/payroll.rst:371 msgid "New working schedule" msgstr "" -#: ../../content/applications/hr/payroll.rst:369 +#: ../../content/applications/hr/payroll.rst:373 msgid "To create a new working schedule, click the :guilabel:`New` button, and enter the information on the form." msgstr "" -#: ../../content/applications/hr/payroll.rst:372 +#: ../../content/applications/hr/payroll.rst:376 msgid "The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any adjustments to the days and times that apply to the new working time." msgstr "" -#: ../../content/applications/hr/payroll.rst:376 +#: ../../content/applications/hr/payroll.rst:380 msgid "In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`, and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified by typing in the time." msgstr "" -#: ../../content/applications/hr/payroll.rst:382 +#: ../../content/applications/hr/payroll.rst:386 msgid "The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example, `2:00 PM` would be entered as `14:00`." msgstr "" -#: ../../content/applications/hr/payroll.rst:385 -msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch to 2 weeks calendar` button in the top left. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." +#: ../../content/applications/hr/payroll.rst:389 +msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch to 2 weeks calendar` button in the top-left. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 msgid "New working schedule form." msgstr "" -#: ../../content/applications/hr/payroll.rst:399 +#: ../../content/applications/hr/payroll.rst:403 msgid "Structure types" msgstr "" -#: ../../content/applications/hr/payroll.rst:401 +#: ../../content/applications/hr/payroll.rst:405 msgid "In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how an employee enters timesheets. Each structure type is an individual set of rules for processing a timesheet entry, which consists of different structures nested within it. Structure types define how often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how many hours the employee worked (varied)." msgstr "" -#: ../../content/applications/hr/payroll.rst:407 +#: ../../content/applications/hr/payroll.rst:411 msgid "For example, a structure type could be `Employee`, and that structure type could have two different structures in it: a `Regular Pay` structure which includes all the separate rules for processing regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures within the `Employee` structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:413 -msgid "The different :guilabel:`Structure Types` can be seen by navigating to :menuselection:`Payroll app --> Configuration --> Salary --> Structure Types`." +#: ../../content/applications/hr/payroll.rst:417 +msgid "The different :guilabel:`Structure Types` can be seen by navigating to :menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:416 -msgid "There are two default structure types configured in Odoo: :guilabel:`Employee` and :guilabel:`Worker`. Typically, :guilabel:`Employee` is used for salaried employees, which is why the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is typically used for employees paid by the hour, so the wage type is :guilabel:`Hourly Wage`." +#: ../../content/applications/hr/payroll.rst:420 +msgid "Two default structure types are configured in Odoo: :guilabel:`Employee` and :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:422 +msgid "Typically, :guilabel:`Employee` is used for salaried employees, which is why the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is typically used for employees paid by the hour, so the wage type is :guilabel:`Hourly Wage`." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 msgid "List of all currently configured structure types available to use." msgstr "" -#: ../../content/applications/hr/payroll.rst:428 +#: ../../content/applications/hr/payroll.rst:433 msgid "New structure type" msgstr "" -#: ../../content/applications/hr/payroll.rst:430 +#: ../../content/applications/hr/payroll.rst:435 msgid "To make a new structure type, click the :guilabel:`New` button, and a blank structure type form appears." msgstr "" -#: ../../content/applications/hr/payroll.rst:433 +#: ../../content/applications/hr/payroll.rst:438 msgid "Proceed to enter information in the fields. Most fields are pre-populated, but all the fields can be modified." msgstr "" -#: ../../content/applications/hr/payroll.rst:436 +#: ../../content/applications/hr/payroll.rst:441 msgid ":guilabel:`Structure Type`: enter the name for the new structure type, such as `Employee` or `Worker`." msgstr "" -#: ../../content/applications/hr/payroll.rst:438 +#: ../../content/applications/hr/payroll.rst:443 msgid ":guilabel:`Country`: select the country that the new structure type applies to from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:440 +#: ../../content/applications/hr/payroll.rst:445 msgid ":guilabel:`Wage Type`: select what type of wage the new structure type uses, either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." msgstr "" -#: ../../content/applications/hr/payroll.rst:443 +#: ../../content/applications/hr/payroll.rst:448 msgid "If the type is to be used for salaried employees, who receive the same wage every pay period, select :guilabel:`Fixed Wage`." msgstr "" -#: ../../content/applications/hr/payroll.rst:446 +#: ../../content/applications/hr/payroll.rst:451 msgid "If the type is to be used for employees, who receive wages based on how many hours they worked during a pay period, select :guilabel:`Hourly Wage`." msgstr "" -#: ../../content/applications/hr/payroll.rst:448 +#: ../../content/applications/hr/payroll.rst:453 msgid ":guilabel:`Default Scheduled Pay`: select the typical pay schedule for the new structure type from the drop-down menu. Options are :guilabel:`Monthly`, :guilabel:`Quarterly`, :guilabel:`Semi-annually`, :guilabel:`Annually`, :guilabel:`Weekly`, :guilabel:`Bi-weekly`, :guilabel:`Bi-monthly`. This indicates how often this specific type of structure is paid out." msgstr "" -#: ../../content/applications/hr/payroll.rst:452 +#: ../../content/applications/hr/payroll.rst:457 msgid ":guilabel:`Default Working Hours`: select the default working hours for the new structure type from the drop-down menu. All available working hours for the currently selected company appear in the drop-down menu. The default working hours that are pre-configured in Odoo is the :guilabel:`Standard 40 hours/week` option. If the needed working hours do not appear in the list, a :ref:`new set of default working hours can be created `." msgstr "" -#: ../../content/applications/hr/payroll.rst:457 +#: ../../content/applications/hr/payroll.rst:462 msgid ":guilabel:`Regular Pay Structure`: type in the name for the regular pay structure." msgstr "" -#: ../../content/applications/hr/payroll.rst:458 +#: ../../content/applications/hr/payroll.rst:463 msgid ":guilabel:`Default Work Entry Type`: select the default type of work entry the new structure type falls under from the drop-down menu. The default options include :guilabel:`Attendance`, :guilabel:`Overtime Hours`, :guilabel:`Generic Time Off`, :guilabel:`Compensatory Time Off`, :guilabel:`Home Working`, :guilabel:`Unpaid`, :guilabel:`Sick Time Off`, :guilabel:`Paid Time Off`, :guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long Term Time Off`." msgstr "" -#: ../../content/applications/hr/payroll.rst:464 +#: ../../content/applications/hr/payroll.rst:469 msgid "To view all the options for the :guilabel:`Default Work Entry Type`, click the :guilabel:`Search More..` button at the bottom of the drop-down list." msgstr "" -#: ../../content/applications/hr/payroll.rst:467 +#: ../../content/applications/hr/payroll.rst:472 msgid "Depending on the localization settings, this list may contain more options in addition to the default options." msgstr "" @@ -5534,75 +5744,75 @@ msgstr "" msgid "New structure type form to fill out when creating a new structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:477 +#: ../../content/applications/hr/payroll.rst:482 msgid "New default working hours" msgstr "" -#: ../../content/applications/hr/payroll.rst:479 +#: ../../content/applications/hr/payroll.rst:484 msgid "To make new default working hours, type the name for the new working hours in the :guilabel:`Default Working Hours` field on the new structure type form. Click :guilabel:`Create and edit`. A default working hours form pops up. The default working hours form has two sections, a general information section and a tab listing out all the individual working hours by day and time. When the form is completed, click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/payroll.rst:485 +#: ../../content/applications/hr/payroll.rst:490 msgid ":guilabel:`Name`: type in the name for the new default working hours. This should be descriptive and clear to understand, such as `Standard 20 Hours/Week`." msgstr "" -#: ../../content/applications/hr/payroll.rst:487 +#: ../../content/applications/hr/payroll.rst:492 msgid ":guilabel:`Company`: select the company that can use these new default working hours from the drop-down menu. Keep in mind, working hours are company-specific, and cannot be shared between companies. Each company needs to have their own working hours set." msgstr "" -#: ../../content/applications/hr/payroll.rst:490 +#: ../../content/applications/hr/payroll.rst:495 msgid ":guilabel:`Average Hour Per Day`: the average hours per day field is auto-populated, based on the working hours configured in the :guilabel:`Working Hours` tab. This entry affects resource planning, since the average daily hours affect what resources can be used, and in what quantity, per work day." msgstr "" -#: ../../content/applications/hr/payroll.rst:494 +#: ../../content/applications/hr/payroll.rst:499 msgid ":guilabel:`Timezone`: select the time zone to be used for the new default working hours from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:496 +#: ../../content/applications/hr/payroll.rst:501 msgid ":guilabel:`Company Full Time`: enter the number of hours per week an employee would need to work to be considered a full-time employee. Typically, this is approximately 40 hours, and this number affects what types of benefits an employee can receive, based on their employment status (full-time vs part-time)." msgstr "" -#: ../../content/applications/hr/payroll.rst:500 +#: ../../content/applications/hr/payroll.rst:505 msgid ":guilabel:`Work Time Rate`: this percentage is auto-generated based on the entry for the :guilabel:`Company Full Time` and the working hours configured in the :guilabel:`Working Hours` tab. This number should be between `0.00%` and `100%`, so if the percentage is above `100%`, it is an indication that the working times and/or :guilabel:`Company Full Time` hours need adjustment." msgstr "" -#: ../../content/applications/hr/payroll.rst:504 +#: ../../content/applications/hr/payroll.rst:509 msgid ":guilabel:`Working Hours` Tab: this tab is where each day's specific working hours are listed. When a new default working hour form is created, the :guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, with each day divided into three timed sections." msgstr "" -#: ../../content/applications/hr/payroll.rst:508 +#: ../../content/applications/hr/payroll.rst:513 msgid "Every day has morning (8:00-12:00), lunch (12:00-13:00), and evening (13:00-17:00) hours configured, using a 24 hour time format." msgstr "" -#: ../../content/applications/hr/payroll.rst:511 +#: ../../content/applications/hr/payroll.rst:516 msgid "To adjust any of these hours, click on the specific field to adjust, and make the adjustment using the drop-down menus, or in the specific case of the times, type in the desired time." msgstr "" -#: ../../content/applications/hr/payroll.rst:514 +#: ../../content/applications/hr/payroll.rst:519 msgid "Keep in mind, working hours are company-specific, and cannot be shared between companies. Each company needs to have their own working hours set." msgstr "" -#: ../../content/applications/hr/payroll.rst:518 +#: ../../content/applications/hr/payroll.rst:523 msgid "If the working hours are not consistent each week, and the hours are on a bi-weekly schedule instead, click the :guilabel:`Switch to 2 week calendar` button at the top of the new default working hours form. This changes the :guilabel:`Working Hours` tab to display two weeks of working times that can be adjusted." msgstr "" -#: ../../content/applications/hr/payroll.rst:524 +#: ../../content/applications/hr/payroll.rst:529 msgid "Structures" msgstr "" -#: ../../content/applications/hr/payroll.rst:526 +#: ../../content/applications/hr/payroll.rst:531 msgid "*Salary structures* are the different ways an employee gets paid within a specific *structure*, and are specifically defined by various rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:529 +#: ../../content/applications/hr/payroll.rst:534 msgid "The amount of structures a company needs for each structure type depends on how many different ways employees are paid, and how their pay is calculated. For example, a common structure that could be useful to add may be a `Bonus`." msgstr "" -#: ../../content/applications/hr/payroll.rst:533 +#: ../../content/applications/hr/payroll.rst:538 msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll app --> Configuration --> Salary --> Structures`." msgstr "" -#: ../../content/applications/hr/payroll.rst:536 +#: ../../content/applications/hr/payroll.rst:541 msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." msgstr "" @@ -5610,7 +5820,7 @@ msgstr "" msgid "All available salary structures." msgstr "" -#: ../../content/applications/hr/payroll.rst:543 +#: ../../content/applications/hr/payroll.rst:548 msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee." msgstr "" @@ -5618,60 +5828,60 @@ msgstr "" msgid "Salary structure details for Regular Pay, listing all the specific Salary Rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:551 -#: ../../content/applications/hr/time_off.rst:258 +#: ../../content/applications/hr/payroll.rst:556 +#: ../../content/applications/hr/time_off.rst:261 msgid "Rules" msgstr "" -#: ../../content/applications/hr/payroll.rst:553 +#: ../../content/applications/hr/payroll.rst:558 msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect actions in the *Accounting* application, so modifications to the default rules, or the creation of new rules, should only be done when necessary." msgstr "" -#: ../../content/applications/hr/payroll.rst:557 +#: ../../content/applications/hr/payroll.rst:562 msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Salary --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:560 +#: ../../content/applications/hr/payroll.rst:565 msgid "To make a new rule, click :guilabel:`New`. A new rule form appears. Enter the following information in the fields." msgstr "" -#: ../../content/applications/hr/payroll.rst:564 +#: ../../content/applications/hr/payroll.rst:569 msgid "Top section" msgstr "" -#: ../../content/applications/hr/payroll.rst:566 +#: ../../content/applications/hr/payroll.rst:571 msgid ":guilabel:`Rule Name`: enter a name for the rule. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:567 +#: ../../content/applications/hr/payroll.rst:572 msgid ":guilabel:`Category`: select a category the rule applies to from the drop-down menu, or enter a new one. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:569 +#: ../../content/applications/hr/payroll.rst:574 msgid ":guilabel:`Code`: enter a code to be used for this new rule. It is recommended to coordinate with the accounting department for a code to use as this affects accounting reports and payroll processing. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:572 +#: ../../content/applications/hr/payroll.rst:577 msgid ":guilabel:`Sequence`: enter a number indicating when this rule is calculated in the sequence of all other rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:574 +#: ../../content/applications/hr/payroll.rst:579 msgid ":guilabel:`Salary Structure`: select a salary structure the rule applies to from the drop-down menu, or enter a new one. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:576 +#: ../../content/applications/hr/payroll.rst:581 msgid ":guilabel:`Active`: enable this toggle, so the rule is available for use. Disable the toggle to hide the rule without deleting it in the database." msgstr "" -#: ../../content/applications/hr/payroll.rst:578 +#: ../../content/applications/hr/payroll.rst:583 msgid ":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on employee payslips." msgstr "" -#: ../../content/applications/hr/payroll.rst:579 +#: ../../content/applications/hr/payroll.rst:584 msgid ":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the rule appear on the :guilabel:`Employer Cost` report, located on the *Payroll* app dashboard." msgstr "" -#: ../../content/applications/hr/payroll.rst:581 +#: ../../content/applications/hr/payroll.rst:586 msgid ":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule appear on payroll reports." msgstr "" @@ -5679,72 +5889,72 @@ msgstr "" msgid "Enter the information for the new rule on the new rule form." msgstr "" -#: ../../content/applications/hr/payroll.rst:589 +#: ../../content/applications/hr/payroll.rst:594 msgid "General tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:592 +#: ../../content/applications/hr/payroll.rst:597 msgid "Conditions" msgstr "" -#: ../../content/applications/hr/payroll.rst:594 +#: ../../content/applications/hr/payroll.rst:599 msgid ":guilabel:`Condition Based on`: select from the drop-down menu whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the code is entered beneath the selection). This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:600 +#: ../../content/applications/hr/payroll.rst:605 msgid "Computation" msgstr "" -#: ../../content/applications/hr/payroll.rst:602 +#: ../../content/applications/hr/payroll.rst:607 msgid ":guilabel:`Amount Type`: select from the drop-down menu whether the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be entered next. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:608 +#: ../../content/applications/hr/payroll.rst:613 msgid "Company contribution" msgstr "" -#: ../../content/applications/hr/payroll.rst:610 +#: ../../content/applications/hr/payroll.rst:615 msgid ":guilabel:`Partner`: if another company financially contributes to this rule, select the company from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:614 -#: ../../content/applications/hr/payroll.rst:810 +#: ../../content/applications/hr/payroll.rst:619 +#: ../../content/applications/hr/payroll.rst:815 msgid "Description tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:616 +#: ../../content/applications/hr/payroll.rst:621 msgid "Provide any additional information in this tab to help clarify the rule. This tab only appears in the rule form." msgstr "" -#: ../../content/applications/hr/payroll.rst:620 +#: ../../content/applications/hr/payroll.rst:625 msgid "Accounting tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:622 +#: ../../content/applications/hr/payroll.rst:627 msgid ":guilabel:`Debit Account`: select the debit account from the drop-down menu the rule affects." msgstr "" -#: ../../content/applications/hr/payroll.rst:623 +#: ../../content/applications/hr/payroll.rst:628 msgid ":guilabel:`Credit Account`: select the credit account from the drop-down menu the rule affects." msgstr "" -#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/payroll.rst:629 msgid ":guilabel:`Not computed in net accountability`: tick the checkbox to delete the value of this rule in the `Net Salary` rule." msgstr "" -#: ../../content/applications/hr/payroll.rst:628 +#: ../../content/applications/hr/payroll.rst:633 msgid "Rule parameters" msgstr "" -#: ../../content/applications/hr/payroll.rst:631 +#: ../../content/applications/hr/payroll.rst:636 msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration --> Salary --> Rule Parameters` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." msgstr "" -#: ../../content/applications/hr/payroll.rst:637 +#: ../../content/applications/hr/payroll.rst:642 msgid "Other input types" msgstr "" -#: ../../content/applications/hr/payroll.rst:639 +#: ../../content/applications/hr/payroll.rst:644 msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by navigating to :menuselection:`Payroll app --> Configuration --> Salary --> Other Input Types`." msgstr "" @@ -5753,11 +5963,11 @@ msgid "A list of other input types for payroll that can be selected when creatin "a payslip." msgstr "" -#: ../../content/applications/hr/payroll.rst:648 +#: ../../content/applications/hr/payroll.rst:653 msgid "To create a new input type, click the :guilabel:`New` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field." msgstr "" -#: ../../content/applications/hr/payroll.rst:653 +#: ../../content/applications/hr/payroll.rst:658 msgid "The :guilabel:`Code` is used in the salary rules to compute payslips. If the :guilabel:`Availability in Structure` field is left blank, it indicates that the new input type is available for all payslips and is not exclusive to a specific structure." msgstr "" @@ -5765,19 +5975,19 @@ msgstr "" msgid "A new Input Type form filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:664 +#: ../../content/applications/hr/payroll.rst:669 msgid "Salary attachment types" msgstr "" -#: ../../content/applications/hr/payroll.rst:666 +#: ../../content/applications/hr/payroll.rst:671 msgid "Salary attachments, also thought of as \"wage garnishments\", are portions of earnings taken out of a payslip for something specific. Much like all other aspects of payroll configurations, the types of salary attachments **must** be defined." msgstr "" -#: ../../content/applications/hr/payroll.rst:670 +#: ../../content/applications/hr/payroll.rst:675 msgid "To view the currently configured salary attachments, navigate to :menuselection:`Payroll app --> Configuration --> Salary --> Salary Attachment Types`. The default salary attachment types are :guilabel:`Attachment of Salary`, :guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." msgstr "" -#: ../../content/applications/hr/payroll.rst:674 +#: ../../content/applications/hr/payroll.rst:679 msgid "To make a new type of salary attachment, click the :guilabel:`New` button. Then, enter the :guilabel:`Name`, the :guilabel:`Code` (used in the salary rules to compute payslips), and decide if it should have :guilabel:`No End Date`." msgstr "" @@ -5785,27 +5995,28 @@ msgstr "" msgid "A new salary attachment form filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:683 +#: ../../content/applications/hr/payroll.rst:688 +#: ../../content/applications/hr/recruitment.rst:168 msgid "Salary package configurator" msgstr "" -#: ../../content/applications/hr/payroll.rst:685 +#: ../../content/applications/hr/payroll.rst:690 msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll app --> Configuration --> Salary Package Configurator` menu all affect an employee's potential salary. These sections (:guilabel:`Benefits`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what benefits can be offered to an employee in their salary package." msgstr "" -#: ../../content/applications/hr/payroll.rst:690 +#: ../../content/applications/hr/payroll.rst:695 msgid "Depending on what information an employee enters (such as deductions, dependents, etc.), their salary is adjusted accordingly. When an applicant applies for a job on the company website, the sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and what is populated, as the applicant enters information." msgstr "" -#: ../../content/applications/hr/payroll.rst:696 +#: ../../content/applications/hr/payroll.rst:701 msgid "Benefits" msgstr "" -#: ../../content/applications/hr/payroll.rst:698 +#: ../../content/applications/hr/payroll.rst:703 msgid "When offering potential employees a position, there can be certain benefits set in Odoo, in addition to the salary, to make an offer more appealing (such as extra time off, the use of a company car, reimbursement for a phone or internet, etc.)." msgstr "" -#: ../../content/applications/hr/payroll.rst:702 +#: ../../content/applications/hr/payroll.rst:707 msgid "To view the benefits, go to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Benefits`. Benefits are grouped by :guilabel:`Structure type`, and the benefit listed for a particular structure type is only available for that specific structure." msgstr "" @@ -5813,67 +6024,67 @@ msgstr "" msgid "A list view of all the benefits available for each structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:711 +#: ../../content/applications/hr/payroll.rst:716 msgid "A company has two structure types, one labeled :guilabel:`Employee`, and another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type contains the benefit of using a company car, while the :guilabel:`Intern` structure type has a meal voucher benefit available." msgstr "" -#: ../../content/applications/hr/payroll.rst:715 +#: ../../content/applications/hr/payroll.rst:720 msgid "A person hired under the :guilabel:`Employee` structure type can use the company car benefit, but cannot have meal vouchers. A person hired under the :guilabel:`Intern` structure type would have meal voucher benefits available to them, not the use of a company car." msgstr "" -#: ../../content/applications/hr/payroll.rst:719 +#: ../../content/applications/hr/payroll.rst:724 msgid "To make a new benefit, click the :guilabel:`New` button, and enter the information in the fields on the blank benefits form." msgstr "" -#: ../../content/applications/hr/payroll.rst:722 +#: ../../content/applications/hr/payroll.rst:727 msgid "The various fields for creating a benefit are as follows:" msgstr "" -#: ../../content/applications/hr/payroll.rst:727 +#: ../../content/applications/hr/payroll.rst:732 msgid ":guilabel:`Benefits`: enter the name for the benefit. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:728 +#: ../../content/applications/hr/payroll.rst:733 msgid ":guilabel:`Benefit Field`: select from the drop-down menu the type of benefit this is." msgstr "" -#: ../../content/applications/hr/payroll.rst:729 +#: ../../content/applications/hr/payroll.rst:734 msgid ":guilabel:`Cost Field`: select from the drop-down menu the type of cost incurred by the company for this specific benefit. The default options are :guilabel:`Calendar Changed`, :guilabel:`Yearly Cost (Real)`, :guilabel:`Extra Time Off`, :guilabel:`Hourly Wage`, :guilabel:`Part Time`, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and :guilabel:`Work time rate`. Depending on the localization settings, additional options are available." msgstr "" -#: ../../content/applications/hr/payroll.rst:734 +#: ../../content/applications/hr/payroll.rst:739 msgid ":guilabel:`Related Type`: select from the drop-down menu what type of benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, :guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:738 +#: ../../content/applications/hr/payroll.rst:743 msgid ":guilabel:`Benefit Field`: select from the drop-down menu the specific field on the contract the benefit appears." msgstr "" -#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll.rst:745 msgid ":guilabel:`Cost Field`: select the specific field on the contract that the cost of the benefit is linked to, using the drop-down menu. If this field is left blank, the cost of the benefit is not computed in the employee budget." msgstr "" -#: ../../content/applications/hr/payroll.rst:743 +#: ../../content/applications/hr/payroll.rst:748 msgid ":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should impact the employee's net salary." msgstr "" -#: ../../content/applications/hr/payroll.rst:745 +#: ../../content/applications/hr/payroll.rst:750 msgid ":guilabel:`Requested Documents`: select any document that is required to be submitted for this benefit, from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:747 +#: ../../content/applications/hr/payroll.rst:752 msgid ":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit that is required in order for this specific benefit to be offered to the employee." msgstr "" -#: ../../content/applications/hr/payroll.rst:750 +#: ../../content/applications/hr/payroll.rst:755 msgid "For example, a benefit for car insurance would populate `Company Car` in this field. This would allow the car insurance benefit to **only** be displayed if the employee has selected/enabled the benefit of a company car." msgstr "" -#: ../../content/applications/hr/payroll.rst:753 +#: ../../content/applications/hr/payroll.rst:758 msgid ":guilabel:`Salary Structure Type`: select from the drop-down menu which salary structure type this benefit applies to. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:755 +#: ../../content/applications/hr/payroll.rst:760 msgid ":guilabel:`Unit of Measure`: select the metric that the benefit is granted, using the drop-down menu. The options are :guilabel:`Days`, :guilabel:`Percent`, or :guilabel:`Currency`." msgstr "" @@ -5881,100 +6092,100 @@ msgstr "" msgid "A new benefit form filled out for an internet subscription." msgstr "" -#: ../../content/applications/hr/payroll.rst:763 +#: ../../content/applications/hr/payroll.rst:768 msgid "Display section" msgstr "" -#: ../../content/applications/hr/payroll.rst:765 +#: ../../content/applications/hr/payroll.rst:770 msgid ":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in the salary package configurator." msgstr "" -#: ../../content/applications/hr/payroll.rst:767 +#: ../../content/applications/hr/payroll.rst:772 msgid ":guilabel:`Display Type`: select from the drop-down menu how this benefit is displayed. The options are :guilabel:`Always Selected`, :guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, :guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:772 +#: ../../content/applications/hr/payroll.rst:777 msgid "Depending on the selection made, additional configurations need to be made. For example, if :guilabel:`Radio Buttons` is selected, the individual radio buttons must be entered." msgstr "" -#: ../../content/applications/hr/payroll.rst:774 +#: ../../content/applications/hr/payroll.rst:779 msgid ":guilabel:`Icon`: an icon from the `Font Awesome 4 library `_ can be visible for this benefit. Enter the text code for the icon in this field. For example, to display a suitcase icon, the code `fa fa-suitcase` is entered on this line." msgstr "" -#: ../../content/applications/hr/payroll.rst:777 +#: ../../content/applications/hr/payroll.rst:782 msgid ":guilabel:`Hide Description`: tick the checkbox to hide the benefit description if the benefit is not selected by the employee." msgstr "" -#: ../../content/applications/hr/payroll.rst:779 +#: ../../content/applications/hr/payroll.rst:784 msgid ":guilabel:`Folded`: if the benefit should be folded, or hidden, because it is dependant on another benefit selection, tick the checkbox. The following fields appear when this is active:" msgstr "" -#: ../../content/applications/hr/payroll.rst:782 +#: ../../content/applications/hr/payroll.rst:787 msgid ":guilabel:`Fold Label`: enter a name for the folded section of the benefit." msgstr "" -#: ../../content/applications/hr/payroll.rst:783 +#: ../../content/applications/hr/payroll.rst:788 msgid ":guilabel:`Fold Res Field`: select the contract field this benefit is tied to using the drop-down menu. If this field is selected on the contract, then this benefit becomes visible." msgstr "" -#: ../../content/applications/hr/payroll.rst:787 +#: ../../content/applications/hr/payroll.rst:792 msgid "Activity section" msgstr "" -#: ../../content/applications/hr/payroll.rst:789 +#: ../../content/applications/hr/payroll.rst:794 msgid ":guilabel:`Activity Type`: from the drop-down menu, select the activity type that is automatically created when this benefit is selected by the employee." msgstr "" -#: ../../content/applications/hr/payroll.rst:791 +#: ../../content/applications/hr/payroll.rst:796 msgid ":guilabel:`Activity Creation`: select when the activity is created, either when the :guilabel:`Employee signs his contract`, or when the :guilabel:`Contract is countersigned`. Click the radio button next to the desired selection." msgstr "" -#: ../../content/applications/hr/payroll.rst:794 +#: ../../content/applications/hr/payroll.rst:799 msgid ":guilabel:`Activity Creation Type`: select the parameters for when the activity is created, either :guilabel:`When the benefit is set` or :guilabel:`When the benefit is modified`. Click the radio button next to the desired selection." msgstr "" -#: ../../content/applications/hr/payroll.rst:797 +#: ../../content/applications/hr/payroll.rst:802 msgid ":guilabel:`Assigned to`: select the user the activity is automatically assigned to, using the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:801 +#: ../../content/applications/hr/payroll.rst:806 #: ../../content/applications/hr/payroll/contracts.rst:143 msgid "Sign section" msgstr "" -#: ../../content/applications/hr/payroll.rst:803 +#: ../../content/applications/hr/payroll.rst:808 msgid ":guilabel:`Template to Sign`: if the employee is required to sign a document when selecting this benefit, select the document template from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:806 +#: ../../content/applications/hr/payroll.rst:811 msgid "For example, a benefit regarding the use of a company car may require the employee to sign a document acknowledging the company's car policies." msgstr "" -#: ../../content/applications/hr/payroll.rst:812 +#: ../../content/applications/hr/payroll.rst:817 msgid "Provide any additional information in this tab to help clarify the benefit." msgstr "" -#: ../../content/applications/hr/payroll.rst:815 +#: ../../content/applications/hr/payroll.rst:820 msgid "Personal info" msgstr "" -#: ../../content/applications/hr/payroll.rst:817 +#: ../../content/applications/hr/payroll.rst:822 msgid "Every employee in Odoo has an *employee card* which is created when a candidate becomes an employee. This card includes all of their personal information, resume, work information, and documents." msgstr "" -#: ../../content/applications/hr/payroll.rst:821 +#: ../../content/applications/hr/payroll.rst:826 msgid "The personal information is gathered from the salary package configurator section that a candidate fills out after being offered a position. This personal information is then transferred to the employee card when they are hired." msgstr "" -#: ../../content/applications/hr/payroll.rst:825 +#: ../../content/applications/hr/payroll.rst:830 msgid "To view an employee's card, go to the main :menuselection:`Employees` app dashboard, and click on the employee's card." msgstr "" -#: ../../content/applications/hr/payroll.rst:829 +#: ../../content/applications/hr/payroll.rst:834 msgid "An employee card can be thought of as an employee personnel file." msgstr "" -#: ../../content/applications/hr/payroll.rst:831 +#: ../../content/applications/hr/payroll.rst:836 msgid "The :guilabel:`Personal Info` section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Personal Info`." msgstr "" @@ -5982,31 +6193,31 @@ msgstr "" msgid "A list of all the personal information that appears on the employee card to enter." msgstr "" -#: ../../content/applications/hr/payroll.rst:839 +#: ../../content/applications/hr/payroll.rst:844 msgid "To edit a personal info entry, select an entry from the list on the :guilabel:`Personal Info` page, and modify the personal info on the form that appears." msgstr "" -#: ../../content/applications/hr/payroll.rst:842 +#: ../../content/applications/hr/payroll.rst:847 msgid "To create a new personal info entry, click the :guilabel:`New` button." msgstr "" -#: ../../content/applications/hr/payroll.rst:844 +#: ../../content/applications/hr/payroll.rst:849 msgid "The required fields, aside from entering the :guilabel:`Information` name, are :guilabel:`Related Model`, :guilabel:`Related Field`, and :guilabel:`Category`." msgstr "" -#: ../../content/applications/hr/payroll.rst:847 +#: ../../content/applications/hr/payroll.rst:852 msgid "Select a :guilabel:`Related Model` from the drop-down menu. :guilabel:`Employee` populates the field by default, but the :guilabel:`Bank Account` option is also available if the information is related to a bank account, instead." msgstr "" -#: ../../content/applications/hr/payroll.rst:851 +#: ../../content/applications/hr/payroll.rst:856 msgid "Select a :guilabel:`Related Field` from the drop-down menu that best describes what kind of personal information this entry is, and where it is stored in the backend. Then, select a :guilabel:`Category` from the drop-down menu that the personal information should be under, such as :guilabel:`Address` or :guilabel:`Personal Documents`." msgstr "" -#: ../../content/applications/hr/payroll.rst:856 +#: ../../content/applications/hr/payroll.rst:861 msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`." msgstr "" -#: ../../content/applications/hr/payroll.rst:859 +#: ../../content/applications/hr/payroll.rst:864 msgid "Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card. The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, like a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." msgstr "" @@ -6014,71 +6225,71 @@ msgstr "" msgid "New personal information entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/payroll.rst:876 msgid "The resumé section, housed within the salary package configurator section of the settings menu, is how salary information rules are configured when offering a position to potential employees." msgstr "" -#: ../../content/applications/hr/payroll.rst:874 +#: ../../content/applications/hr/payroll.rst:879 msgid "When an offer is sent to a prospective employee, the values for the offer are computed from these settings, and appear on the offer page." msgstr "" -#: ../../content/applications/hr/payroll.rst:877 +#: ../../content/applications/hr/payroll.rst:882 msgid "To configure this section, navigate to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Resumé`." msgstr "" -#: ../../content/applications/hr/payroll.rst:880 +#: ../../content/applications/hr/payroll.rst:885 msgid "By default, there are three :guilabel:`Salary Structure Types` pre-configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and :guilabel:`None`." msgstr "" -#: ../../content/applications/hr/payroll.rst:883 +#: ../../content/applications/hr/payroll.rst:888 msgid "Each :guilabel:`Salary Structure Type` has several rules configured. These affect how an offer is calculated using that particular :guilabel:`Salary Structure Type`." msgstr "" -#: ../../content/applications/hr/payroll.rst:886 +#: ../../content/applications/hr/payroll.rst:891 msgid "To create a new rule, click the :guilabel:`New` button, and a blank :guilabel:`Contract Salary Resumé` form loads." msgstr "" -#: ../../content/applications/hr/payroll.rst:891 +#: ../../content/applications/hr/payroll.rst:896 msgid ":guilabel:`Information`: type in a name for this field." msgstr "" -#: ../../content/applications/hr/payroll.rst:892 +#: ../../content/applications/hr/payroll.rst:897 msgid ":guilabel:`Category`: select the category this value is housed under, using the drop-down menu. The default options are :guilabel:`Monthly Salary`, :guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and :guilabel:`Total`." msgstr "" -#: ../../content/applications/hr/payroll.rst:896 +#: ../../content/applications/hr/payroll.rst:901 msgid "New categories can be made if needed." msgstr "" -#: ../../content/applications/hr/payroll.rst:898 +#: ../../content/applications/hr/payroll.rst:903 msgid "Click the :guilabel:`New` button, then enter the name for the new category in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last, enter a number for the sequence. This corresponds to where this rule appears in the :guilabel:`Salary Structure Type` rule list." msgstr "" -#: ../../content/applications/hr/payroll.rst:903 +#: ../../content/applications/hr/payroll.rst:908 msgid "Finally, click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/payroll.rst:904 +#: ../../content/applications/hr/payroll.rst:909 msgid ":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added in the monthly total calculation." msgstr "" -#: ../../content/applications/hr/payroll.rst:906 +#: ../../content/applications/hr/payroll.rst:911 msgid ":guilabel:`Unit of Measure`: select what kind of value this rule is, either :guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." msgstr "" -#: ../../content/applications/hr/payroll.rst:909 +#: ../../content/applications/hr/payroll.rst:914 msgid ":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for compensation in the form of time off, and :guilabel:`Percent` is for a monetary value awarded that is based upon another metric, such as commissions." msgstr "" -#: ../../content/applications/hr/payroll.rst:912 +#: ../../content/applications/hr/payroll.rst:917 msgid ":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure Type` this rule is nested under, from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:914 +#: ../../content/applications/hr/payroll.rst:919 msgid ":guilabel:`Value Type`: select how the value is computed, using the drop-down menu. The default options are :guilabel:`Fixed Value`, :guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of Benefits Values`, and :guilabel:`Monthly Total`." msgstr "" -#: ../../content/applications/hr/payroll.rst:917 +#: ../../content/applications/hr/payroll.rst:922 msgid ":guilabel:`Code`: select the code this rule applies to from the drop-down menu." msgstr "" @@ -6086,28 +6297,28 @@ msgstr "" msgid "The net wage rule form filled out, with all the information for net pay." msgstr "" -#: ../../content/applications/hr/payroll.rst:924 +#: ../../content/applications/hr/payroll.rst:929 msgid "Jobs" msgstr "" -#: ../../content/applications/hr/payroll.rst:926 +#: ../../content/applications/hr/payroll.rst:931 msgid "Since the *Payroll* application is responsible for paying employees for specific job positions, the complete list of job positions can be found in both the *Payroll* and *Recruitment* applications." msgstr "" -#: ../../content/applications/hr/payroll.rst:932 +#: ../../content/applications/hr/payroll.rst:937 #: ../../content/applications/hr/recruitment/new_job.rst:3 msgid "Job positions" msgstr "" -#: ../../content/applications/hr/payroll.rst:934 +#: ../../content/applications/hr/payroll.rst:939 msgid "The job positions listed in the *Payroll* application are identical to the job positions listed in the *Recruitment* application. If a new job position is added in the *Recruitment* application, it is also visible in the *Payroll* application, and vice versa." msgstr "" -#: ../../content/applications/hr/payroll.rst:938 +#: ../../content/applications/hr/payroll.rst:943 msgid "To view the job positions, navigate to :menuselection:`Payroll app --> Configuration --> Jobs: Job Positions`." msgstr "" -#: ../../content/applications/hr/payroll.rst:941 +#: ../../content/applications/hr/payroll.rst:946 msgid "A list of all the job positions appear, along with the corresponding department, on the :guilabel:`Job Position` page." msgstr "" @@ -6115,31 +6326,31 @@ msgstr "" msgid "A list of all the job positions and corresponding departments." msgstr "" -#: ../../content/applications/hr/payroll.rst:948 +#: ../../content/applications/hr/payroll.rst:953 msgid "To create a new job description, click the :guilabel:`New` button and a job form appears." msgstr "" -#: ../../content/applications/hr/payroll.rst:950 +#: ../../content/applications/hr/payroll.rst:955 msgid "Enter the information on the form for the new position. The information is identical as to the information entered when creating a new job position in the *Recruitment* application." msgstr "" -#: ../../content/applications/hr/payroll.rst:953 +#: ../../content/applications/hr/payroll.rst:958 msgid "Refer to the :doc:`../hr/recruitment/new_job` documentation for more details on how to fill out this form." msgstr "" -#: ../../content/applications/hr/payroll.rst:957 +#: ../../content/applications/hr/payroll.rst:962 msgid ":doc:`payroll/contracts`" msgstr "" -#: ../../content/applications/hr/payroll.rst:958 +#: ../../content/applications/hr/payroll.rst:963 msgid ":doc:`payroll/payslips`" msgstr "" -#: ../../content/applications/hr/payroll.rst:959 +#: ../../content/applications/hr/payroll.rst:964 msgid ":doc:`payroll/work_entries`" msgstr "" -#: ../../content/applications/hr/payroll.rst:960 +#: ../../content/applications/hr/payroll.rst:965 msgid ":doc:`payroll/reporting`" msgstr "" @@ -7828,7 +8039,7 @@ msgid "Recruitment" msgstr "" #: ../../content/applications/hr/recruitment.rst:8 -msgid "Odoo keeps all job applicants organized with a pre-configured series of steps and stages that each applicant goes through. Each stage has a specific step(s) that should be performed. These range from scheduling a phone call, conducting an interview, to sending a job offer, just to name a few. This process is referred to as the 'applicant flow'." +msgid "Odoo keeps all job applicants organized with a pre-configured series of steps and stages that each applicant goes through. Each stage has a specific step(s) that should be performed. These range from scheduling a phone call, conducting an interview, or sending a job offer, for example. This process is referred to as the 'applicant flow.'" msgstr "" #: ../../content/applications/hr/recruitment.rst:13 @@ -7844,95 +8055,243 @@ msgid "The applicant flow explained in this document is the default flow in Odoo msgstr "" #: ../../content/applications/hr/recruitment.rst:26 -msgid "The applicant flow with all its stages are universal and applies to all job positions, unless specified. :ref:`A specific stage can be configured ` to be job-specific, meaning that specific stage is only visible for that specific job position. Otherwise, if a new stage is created, or an existing stage is modified, those changes will be visible on all job positions." +msgid "The applicant flow with all its stages are universal and applies to all job positions, unless specified. :ref:`A specific stage can be configured ` to be job-specific, meaning that specific stage is only visible for that specific job position. Otherwise, if a new stage is created, or an existing stage is modified, those changes are visible on all job positions." msgstr "" -#: ../../content/applications/hr/recruitment.rst:35 -msgid "To access the kanban view for a job position, navigate to the main :menuselection:`Recruitment app` dashboard, which is the default view when opening the application. All job positions appear on the main dashboard. Click the :guilabel:`New Applications` smart button on a job position card to navigate to the kanban view for all the applicants for that particular job position." +#: ../../content/applications/hr/recruitment.rst:37 +msgid "Before creating a job position in Odoo, configure the necessary settings for the *Recruitment* app. To view and edit the settings, navigate to :menuselection:`Recruitment app --> Configuration --> Settings`. After any changes are made, click the :guilabel:`Save` button in the top-left corner to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:43 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:45 +msgid "The :guilabel:`Job Posting` section of the *Recruitment* app settings has only one selection to make. If job positions are to be posted to the company's website, enable the :guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:50 +msgid "The :guilabel:`Online Posting` is only available if the *Website* application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:53 +msgid "Recruitment process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:55 +msgid "The :guilabel:`Recruitment process` section of the settings page specifies what the database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:59 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Odoo is capable of having a survey sent to an applicant to gather more information about them. Surveys can be thought of as exams, or questionnaires, and can be customized in various ways to provide the recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:65 +msgid "Enable the :guilabel:`Send Interview Survey` option to send surveys to applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview Survey` internal link appears. Click the :icon:`fa-arrow-right` :guilabel:`Interview Survey` link to navigate to a list of all created surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "This list includes all surveys that were created in the database, not just surveys used in the *Recruitment* app. If no surveys have been created, the surveys list displays a :guilabel:`No Survey Found` message, and presents options to create a survey from several pre-configured survey templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "For more detailed information about surveys, refer to the :doc:`survey essentials <../marketing/surveys/create>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:80 +msgid "Enabling the :guilabel:`Send Interview Survey` option will install the *Surveys* application once the settings are saved, if it is not installed already." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:84 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:86 +msgid "It is possible to send text messages to applicants directly through the *Recruitment* app. To do so, enable the :guilabel:`Send SMS` option. This option requires credits to use, which can be obtained by clicking the :icon:`fa-arrow-right` :guilabel:`Buy credits` internal link that emerges when the feature is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:92 +msgid "For more information, refer to the :doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:98 +msgid "CV display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:100 +msgid "When applicants submit an application, one of the default required fields is a resumé, or :abbr:`CV (curriculum vitae)`. All resumés are stored in the *Documents* application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:104 +msgid "A resumé has the option to appear on the applicant's form, which can be viewed by clicking on the applicant's card. The resumé appears on the right-side of the screen. If this is not enabled, the resumé is accessed via a link in the chatter, where it needs to be clicked to expand and view it, or downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "Enable the :guilabel:`CV Display` option to show the resumé on the applicant's card by default, and in addition to the document link. When enabled, the resumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "For the resumé to appear on the right-side, the browser window must be in full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:117 +msgid "If the browser window is set to a size smaller than the entire width of the screen (not full-screen), then the resumé does not appear on the right-side. Instead, the resumé appears in the :guilabel:`Files` section of the chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The resumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:128 +msgid "CV digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "When an application is submitted using any of the available methods, such as an online application submission, emailing a resume to the job position alias, or creating an applicant record directly from the database, it is possible to have Odoo extract the applicant's name, phone number, and email address from the resumé and populate the applicant's form. To do so, enable the :guilabel:`CV Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:136 +msgid "When enabled, additional options appear. Click on the corresponding radio button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:139 +msgid ":guilabel:`Do not digitize`: this option turns off resumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +msgid ":guilabel:`Digitize on demand only`: this option only digitizes resumes when requested. A :guilabel:`Digitize document` buttons appears on applicant cards. When clicked, the resumé is scanned and the applicant's card is updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:143 +msgid ":guilabel:`Digitize automatically`: this option automatically digitizes all resumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:146 +msgid "Beneath these options are two additional links. Click the :icon:`fa-arrow-right` :guilabel:`Buy credits` button to purchase credits for CV digitization. Click the :icon:`fa-arrow-right` :guilabel:`View My Services` to view a list of all current services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:151 +msgid "For more information on document digitization and :abbr:`IAP's (in-app purchases)`, refer to the :doc:`In-app purchase (IAP) <../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:155 +msgid "The :guilabel:`Do not digitize` option for :guilabel:`CV digitization (OCR)` at first may seem like a redundancy. It seems to be the same as disabling the :guilabel:`CV digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:159 +msgid "When the :guilabel:`CV digitization (OCR)` option is enabled, a module is installed so that resumés can be scanned. Disabling this option would uninstall the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "If at some point, there is a desire to temporarily stop digitizing resumés, the :guilabel:`Do not digitize` option is selected. The reason this option is available is so that the module is not uninstalled, allowing for digitization to be enabled in the future by selecting one of the other two options." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:170 +msgid "When sending an offer to an applicant, an expiration date can be set on the offer. Enter the number of days an offer is valid for in the :guilabel:`days` field. After the set amount of days has passed, if the applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "To access the Kanban view for a job position, navigate to the main :menuselection:`Recruitment app` dashboard, which is the default view when opening the application. All job positions appear on the main dashboard. Click the :guilabel:`(#) New Applications` smart button on a job position card to navigate to the Kanban view for all the applicants for that particular job position." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 msgid "Main dashboard view of job position card, showing new applications button." msgstr "" -#: ../../content/applications/hr/recruitment.rst:44 -msgid "Inside the job application, the kanban stages appear, with all the applicants populated in their respective columns, indicating what stage they are currently in. There are five default stages in Odoo:" +#: ../../content/applications/hr/recruitment.rst:186 +msgid "Inside the job application, the Kanban stages appear, with all the applicants populated in their respective columns, indicating what stage they are currently in. There are six default stages in Odoo:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:48 +#: ../../content/applications/hr/recruitment.rst:190 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:191 msgid ":ref:`Initial Qualification `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:49 +#: ../../content/applications/hr/recruitment.rst:192 msgid ":ref:`First Interview `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:50 +#: ../../content/applications/hr/recruitment.rst:193 msgid ":ref:`Second Interview `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:51 +#: ../../content/applications/hr/recruitment.rst:194 msgid ":ref:`Contract Proposal `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:52 +#: ../../content/applications/hr/recruitment.rst:195 msgid ":ref:`Contract Signed `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:54 -msgid "The last column, :guilabel:`Contract Signed`, is folded by default, meaning that the column appears in gray and the applicants in it are hidden from view. To expand the folded stage and view the applicant cards for that column, click anywhere on the thin gray column that says the stage name and the column expands, revealing the applicants." +#: ../../content/applications/hr/recruitment.rst:197 +msgid "The last column, :guilabel:`Contract Signed`, is folded by default. Folded columns appear gray, and the applicants in it are hidden from view. To expand the folded stage and view the applicant cards for that column, click anywhere on the thin gray column that says the stage name and the column expands, revealing the applicants." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 -msgid "Expand a folded column by clicking on it in the kanban view." +msgid "Expand a folded column by clicking on it in the Kanban view." msgstr "" -#: ../../content/applications/hr/recruitment.rst:63 -msgid "Each stage has a color-coded bar beneath the stage name, giving information about the applicant's status in the stage. The colors are:" +#: ../../content/applications/hr/recruitment.rst:206 +msgid "Each stage has a color-coded bar beneath the stage name, providing status information for the applicant's in that specific stage. The status colors are:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:66 -msgid ":guilabel:`Green`: there are applicants in the stage with an activity that is either already scheduled or needs to be scheduled in the future (such as a phone call or interview), according to the parameters for that particular stage." +#: ../../content/applications/hr/recruitment.rst:209 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:69 -msgid ":guilabel:`Yellow`: there are applicants in the stage with an activity either scheduled for today or due to be scheduled today." +#: ../../content/applications/hr/recruitment.rst:210 +msgid ":guilabel:`Red`: the applicant is blocked from moving to the next stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:71 -msgid ":guilabel:`Red`: there are applicants in the stage with overdue activities which need to be scheduled." +#: ../../content/applications/hr/recruitment.rst:211 +msgid ":guilabel:`Gray`: the applicant is still in progress in the current stage and is neither ready nor blocked from the next stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:73 -msgid ":guilabel:`Gray`: there are either no activities currently scheduled and no future activities that are required to be scheduled, or there are no applicants currently in the stage." +#: ../../content/applications/hr/recruitment.rst:214 +msgid "The status for each card is set manually. To set the status, click on the small circle in the lower-left of the applicant card. A status pop-up window appears. Click on the desired status for the applicant. The status dot on the applicant card as well as the status bar updates." msgstr "" -#: ../../content/applications/hr/recruitment.rst:79 +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:223 +msgid "The names for the three status colors (`In Progress`, `Blocked`, and `Ready for Next Stage`) :ref:`can be modified `, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:229 msgid "Customize stages" msgstr "" -#: ../../content/applications/hr/recruitment.rst:81 +#: ../../content/applications/hr/recruitment.rst:231 msgid "Stages can be modified, added, or deleted to best meet the needs of the particular hiring steps of a business." msgstr "" -#: ../../content/applications/hr/recruitment.rst:85 +#: ../../content/applications/hr/recruitment.rst:235 msgid "New stage" msgstr "" -#: ../../content/applications/hr/recruitment.rst:87 -msgid "To create a new stage, click on :guilabel:`+ Add a Column` and a new column appears. Enter the title for the new stage in the :guilabel:`Column title` field, then click :guilabel:`Add`. The new column appears, and another new stage is available to create. If no new stages are needed, click anywhere on the screen to exit the new column creation." +#: ../../content/applications/hr/recruitment.rst:237 +msgid "To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new column appears. Enter the title for the new stage in the :guilabel:`Stage title` field, then click :guilabel:`Add`. The new column appears, and another new stage is available to create. If no new stages are needed, click anywhere on the screen to exit the new stage creation." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 -msgid "The plus sign to click in order to add a new column to the kanban stages." +msgid "The plus sign to click to add a new column to the Kanban stages." msgstr "" -#: ../../content/applications/hr/recruitment.rst:99 +#: ../../content/applications/hr/recruitment.rst:249 msgid "Modify stage" msgstr "" -#: ../../content/applications/hr/recruitment.rst:101 -msgid "To modify the settings of a stage, hover over the name of the stage, and a :guilabel:`⚙️ (gear)` icon appears in the upper right hand side of the stage. Click on the :guilabel:`⚙️ (gear)` icon and a menu appears. Then click on the :guilabel:`Edit Stage` option. An :guilabel:`Edit Column` form appears. Make any modifications to the form, then click :guilabel:`Save` when done." +#: ../../content/applications/hr/recruitment.rst:251 +msgid "To modify the settings of a stage, hover over the name of the stage, and a :icon:`fa-cog` :guilabel:`(gear)` icon appears in the upper right hand side of the stage. Click on the :icon:`fa-cog` :guilabel:`(gear)` icon and a menu appears. Then click on the :guilabel:`Edit` option. An :guilabel:`Edit: (Stage)` form appears. Make any desired modifications to the form, then click :guilabel:`Save & Close` when done." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 @@ -7940,128 +8299,140 @@ msgid "The gear icon that appears when a column name is moused over, and the dro "displays when clicked." msgstr "" -#: ../../content/applications/hr/recruitment.rst:112 -msgid "Edit column form" +#: ../../content/applications/hr/recruitment.rst:265 +msgid "Edit stage form" msgstr "" -#: ../../content/applications/hr/recruitment.rst:114 -msgid "The :guilabel:`Edit Column` form is where the stage's settings are configured. The only required fields are the :guilabel:`Stage Name`, and the :guilabel:`Tooltips` section." +#: ../../content/applications/hr/recruitment.rst:267 +msgid "The :guilabel:`Edit: (Stage)` form is where the stage's settings are configured. The only required field is the :guilabel:`Stage Name`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:117 +#: ../../content/applications/hr/recruitment.rst:270 msgid "The fields to be populated or modified are:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:119 +#: ../../content/applications/hr/recruitment.rst:272 msgid ":guilabel:`Stage Name`: type in a name for the stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:120 -msgid ":guilabel:`Email Template`: select an email template to be used from the drop-down menu. If a template is selected, when the applicant card enters the stage, an email will automatically be sent to the applicant using the selected template." +#: ../../content/applications/hr/recruitment.rst:273 +msgid ":guilabel:`Email Template`: select an email template to be used from the drop-down menu. If a template is selected, when the applicant card enters the stage, an email is automatically sent to the applicant using the selected template." msgstr "" -#: ../../content/applications/hr/recruitment.rst:123 +#: ../../content/applications/hr/recruitment.rst:276 msgid ":guilabel:`Folded in Kanban`: check the box to have the stage appear folded (hidden) at all times in the default view." msgstr "" -#: ../../content/applications/hr/recruitment.rst:125 +#: ../../content/applications/hr/recruitment.rst:278 msgid ":guilabel:`Hired Stage`: check the box if this stage indicates that the applicant is hired. When an applicant's card enters this stage, the card displays a :guilabel:`Hired` banner in the upper right corner. If this box is checked, this stage is used to determine the hire date of an applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:129 -msgid ":guilabel:`Job Specific`: if the stage only applies to a specific job position(s), select the job position(s) from the drop-down menu. Multiple job positions can be selected." +#: ../../content/applications/hr/recruitment.rst:282 +msgid ":guilabel:`Job Specific`: if the stage only applies to specific job positions, select the job positions from the drop-down menu. Multiple job positions can be selected." msgstr "" -#: ../../content/applications/hr/recruitment.rst:131 -msgid ":guilabel:`Show in Referrals`: check the box if this stage should be seen in the *Referrals* application, and allow the referrer to accrue points when a referral of theirs reaches this stage. If this is active, a :guilabel:`Points` field appears. Enter the amount of referral points the employee receives when an applicant enters this stage." +#: ../../content/applications/hr/recruitment.rst:284 +msgid ":guilabel:`Show in Referrals`: check the box if this stage should be seen in the *Referrals* application, and allow the referrer to accrue points when a referral of theirs reaches this stage. If this is active, a :guilabel:`Points` field appears. Enter the amount of referral points the employee receives when an applicant enters this stage. The *Referrals* app must be installed in order to use this option." msgstr "" -#: ../../content/applications/hr/recruitment.rst:135 -msgid ":guilabel:`Tooltips` section: there are three pre-configured labels (colored circles) for each applicant's card, indicating its status. These colors are displayed at the top of each stage to reflect the statuses of the applicants in the stage. The *names* for the label can be modified, but the label itself (the color) cannot. The default names and labels are: :guilabel:`In Progress` (gray), :guilabel:`Blocked` (red), and :guilabel:`Ready for Next Stage` (green)." +#: ../../content/applications/hr/recruitment.rst:289 +msgid ":guilabel:`Tooltips` section: there are three pre-configured status labels (colored circles) for each applicant's card, indicating its status. These colors are displayed at the top of each stage to reflect the statuses of the applicants in the stage. The *names* for the label can be modified, but the label itself (the color) cannot. The default names and labels are: :guilabel:`In Progress` (gray), :guilabel:`Blocked` (red), and :guilabel:`Ready for Next Stage` (green)." msgstr "" -#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/recruitment.rst:294 msgid ":guilabel:`Requirements`: enter any internal notes for this stage explaining any requirements of the stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:144 +#: ../../content/applications/hr/recruitment.rst:298 msgid "Delete stage" msgstr "" -#: ../../content/applications/hr/recruitment.rst:146 -msgid "If a stage is no longer needed, the stage can be deleted. To delete a stage, hover over the name of the stage, and a :guilabel:`⚙️ (gear)` icon appears. First, click on the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu, then click :guilabel:`Delete`. A pop-up warning appears, asking :guilabel:`Are you sure you want to remove this column?`. Click :guilabel:`OK` to delete the column." +#: ../../content/applications/hr/recruitment.rst:300 +msgid "If a stage is no longer needed, the stage can be deleted. To delete a stage, hover over the name of the stage, and a :icon:`fa-cog` :guilabel:`(gear)` icon appears. First, click on the :icon:`fa-cog` :guilabel:`(gear)` icon to reveal a drop-down menu, then click :guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, asking :guilabel:`Are you sure you want to delete this column?` Click :guilabel:`Delete` to delete the column." msgstr "" -#: ../../content/applications/hr/recruitment.rst:152 -msgid "If there are applicants currently in the stage being deleted, an error pops up when attempting to delete the stage, explaining that there are records in the stage which need to be deleted, archived, or moved to a different stage before deleting." +#: ../../content/applications/hr/recruitment.rst:307 +msgid "If there are applicants currently in the stage being deleted, an error pops up when attempting to delete the stage. The records currently in the stage to need to be either deleted, archived, or moved to a different stage before the stage can be deleted." msgstr "" -#: ../../content/applications/hr/recruitment.rst:157 +#: ../../content/applications/hr/recruitment.rst:312 msgid "Email templates" msgstr "" -#: ../../content/applications/hr/recruitment.rst:159 +#: ../../content/applications/hr/recruitment.rst:314 msgid "To communicate with the applicant, Odoo has several pre-configured email templates that can be used. The pre-configured email templates and when to use them are as follows:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:162 -msgid ":guilabel:`Applicant: Acknowledgement`: this template is used to let the applicant know that their application was received. This email is automatically sent out once the applicant is in the :guilabel:`First Interview` stage." +#: ../../content/applications/hr/recruitment.rst:317 +msgid ":guilabel:`Recruitment: Applicant Acknowledgement`: this template is used to let the applicant know that their application was received. This email is automatically sent out once the applicant is in the :guilabel:`New` stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:165 -msgid ":guilabel:`Applicant: Interest`: this template is used to let the applicant know that they have passed the :guilabel:`Initial Qualification` stage and they will be contacted to set up an interview with the recruiter." +#: ../../content/applications/hr/recruitment.rst:320 +msgid ":guilabel:`Recruitment: Interest`: this template is used to let the applicant know that their application caught the recruiter's attention, and they have been shortlisted for either a phone call or an interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:168 -msgid ":guilabel:`Applicant: Not interested anymore`: this template is used when an applicant communicates that they are no longer interested in the position, and thanks them for their time and consideration." +#: ../../content/applications/hr/recruitment.rst:323 +msgid ":guilabel:`Recruitment: Schedule Interview`: this template is used to let the applicant know that they have passed the :guilabel:`Initial Qualification` stage and they will be contacted to set up an interview with the recruiter. This email is automatically sent out once the applicant is in the :guilabel:`Initial Qualification` stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:171 -msgid ":guilabel:`Applicant: Refuse`: this template is used when an applicant is no longer being considered for the position." +#: ../../content/applications/hr/recruitment.rst:327 +msgid ":guilabel:`Recruitment: Not interested anymore`: this template is used when an applicant communicates that they are no longer interested in the position, and thanks them for their time and consideration." msgstr "" -#: ../../content/applications/hr/recruitment.rst:173 -msgid ":guilabel:`Applicant: Your Salary Package`: this template is used when offering an applicant a position. This informs the applicant they can configure their salary package." +#: ../../content/applications/hr/recruitment.rst:330 +msgid ":guilabel:`Recruitment: Refuse`: this template is used when an applicant is no longer being considered for the position." msgstr "" -#: ../../content/applications/hr/recruitment.rst:177 +#: ../../content/applications/hr/recruitment.rst:334 msgid "Email templates can be created, modified, and deleted to suit the needs of a business. For more information on email templates, refer to the :doc:`../general/companies/email_template` document." msgstr "" -#: ../../content/applications/hr/recruitment.rst:180 -msgid "To manually send an email click :guilabel:`Send message` in the chatter. A text box appears, as well as the applicant's email address. Click the :guilabel:`⤢ (double arrow)` full composer icon in the bottom right corner of the :guilabel:`Send Message` tab in the chatter." +#: ../../content/applications/hr/recruitment.rst:337 +msgid "To manually send an email, click :guilabel:`Send message` in the chatter. A text box appears, as well as the applicant's email address." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 msgid "Send an email from the chatter." msgstr "" -#: ../../content/applications/hr/recruitment.rst:188 -msgid "An email composer pop-up loads, with the :guilabel:`Recipients` and :guilabel:`Subject` pre-populated. The applicant's email address is entered on the :guilabel:`Recipients` line, and the :guilabel:`Subject` is `Re: (Subject / Application Name)`. The email body is empty by default." +#: ../../content/applications/hr/recruitment.rst:344 +msgid "Click the :icon:`fa-expand` :guilabel:`(expand)` full composer icon in the bottom right corner of the :guilabel:`Send Message` tab in the chatter. A :guilabel:`Compose Email` pop-up window loads, with the :guilabel:`Recipients` and :guilabel:`Subject` pre-populated. The applicant's email address is entered in the :guilabel:`Recipients` line, and the :guilabel:`Subject` is `(Job Position)`. The email body is empty by default." msgstr "" -#: ../../content/applications/hr/recruitment.rst:192 -msgid "To use a pre-configured email template, click the drop-down next to the :guilabel:`Load template` field in the lower right section of the window. Pre-configured email templates may contain dynamic placeholders so unique information can be populated in the email for a more personalized message to the applicant. There are several pre-configured email templates to choose from. Depending on the template selected, the email subject and/or body may change." +#: ../../content/applications/hr/recruitment.rst:350 +msgid "To use a pre-configured email template, click the field next to :guilabel:`Load template` in the bottom section of the window. Select the email template to use from the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:199 -msgid "Only the email templates that are configured for the model will load. There are other email templates pre-configured in Odoo, but if they are not configured for the recruitment application, they will not appear in the list of available templates." +#: ../../content/applications/hr/recruitment.rst:353 +msgid "Pre-configured email templates may contain dynamic placeholders so unique information can be populated in the email for a more personalized message to the applicant. There are several pre-configured email templates to choose from. Depending on the template selected, the email subject and/or body may change." msgstr "" -#: ../../content/applications/hr/recruitment.rst:203 -msgid "If any attachments are to be added, click the :guilabel:`Attach A File` button in the lower left corner. Navigate to the file to be attached, then click :guilabel:`Open` to attach it. To delete an attachment, click the :guilabel:`X (Delete)` icon to the right of the attachment. If any changes need to be made to the email, edit the body of the email. If the edits should be saved to be used in the future, the email can be saved as a new template. Click the :guilabel:`Save As New Template` button in the bottom right corner. To send the email, click :guilabel:`Send` and the email will be sent to the applicant. The email then appears in the chatter." +#: ../../content/applications/hr/recruitment.rst:359 +msgid "Only the email templates that are configured for the model load. There are other email templates pre-configured in Odoo, but if they are not configured for the recruitment application, they do not appear in the list of available templates." msgstr "" -#: ../../content/applications/hr/recruitment.rst:212 +#: ../../content/applications/hr/recruitment.rst:363 +msgid "If any attachments are to be added, click the :guilabel:`Attachments` button in the lower left corner. Navigate to the file to be attached, then click :guilabel:`Open` to attach it. To delete an attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "If any changes need to be made to the email, edit the body of the email. If the edits should be saved to be used in the future, the email can be saved as a new template. Click the :guilabel:`Save Template` button in the bottom. To send the email, click :guilabel:`Send` and the email is sent to the applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:373 msgid "Stage flow" msgstr "" -#: ../../content/applications/hr/recruitment.rst:214 -msgid "In order to move an applicant's card from one stage to another, the applicant's card can either be dragged and dropped in the kanban view to the desired stage, or the stage can be modified on the applicant's card." +#: ../../content/applications/hr/recruitment.rst:375 +msgid "In order to move an applicant's card from one stage to another, the applicant's card can either be dragged and dropped in the Kanban view to the desired stage, or the stage can be modified on the applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:218 -msgid "To change the stage on the applicant's card, click on the applicant's card in the kanban view to go to a detailed view of the card. The current stage for the card is highlighted in purple at the top, above the card. Simply click the desired stage for the card, and the stage changes. A log note indicating the stage change appears in the chatter. Navigate back to the kanban view by clicking on :guilabel:`Applications` in the breadcrumb menu in the top left, and the applicant's card now appears in the new stage." +#: ../../content/applications/hr/recruitment.rst:379 +msgid "To change the stage on the applicant's card, click on the applicant's card in the Kanban view to go to a detailed view of the card. The current stage for the card is highlighted at the top, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:383 +msgid "Click the desired stage for the card, and the stage changes. A log note indicating the stage change appears in the chatter. Navigate back to the Kanban view by clicking on :guilabel:`Applications` in the breadcrumb menu in the top-left, and the applicant's card now appears in the new stage." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 @@ -8069,63 +8440,89 @@ msgid "Change the stage of an applicant by clicking on the desired stage at the "applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:233 -msgid "Initial qualification" +#: ../../content/applications/hr/recruitment.rst:395 +#: ../../content/applications/hr/recruitment.rst:643 +msgid "New" msgstr "" -#: ../../content/applications/hr/recruitment.rst:236 +#: ../../content/applications/hr/recruitment.rst:398 msgid "The following information is based on Odoo's default recruitment pipeline flow. Be advised that if modifications are made to create a customized recruitment pipeline flow, it will vary from the following information." msgstr "" -#: ../../content/applications/hr/recruitment.rst:240 -msgid "All applicants appear in the :guilabel:`Initial Qualification` stage, whether submitted online or if the applicant is manually entered by a recruiter. When the applicant's card is created, Odoo automatically populates the applicant's :guilabel:`Name`, :guilabel:`Email address`, and :guilabel:`Phone number` on the applicant's card. This information is required when applying for a job position." +#: ../../content/applications/hr/recruitment.rst:402 +msgid "All applicants appear in the :guilabel:`New` stage, whether submitted online or if the applicant is manually entered by a recruiter." msgstr "" -#: ../../content/applications/hr/recruitment.rst:246 -msgid "If the applicant entered any information in the :guilabel:`Short Introduction` section of the online application, it is populated in the :guilabel:`Application Summary` tab at the bottom of the applicant's card. If a resumé was attached to the online application, the resumé appears in the attachments section of the chatter, and is also stored in the *Documents* application. To find the recruitment documents stored in the Documents application, navigate to the main :menuselection:`Documents` dashboard, and click the folder labeled :guilabel:`Recruitment` on the right side. All recruitment documents will be stored within that folder." +#: ../../content/applications/hr/recruitment.rst:405 +msgid "When the applicant's card is created, Odoo automatically populates the :guilabel:`Subject/Application`, the applicant's :guilabel:`Name`, :guilabel:`Email`, :guilabel:`Mobile` number, and :guilabel:`LinkedIn Profile` on the applicant's card. This information is required when applying for a job position, by default." msgstr "" -#: ../../content/applications/hr/recruitment.rst:255 +#: ../../content/applications/hr/recruitment.rst:411 +msgid "If the website application form is modified, different fields may be populated based on what information is requested on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:414 +msgid "If the applicant entered any information in the :guilabel:`Short Introduction` section of the online application, it will populate in the :guilabel:`Application Summary` tab at the bottom of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:421 +msgid "If a resumé was attached to the online application, the resumé would appear in the attachments section of the chatter, and is also stored in the *Documents* application. To find the recruitment documents stored in the *Documents* application, navigate to the main :menuselection:`Documents` dashboard, and click the folder labeled :guilabel:`Recruitment` on the left-hand side. All recruitment documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:427 +msgid "If the :ref:`CV Display ` option was enabled in the :ref:`Settings ` menu, the resumé appears on the applicant's card, on the right-hand side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:431 msgid "Send interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:257 +#: ../../content/applications/hr/recruitment.rst:433 msgid "At any point in the hiring process, an *interview* can be sent to the applicant to obtain more information. These interviews are custom-made, and can be formatted in a variety of ways." msgstr "" -#: ../../content/applications/hr/recruitment.rst:260 -msgid "Odoo uses the term *interview*, but these can be thought of as questionnaires, surveys, tests, certifications, etc. Custom interviews can be formatted to suit each individual job position's needs. For example, a job position for a computer programmer could have an interview in the form of a programming quiz to determine the skill level of the applicant. A job position for a restaurant server could have a questionnaire inquiring about the applicant's availability, if the desired applicant needs to be available on weekend evenings. For more information on creating and editing interview forms, refer to the :doc:`../hr/recruitment/new_job` documentation." +#: ../../content/applications/hr/recruitment.rst:436 +msgid "The *Surveys* application is used to send these *interviews*, therefore the *Surveys* application must be installed to send an interview to an applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:269 -msgid "In order to send an email to an applicant, there must be an email address on the applicant's card. If an email address is not entered on the applicant's card, when :guilabel:`Send Interview` is clicked, the applicant's card appears instead of the :guilabel:`Survey` pop-up window. Enter the email address in the email field, then click :guilabel:`Save`. Once the applicant's card is saved, the applicant's card closes and the :guilabel:`Survey` pop-up window appears." +#: ../../content/applications/hr/recruitment.rst:439 +msgid "Odoo uses the term *interview*, but these can be thought of as questionnaires, surveys, tests, certifications, etc. Custom interviews can be formatted to suit each individual job positions needs. For more information on creating and editing interview forms, refer to the :doc:`../hr/recruitment/new_job` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:275 -msgid "To send an interview to an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, click the button labeled :guilabel:`Send Interview`." +#: ../../content/applications/hr/recruitment.rst:445 +msgid "A job position for a computer programmer could have an interview in the form of a programming quiz to determine the skill level of the applicant. A job position for a restaurant server could have a questionnaire inquiring about the applicant's availability, if the desired applicant needs to be available on weekend evenings." msgstr "" -#: ../../content/applications/hr/recruitment.rst:279 -msgid "If the applicant's card has an email address on file, a :guilabel:`Survey` pop-up window appears, with all the information populated. If an email is not on the applicant's card, then a contact form appears. Enter the applicants email address, then click :guilabel:`Save`. The card closes and the :guilabel:`Survey` pop-up window appears." +#: ../../content/applications/hr/recruitment.rst:450 +msgid "To send an interview to an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top-left of the applicant's card, click the :guilabel:`Send Interview` button." msgstr "" -#: ../../content/applications/hr/recruitment.rst:284 -msgid "Odoo refers to the interview forms as *surveys*. These email templates also use dynamic placeholders to personalize the email to the applicant and the job position. Add any additional recipients for the survey if more people should receive the email. If an email is in the database as a contact, add that contact on the :guilabel:`Recipients` line. If an email should be sent to someone who is not in the database as a contact, and they should **not** be added as a contact, add their email to the :guilabel:`Additional emails` line." +#: ../../content/applications/hr/recruitment.rst:454 +msgid "If the applicant's card has an email address on file, a :guilabel:`Send an interview` pop-up window appears, with all the information populated." msgstr "" -#: ../../content/applications/hr/recruitment.rst:291 +#: ../../content/applications/hr/recruitment.rst:458 +msgid "In order to send an email to an applicant, there must be an email address on the applicant's card. If an email address is not entered on the applicant's card, when :guilabel:`Send Interview` is clicked, an :guilabel:`Edit:(Applicant)` pop-up window appears on top of the :guilabel:`Send an interview` pop-up window. Enter the email address in the :guilabel:`email` field, then click :guilabel:`Save & Close`. Once the applicant's information is saved, the :guilabel:`Edit: (Applicant)` closes and the :guilabel:`Send an interview` pop-up window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:465 +msgid "Email templates use dynamic placeholders to personalize the email to the applicant and the job position. Add any additional recipients for the survey if more people should receive the email. If an email is in the database as a contact, add that contact in the :guilabel:`Recipients` field. If an email should be sent to someone who is not in the database as a contact, and they should **not** be added as a contact, add their email in the :guilabel:`Additional emails` field." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:471 +#: ../../content/applications/hr/recruitment.rst:1066 msgid "If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button." msgstr "" -#: ../../content/applications/hr/recruitment.rst:295 -msgid "If the emailed interview must be completed by a specific date, select a date for the :guilabel:`Answer deadline` in the lower-right area of the pop-up window. Click on the line next to :guilabel:`Answer deadline`, and a calendar selector appears. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." +#: ../../content/applications/hr/recruitment.rst:475 +msgid "If the emailed interview must be completed by a specific date, select a date for the :guilabel:`Answer deadline` in the lower-right area of the pop-up window. Click on the line next to :guilabel:`Answer deadline`, and a calendar selector appears. Use the :icon:`fa-chevron-left` :guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." msgstr "" -#: ../../content/applications/hr/recruitment.rst:301 -msgid "The :guilabel:`Mail template` field is pre-populated based on the configuration for the interview. A different template can be chosen from the drop-down menu if desired. If a new template is selected, the new email template loads in the email body." +#: ../../content/applications/hr/recruitment.rst:481 +msgid "The :guilabel:`Mail Template` field is pre-populated based on the configuration for the interview. A different template can be chosen from the drop-down menu if desired. If a new template is selected, the new email template loads in the email body." msgstr "" -#: ../../content/applications/hr/recruitment.rst:305 +#: ../../content/applications/hr/recruitment.rst:485 msgid "To send the email with the interview link to the applicant, click :guilabel:`Send` at the bottom of the email pop-up." msgstr "" @@ -8134,465 +8531,613 @@ msgid "Send a custom survey, also referred to as an interview form, to an applic "pre-configured template." msgstr "" -#: ../../content/applications/hr/recruitment.rst:314 +#: ../../content/applications/hr/recruitment.rst:494 msgid "Refuse" msgstr "" -#: ../../content/applications/hr/recruitment.rst:316 +#: ../../content/applications/hr/recruitment.rst:496 msgid "At any point in the recruitment pipeline, an applicant can be refused from the job application process. To refuse an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, there are several buttons. Click the one labeled :guilabel:`Refuse`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:321 -msgid "A :guilabel:`Refuse Reason` pop-up appears. Select the :guilabel:`Refuse Reason` from the drop-down menu. The default refuse reasons in Odoo are: :guilabel:`Doesn't fit the job requirements`, :guilabel:`The applicant is not interested anymore`, and :guilabel:`The applicant gets a better offer`. These three refusal reasons have pre-configured email templates associated with them. Additional refusal reasons can be created and existing ones can be modified or deleted. To add a new refusal reason, type in the name of the reason, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: Refuse Reason` pop-up window appears. Type in the name of the new email template in the :guilabel:`Email Template` field, and click :guilabel:`Create and Edit...`. A :guilabel:`Create: Email Template` window loads. Configure the new email template, then click :guilabel:`Save`." +#: ../../content/applications/hr/recruitment.rst:501 +msgid "A :guilabel:`Refuse Reason` pop-up window appears. Click the :guilabel:`Refuse Reason` from the presented options. The default refuse reasons in Odoo, and their corresponding email templates, are:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:333 -msgid "Pre-configured email templates in Odoo sometimes use dynamic placeholders, which are customized pieces of data that populate dynamic content. For example, if the applicant's name is a piece of dynamic content, the applicant's name will appear anytime that dynamic placeholder appears on the email template. For more detailed information on email templates, refer to the :doc:`../general/companies/email_template` documentation." +#: ../../content/applications/hr/recruitment.rst:508 +msgid "Email Template" msgstr "" -#: ../../content/applications/hr/recruitment.rst:339 -msgid "An email template populates the :guilabel:`Email Template` field after a refusal reason is selected. If an email should not be sent to the applicant, uncheck the :guilabel:`Send Email` checkbox. To view the email template, click the :guilabel:`External Link` icon to the right of the email template selected. The email template loads in the pop-up window, and can be modified if needed. After making modifications, click :guilabel:`Save`. To close the email template, click :guilabel:`Discard`." +#: ../../content/applications/hr/recruitment.rst:509 +msgid "Refusal Reason" msgstr "" -#: ../../content/applications/hr/recruitment.rst:345 -msgid "To send the refusal email to the applicant, click :guilabel:`Send`. The refusal email is sent to the applicant, and a :guilabel:`Refused` banner appears on the applicant's card." +#: ../../content/applications/hr/recruitment.rst:510 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:0 +msgid ":guilabel:`Doesn't fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:0 +msgid ":guilabel:`Language issues`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:0 +msgid ":guilabel:`Role already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:516 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:0 +msgid ":guilabel:`Refused by Applicant: don't like job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:0 +msgid ":guilabel:`Refused by Applicant: better offer`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:0 +msgid ":guilabel:`Refused by Applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:521 +msgid "Additional refusal reasons :ref:`can be created and existing ones can be modified or deleted `." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:525 +msgid "Pre-configured email templates in Odoo sometimes use dynamic placeholders, which are customized pieces of data that populate dynamic content. For example, if the applicant's name is a piece of dynamic content, the applicant's name appears anytime that dynamic placeholder appears on the email template. For more detailed information on email templates, refer to the :doc:`../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:531 +msgid "After a :guilabel:`Refuse Reason` is selected, two fields appear below the refusal reason: :guilabel:`Send Email` and :guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:534 +msgid "The applicant's email address automatically populates the :guilabel:`Send Email` field; additional email recipients cannot be added. If an email should **not** be sent to the applicant, uncheck the :guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:538 +msgid "The email template associated with the refusal reason populates the :guilabel:`Email Template` field. If a different email template is desired, select a different template from the :guilabel:`Email Template` drop-down menu. To view the email template, click the :guilabel:`External Link` icon to the right of the :guilabel:`Email Template` field. The email template loads in a :guilabel:`Open: Email Template` pop-up window, and can be modified if needed. After making modifications, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:545 +msgid "To send the refusal email to the applicant, click :guilabel:`Refuse`. The refusal email is sent to the applicant, and a :guilabel:`Refused` banner appears on the applicant's card in the top-right corner." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 -msgid "An applicant's card with the refused banner appearing in the top right corner in red." +msgid "An applicant's card with the refused banner appearing in the top-right corner in red." msgstr "" -#: ../../content/applications/hr/recruitment.rst:352 -msgid "After refusal, the applicant's card is no longer visible in the job position's kanban view. To view refused applicants, navigate to the :menuselection:`Recruitment app --> Applications --> All Applications`. All applications for all job positions are presented in a list view. To view the refused applicants only, click :guilabel:`Filters`, then click :guilabel:`Archived/Refused`. All applicants that have been archived and/or refused appear in the list. To further organize this list and view refusals by job position, click :guilabel:`≣ Group By`, then click :guilabel:`Job`." +#: ../../content/applications/hr/recruitment.rst:553 +msgid "After refusal, the applicant's card is no longer visible in the job position's Kanban view. To view the refused applicants only, click the :guilabel:`▼ Toggle Search Panel` button in the search box, then click :guilabel:`Refused` under the :guilabel:`Filters` section. All applicants that have been refused for the job position appear, in the stage they were when they were refused." msgstr "" -#: ../../content/applications/hr/recruitment.rst:360 +#: ../../content/applications/hr/recruitment.rst:558 +msgid "To view all applicants that have been refused from all job positions, navigate to the :menuselection:`Recruitment app --> Applications --> All Applications`. Click the :guilabel:`▼ Toggle Search Panel` button in the search box, then click :guilabel:`Refused` under the :guilabel:`Filters` section. All applications for all job positions are presented in a list view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:567 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:569 +msgid "To view all currently configured refuse reasons, navigate to :menuselection:`Recruitment app --> Settings --> Applications: Refuse Reasons`. All the refuse reasons appear in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:572 +msgid "To create a new refuse reason, click the :guilabel:`New` button in the top-left corner. A blank line appears at the bottom of the :guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:575 +msgid "Type in the new refuse reason in the field. It is recommended to enter a reason that is short and concise, such as `offer expired` or `withdrew application`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:578 +msgid "Then, in the :guilabel:`Email Template` field, click on the field to reveal a drop-down menu. Select an :guilabel:`Email Template` from the list to be used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:581 +msgid "If a new :guilabel:`Email Template` is desired, type in the name for the new template in the field. Then, click :guilabel:`Create and edit...` and a :guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:585 +msgid "Enter a :guilabel:`Name` for the form and an email :guilabel:`Subject` in the corresponding fields. Enter the email content in the :guilabel:`Content` tab. Make any other desired modifications to the template, then click :guilabel:`Save & Close` to save the template and return to the :guilabel:`Refuse Reasons` list. The new template appears in the new refuse reason :guilabel:`Email Template` field." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:591 +msgid "To make any modifications to a refuse reason, click on the line, and make any desired changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:594 msgid "New applicant" msgstr "" -#: ../../content/applications/hr/recruitment.rst:362 -msgid "An applicant card can be manually added if needed. If an applicant needs to be added to the list of prospective candidates and an applicant card has not been created yet (they have not applied for the job online yet) an applicant card can be easily added from the job position kanban view in one of two ways, using either the :ref:`Quick add ` icon or the :ref:`Create ` button." +#: ../../content/applications/hr/recruitment.rst:596 +msgid "An applicant card can be manually added if needed. If an applicant needs to be added to the list of prospective candidates and an applicant card has not been created yet (they have not applied for the job online) an applicant card can be easily added from the job position Kanban view in one of two ways, using either the :ref:`quick add ` button or the :ref:`New ` button." msgstr "" -#: ../../content/applications/hr/recruitment.rst:371 +#: ../../content/applications/hr/recruitment.rst:605 msgid "Quick add" msgstr "" -#: ../../content/applications/hr/recruitment.rst:373 -msgid "Quickly add a new applicant using the :guilabel:`Quick add` icon. If not already in the job position kanban view, navigate to the main recruitment dashboard, and click the :guilabel:`New Applicants` button on the job position card that the applicant should be added to. Then, click on the small :guilabel:`+ (plus sign) Quick add` icon in the top right of the :guilabel:`Initial Qualification` stage to quickly add a new applicant." +#: ../../content/applications/hr/recruitment.rst:607 +msgid "Quickly add a new applicant using the *quick add* button. If not already in the job position Kanban view, navigate to the main recruitment dashboard by going to :menuselection:`Recruitment app --> Applications --> By Job Positions`. Click the :guilabel:`(#) New Applications` button on the job position card that the applicant should be added to. Then, click on the small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-right of the :guilabel:`New` stage to quickly add a new applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:614 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:616 +msgid ":guilabel:`Subject/Application`: Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - HR Manager`. This field is not visible in the Kanban view, unless the :guilabel:`Applicant's Name` is left blank. If there is no :guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` is what is displayed on the applicant card in the Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:621 +#: ../../content/applications/hr/recruitment.rst:670 +msgid ":guilabel:`Applicant's Name`: enter the applicant's name." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:622 +#: ../../content/applications/hr/recruitment.rst:671 +msgid ":guilabel:`Email`: enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:623 +msgid ":guilabel:`Applied Job`: the current job position populates this field. If needed, the job position can be changed by selecting a different position from the drop-down menu. If a different job position is selected, after the card is created, the card appears in the selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:628 +msgid "After the information is entered, click :guilabel:`Add`. The applicant appears in the list, and a new blank applicant card appears. Click either the :icon:`fa-trash-o` :guilabel:`delete` icon or anywhere on the screen to close the card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:632 +msgid "If preferred, after entering the applicant name, click :guilabel:`Edit` and a detailed :guilabel:`Applicant Form` loads. :ref:`Enter the information on the form `." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 msgid "All the fields for a new applicant form entered when using the Quick Add option." msgstr "" -#: ../../content/applications/hr/recruitment.rst:383 -msgid "Enter the following information on the card:" +#: ../../content/applications/hr/recruitment.rst:645 +msgid "Add a new applicant including all the relevant information using the *New* button. If not already in the Kanban view for the job position to add an applicant to, navigate to the main recruitment dashboard by going to :menuselection:`Recruitment app --> Applications --> By Job Positions`. Then, click the :guilabel:`New` button in the top-left of the Kanban view and a blank applicant form loads." msgstr "" -#: ../../content/applications/hr/recruitment.rst:385 -msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - Experienced Developer`. This field is not visible in the kanban view (unless in the Developer mode), but is visible on the individual card." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:389 -#: ../../content/applications/hr/recruitment.rst:434 -msgid ":guilabel:`Applicant's Name`: enter the applicant's name." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:390 -#: ../../content/applications/hr/recruitment.rst:435 -msgid ":guilabel:`Email`: enter the applicant's email address." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:391 -msgid ":guilabel:`Applied Job`: the current job position populates this field. If needed, the job position can be changed by selecting a different position from the drop-down menu. If a different job position is selected, after the card is created, the card will appear in the selected job position." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:396 -msgid "After the information is entered, click :guilabel:`Add`. The applicant appears in the list, and a new blank applicant card appears. Click either the :guilabel:`🗑️ (delete)` icon or click anywhere on the screen to close the card." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:400 -msgid "If preferred, after entering the applicant name, click :guilabel:`Edit` and a detailed :guilabel:`Applicant Form` loads. :ref:`Enter the information on the form `, then click :guilabel:`Save`" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:407 -msgid "Create" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:409 -msgid "Add a new applicant including all the relevant information using the :guilabel:`Create` button. If not already in the kanban view for the job position to add an applicant to, navigate to the main recruitment dashboard, and click the :guilabel:`New Applicants` button on the job position card that the applicant should be added to. Then, click the :guilabel:`Create` button in the top left of the kanban view and an applicant form loads." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:415 +#: ../../content/applications/hr/recruitment.rst:651 msgid "Certain fields on the applicant card may be pre-populated, depending on how the job position is configured. Typically, the :guilabel:`Job` section, as well as the :guilabel:`Recruiter` field, are all pre-populated." msgstr "" -#: ../../content/applications/hr/recruitment.rst:419 +#: ../../content/applications/hr/recruitment.rst:655 msgid "Enter the following information on the new applicant form. Note that not all fields listed below may be visible. Depending on installed applications and configurations, some fields may not be displayed." msgstr "" -#: ../../content/applications/hr/recruitment.rst:426 +#: ../../content/applications/hr/recruitment.rst:662 msgid "Applicant section" msgstr "" -#: ../../content/applications/hr/recruitment.rst:428 -msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - Experienced Developer`. This field is not visible in the kanban view, unless the :guilabel:`Applicant's Name` is left blank. If there is no :guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` is what is displayed on the applicant card in the kanban view." +#: ../../content/applications/hr/recruitment.rst:664 +msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `John Smith - Experienced Developer`. This field is not visible in the Kanban view, unless the :guilabel:`Applicant's Name` is left blank. If there is no :guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` is what is displayed on the applicant card in the Kanban view." msgstr "" -#: ../../content/applications/hr/recruitment.rst:436 +#: ../../content/applications/hr/recruitment.rst:672 msgid ":guilabel:`Phone`: enter the applicant's phone number." msgstr "" -#: ../../content/applications/hr/recruitment.rst:437 +#: ../../content/applications/hr/recruitment.rst:673 msgid ":guilabel:`Mobile`: enter the applicant's mobile number." msgstr "" -#: ../../content/applications/hr/recruitment.rst:438 +#: ../../content/applications/hr/recruitment.rst:674 +msgid ":guilabel:`LinkedIn Profile`: enter the web address for the applicant's personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:676 msgid ":guilabel:`Degree`: select the applicant's highest level of education earned from the drop-down menu. Options are :guilabel:`Graduate`, :guilabel:`Bachelor Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The :guilabel:`Graduate` option indicates graduating the highest level of school before a Bachelor's degree, such as a high school or secondary school diploma, depending on the country." msgstr "" -#: ../../content/applications/hr/recruitment.rst:443 -msgid ":guilabel:`Tags`: select as many tags as desired from the drop-down menu. To add a tag that does not exist, type in the tag name, the click :guilabel:`Create \"new tag\"`." +#: ../../content/applications/hr/recruitment.rst:681 +msgid ":guilabel:`Interviewers`: using the drop-down menu, select the people who will conduct the interview(s). The selected people must have either *recruiter* or *officer* rights configured for the Recruitment application to appear in the drop-down list." msgstr "" -#: ../../content/applications/hr/recruitment.rst:445 -msgid ":guilabel:`Interviewer`: select the person who will be conducting the interview(s) from the drop-down menu. The person must have either *recruiter* or *officer* rights configured for the Recruitment application in order to appear on the drop-down." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:448 +#: ../../content/applications/hr/recruitment.rst:684 msgid ":guilabel:`Recruiter`: select the person responsible for the entire recruitment process for the job position. Only *users* can be selected, and all users are presented in the drop-down to select from." msgstr "" -#: ../../content/applications/hr/recruitment.rst:451 -msgid ":guilabel:`Appreciation`: click on one of the stars to select a rating for the applicant. One star indicates :guilabel:`Good`, two stars indicates :guilabel:`Very Good`, and three stars indicates :guilabel:`Excellent.`" +#: ../../content/applications/hr/recruitment.rst:687 +msgid ":guilabel:`Evaluation`: click on one of the stars to select a rating for the applicant. One star indicates :guilabel:`Good`, two stars indicates :guilabel:`Very Good`, and three stars indicates :guilabel:`Excellent.`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:454 -msgid ":guilabel:`Referred By User`: if referral points are to be earned for this job position in the *Referrals* application, select the user who referred the applicant from the drop-down menu. The *Referrals* application must be installed for this to appear." +#: ../../content/applications/hr/recruitment.rst:690 +msgid ":guilabel:`Source`: using the drop-down menu, select where the applicant learned about the job position. The following options come pre-configured in Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, :guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`Twitter`, :guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and :guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source, then click :guilabel:`Create \"(new source)\"`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:459 +#: ../../content/applications/hr/recruitment.rst:695 +msgid ":guilabel:`Medium`: using the drop-down menu, select the method, or :guilabel:`Medium`, for the :guilabel:`Source` that the applicant found the job listing with. The pre-configured options are: :guilabel:`Banner`, :guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, :guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, :guilabel:`Television`, :guilabel:`Twitter` (now known as \"X\"), or :guilabel:`Website`. To add a new :guilabel:`Medium`, type in the medium, then click :guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:701 +msgid ":guilabel:`Referred By User`: if referral points are to be earned for this job position in the *Referrals* application, select the user who referred the applicant from the drop-down menu. The *Referrals* application must be installed for this field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:704 +msgid ":guilabel:`Availability`: select the available start date for the applicant. To select a date, click on the field to reveal a calendar. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date. If no entry is selected that indicates the applicant is ready to begin work immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:709 +msgid ":guilabel:`Tags`: select as many tags as desired from the drop-down menu. To add a tag that does not exist, type in the tag name, then click :guilabel:`Create \"new tag\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:713 msgid "Job section" msgstr "" -#: ../../content/applications/hr/recruitment.rst:461 +#: ../../content/applications/hr/recruitment.rst:715 msgid "The following fields are pre-populated when creating a new applicant, as long as these field are specified on the Job Position. Editing the fields is possible, if desired." msgstr "" -#: ../../content/applications/hr/recruitment.rst:464 +#: ../../content/applications/hr/recruitment.rst:718 msgid ":guilabel:`Applied Job`: select the job position the applicant is applying to from the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:466 +#: ../../content/applications/hr/recruitment.rst:720 msgid ":guilabel:`Department`: select the department the job position falls under from the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:468 -msgid ":guilabel:`Company`: select the company the job positions is for using the drop-down menu." +#: ../../content/applications/hr/recruitment.rst:722 +msgid ":guilabel:`Company`: select the company the job position is for using the drop-down menu. This field only appears when in a multi-company database." msgstr "" -#: ../../content/applications/hr/recruitment.rst:471 +#: ../../content/applications/hr/recruitment.rst:726 msgid "Contract section" msgstr "" -#: ../../content/applications/hr/recruitment.rst:473 +#: ../../content/applications/hr/recruitment.rst:728 msgid ":guilabel:`Expected Salary`: enter the amount the applicant is requesting for the role in this field. The number should be in a `XX,XXX.XX` format. The currency is determined by the localization setting for the company." msgstr "" -#: ../../content/applications/hr/recruitment.rst:476 -msgid ":guilabel:`Expected Salary - Extra advantages...`: if any extra advantages are requested by the applicant, enter it in this field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." +#: ../../content/applications/hr/recruitment.rst:731 +msgid ":guilabel:`Extra advantages...`: if any extra advantages are requested by the applicant, enter it in the :guilabel:`Extra advantages...` field to the right of the :guilabel:`Expected Salary` field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:479 -msgid ":guilabel:`Proposed Salary`: enter the amount to be offered to the applicant for the role in this field. The number should be in a `XX,XXX.XX` format." +#: ../../content/applications/hr/recruitment.rst:734 +msgid ":guilabel:`Proposed Salary`: enter the amount to be offered to the applicant for the role in this field. The number should be in a `XX,XXX.XX` format. The currency is determined by the localization setting for the company." msgstr "" -#: ../../content/applications/hr/recruitment.rst:481 -msgid ":guilabel:`Proposed Salary - Extra advantages...`: if any extra advantages are offered to the applicant, enter it in this field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." +#: ../../content/applications/hr/recruitment.rst:737 +msgid ":guilabel:`Extra advantages...`: if any extra advantages are offered to the applicant, enter it in the :guilabel:`Extra advantages...` field to the right of the :guilabel:`Proposed Salary` field. This should be short and descriptive, such as `unlimited sick time` or `retirement plan`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:484 -msgid ":guilabel:`Availability`: using the calendar module in the drop-down menu, select the available start date for the applicant." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:488 +#: ../../content/applications/hr/recruitment.rst:742 msgid "Application summary tab" msgstr "" -#: ../../content/applications/hr/recruitment.rst:490 +#: ../../content/applications/hr/recruitment.rst:744 msgid "Any additional details or notes that should be added to the applicant's card can be typed into this field." msgstr "" +#: ../../content/applications/hr/recruitment.rst:750 +msgid "Skills can be added to the applicant's card. To add a skill, follow the same steps as outlined in the skills section of the :ref:`Create new employees ` document." +msgstr "" + #: ../../content/applications/hr/recruitment.rst:-1 msgid "All the fields for a new applicant form entered." msgstr "" -#: ../../content/applications/hr/recruitment.rst:500 +#: ../../content/applications/hr/recruitment.rst:760 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:762 +msgid "If an applicant seems to be a good potential candidate, they are moved to the :guilabel:`Initial Qualification` stage. This could be for a number of reasons, such as they have the relevant experience, education, or certifications the position requires." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:766 +msgid "This stage is to quickly sort candidates that have potential, and those that do not meet the requirements. No automatic actions, such as emails, are set for this stage. This stage simply informs the recruitment team to potentially set up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:773 msgid "First interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:502 -msgid "After an applicant has passed the :guilabel:`Initial Qualification` stage, they can be moved to the :guilabel:`First Interview` stage in the job position kanban view. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`First Interview` stage, or click on the :guilabel:`First Interview` stage button at the top of the individual applicant's card." +#: ../../content/applications/hr/recruitment.rst:775 +msgid "After an applicant has passed the :guilabel:`Initial Qualification` stage, they can be moved to the :guilabel:`First Interview` stage in the job position Kanban view. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`First Interview` stage, or click on the :guilabel:`First Interview` stage button at the top of the individual applicant's card." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 -msgid "An applicant's card moves from one stage t another by using the click and drag method." +msgid "An applicant's card moves from one stage to another by using the click and drag method." msgstr "" -#: ../../content/applications/hr/recruitment.rst:511 -msgid "When the applicant's card moves to the :guilabel:`First Interview` stage, an acknowledgement email is automatically sent to the applicant. The email is created using an email template titled :guilabel:`Applicant: Acknowledgement`. This email template is pre-configured in Odoo, and contains dynamic placeholders for the job position, the recruiter's name, and the company's information. Once the email is sent, the email appears in the chatter." +#: ../../content/applications/hr/recruitment.rst:785 +msgid "The :guilabel:`First Interview` stage can be modified so when the applicant's card moves to the :guilabel:`First Interview` stage, an email is automatically sent to the applicant stating an interview is requested. In this pre-configured email template, a link to the recruiting team's calendar appears, allowing the applicant to schedule their interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:522 -msgid "When a date and time have been agreed upon for both the applicant and interviewer, the interview can be scheduled. To schedule an interview, whether a phone or in-person interview, click the :guilabel:`Meeting` smart button at the top of the applicant's record." +#: ../../content/applications/hr/recruitment.rst:790 +msgid ":ref:`Edit ` the :guilabel:`First Interview` stage, and select the :guilabel:`Recruitment: Schedule Interview` for the :guilabel:`Email Template` field, to automate this action." msgstr "" -#: ../../content/applications/hr/recruitment.rst:526 -msgid "The applicant's card can be found by navigating to the :menuselection:`Recruitment application` dashboard, click on a :guilabel:`New Applications` button in the job position card, then click on the applicant's card." +#: ../../content/applications/hr/recruitment.rst:799 +msgid "An interview can be scheduled in one of two ways: either manually by the recruitment team, or by the applicant themselves." msgstr "" -#: ../../content/applications/hr/recruitment.rst:531 -msgid "The meeting smart button will display :guilabel:`No Meeting` if no meetings are currently scheduled. For new applicants who are new to the :guilabel:`First Interview` stage, this will be the default. If there are any meetings already scheduled, the smart button will display :guilabel:`Next Meeting` with the date of the upcoming meeting." +#: ../../content/applications/hr/recruitment.rst:802 +msgid "If the :guilabel:`First Interview` stage was modified to send the :guilabel:`Recruitment: Schedule Interview` email template when an applicant reaches that stage, the applicant received a link to the recruitment team's calendar, and can schedule the interview on their own. The recruitment team's availability is reflected in the calendar." msgstr "" -#: ../../content/applications/hr/recruitment.rst:536 -msgid "Doing so loads the *Calendar* application, showing the currently scheduled meetings and events for the user. The meetings and events displayed are for the employees who are listed under the :guilabel:`Attendees` section on the right side of the calendar view. To change the currently loaded meetings and events being displayed, uncheck the person who's calendar events are to be hidden. Only the checked attendees will be visible on the calendar." +#: ../../content/applications/hr/recruitment.rst:807 +msgid "If the interview needs to be scheduled by the recruitment team, they should reach out to the applicant for a date and time that works. When a date and time have been agreed upon for both the applicant and interviewer, the interview can be scheduled. To schedule an interview, whether a phone or in-person interview, click the :guilabel:`Meeting` smart button at the top of the applicant's record." msgstr "" -#: ../../content/applications/hr/recruitment.rst:542 -msgid "The default view is the week view. To change the calendar view, click on a button to present the calendar in a different view, either :guilabel:`Day`, :guilabel:`Month`, or :guilabel:`Year`. To change the displayed date range for the calendar, either use the :guilabel:`⬅️ (Left)`, :guilabel:`➡️ (Right)`, or :guilabel:`Today` buttons above the calendar, or click on a date in the calendar on the right side of the displayed calendar." +#: ../../content/applications/hr/recruitment.rst:814 +msgid "The meeting smart button displays :guilabel:`No Meeting` if no meetings are currently scheduled. For new applicants who are new to the :guilabel:`First Interview` stage, this is the default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:817 +msgid "If there is one meeting already scheduled, the smart button displays :guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If more than one meeting is scheduled, the button displays :guilabel:`Next Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:821 +msgid "Doing so loads the *Calendar* application, showing the currently scheduled meetings and events for the user. The meetings and events displayed are for the employees who are listed under the :guilabel:`Attendees` section on the right side of the calendar view. To change the currently loaded meetings and events being displayed, uncheck the person who's calendar events are to be hidden. Only the checked attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:827 +msgid "The default view is the :guilabel:`Week` view. To change the calendar view, click the :guilabel:`Week` button, then select the desired view from the drop-down menu. The other options are either :guilabel:`Day`, :guilabel:`Month`, or :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:831 +msgid "An option to display or hide weekends is available. Click the :guilabel:`Week` button, then click :guilabel:`Show weekends` to deactivate it (the default is to show weekends). If a check mark is next to :guilabel:`Show weekends`, weekends are visible. If there is no check mark, weekends are hidden." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:836 +msgid "To change the displayed date range for the calendar, either use the :icon:`fa-arrow-left` :guilabel:`(left arrow)`, :icon:`fa-arrow-right` :guilabel:`(Right arrow)`, or :guilabel:`Today` buttons above the calendar, or click on a date in the calendar on the right side of the displayed calendar." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 msgid "The calendar view, highlighting how to change the displayed meetings." msgstr "" -#: ../../content/applications/hr/recruitment.rst:552 -msgid "To add a meeting to the calendar, click on the day the meeting is to take place, or click on the start time of the meeting and drag to the end time, to select the date, time, and the length of the meeting. If the calendar is displaying the day or week view, click on the day *and* the time slot the meeting is to take place. A :guilabel:`New Event` pop up appears, with the :guilabel:`Meeting Subject` populated with the applicant card's :guilabel:`Subject/Application Name`. The default time slot is 30 minutes. If the information is correct, click :guilabel:`Create` to add the meeting to the calendar, or click :guilabel:`Edit` to modify the meeting." +#: ../../content/applications/hr/recruitment.rst:845 +msgid "To add a meeting to the calendar when in the day or week view, click on the start time of the meeting and drag to the end time, to select the date, time, and the length of the meeting. A meeting can also be added in this view by clicking on the day *and* the time slot the meeting is to take place." msgstr "" -#: ../../content/applications/hr/recruitment.rst:560 -msgid "If :guilabel:`Edit` is clicked, an expanded :guilabel:`New Event` card loads. Make any changes needed to the form." +#: ../../content/applications/hr/recruitment.rst:850 +msgid "Both methods cause a :ref:`New Event ` pop up window to appear." msgstr "" -#: ../../content/applications/hr/recruitment.rst:564 -msgid "New event card" +#: ../../content/applications/hr/recruitment.rst:855 +msgid "New event pop-up window" msgstr "" -#: ../../content/applications/hr/recruitment.rst:566 -msgid "The fields available to populate or modify on the detailed :guilabel:`New Event` card are as follows. The only required fields to enter are the :guilabel:`Meeting Subject`, :guilabel:`Starting At`, and :guilabel:`Ending At` fields. Once the card details are entered, click :guilabel:`Save` to save the changes and create the meeting." +#: ../../content/applications/hr/recruitment.rst:857 +msgid "Enter the information on the form. The only required fields to enter are the :guilabel:`Meeting Title`, and the :guilabel:`Start` and :guilabel:`End` fields. Once the card details are entered, click :guilabel:`Save & Close` to save the changes and create the interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:571 -msgid ":guilabel:`Meeting Subject`: enter the subject for the meeting. This should clearly indicate the purpose of the meeting. The default subject is the :guilabel:`Subject/Application Name` on the applicant's card." +#: ../../content/applications/hr/recruitment.rst:861 +msgid "The fields available to populate or modify on the :guilabel:`New Event` card are as follows:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:574 +#: ../../content/applications/hr/recruitment.rst:863 +msgid ":guilabel:`Meeting Title`: enter the subject for the meeting. This should clearly indicate the purpose of the meeting. The default subject is the :guilabel:`Subject/Application Name` on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:866 +msgid ":guilabel:`Start` and :guilabel:`End`: select the start and end date and times for the meeting. Click on one of the fields and a calendar pop-up window appears. Select both the start and end date and times, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:869 +msgid ":guilabel:`All Day`: if the meeting is an all-day interview, check the box. If this box is checked, the :guilabel:`Start` and :guilabel:`End` fields are hidden from view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:871 msgid ":guilabel:`Attendees`: select the people who should be in attendance. The default employee listed is the person who is creating the meeting. Add as many other people as desired." msgstr "" -#: ../../content/applications/hr/recruitment.rst:578 -msgid "Meeting details tab" +#: ../../content/applications/hr/recruitment.rst:873 +msgid ":guilabel:`Videocall URL`: if the meeting is virtual, or if there is a virtual option available, click :guilabel:`+ Odoo meeting` and a URL is automatically created for the meeting and populates the field." msgstr "" -#: ../../content/applications/hr/recruitment.rst:580 -msgid ":guilabel:`Starting At`: using the drop-down calendar, select the date and time for the meeting start time." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:582 -msgid ":guilabel:`Ending At`: using the drop-down calendar, select the date and time for the meeting end time." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:584 -msgid ":guilabel:`Duration`: this field auto populates based on the :guilabel:`Starting At` and :guilabel:`Ending At` times entered. If the meeting time is adjusted, this field automatically adjusts to the correct duration length." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:587 -msgid ":guilabel:`All Day`: if the meeting is an all day long event, check the box next to :guilabel:`All Day`. After this box is checked, the :guilabel:`Duration` field is hidden from view, a well as the meeting start and end times." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:590 -msgid ":guilabel:`Organizer`: the employee who created the meeting is populated in this field. Use the drop-down menu to change the selected employee." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:592 +#: ../../content/applications/hr/recruitment.rst:876 msgid ":guilabel:`Description`: enter a brief description in this field. There is an option to enter formatted text, such as numbered lists, headings, tables, as well as links, photos, and more. Use the powerbox feature, by typing a `/`, and a list of options are presented. Scroll through the options and click on the desired item. The item appears in the field and can be modified. Each command presents a different pop-up window. Follow the instructions for each command to complete the entry." msgstr "" -#: ../../content/applications/hr/recruitment.rst:598 -msgid ":guilabel:`Reminders`: select a reminder from the drop-down menu. Options include :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text Message`, each with a specific time period before the event (hours, days, etc). The reminder chosen will alert the meeting participants of the meeting via the selected option." +#: ../../content/applications/hr/recruitment.rst:884 +msgid "More options" msgstr "" -#: ../../content/applications/hr/recruitment.rst:602 +#: ../../content/applications/hr/recruitment.rst:886 +msgid "To add additional information to the meeting, click the :guilabel:`More Options` button in the lower-right corner of the pop-up window. Enter any of the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:889 +msgid ":guilabel:`Duration`: this field auto populates based on the :guilabel:`Starting At` and :guilabel:`Ending At` times entered. If the meeting time is adjusted, this field automatically adjusts to the correct duration length. The default length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:892 +msgid ":guilabel:`Recurrent`: if the meeting should repeat at a selected interval (not typical for a first interview), check the box next to :guilabel:`Recurrent`. Several additional fields appear when this is enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:896 +msgid ":guilabel:`Timezone`: using the drop-down menu, select the :guilabel:`Timezone` for the meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:898 +msgid ":guilabel:`Repeat`: using the drop-down menu, select when the meetings repeat. The available options are :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom`. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` field appears beneath it, along with another time frequency parameter (:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or :guilabel:`Years`). Enter a number in the blank field, then select the time period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:904 +msgid ":guilabel:`Repeat on`: if :guilabel:`Weekly` is selected for the :guilabel:`Repeat` field, the :guilabel:`Repeat on` field appears. Click on the corresponding day to select it." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:906 +msgid ":guilabel:`Day of Month`: if :guilabel:`Monthly` is selected for the :guilabel:`Repeat` field, the :guilabel:`Day of Month` field appears. Using the drop-down menu, select either :guilabel:`Date of month` or :guilabel:`Day of month`. If :guilabel:`Date of month` is selected, enter the date the meeting repeats. If :guilabel:`Day of month` is selected, use the drop-down menus to determine the frequency. Select either :guilabel:`First`, :guilabel:`Second`, :guilabel:`Third`, :guilabel:`Fourth`, or :guilabel:`Last` for the first drop-down menu, then select the day (:guilabel:`Monday`, :guilabel:`Tuesday`, etc.) in the second drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:913 +msgid ":guilabel:`Until`: using the drop-down menu, select when the meetings stop repeating. The available options are :guilabel:`Number of repetitions`, :guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of repetitions` is selected, enter the number of total meetings to occur in the blank field. If :guilabel:`End date` is selected, specify the date using the calendar pop-up window, or type in a date in a XX/XX/XXXX format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:920 msgid ":guilabel:`Location`: enter the location for the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:603 -msgid ":guilabel:`Meeting URL`: if the meeting is virtual, enter the meeting link in this field." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:604 +#: ../../content/applications/hr/recruitment.rst:921 msgid ":guilabel:`Tags`: select any tag(s) for the meeting using the drop-down menu. There is no limit to the number of tags that can be used." msgstr "" -#: ../../content/applications/hr/recruitment.rst:610 -msgid ":guilabel:`Recurrent`: if the meeting should repeat at a selected interval (not typical for a first interview), check the box next to :guilabel:`Recurrent`. This reveals a recurrence section. Enter the details for how often the meeting should repeat, including an end time." +#: ../../content/applications/hr/recruitment.rst:923 +msgid ":guilabel:`Appointment`: if an appointment is associated with this meeting, select it form the drop-down menu, or create a new appointment by typing in the appointment name, then click :guilabel:`Create & Edit...`. A :guilabel:`Create Appointment` form loads. Enter the information on the form, then click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:613 -msgid ":guilabel:`Privacy`: select the visibility of this meeting. Options are :guilabel:`Public`, :guilabel:`Private`, and :guilabel:`Only internal users`. :guilabel:`Public` allows for everyone to see the meeting, :guilabel:`Private` allows only the attendees listed on the meeting to see the meeting, and :guilabel:`Only internal users` allows anyone logged into the company database to see the meeting." +#: ../../content/applications/hr/recruitment.rst:927 +msgid ":guilabel:`Privacy`: select if the organizer appears either :guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting, using the drop-down menu. Next, select the visibility of this meeting, using the drop-down menu to the right of the first selection. Options are :guilabel:`Public`, :guilabel:`Private`, and :guilabel:`Only internal users`. :guilabel:`Public` allows for everyone to see the meeting, :guilabel:`Private` allows only the attendees listed on the meeting to see the meeting, and :guilabel:`Only internal users` allows anyone logged into the company database to see the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:618 -msgid ":guilabel:`Show as`: select from the drop-down whether the meeting time should appear as :guilabel:`Busy` or :guilabel:`Available` in the attendees' schedules. Setting this field to :guilabel:`Available` allows other meetings to be scheduled for the same time. It is recommended to set this field to :guilabel:`Busy`, so no other meetings can be scheduled for the attendees at the same time." +#: ../../content/applications/hr/recruitment.rst:934 +msgid ":guilabel:`Organizer`: the employee who created the meeting is populated in this field. Use the drop-down menu to change the selected employee." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:936 +msgid ":guilabel:`Reminders`: select a reminder from the drop-down menu. Default options include :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text Message`, each with a specific time period before the event (hours, days, etc). The reminder chosen alerts the meeting participants of the meeting via the selected option at the specified time. Multiple reminders can be selected in this field." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 msgid "A new meeting card with all the details populated, and ready to save." msgstr "" -#: ../../content/applications/hr/recruitment.rst:629 +#: ../../content/applications/hr/recruitment.rst:947 msgid "Send meeting to attendees" msgstr "" -#: ../../content/applications/hr/recruitment.rst:631 -msgid "Once changes have been entered and the meeting details are correct, the meeting can be sent to the attendees via email or text message." +#: ../../content/applications/hr/recruitment.rst:949 +msgid "Once changes have been entered and the meeting details are correct, the meeting can be sent to the attendees via email or text message from the expanded :guilabel:`Event Form` (what is seen when the :guilabel:`More Options` button is clicked on in the event pop-up window)." msgstr "" -#: ../../content/applications/hr/recruitment.rst:634 -msgid "To send the meeting via email, click the :guilabel:`Email` button next to the list of attendees. A :guilabel:`Contact Attendees` email configurator pop-up appears. A pre-formatted email using the default :guilabel:`Calendar: Event Update` email template populates the email body field. The followers of the document (job application), as well as the user who created the meeting are added as :guilabel:`Recipients` by default. Add the applicant's email address to the list to send the email to the applicant as well. Make any other desired changes to the email. If an attachment is needed, click the :guilabel:`Attach A File` button, navigate to the file, then click :guilabel:`Open`. Once the email is ready to be sent, click :guilabel:`Send`." +#: ../../content/applications/hr/recruitment.rst:953 +msgid "To send the meeting via email, click the :icon:`fa-envelope` :guilabel:`Email` button next to the list of attendees. A :guilabel:`Contact Attendees` email configurator pop-up window appears. A pre-formatted email using the default :guilabel:`Calendar: Event Update` email template populates the email body field. The followers of the document (job application), as well as the user who created the meeting are added as :guilabel:`Recipients` by default. Add the applicant's email address to the list to send the email to the applicant as well. Make any other desired changes to the email. If an attachment is needed, click the :guilabel:`Attachments` button, navigate to the file, then click :guilabel:`Open`. Once the email is ready to be sent, click :guilabel:`Send`." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 msgid "Enter the information to send the event via email." msgstr "" -#: ../../content/applications/hr/recruitment.rst:647 -msgid "To send the meeting via text message, click the :guilabel:`SMS` button next to the list of attendees. A :guilabel:`Send SMS Text Message` pop-up appears. At the top, in a blue box, information appears regarding the message. The first line lists how many records (phone numbers) are selected. The second line lists the number of recipients and how many of them are invalid. If a contact does not have a valid phone number listed, click :guilabel:`Close`, and edit the attendee's record, then redo these steps." +#: ../../content/applications/hr/recruitment.rst:966 +msgid "To send the meeting via text message, click the :icon:`fa-mobile` :guilabel:`SMS` button next to the list of attendees. A :guilabel:`Send SMS Text Message` pop-up appears." msgstr "" -#: ../../content/applications/hr/recruitment.rst:655 -msgid "It is *not* recommended to check the box to send to all the records in the :guilabel:`Send SMS Text Message` pop-up. This would send a message to all contacts with a valid phone number." +#: ../../content/applications/hr/recruitment.rst:969 +msgid "At the top, a blue box appears if any attendees do not have valid mobile numbers, and lists how many records are invalid. If a contact does not have a valid mobile number listed, click :guilabel:`Close`, and edit the attendee's record, then redo these steps." msgstr "" -#: ../../content/applications/hr/recruitment.rst:658 -msgid "When the message reads :guilabel:`0 are invalid`, type in the message to be sent in the :guilabel:`Message` field. Beneath the message field, the number of characters, as well as the amount of text messages required to send the message (according to GSM7 criteria) appears. Click :guilabel:`Put In Queue` to have the text sent later, after any other messages are scheduled, or click :guilabel:`Send Now` to send the message immediately." +#: ../../content/applications/hr/recruitment.rst:973 +msgid "When no warning message appears, type in the message to be sent to the attendees in the :guilabel:`Message` field. to add any emojis to the message, click the :guilabel:`Add Emoji` icon on the right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:977 +msgid "Beneath the message field, the number of characters, as well as the amount of text messages required to send the message (according to GSM7 criteria) appears. Click :guilabel:`Put In Queue` to have the text sent later, after any other messages are scheduled, or click :guilabel:`Send Now` to send the message immediately." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 msgid "Send a text message to the attendees of the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:669 +#: ../../content/applications/hr/recruitment.rst:987 msgid "Sending text messages is not a default capability with Odoo. To send text messages, credits are required, which need to be purchased. For more information on IAP credits and plans, refer to the :doc:`../essentials/in_app_purchase` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:676 +#: ../../content/applications/hr/recruitment.rst:994 msgid "Second interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:678 +#: ../../content/applications/hr/recruitment.rst:996 msgid "After an applicant has passed the :guilabel:`First Interview` stage, they can be moved to the :guilabel:`Second Interview` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Second Interview` stage, or click on the :guilabel:`Second Interview` stage button at the top of the individual applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:683 -msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured for this stage, unlike for the :guilabel:`First Interview` stage. The recruiter can now :ref:`schedule a second interview ` with the applicant, following the same process as for the first interview." +#: ../../content/applications/hr/recruitment.rst:1001 +msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured for this stage. The recruiter can now :ref:`schedule a second interview ` with the applicant, following the same process as the first interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:691 +#: ../../content/applications/hr/recruitment.rst:1009 msgid "Contract proposal" msgstr "" -#: ../../content/applications/hr/recruitment.rst:693 -msgid "When the applicant has passed the interview stages and an offer is ready to be sent, they can be moved to the :guilabel:`Contract Proposal` stage. Drag and drop the applicant's card to the :guilabel:`Contract Proposal` stage, or click on the :guilabel:`Contract Proposal` stage button at the top right of the individual applicant's card." +#: ../../content/applications/hr/recruitment.rst:1011 +msgid "When the applicant has passed the interview stages and an offer is ready to be sent, they can be moved to the :guilabel:`Contract Proposal` stage. Drag and drop the applicant's card to the :guilabel:`Contract Proposal` stage, or click on the :guilabel:`Contract Proposal` stage button at the top-right of the individual applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:698 -msgid "The next step is to send an offer to the applicant. On the applicant's card, click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a Simulation Link` pop-up appears. All fields are pre-populated with information from the job position, except for the :guilabel:`Force New Cars List`, :guilabel:`Default Vehicle`, and the :guilabel:`Canteen Cost` (this is set to `0.00`)." +#: ../../content/applications/hr/recruitment.rst:1016 +msgid "The next step is to send an offer to the applicant. On the applicant's card, click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a Simulation Link` pop-up appears. Most fields are pre-populated with information from the job position. If any necessary fields are blank, enter the relevant information in the fields." msgstr "" -#: ../../content/applications/hr/recruitment.rst:705 -msgid "Not all fields may appear on the :guilabel:`Generate a Simulation Link` pop-up. Depending on the localization setting for the company and the applications installed, some fields may not appear. For example if the *Fleet* application is not installed, the fields related to vehicles will not appear on the pop-up." +#: ../../content/applications/hr/recruitment.rst:1022 +msgid "Not all fields may appear on the :guilabel:`Generate a Simulation Link` pop-up. Depending on the localization setting for the company and the applications installed, some fields may not appear. For example if the *Fleet* application is not installed, any fields related to vehicles do not appear on the pop-up window." msgstr "" -#: ../../content/applications/hr/recruitment.rst:711 +#: ../../content/applications/hr/recruitment.rst:1028 msgid "Universal fields" msgstr "" -#: ../../content/applications/hr/recruitment.rst:713 +#: ../../content/applications/hr/recruitment.rst:1030 msgid "The following fields appear for all offers sent to applicants regardless of localization settings." msgstr "" -#: ../../content/applications/hr/recruitment.rst:715 -msgid ":guilabel:`Offer Template`: the template currently being used to populate the :guilabel:`Generate a Simulation Link` pop-up. To modify the template, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." +#: ../../content/applications/hr/recruitment.rst:1032 +msgid ":guilabel:`Contract Template`: the template currently being used to populate the :guilabel:`Generate a Simulation Link` pop-up window. To modify the template, click the :guilabel:`Internal link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save & Close`. A different :guilabel:`Contract Template` can be selected using the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:718 -msgid ":guilabel:`Job Title`: the name of the position being offered to the applicant." +#: ../../content/applications/hr/recruitment.rst:1037 +msgid ":guilabel:`Job Position`: the name of the :guilabel:`Job Position` being offered to the applicant. The selections available in the drop-down menu correspond to the :guilabel:`Job Positions` configured on the main *Recruitment* dashboard." msgstr "" -#: ../../content/applications/hr/recruitment.rst:719 +#: ../../content/applications/hr/recruitment.rst:1040 +msgid ":guilabel:`Job Title`: the specific name of the position being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1041 +msgid ":guilabel:`Department`: the :guilabel:`Department` the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1042 msgid ":guilabel:`Contract Start Date`: the date the contract takes effect. The default date is the current date. To modify the date, click the drop-down to reveal a calendar. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." msgstr "" -#: ../../content/applications/hr/recruitment.rst:723 +#: ../../content/applications/hr/recruitment.rst:1046 msgid ":guilabel:`Yearly Cost`: the annual salary being offered." msgstr "" -#: ../../content/applications/hr/recruitment.rst:724 -msgid ":guilabel:`Offer Link`: this link takes the applicant to a webpage where they can enter their personal information, which will be imported to their employee record when created. If applicable, the applicant can modify their salary package (this option is not available for all localizations). Lastly, this is where the applicant accepts the offer by clicking :guilabel:`Review Contract & Sign` to accept the contract and sign it using the *Sign* application." +#: ../../content/applications/hr/recruitment.rst:1047 +msgid ":guilabel:`Link Expiration Date`: job offers are only valid for a specific period of time. The default expiration date is 30 days. Modify the expiration date, if desired." msgstr "" -#: ../../content/applications/hr/recruitment.rst:732 -msgid "The *Sign* application must be installed in order for a document to be signed. Ensure the *Sign* application is installed to use this feature." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:738 -msgid "The following fields will only appear if specific localization settings are selected, and/or certain applications are installed. For example if the *Fleet* application is not installed, none of the optional fields related to vehicles will appear, such as :guilabel:`Force New Cars List` or :guilabel:`Default Vehicle`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:743 -msgid ":guilabel:`Job Position`: the official title of the job being offered to the applicant, from the :guilabel:`Job Position` card. To modify the name, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:746 -msgid ":guilabel:`Department`: the department the job position falls under. To modify the department, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:749 -msgid ":guilabel:`Force New Cars List`: check this box to offer a new vehicle to the applicant." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:750 -msgid ":guilabel:`Default Vehicle`: using the drop-down menu, select the vehicle that will be assigned to the applicant." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:752 -msgid ":guilabel:`Canteen Cost`: enter the amount that is offered to the applicant for the cafeteria." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:753 -msgid ":guilabel:`Contract Type`: using the drop-down menu, select the type of contract that is being offered." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:-1 -msgid "Format the offer to send to the applicant. Make any modifications before sending." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:761 +#: ../../content/applications/hr/recruitment.rst:1051 msgid "Send offer" msgstr "" -#: ../../content/applications/hr/recruitment.rst:763 -msgid "To send the offer to the applicant, click :guilabel:`Send`. If the applicant does not have an email address listed on their applicant card, the applicant form appears so their email can be configured. If there is already an email configured on the applicant's card, the email pop-up appears instead. If prompted with the applicant's card, enter the applicant's email address in the :guilabel:`Email` field, then click :guilabel:`Save`. The applicant form closes and the email pop-up appears." +#: ../../content/applications/hr/recruitment.rst:1053 +msgid "When the information is all updated, click :guilabel:`Send By Email` to send the offer to the applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:769 -msgid "The :guilabel:`Applicant: Your Salary Package` email template is used, and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-populated based on the email template. If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button. Once the email is ready to send, click :guilabel:`Send`." +#: ../../content/applications/hr/recruitment.rst:1056 +msgid "If the applicant does not have an email address listed on their applicant card, a warning appears in a red box at the bottom of the :guilabel:`Generate a Simulation Link` pop-up window, stating :guilabel:`The applicant does not have a valid email set. The Offer Link won't be able to be completed.` Click :guilabel:`Discard`, enter an email on the applicant's card, then click the :guilabel:`Generate Offer` button again." msgstr "" -#: ../../content/applications/hr/recruitment.rst:777 +#: ../../content/applications/hr/recruitment.rst:1062 +msgid "An email pop-up window loads. The default :guilabel:`Recruitment: Your Salary Package` email template is used, and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-populated based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1070 +msgid "Once the email is ready to send, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1073 msgid "To send an offer, ensure the *Sign* application is installed. This is necessary so the offer can be sent to the applicant by the recruiter. The applicant does not need any software installed." msgstr "" @@ -8600,36 +9145,56 @@ msgstr "" msgid "Send an email to the applicant with a link to the offered salary." msgstr "" -#: ../../content/applications/hr/recruitment.rst:787 +#: ../../content/applications/hr/recruitment.rst:1081 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1083 +msgid "The email template includes a :guilabel:`Configure your package` button. This link takes the applicant to a webpage where they can modify the proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1087 +msgid "Once the applicant is hired, the personal information entered on the webpage is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1090 +msgid "If applicable, the applicant can modify their salary package. This option is not available for all localizations. Depending on where the company is located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1093 +msgid "Once all the information is completed, the applicant accepts the offer by clicking the :guilabel:`Review Contract & Sign` button to accept the contract and sign it using the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:1100 msgid "Contract signed" msgstr "" -#: ../../content/applications/hr/recruitment.rst:789 +#: ../../content/applications/hr/recruitment.rst:1102 msgid "Once the applicant has accepted the offer and signed the contract, the next step is to move the applicant to the :guilabel:`Contract Signed` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Contract Signed` stage, or click the :guilabel:`More` button at the top of the applicant's card to reveal the :guilabel:`Contract Signed` stage button at the top of the individual applicant's card, and click :guilabel:`Contract Signed`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:796 -msgid "The :guilabel:`Contract Signed` stage is folded in the kanban view, but the card may still be dragged and dropped into that stage." +#: ../../content/applications/hr/recruitment.rst:1109 +msgid "The :guilabel:`Contract Signed` stage is folded in the Kanban view, but the card may still be dragged and dropped into that stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:799 -msgid "Once the applicant's card moves to the :guilabel:`Contract Signed` stage, a green :guilabel:`Hired` banner appears in the top right of the applicant's card." +#: ../../content/applications/hr/recruitment.rst:1112 +msgid "Once the applicant's card moves to the :guilabel:`Contract Signed` stage, a green :guilabel:`HIRED` banner appears in the top-right of the applicant's card." msgstr "" #: ../../content/applications/hr/recruitment.rst:-1 msgid "Hired banner in the top right corner of applicant card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:807 +#: ../../content/applications/hr/recruitment.rst:1120 msgid "Create employee" msgstr "" -#: ../../content/applications/hr/recruitment.rst:809 -msgid "Once the applicant has been hired, the next step is to create an employee record of them. On the applicant's card, click the :guilabel:`Create Employee` button in the top left. An employee form appears, and any information from the applicant's card that can be imported into the employee card appears in the form." +#: ../../content/applications/hr/recruitment.rst:1122 +msgid "Once the applicant has been hired, the next step is to create an employee record of them. On the applicant's card, click the :guilabel:`Create Employee` button in the top-left. An employee form appears, and any information from the applicant's card that can be imported into the employee card appears in the form." msgstr "" -#: ../../content/applications/hr/recruitment.rst:814 -msgid "Fill out the rest of the form. For detailed information on the fields, refer to the :doc:`employees/new_employee` documentation. When done, click :guilabel:`Save`. The employee record is now saved in the *Employees* app." +#: ../../content/applications/hr/recruitment.rst:1127 +msgid "Fill out the rest of the form. For detailed information on the fields, refer to the :doc:`employees/new_employee` documentation. When done, the employee record is saved in the *Employees* app." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:5 @@ -8804,429 +9369,120 @@ msgstr "" msgid "Proceed to fill out the modal interview form as a typical survey. For specific directions on how to create a survey, refer to the :doc:`survey essentials <../../marketing/surveys/create>` document, which provides step-by-step instructions on how to create and configure a survey." msgstr "" -#: ../../content/applications/hr/referrals.rst:3 +#: ../../content/applications/hr/referrals.rst:5 msgid "Referrals" msgstr "" -#: ../../content/applications/hr/referrals.rst:5 -msgid "Odoo's *Referrals* application is a centralized place where all information regarding referrals is housed, from points earned, coworkers hired, and rewards selected. Users can recommend people they know for job positions, then earn referral points as those people progress through the recruitment pipeline. Once enough referral points are earned, they can be exchanged for prizes. The Referrals application integrates with the *Employees*, *Recruitment*, and *Website* applications, all of which must be installed in order for the *Referrals* application to function." +#: ../../content/applications/hr/referrals.rst:7 +msgid "Odoo's *Referrals* application is a centralized place where all information regarding referrals is housed - from points earned, coworkers hired, and rewards selected. Users can recommend people they know for job positions, and then earn referral points as those people progress through the recruitment pipeline. Once enough referral points are earned, they can be exchanged for prizes. The *Referrals* application integrates with the *Employees*, *Recruitment*, and *Website* applications, all of which must be installed in order for the *Referrals* application to function." msgstr "" -#: ../../content/applications/hr/referrals.rst:12 -msgid "The only configuration needed for the Referrals application after it is installed are the :ref:`rewards `; everything else is pre-configured when Odoo Referrals is installed." +#: ../../content/applications/hr/referrals.rst:14 +msgid "The only configurations needed for the *Referrals* application *after* installation are related to the :ref:`rewards `; everything else is pre-configured when Odoo *Referrals* is installed." msgstr "" -#: ../../content/applications/hr/referrals.rst:16 -msgid "Any user with either :guilabel:`Referral User`, :guilabel:`Officer`, or :guilabel:`Administrator` rights for the Recruitment application has access to the Referrals application. Only user's with :guilabel:`Administrator` rights for the Recruitment application have access to the :ref:`reporting ` and configurations menus. For more information on users and access rights, refer to these documents: :doc:`../general/users` and :doc:`../general/users/access_rights`." +#: ../../content/applications/hr/referrals.rst:18 +msgid "Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or :guilabel:`Administrator` access rights for the *Recruitment* application have access to the *Referrals* application. Only users with :guilabel:`Administrator` access rights for the *Recruitment* application have access to the :ref:`reporting ` and configurations menus. For more information on users and access rights, refer to these documents: :doc:`../general/users` and :doc:`../general/users/access_rights`." msgstr "" -#: ../../content/applications/hr/referrals.rst:23 +#: ../../content/applications/hr/referrals.rst:26 msgid "Onboarding" msgstr "" -#: ../../content/applications/hr/referrals.rst:25 -msgid "When opening the *Referrals* application for the first time, a pre-configured onboarding script appears. This is in the form of four slides, each explaining the different parts of the Referrals application. At the top of the dashboard, the following message is displayed throughout all the onboarding slides: :guilabel:`GATHER YOUR TEAM! Job Referral Program`. Behind this main message is an image, and beneath it some more explanatory text." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:31 -msgid "Each of the onboarding slides has a corresponding image and message that is displayed. After reading each message, click the :guilabel:`Next` button to advance to the next slide." +#: ../../content/applications/hr/referrals.rst:28 +msgid "When opening the *Referrals* application for the first time, a pre-configured onboarding script appears. This is in the form of four slides, each explaining the different parts of the *Referrals* application. At the top of the dashboard, the following message is displayed throughout all the onboarding slides: :guilabel:`GATHER YOUR TEAM! Job Referral Program`. Behind this main message is an image, and beneath it some more explanatory text." msgstr "" #: ../../content/applications/hr/referrals.rst:34 +msgid "Each of the onboarding slides has a corresponding image and message that is displayed. After reading each message, click the :guilabel:`Next` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:37 msgid "The text that appears on each slide is as follows:" msgstr "" -#: ../../content/applications/hr/referrals.rst:36 +#: ../../content/applications/hr/referrals.rst:39 msgid ":guilabel:`Oh no! Villains are lurking the city! Help us recruit a team of superheroes to save the day!`" msgstr "" -#: ../../content/applications/hr/referrals.rst:38 +#: ../../content/applications/hr/referrals.rst:41 msgid ":guilabel:`Browse through open job positions, promote them on social media, or refer friends.`" msgstr "" -#: ../../content/applications/hr/referrals.rst:39 +#: ../../content/applications/hr/referrals.rst:42 msgid ":guilabel:`Collect points and exchange them for awesome gifts in the shop.`" msgstr "" -#: ../../content/applications/hr/referrals.rst:40 +#: ../../content/applications/hr/referrals.rst:43 msgid ":guilabel:`Compete against your colleagues to build the best justice league!`" msgstr "" -#: ../../content/applications/hr/referrals.rst:43 -msgid "The onboarding slides will appear every time the Referrals application is opened, until all the slides have been viewed and the :guilabel:`Start Now` button has been clicked. If the onboarding is exited at any point, or if the :guilabel:`Start Now` button has *not* been clicked, the onboarding slides will begin again when the Referrals application is opened. Once the :guilabel:`Start Now` button has been clicked, the onboarding slides will not be seen again, and the main dashboard will load when the Referrals application is opened from that point on." +#: ../../content/applications/hr/referrals.rst:46 +msgid "The onboarding slides will appear every time the *Referrals* application is opened, until all the slides have been viewed and the :guilabel:`Start Now` button has been clicked. If the onboarding is exited at any point, or if the :guilabel:`Start Now` button has *not* been clicked, the onboarding slides will begin again when the *Referrals* application is opened. Once the :guilabel:`Start Now` button has been clicked, the onboarding slides will not be seen again, and the main dashboard will load when the *Referrals* application is opened from that point on." msgstr "" -#: ../../content/applications/hr/referrals.rst:50 -msgid "At any point during onboarding, the :guilabel:`Skip` button may be clicked. This exits the onboarding, and the main Referrals dashboard loads. If :guilabel:`Skip` is clicked, onboarding slides will not load anymore when opening the Referrals application." +#: ../../content/applications/hr/referrals.rst:53 +msgid "At any point during onboarding, the :guilabel:`Skip` button may be clicked. This exits the onboarding, and the main *Referrals* dashboard loads. If :guilabel:`Skip` is clicked, onboarding slides will not load anymore when opening the *Referrals* application." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 msgid "An onboarding slide with the skip and next buttons visible at the bottom." msgstr "" -#: ../../content/applications/hr/referrals.rst:59 +#: ../../content/applications/hr/referrals.rst:62 msgid "If there are any candidates hired that the user had referred prior to opening the Referrals app (meaning the onboarding slides have not appeared before), when :guilabel:`Start Now` is clicked at the end of onboarding, instead of going to the main dashboard, a :ref:`hired ` screen appears instead." msgstr "" -#: ../../content/applications/hr/referrals.rst:65 +#: ../../content/applications/hr/referrals.rst:68 msgid "Modifying onboarding slides" msgstr "" -#: ../../content/applications/hr/referrals.rst:67 -msgid "Onboarding slides can be modified if desired. Only users with :guilabel:`Administrator` rights for the Recruitment application can modify onboarding slides. To edit a slide, navigate to :menuselection:`Referrals app --> Configuration --> Onboarding.` Each line displays the text for the individual onboarding slide. To edit an onboarding slide, click on an individual slide line to open the slide's onboarding form, then click :guilabel:`Edit`." +#: ../../content/applications/hr/referrals.rst:70 +msgid "Onboarding slides can be modified if desired. Only users with :guilabel:`Administrator` rights for the *Recruitment* application can modify onboarding slides. To edit a slide, navigate to :menuselection:`Referrals app --> Configuration --> Onboarding.` Each line displays the text for the individual onboarding slide. To edit an onboarding slide, click on an individual slide line to open the slide's onboarding form." msgstr "" -#: ../../content/applications/hr/referrals.rst:73 -msgid "Make any changes to the message in the :guilabel:`Text` box. To change the order the slide appear in the onboarding, the :guilabel:`Sequence` can be modified. Type in the corresponding number to indicate the order in which the slides should be displayed. A :guilabel:`Company` may be selected, however, if this field is populated, that slide will only be displayed for that particular company." +#: ../../content/applications/hr/referrals.rst:76 +msgid "Make any changes to the message in the :guilabel:`Text` field. A :guilabel:`Company` may be selected, as well. However, if this field is populated, that slide is *only* displayed for that particular company." msgstr "" -#: ../../content/applications/hr/referrals.rst:78 -msgid "The image can be modified as well. Hover over the image thumbnail in the top right corner of the form. A :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon appear. Click the :guilabel:`✏️ (pencil)` icon to change the image. A file navigator window loads. Navigate to the desired image, select it, then click :guilabel:`Open`. The new image appears in the thumbnail. To delete an image, click the :guilabel:`🗑️ (garbage can)` icon, then select a new image using the :guilabel:`✏️ (pencil)` icon." +#: ../../content/applications/hr/referrals.rst:81 +msgid "The :guilabel:`Company` field only appears when in a multi-company database." msgstr "" -#: ../../content/applications/hr/referrals.rst:85 -msgid "To save any changes, click :guilabel:`Save`, or click :guilabel:`Discard` to delete any changes and revert to the original content." +#: ../../content/applications/hr/referrals.rst:83 +msgid "The image can be modified, as well. Hover over the image thumbnail in the top-right corner of the form. A :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon appear. Click the :guilabel:`✏️ (pencil)` icon to change the image. A file navigator window loads. Navigate to the desired image, select it, then click :guilabel:`Open`. The new image appears in the thumbnail. To delete an image, click the :guilabel:`🗑️ (garbage can)` icon, then select a new image using the :guilabel:`✏️ (pencil)` icon." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 msgid "An onboarding slide in edit mode, with the main fields highlighted." msgstr "" -#: ../../content/applications/hr/referrals.rst:92 -msgid "The order of the slides can also be changed directly in the Onboarding dashboard, without having to edit an individual onboarding slide. Click the up and down arrow symbol that appears after the checkbox and before the slide text, and drag the slide to the desired position. The :guilabel:`Sequence` automatically changes on all the slide's onboarding forms, reflecting the new sequence." +#: ../../content/applications/hr/referrals.rst:94 +msgid "The sequence in which the slides appear can be changed from the *Onboarding* dashboard. Click the :guilabel:`(six small gray boxes)` icon to the left of the the slide text, and drag the slide to the desired position." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 msgid "The onboarding slides in a list, with the drag and drop arrows highlighted." msgstr "" -#: ../../content/applications/hr/referrals.rst:103 -msgid "Share job positions" -msgstr "" - #: ../../content/applications/hr/referrals.rst:105 -msgid "In order to earn referral points, a user must first share a job position so the applicant can apply for the position. There are several ways to share job positions within the Referrals application, through the :ref:`View Jobs ` button and the :ref:`Email A Friend ` button." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:113 -msgid "View Jobs" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:115 -msgid "To see all job positions that are actively recruiting candidates, click the :guilabel:`View Jobs` button on the main Referrals dashboard. This presents all job positions, with each individual job presented in its own card." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "The 'View Jobs' screen, displaying all current open job positions. All information is\n" -"displayed on the card." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:124 -msgid "Each job position card contains the following information:" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:126 -msgid "The title of the job position. This information is taken from the :guilabel:`Job Position` field of the job form." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:128 -msgid "The number of positions being recruited. This information is taken from the :guilabel:`Expected New Employees` field of the :guilabel:`Recruitment` tab of the job form." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:130 -msgid "The points a user will earn when an applicant applies for the position." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:131 -msgid "The job description detailing the job position. This information is taken from the :guilabel:`Job Position` tab of the job form." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:134 -msgid "To see all the details for a job position, click the :guilabel:`More Info` button on the specific card. This opens the job position webpage in a new browser tab. This is what an applicant sees before applying for a position." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:139 -msgid "Only published job positions will be visible in the Referrals app. To check which job positions are published or not, refer to the :doc:`recruitment/new_job` documentation." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:143 -msgid "Refer friends" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:145 -msgid "To share a job position with someone, click the :guilabel:`Refer Friend` button on the specific job position card. A pre-configured :guilabel:`Send Job Offer by Mail` email pop-up window appears. Enter the recipient's email address in the :guilabel:`Email` field." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:149 -msgid "The subject and body are populated using a default template. The subject `Job for you` appears, and can be modified if desired." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:152 -msgid "The specific title of the job position will populate the :guilabel:`Job Position` placeholder in the email body. The `See Job Offer` text in the email body is an individualized tracking link to the specific job position listed on the website. When the prospective employee receives the email, the link will send them to the job position page, where they can apply for the position, and the person who referred them is tracked in the Referrals application." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:158 -msgid "If desired, add any text or closing salutation to the email body. When all edits have been made, click :guilabel:`Send Email` to send the email, or click :guilabel:`Cancel` to close the email pop-up window." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "Referral email pop-up window with the email message inside it." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:167 -msgid "Share a job" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:169 -msgid "There are several other ways to share a job position aside from sending an email, via social media platforms and tracking links to the job position. At the bottom of each job position card are four icons and corresponding tracking links that can be used to share the job position, keeping track of applicants in the Referrals application." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "The various sharing icons that appear for each job." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:179 -msgid "Link" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:181 -msgid "To share the job position with a customized tracking link, click the :guilabel:`Share Now` button with the :guilabel:`🔗 (chain)` icon inside it. A :guilabel:`Link to Share` pop-up window appears with the tracking link. Click :guilabel:`Copy` to copy the link. After the link is copied, click the :guilabel:`Close` button to close the pop-up. Next, share the link with the prospective employee however desired." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:188 -msgid "Facebook" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:190 -msgid "To share the job position using Facebook, click the :guilabel:`Share Now` button with the :guilabel:`f (Facebook icon)` inside it. If the user is already logged into Facebook, when the :guilabel:`f (Facebook icon)` is clicked, a :guilabel:`Share on Facebook` page loads in a new tab, with the link populated in the main body of the new post. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to Facebook first." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:196 -msgid "Type in any additional information to add to the post, in the space directly below your name. If desired, :guilabel:`tag` users, :guilabel:`check-in` at a location, or add a :guilabel:`status` to the post. To tag a user, click the :guilabel:`Tag Friends` icon and select the people to tag to the post. To add a check-in location, click the :guilabel:`Check in` icon, and select the location from the pop-up of predetermined locations based on your current location. To add a :guilabel:`status`, click the :guilabel:`Feeling/Activity` icon, then select either the feeling or the activity type, and lastly, if an activity type was selected, select the specific activity." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:204 -msgid "There are five methods to share the job position, :guilabel:`Your Story`, :guilabel:`Share on a Friend's Timeline`, :guilabel:`Share in a Group`, :guilabel:`Share in an Event`, and :guilabel:`Share in a Private Message`. To select the sharing method, click the drop-down menu located at the top of the page, directly beneath the :guilabel:`Share on Facebook` banner." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "The view on Facebook when sharing a job description. All the various ways to share are\n" -"highlighted, as are all the required settings." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:216 -msgid "Share to news feed or story" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:218 -msgid "The default sharing method is through the :guilabel:`News Feed`, :guilabel:`Story`, or both. At the lower portion of the form are radio buttons next to the two options, :guilabel:`Feed` (for the News Feed) and :guilabel:`Your Story` for stories. When :guilabel:`Share to News Feed or Story` is selected, these buttons are active, if another option is selected, these radio buttons are greyed out. Activate the radio button(s) to indicate how the job position should be shared, either in the news feed, the story, or both." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:225 -msgid "The :guilabel:`Share to news feed or story` option allows for specific privacy settings to be selected. In the lower right corner of the screen, there are two drop-down menu options, one for the :guilabel:`Feed` option, the other for the :guilabel:`Your story` option. Select the posting parameters from the drop-down menus. The :guilabel:`Feed` ad :guilabel:`Your story` options appear different from user to user, depending on what privacy settings have been created in Facebook. :guilabel:`Public` and :guilabel:`Friends` are default options, but other options that the user may have configured will appear as well, such as custom groups." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:233 -msgid "When the post and/or story is ready to be shared, click the blue :guilabel:`Post to Facebook` button at the bottom of the screen." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:236 -msgid "Share on a friend's timeline" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:238 -msgid "Instead of making a public post on the user's on Facebook page, the job position can be shared directly on a friend's timeline. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share on a Fried's Timeline`." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:242 -msgid "When selected, a :guilabel:`Friend` field appears below the selection. Begin to type in the friend's name. As the name is typed, a list appears, populated with names that match what is entered. Select the friend from the list. **Only** one friend can be selected." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:246 -#: ../../content/applications/hr/referrals.rst:261 -#: ../../content/applications/hr/referrals.rst:275 -msgid "When the post is ready to be shared, click the blue :guilabel:`Post to Facebook` button at the bottom of the screen." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:249 -msgid "Share in a group" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:251 -msgid "To reach a specific audience and not share the job position publicly with everyone, a job can be shared in a group. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in a Group`." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:255 -msgid "When selected, a :guilabel:`Group` field appears below the selection. The available groups that can be posted to are groups the user is currently a member of. Job positions cannot be shared with groups the user has not joined. Begin to type in the name of the group. As the group name is typed, a list appears, populated with the group names that match what is entered. Select the group from the list. Only one group can be selected." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:264 -msgid "Share in an event" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:266 -msgid "A job position can also be shared on an event page. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in an Event`." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:269 -msgid "When selected, an :guilabel:`Event` field appears below the selection. The available events that can be posted to are events the user is invited to. This includes events that the user has not responded to yet, and events that have occurred in the past. Begin to type in the name of the event. As the event name is typed, a list appears, populated with the events that match what is entered. Select the event from the list. Only one event can be selected." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:278 -msgid "Share in a private message" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:280 -msgid "The last option is to share a job position privately instead of publicly, in a Facebook message. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in an Private Message`." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:284 -msgid "When selected, a :guilabel:`To` field appears below the selection. Begin to type in the friend's name. As the name is typed, a list appears, populated with names that match what is entered. Select the friend from the list. Multiple friends can be selected and added to a single message. Repeat this process for each friend to be added." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:289 -msgid "When the message is ready to be sent, click the blue :guilabel:`Send message` button at the bottom of the screen." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:293 -msgid "X/Twitter" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:295 -msgid "A job position can also be shared on X/Twitter. Click the :guilabel:`Share Now` button with the bird icon inside it. If the user is already signed in to X/Twitter, when the :guilabel:`Share Now` icon is clicked, an X/Twitter page loads in a new tab with a pre-populated message ready to post, in a draft pop-up. If the user is *not* already signed in, a sign-in screen loads instead, prompting the user to sign in to X/Twitter." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:301 -msgid "The default message is:" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:303 -msgid ":guilabel:`Amazing job offer for (Job Position)! Check it live: (link to Job Position)`" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:305 -msgid "Type in any additional information or make any edits to the message. If desired, click the :guilabel:`X` in the top left corner of the thumbnail preview of the webpage to remove it. To adjust the audience for the message, click the drop-down button labeled :guilabel:`Everyone`. Select the preferred audience from the drop-down menu. The default option is :guilabel:`Everyone`, and the other options is :guilabel:`Circle`. The :guilabel:`Circle` is a group of people that the user has selected in X/Twitter." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:312 -msgid "The default setting is :guilabel:`🌎 (globe) Everyone can reply`, an allows everyone on X/Twitter to reply to the message. To change this, click the :guilabel:`🌎 (globe) Everyone can reply` button in the lower left section of the message. There are four options presented: :guilabel:`Everyone`, :guilabel:`Accounts you follow`, :guilabel:`Verified accounts`, and :guilabel:`Only accounts you mention`. Selecting one of the other options restricts who can reply to the message." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:318 -msgid "There are various other items that can be added to the message. Media (photos, videos, etc), GIF's, polls, emojis, and a location may all be added. Click the corresponding icon in the bottom left of the message and follow the prompts to add the desired additional elements." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:322 -msgid "To have the message posted at a future date and time, click the :guilabel:`Schedule` icon in the lower left of the message window. It is the fifth icon from the left. Enter the date and time that the message should be posted using the date and time selector presented. Click :guilabel:`Confirm` to add the scheduled time to the message." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:327 -msgid "To post the message, click :guilabel:`Post`. The message will be immediately posted, or, if it was scheduled, will be posted at the scheduled date and time." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "The X/Twitter pop-up when sharing a job description. All the other items than can be added\n" -"to the message are highlighted, as is the visibility setting and the post button." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:336 -msgid "LinkedIn" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:338 -msgid "To share a job position on LinkedIn, click the :guilabel:`Share Now` button with the :guilabel:`in (LinkedIn logo)` inside it. If the user is already logged into LinkedIn, when the :guilabel:`Share Now` button is clicked, a new tab loads in LinkedIn, with a link to the job position at the top. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to LinkedIn first." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:344 -msgid "The job position can be shared either in a public post, or in a private message to an individual or group of individuals." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:348 -msgid "Share in a post" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:350 -msgid "To share the job position in a public post, click the :guilabel:`✏️ (pencil) Share in a post` button in the lower-left corner of the screen. A :guilabel:`Create a post` window loads, with the job position link populated. Enter any other information to the post in the field." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:354 -msgid "To change the audience that will see the post, click the :guilabel:`🌎 (globe) Anyone` drop-down, located directly beneath the account name. Click on the desired selection, then click the :guilabel:`Save` button on the far right side of the screen, beneath the last listed option." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:358 -msgid ":guilabel:`Anyone` allows anyone on LinkedIn to see the post. :guilabel:`Connections only` will only share the post with people who are connected with the user, and will be hidden from everyone else. :guilabel:`Group` shares the post with a specific group the user is a member of. The post can only be shared with one group; posting to multiple groups at once is not available. If :guilabel:`Group` is selected, a page loads with a list of all the groups the user is currently a member of. Click on a group to select it, then click the :guilabel:`Save` button in the lower right corner." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:366 -msgid "Next, select who can comment on the post. To change this setting, click on the :guilabel:`💬 (speech bubble) Anyone` button located beneath the body of the post. A page loads with the various options. Click on one of the three options to select it. The three options are :guilabel:`Anyone`, :guilabel:`Connections only`, and :guilabel:`No one`. The default option is :guilabel:`Anyone`, which allows anyone with a LinkedIn account to comment on the post. :guilabel:`Connections only` will only allow people who are connected with the user to comment on the post. :guilabel:`No one` turns off commenting. After making a selection, click the :guilabel:`Save` button in the far lower right corner." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:375 -msgid "Finally, once the post is edited and the settings have been selected, click :guilabel:`Post` to share the job position." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "A linkedIn post to share a job. The job position is highlighted as is the post button." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:383 -msgid "Send as private message" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:385 -msgid "Instead of making a public post, the post can be sent to a connection in a private message. To do so, click the :guilabel:`Send as private message` button in the lower left corner. A message window loads with the link to the job description in the bottom of the window. First, select the recipient(s) for the message. Type the name in the :guilabel:`Search for message recipients` field. As the name is typed in, any matching connections appear. Click on a connection to add them. Repeat this for all the recipients to send the message to. There is no limit on the number of connections that can be messaged. Next, enter any additional text in the message body. Click :guilabel:`Send` in the lower right corner to send the message. A :guilabel:`Message successfully sent!` screen loads. Two options are presented, :guilabel:`View Message` and :guilabel:`Continue to LinkedIn`. Click on the desired selection to navigate to that choice, or close the browser tab to exit." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:399 -msgid "Email a friend" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:401 -msgid "Another way to share job opportunities is to share the entire current list of open job positions instead of one job position at a time. To do this, navigate to the main *Referrals* app dashboard. Click the :guilabel:`Email a friend` button at the bottom of the screen. A :guilabel:`Send Job Offer by Mail` pop-up window appears." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:406 -msgid "Enter the email address(es) in the :guilabel:`Email` line. The email can be sent to multiple recipients, simply enter a comma followed by a single space after each email address. The :guilabel:`Subject` is pre-configured with `Job for you`, but can be edited." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:410 -msgid "The email body is also populated with pre-configured text. The text that appears is:" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:412 -msgid "`Hello,`" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:414 -msgid "`There are some amazing job offers in my company! Have a look, they can be interesting for you`" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:416 -msgid "`See Job Offers`" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:418 -msgid "The `See Job Offers` text is a tracking link to a complete list of all job positions currently being recruited for, that are live on the company's website (published). Add any additional text and/or make any edits to the message body, then click :guilabel:`Send Mail` to send the email. The message will be sent and the window will close." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:426 msgid "Hired referrals" msgstr "" -#: ../../content/applications/hr/referrals.rst:428 +#: ../../content/applications/hr/referrals.rst:107 msgid "When a candidate that has been referred by a user is hired, the user \"grows their superhero team\" and adds superhero avatars to their Referrals dashboard." msgstr "" -#: ../../content/applications/hr/referrals.rst:431 +#: ../../content/applications/hr/referrals.rst:110 msgid "After a referral has been hired, when the user next opens the Referrals app, instead of the main dashboard, a hired page loads. The text :guilabel:`(Referral Name) has been hired! Choose an avatar for your new friend!` appears." msgstr "" -#: ../../content/applications/hr/referrals.rst:435 -msgid "Below this message are five avatar thumbnails to choose from. If an avatar has already been assigned to a referral, the thumbnail is greyed out, and the name the avatar has been chosen for appears beneath the avatar. Click on an available avatar to select it." +#: ../../content/applications/hr/referrals.rst:114 +msgid "Below this message are five avatar thumbnails to choose from. If an avatar has already been assigned to a referral, the thumbnail is grayed out, and the name that the avatar has been chosen for appears beneath the avatar. Click on an available avatar to select it." msgstr "" -#: ../../content/applications/hr/referrals.rst:439 -msgid "If more than one referral was hired since opening the Referrals application, after selecting the first avatar, the user is prompted to select another avatar for the subsequent hired referral. Once all avatars have been selected, the dashboard loads and all the avatars are now visible. Mouse over each avatar and their name is displayed above them." +#: ../../content/applications/hr/referrals.rst:118 +msgid "If more than one referral was hired since opening the *Referrals* application, after selecting the first avatar, the user is prompted to select another avatar for the subsequent hired referral. Once all avatars have been selected, the dashboard loads and all the avatars are now visible. Mouse over each avatar and their name is displayed above them." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 @@ -9234,185 +9490,188 @@ msgid "The hired screen. A selection of avatars are presented to chose from, wit "chosen are greyed out." msgstr "" -#: ../../content/applications/hr/referrals.rst:450 +#: ../../content/applications/hr/referrals.rst:129 msgid "Modify friends" msgstr "" -#: ../../content/applications/hr/referrals.rst:452 -msgid "Friend avatars are able to be modified in the same manner that :ref:`levels ` are modified. Only users with :guilabel:`Administrator` rights for the Recruitment application can make modifications to friends. The pre-configured friends can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Friends`. Each friend avatar appears in the :guilabel:`Dashboard Image` column, and the corresponding name appears in the :guilabel:`Friend Name` column. The default images are a motley group of hero characters, ranging from robots to dogs." +#: ../../content/applications/hr/referrals.rst:131 +msgid "Friend avatars are able to be modified in the same manner that :ref:`levels ` are modified. Only users with :guilabel:`Administrator` rights for the *Recruitment* application can make modifications to friends. The pre-configured friends can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Friends`. Each friend avatar appears in the :guilabel:`Dashboard Image` column, and the corresponding name appears in the :guilabel:`Friend Name` column. The default images are a motley group of hero characters, ranging from robots to dogs." msgstr "" -#: ../../content/applications/hr/referrals.rst:459 -msgid "To modify a friend's dashboard image, thumbnail, name, or position, click on an individual friend to open the referral friend form. Click :guilabel:`Edit` to make modifications. Type the name in the :guilabel:`Friend Name` field. The name is solely to differentiate the friends in the configuration menu; the friend's name is not visible anywhere else in the Referrals application." +#: ../../content/applications/hr/referrals.rst:138 +msgid "To modify a friend's dashboard image, thumbnail, name, or position, click on an individual friend to open the referral friend form. Click :guilabel:`Edit` to make modifications. Type the name in the :guilabel:`Friend Name` field. The name is solely to differentiate the friends in the configuration menu; the friend's name is not visible anywhere else in the *Referrals* application." msgstr "" -#: ../../content/applications/hr/referrals.rst:464 +#: ../../content/applications/hr/referrals.rst:143 msgid "The :guilabel:`Position` can be set to either :guilabel:`Front` or :guilabel:`Back`. This determines the position of the friend in relation to the user's super hero avatar. Click the radio button next to the desired selection, and the friend will appear either in front of or behind the user's avatar when activated." msgstr "" -#: ../../content/applications/hr/referrals.rst:469 -msgid "If desired, both the thumbnail :guilabel:`Image` and the :guilabel:`Dashboard Image` can be modified. Hover over the image being replaced to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file then click :guilabel:`Open` to select it." +#: ../../content/applications/hr/referrals.rst:148 +msgid "If desired, both the thumbnail :guilabel:`Image` and the :guilabel:`Dashboard Image` can be modified. Hover over the image being replaced to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon, and a file explorer window appears. Navigate to the desired image file, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/referrals.rst:474 -#: ../../content/applications/hr/referrals.rst:659 -msgid "Once all changes have been made, click the :guilabel:`Save` button to save the changes, or click the :guilabel:`Discard` button to revert to the original information." +#: ../../content/applications/hr/referrals.rst:153 +msgid "The referral friend form automatically saves, but can be saved manually at any time by clicking the *Save manually* option, represented by a :guilabel:`(cloud upload)` icon, located in the top-left corner. To cancel any changes made, click the :guilabel:`✖️ (Discard all changes)` icon to delete any changes, and revert to the original content." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 msgid "A friend form in edit mode." msgstr "" -#: ../../content/applications/hr/referrals.rst:482 -#: ../../content/applications/hr/referrals.rst:667 -msgid "It is not advised to edit the images. An image file must have a transparent background in order for it to render properly. Only users with knowledge about transparent images should attempt adjusting any images in the Referrals application." +#: ../../content/applications/hr/referrals.rst:163 +#: ../../content/applications/hr/referrals.rst:358 +msgid "It is not advised to edit the images. An image file must have a transparent background in order for it to render properly. Only users with knowledge about transparent images should attempt adjusting any images in the *Referrals* application." msgstr "" -#: ../../content/applications/hr/referrals.rst:486 -msgid "Once an image is changed and the friend is saved, it is **not possible** to revert to the original image. To revert to the original image, the Referrals application must be *uninstalled then reinstalled.*" +#: ../../content/applications/hr/referrals.rst:167 +msgid "Once an image is changed and the friend is saved, it is **not possible** to revert to the original image. To revert to the original image, the *Referrals* application must be *uninstalled then reinstalled.*" msgstr "" -#: ../../content/applications/hr/referrals.rst:491 +#: ../../content/applications/hr/referrals.rst:172 msgid "Referral points" msgstr "" -#: ../../content/applications/hr/referrals.rst:493 -msgid "The referral program is based on earning points that are then exchanged for rewards. On the main Referrals application dashboard, the top displays a summary of the user's current points. The left side of the summary displays the total points earned, and the right side displays the points that are available to spend." +#: ../../content/applications/hr/referrals.rst:174 +msgid "The referral program is based on earning points that are then exchanged for rewards. On the main *Referrals* application dashboard, the top displays a summary of the user's current points. The left side of the summary displays the total points earned, and the right side displays the points that are available to spend." msgstr "" -#: ../../content/applications/hr/referrals.rst:498 +#: ../../content/applications/hr/referrals.rst:179 msgid "To see the various referrals and the points earned for each, click on one of the buttons directly beneath the avatars. The options are :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." msgstr "" -#: ../../content/applications/hr/referrals.rst:502 +#: ../../content/applications/hr/referrals.rst:183 msgid "The current number of referrals who are still active in the recruitment pipeline, and have not yet been hired or refused, appear above the :guilabel:`Ongoing` button. The number of referrals who have been hired appear above the :guilabel:`Successful` button. The total number of referrals (both the ongoing and successful referrals combined) appear above the :guilabel:`Referrals` button." msgstr "" -#: ../../content/applications/hr/referrals.rst:508 +#: ../../content/applications/hr/referrals.rst:189 msgid "To view the referrals associated with each of the categories, :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`, click on the corresponding button. All the referrals for that specific category are displayed." msgstr "" -#: ../../content/applications/hr/referrals.rst:513 +#: ../../content/applications/hr/referrals.rst:194 msgid "My referrals" msgstr "" -#: ../../content/applications/hr/referrals.rst:515 +#: ../../content/applications/hr/referrals.rst:196 msgid "To see all the referrals (both ongoing and successful) click the :guilabel:`Referrals` button. A :guilabel:`My Referral` window loads. This screen displays all the referrals, with each referral in its own referral card." msgstr "" -#: ../../content/applications/hr/referrals.rst:519 -msgid "A successful referral has a green line down the left side of the card, and displays a :guilabel:`✓ Hired` image in the top right corner of the card. Referrals that are in process display an :guilabel:`In Progress` image in the top right corner." +#: ../../content/applications/hr/referrals.rst:200 +msgid "A successful referral displays a green :guilabel:`Hired` banner in the top-right corner of the card. Referrals that are in process display a purple :guilabel:`In Progress` banner in the top-right corner." msgstr "" -#: ../../content/applications/hr/referrals.rst:523 -msgid "Each referral card lists the name of the applicant, the department the job position is in, the name of the job position, the person responsible for filling the role (recruiter), and the points earned." +#: ../../content/applications/hr/referrals.rst:204 +msgid "Each referral card lists the name of the applicant, the subject/application title (as it appears on the applicant card in the *Recruitment* app), the name of the job position, the person responsible for filling the role (recruiter), and the points earned. For referrals that have been hired, the selected avatar also appears on the card." msgstr "" -#: ../../content/applications/hr/referrals.rst:527 +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:214 msgid "Points" msgstr "" -#: ../../content/applications/hr/referrals.rst:529 +#: ../../content/applications/hr/referrals.rst:216 msgid "The points that can be earned for a referral are the same across all job positions. Each stage of the recruitment process has corresponding points assigned to it. The stages listed correspond to the stages configured in the *Recruitment* application." msgstr "" -#: ../../content/applications/hr/referrals.rst:533 +#: ../../content/applications/hr/referrals.rst:220 msgid "On each individual referral card, beneath the points earned is a bar chart that displays how many points have been earned out of the total possible points that can be earned if the applicant is hired." msgstr "" -#: ../../content/applications/hr/referrals.rst:537 +#: ../../content/applications/hr/referrals.rst:224 msgid "Beneath the bar chart is a list of the various recruitment stages and the points earned when the referral moves to that stage. If a stage has been achieved and the points have been earned, a green check mark appears next to the stage." msgstr "" -#: ../../content/applications/hr/referrals.rst:542 +#: ../../content/applications/hr/referrals.rst:229 msgid "The pre-configured point structure for referrals is as follows:" msgstr "" -#: ../../content/applications/hr/referrals.rst:544 +#: ../../content/applications/hr/referrals.rst:231 msgid ":guilabel:`Initial Qualification`: 1 point" msgstr "" -#: ../../content/applications/hr/referrals.rst:545 +#: ../../content/applications/hr/referrals.rst:232 msgid ":guilabel:`First Interview`: 20 points" msgstr "" -#: ../../content/applications/hr/referrals.rst:546 +#: ../../content/applications/hr/referrals.rst:233 msgid ":guilabel:`Second Interview`: 9 points" msgstr "" -#: ../../content/applications/hr/referrals.rst:547 +#: ../../content/applications/hr/referrals.rst:234 msgid ":guilabel:`Contract Proposal`: 5 points" msgstr "" -#: ../../content/applications/hr/referrals.rst:548 +#: ../../content/applications/hr/referrals.rst:235 msgid ":guilabel:`Contract Signed`: 50 points" msgstr "" -#: ../../content/applications/hr/referrals.rst:550 -msgid "The total points earned for a referral that is hired is 85 points. Modifications of the points earned for each stage is done in the Recruitment application. Refer to the :ref:`Recruitment ` documentation to modify the points for each stage." +#: ../../content/applications/hr/referrals.rst:237 +msgid "The total points earned for a referral that is hired is 85 points. Modifications of the points earned for each stage are done in the *Recruitment* application. Refer to the :ref:`Recruitment ` documentation to modify the points for each stage." msgstr "" -#: ../../content/applications/hr/referrals.rst:557 +#: ../../content/applications/hr/referrals.rst:244 msgid "Rewards" msgstr "" -#: ../../content/applications/hr/referrals.rst:560 +#: ../../content/applications/hr/referrals.rst:247 msgid "Create rewards" msgstr "" -#: ../../content/applications/hr/referrals.rst:562 -msgid "The rewards are the only configurations needed when setting up the Referrals application. Only users with :guilabel:`Administrator` rights for the Recruitment application can create or modify rewards. To add rewards, navigate to :menuselection:`Referrals app --> Configuration --> Rewards`. Click :guilabel:`Create` and a reward form loads. Enter the following information on the form:" +#: ../../content/applications/hr/referrals.rst:249 +msgid "The rewards are the only configurations needed when setting up the *Referrals* application. Only users with :guilabel:`Administrator` rights for the *Recruitment* application can create or modify rewards. To add rewards, navigate to :menuselection:`Referrals app --> Configuration --> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/referrals.rst:567 -msgid ":guilabel:`Product Name`: Enter the name as it should appear for the reward." +#: ../../content/applications/hr/referrals.rst:254 +msgid ":guilabel:`Product Name`: enter the name as it should appear for the reward." msgstr "" -#: ../../content/applications/hr/referrals.rst:568 -msgid ":guilabel:`Cost`: Enter the amount of points required to redeem the reward." +#: ../../content/applications/hr/referrals.rst:255 +msgid ":guilabel:`Cost`: enter the amount of points required to redeem the reward." msgstr "" -#: ../../content/applications/hr/referrals.rst:569 -msgid ":guilabel:`Company`: Using the drop-down menu, select the company the reward will appear for. If a reward is to be used for several companies, each company needs to have a record of the reward, with the company listed on the form." +#: ../../content/applications/hr/referrals.rst:256 +msgid ":guilabel:`Company`: using the drop-down menu, select the company the reward appears for. If a reward is to be used for several companies, each company needs to have a record of the reward, with the company listed on the form. This field only appears if in a multi-company environment." msgstr "" -#: ../../content/applications/hr/referrals.rst:572 -msgid ":guilabel:`Gift Responsible`: Select the person who will be responsible for procuring and delivering the reward to the recipient, using the drop-down menu. This person is alerted when the reward is purchased, so they know when to deliver the reward to the recipient." +#: ../../content/applications/hr/referrals.rst:259 +msgid ":guilabel:`Gift Responsible`: select the person who will be responsible for procuring and delivering the reward to the recipient, using the drop-down menu. This person is alerted when the reward is bought in the *Referrals* application, so they know when to deliver the reward to the recipient." msgstr "" -#: ../../content/applications/hr/referrals.rst:575 -msgid ":guilabel:`Description`: Type in the description for the reward. This will be visible on the reward card, beneath the title." +#: ../../content/applications/hr/referrals.rst:263 +msgid ":guilabel:`Description`: type in the description for the reward. This will be visible on the reward card, beneath the title." msgstr "" -#: ../../content/applications/hr/referrals.rst:577 -msgid ":guilabel:`Photo`: Add a photo of the reward, which appears on the rewards page. Hover over the image square, and two icons appear, a :guilabel:`✏️ (pencil)` and a :guilabel:`🗑️ (garbage can)`. Click the :guilabel:`✏️ (pencil)` icon and a file explorer appears. Navigate to the photo file, then click :guilabel:`Open` to select it." +#: ../../content/applications/hr/referrals.rst:265 +msgid ":guilabel:`Photo`: add a photo of the reward, which appears on the rewards page. Hover over the image square, and two icons appear, a :guilabel:`✏️ (pencil)` and a :guilabel:`🗑️ (garbage can)`. Click the :guilabel:`✏️ (pencil)` icon, and a file explorer appears. Navigate to the photo file, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/referrals.rst:582 -msgid "The only required fields are the :guilabel:`Product Name`, :guilabel:`Company`, and :guilabel:`Description`." +#: ../../content/applications/hr/referrals.rst:270 +msgid "The only required fields are the :guilabel:`Product Name`, :guilabel:`Company` (if applicable), and :guilabel:`Description`." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 msgid "A filled out reward form with all details entered." msgstr "" -#: ../../content/applications/hr/referrals.rst:590 +#: ../../content/applications/hr/referrals.rst:278 msgid "It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a cost is not entered, the default cost will be listed as zero, which would list the reward as free in the reward shop. If a photo is not selected, a placeholder icon will be displayed on the rewards page." msgstr "" -#: ../../content/applications/hr/referrals.rst:595 +#: ../../content/applications/hr/referrals.rst:283 msgid "Redeem rewards" msgstr "" -#: ../../content/applications/hr/referrals.rst:597 -msgid "To redeem points for a reward, click the :guilabel:`Rewards` button on the main Referrals dashboard. All the configured rewards are listed in individual reward cards. The points required to purchase the reward is listed in the top right corner of the card. If the user has enough points to purchase a reward, a :guilabel:`🧺 (basket) Buy` button appears at the bottom of the reward card. If they do not have enough points for a reward, the reward card displays :guilabel:`You need another (x) points to buy this` instead of a buy button." +#: ../../content/applications/hr/referrals.rst:285 +msgid "To redeem points for a reward, click the :guilabel:`Rewards` button on the main Referrals dashboard. All the configured rewards are listed in individual reward cards. The points required to purchase the reward is listed in the top-right corner of the card. If the user has enough points to purchase a reward, a :guilabel:`🧺 (basket) Buy` button appears at the bottom of the reward card. If they do not have enough points for a reward, the reward card displays :guilabel:`You need another (x) points to buy this` instead of a buy button." msgstr "" -#: ../../content/applications/hr/referrals.rst:604 -msgid "Click the :guilabel:`🧺 (basket) Buy` button on a reward to purchase it. A confirmation pop-up appears, asking if the user is sure they want to purchase the reward. Click :guilabel:`OK` to purchase the item, or :guilabel:`Cancel` to close the window and cancel the purchase." +#: ../../content/applications/hr/referrals.rst:292 +msgid "Click the :guilabel:`🧺 (basket) Buy` button on a reward to purchase it. A :guilabel:`Confirmation` pop-up window appears, asking if the user is sure they want to purchase the reward. Click :guilabel:`OK` to purchase the item, or :guilabel:`Cancel` to close the window and cancel the purchase." msgstr "" -#: ../../content/applications/hr/referrals.rst:608 +#: ../../content/applications/hr/referrals.rst:297 msgid "After :guilabel:`OK` is clicked, the pop-up window closes, and the points used to purchase the reward are subtracted from the user's available points. The rewards presented are now updated to reflect the user's current available points." msgstr "" @@ -9421,63 +9680,67 @@ msgid "Buy button appears below a mug and backpack reward, while the bicycle rew "many more reward points are needed to redeem." msgstr "" -#: ../../content/applications/hr/referrals.rst:620 +#: ../../content/applications/hr/referrals.rst:309 msgid "Levels" msgstr "" -#: ../../content/applications/hr/referrals.rst:622 -msgid "The referrals application has pre-configured levels that are reflected in the user's avatar on the Referrals dashboard. As a user refers potential employees and earns points, they can *level up*, much like in a video game." +#: ../../content/applications/hr/referrals.rst:311 +msgid "The *Referrals* application has pre-configured levels that are reflected in the user's avatar on the Referrals dashboard. As a user refers potential employees and earns points, they can *level up*, much like in a video game." msgstr "" -#: ../../content/applications/hr/referrals.rst:626 +#: ../../content/applications/hr/referrals.rst:315 msgid "Levels have no functional impact on the performance of the application. They are solely used for the purpose of adding achievement tiers for participants to aim for, gamifying referrals for the user." msgstr "" -#: ../../content/applications/hr/referrals.rst:629 -msgid "The user's current level is displayed at the top of the main Referrals application dashboard, directly beneath their photo, in a :guilabel:`Level: X` format. In addition, a colored ring appears around the user's photo, indicating how many points the user currently has, and how many additional points they need to level up. The cyan colored portion of the ring represents points earned, while the white colored portion represents the points still needed before they can level up." +#: ../../content/applications/hr/referrals.rst:318 +msgid "The user's current level is displayed at the top of the main *Referrals* application dashboard, directly beneath their photo, in a :guilabel:`Level: X` format. In addition, a colored ring appears around the user's photo, indicating how many points the user currently has, and how many additional points they need to level up. The cyan colored portion of the ring represents points earned, while the white colored portion represents the points still needed before they can level up." msgstr "" -#: ../../content/applications/hr/referrals.rst:636 +#: ../../content/applications/hr/referrals.rst:325 msgid "Modify levels" msgstr "" -#: ../../content/applications/hr/referrals.rst:638 -msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application can modify levels. The pre-configured levels can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Levels`. Each avatar appears in the :guilabel:`Image` column, and the corresponding level number appears in the :guilabel:`Level Name` column. The default images are of Odoo superheroes, and each level adds an additional element to their avatar, such as capes and shields." +#: ../../content/applications/hr/referrals.rst:327 +msgid "Only users with :guilabel:`Administrator` rights for the *Recruitment* application can modify levels. The pre-configured levels can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Levels`. Each avatar appears in the :guilabel:`Image` column, and the corresponding level number appears in the :guilabel:`Level Name` column. The default images are of Odoo superheroes, and each level adds an additional element to their avatar, such as capes and shields." msgstr "" -#: ../../content/applications/hr/referrals.rst:645 -msgid "To modify a level's image, name, or points required to reach the level, click on an individual level in the list to open the level form. Click :guilabel:`Edit` to make modifications." +#: ../../content/applications/hr/referrals.rst:334 +msgid "To modify a level's image, name, or points required to reach the level, click on an individual level in the list to open the level form, then make modifications." msgstr "" -#: ../../content/applications/hr/referrals.rst:648 -msgid "Type in the name or number of the level in the :guilabel:`Level Name` field. What is entered is displayed beneath the user's photo on the main dashboard when they reach that level. Enter the number of referral points needed to reach that level in the :guilabel:`Requirements` field. The points needed to level up are the total accumulated points earned over the lifetime of the employee, not additional points from the previous level that must be earned." +#: ../../content/applications/hr/referrals.rst:337 +msgid "Type in the name (or number) of the level in the :guilabel:`Level Name` field. What is entered is displayed beneath the user's photo on the main dashboard when they reach that level. Enter the number of referral points needed to reach that level in the :guilabel:`Requirements` field. The points needed to level up are the total accumulated points earned over the lifetime of the employee, not additional points from the previous level that must be earned." msgstr "" -#: ../../content/applications/hr/referrals.rst:654 -msgid "If desired, the :guilabel:`Image` can also be modified. Hover over the image to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file then click :guilabel:`Open` to select it." +#: ../../content/applications/hr/referrals.rst:343 +msgid "If desired, the :guilabel:`Image` can also be modified. Hover over the image to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon, and a file explorer window appears. Navigate to the desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:348 +msgid "The level form saves automatically, but can be saved manually at any time by clicking the *save manually* option, represented by a :guilabel:`(cloud upload)` icon, located in the top-left corner. To cancel any changes made, click the :guilabel:`✖️ (Discard all changes)` icon to delete any changes, and revert to the original content." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 msgid "A level form in edit mode." msgstr "" -#: ../../content/applications/hr/referrals.rst:671 -msgid "Once an image is changed and the level is saved, it is **not possible** to revert to the original image. To revert to the original image, the Referrals application must be *uninstalled then reinstalled.*" +#: ../../content/applications/hr/referrals.rst:362 +msgid "Once an image is changed and the level is saved, it is **not possible** to revert to the original image. To revert to the original image, the *Referrals* application must be *uninstalled then reinstalled.*" msgstr "" -#: ../../content/applications/hr/referrals.rst:676 +#: ../../content/applications/hr/referrals.rst:367 msgid "Level up" msgstr "" -#: ../../content/applications/hr/referrals.rst:678 +#: ../../content/applications/hr/referrals.rst:369 msgid "Once enough points have been accumulated to level up, the circle around the user's photo is completely filled in with a cyan color, a large image stating :guilabel:`Level up!` appears above the photo, and the phrase :guilabel:`Click to level up!` appears beneath the user's photo and current level." msgstr "" -#: ../../content/applications/hr/referrals.rst:683 +#: ../../content/applications/hr/referrals.rst:374 msgid "Click on either the :guilabel:`LEVEL UP!` graphic, the user's photo, or the text :guilabel:`Click to level up!` beneath the user's photo to level up the user. The user's avatar changes to the current level, and the ring around the photo is updated to indicate the current amount of points." msgstr "" -#: ../../content/applications/hr/referrals.rst:687 +#: ../../content/applications/hr/referrals.rst:378 msgid "Leveling up does not cost the user any points, the user simply needs to earn the specified amount of points required." msgstr "" @@ -9486,275 +9749,472 @@ msgid "A 'Click to level up!' appears beneath the user's image, and a large 'Lev "above their image." msgstr "" -#: ../../content/applications/hr/referrals.rst:696 +#: ../../content/applications/hr/referrals.rst:387 msgid "Once a user has reached the highest configured level, they will continue to accrue points that can be redeemed for rewards, but they are no longer able to level up. The ring around their photo remains solid cyan." msgstr "" -#: ../../content/applications/hr/referrals.rst:703 -msgid "In the Referrals application, it is possible to post a message, also referred to as an *alert*, at the top of the dashboard to share important information with users. These alerts appear as a thin semi-transparent banner, with the word :guilabel:`New!` appearing on the far left. The text for the alert is in the center of the banner, and on the far right side is an :guilabel:`X`." +#: ../../content/applications/hr/referrals.rst:394 +msgid "In the *Referrals* application, it is possible to post a message, also referred to as an *alert*, at the top of the dashboard to share important information with users. These alerts appear as a thin semi-transparent banner, with the word :guilabel:`New!` appearing on the far left. The text for the alert is in the center of the banner, and on the far right side is an :guilabel:`X`." msgstr "" -#: ../../content/applications/hr/referrals.rst:708 -msgid "Alerts appear on the main dashboard for the specified time configured on the individual alert. If a user does not wish to see a specific alert again, click the :guilabel:`X` in the far right side of the alert. This removes the alert from the dashboard and will not appear again, even when opening the Referrals application for the first time in a new session." +#: ../../content/applications/hr/referrals.rst:399 +msgid "Alerts appear on the main dashboard for the specified time configured on the individual alert. If a user does not wish to see a specific alert again, click the :guilabel:`X` in the far right side of the alert. This removes the alert from the dashboard and will not appear again, even when opening the *Referrals* application for the first time in a new session." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 msgid "Two alert banners appear above the user's photo." msgstr "" -#: ../../content/applications/hr/referrals.rst:718 +#: ../../content/applications/hr/referrals.rst:409 msgid "Create an alert" msgstr "" -#: ../../content/applications/hr/referrals.rst:720 -msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application can create alerts. To add a new alert, navigate to the :menuselection:`Referrals application --> Configuration --> Alerts`." +#: ../../content/applications/hr/referrals.rst:411 +msgid "Only users with :guilabel:`Administrator` rights for the *Recruitment* application can create alerts. To add a new alert, navigate to the :menuselection:`Referrals application --> Configuration --> Alerts`." msgstr "" -#: ../../content/applications/hr/referrals.rst:724 +#: ../../content/applications/hr/referrals.rst:415 msgid "Click :guilabel:`Create` and a blank alert form loads. Enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/referrals.rst:726 -msgid ":guilabel:`Date From`: The date the alert starts. On this date, the alert will be visible on the dashboard." +#: ../../content/applications/hr/referrals.rst:417 +msgid ":guilabel:`Date From`: the date the alert starts. On this date, the alert will be visible on the dashboard." msgstr "" -#: ../../content/applications/hr/referrals.rst:728 -msgid ":guilabel:`Date To`: The date the alert ends. After this date, the alert will be hidden from view." +#: ../../content/applications/hr/referrals.rst:419 +msgid ":guilabel:`Date To`: the date the alert ends. After this date, the alert will be hidden from view." msgstr "" -#: ../../content/applications/hr/referrals.rst:729 -msgid ":guilabel:`Company`: The current company populates this field by default. To modify the company the alert should be displayed for, select the company from the drop-down menu. If this field remains blank, the alert is visible to everyone with access to the Referrals application. If a company is specified, only user's within that company (who also have access to the Referrals application) will see the alert." +#: ../../content/applications/hr/referrals.rst:420 +msgid ":guilabel:`Company`: the current company populates this field by default. To modify the company the alert should be displayed for, select the company from the drop-down menu. If this field remains blank, the alert is visible to everyone with access to the *Referrals* application. If a company is specified, only user's within that company (who also have access to the *Referrals* application) will see the alert. This field only appears when in a multi-company database." msgstr "" -#: ../../content/applications/hr/referrals.rst:734 -msgid ":guilabel:`Alert`: Enter the text for the alert. This message appears inside the alert banner on the main dashboard." +#: ../../content/applications/hr/referrals.rst:425 +msgid ":guilabel:`Alert`: enter the text for the alert. This message appears inside the alert banner on the main dashboard." msgstr "" -#: ../../content/applications/hr/referrals.rst:736 -msgid ":guilabel:`On Click`: There are three options for the alert. Click the radio button next to the desired selection. The options are:" +#: ../../content/applications/hr/referrals.rst:427 +msgid ":guilabel:`On Click`: there are three options for the alert. Click the radio button next to the desired selection. The options are:" msgstr "" -#: ../../content/applications/hr/referrals.rst:739 -msgid ":guilabel:`Not Clickable`: The alert only displays text, there is no link to click." +#: ../../content/applications/hr/referrals.rst:430 +msgid ":guilabel:`Not Clickable`: the alert only displays text, there is no link to click." msgstr "" -#: ../../content/applications/hr/referrals.rst:740 -msgid ":guilabel:`Go to All Jobs`: The alert contains a link that when clicked, navigates to the website with all the currently posted job positions." +#: ../../content/applications/hr/referrals.rst:431 +msgid ":guilabel:`Go to All Jobs`: the alert contains a link that when clicked, navigates to the website with all the currently posted job positions." msgstr "" -#: ../../content/applications/hr/referrals.rst:742 -msgid ":guilabel:`Specify URL`: The alert contains a link to a specific URL, that when clicked, navigates to that URL. When selected, a :guilabel:`URL` field appears below the :guilabel:`On Click` section. Enter the URL in the field." +#: ../../content/applications/hr/referrals.rst:433 +msgid ":guilabel:`Specify URL`: the alert contains a link to a specific URL, that when clicked, navigates to that URL. When selected, a :guilabel:`URL` field appears below the :guilabel:`On Click` section. Enter the URL in the field." msgstr "" #: ../../content/applications/hr/referrals.rst:-1 msgid "An alert form completely filled in with all selections entered." msgstr "" -#: ../../content/applications/hr/referrals.rst:755 -msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application have access to the Reporting feature in Referrals. To access the reports, click :menuselection:`Referrals application --> Reporting`. The main view is the Reporting Dashboard view, which contains three sections." +#: ../../content/applications/hr/referrals.rst:446 +msgid "Only users with :guilabel:`Administrator` rights for the *Recruitment* application have access to the Reporting feature in *Referrals*. To access the reports, click :menuselection:`Referrals application --> Reporting`. The main view is the Reporting Dashboard view, which contains three sections." msgstr "" -#: ../../content/applications/hr/referrals.rst:759 +#: ../../content/applications/hr/referrals.rst:451 msgid "In the top portion of the window, the report displays a bar chart of how many referred candidates are hired, and how many are still in the hiring pipeline. The candidates are further divided by channel, showing specifically where the referral came from, such as a direct referral, Facebook, etc. If a channel does not appear on the report, that indicates there are no referrals from that particular channel." msgstr "" -#: ../../content/applications/hr/referrals.rst:765 +#: ../../content/applications/hr/referrals.rst:457 msgid "The middle third provides all the specific data that has been tracked. This includes how many total points have been earned across all referrals, how many applicants were referred, hired, or refused, how many applicants the current logged-in user referred, how many total points were earned, and how many points were given for refused applicants." msgstr "" -#: ../../content/applications/hr/referrals.rst:770 +#: ../../content/applications/hr/referrals.rst:462 msgid "The bottom third displays a pivot table. This table can be inserted into a new or existing spreadsheet. To do so, click the :guilabel:`Insert in Spreadsheet` button right above the chart. A pop-up appears, asking which spreadsheet to insert the pivot chart into. Select the desired spreadsheet from the drop-down menu, or select :guilabel:`New Spreadsheet`. Click :guilabel:`Confirm` and the selected spreadsheet loads, with the new table in it." msgstr "" -#: ../../content/applications/hr/referrals.rst:777 -msgid "The spreadsheet is stored in the *Documents* application. This application needs to be installed in order to use the :guilabel:`Insert in Spreadsheet` option." +#: ../../content/applications/hr/referrals.rst:469 +msgid "The spreadsheet is stored in the *Documents* application. This application needs to be installed to use the :guilabel:`Insert in Spreadsheet` option." msgstr "" -#: ../../content/applications/hr/time_off.rst:3 -msgid "Time Off" +#: ../../content/applications/hr/referrals.rst:473 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "In Odoo *Referrals*, users can earn referral points by sharing job positions with potential applicants. Job positions can be shared in several ways, through the :ref:`View Jobs ` button and the :ref:`Email A Friend ` button, located at the bottom of the *Referrals* app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:11 +msgid "Sharing jobs can **only** occur after onboarding slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:16 +msgid "View Jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:18 +msgid "To see all job positions that are actively recruiting candidates, click the :guilabel:`View Jobs` button on the main *Referrals* dashboard. This presents all job positions, with each individual job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "The 'View Jobs' screen, displaying all current open job positions. All information is\n" +"displayed on the card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:27 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:29 +msgid "The title of the job position. This information is taken from the *Job Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:31 +msgid "The number of :guilabel:`Open Positions` being recruited. This information is taken from the *Expected New Employees* field of the *Recruitment* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:33 +msgid "The points a user earns when an applicant applies for the position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "The job description detailing the job position. This information is taken from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "To see all the details for a job position, click the :guilabel:`More Info` button on the specific card. This opens the job position webpage in a new browser tab. This is what an applicant sees before applying for a position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:42 +msgid "Only published job positions are visible in the *Referrals* app. To check which job positions are published or not, refer to the :doc:`../recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:46 +msgid "Refer friends" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:48 +msgid "To share a job position with someone, click the :guilabel:`Refer Friend` button on the specific job position card. A pre-configured :guilabel:`Send Job Offer by Mail` pop-up window appears. Enter the recipient's email address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:52 +msgid "The :guilabel:`Subject` and :guilabel:`Body` are populated using a default template. The :guilabel:`Subject` `Job for you` is present, by default, but can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:55 +msgid "The specific title of the job position populates the *Job Position* placeholder in the email body. The `See Job Offer` text in the email body is an individualized tracking link to the specific job position listed on the website." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:59 +msgid "When the prospective employee receives the email, the link sends them to the job position page, where they can apply for the position, and the person who referred them is tracked in the *Referrals* application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:63 +msgid "If desired, add any text or closing salutation to the email body. When all edits have been made, click :guilabel:`Send Mail` to send the email, or click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "Share a job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:74 +msgid "Other than sending an email, job positions can be shared, via social media platforms, and by tracking links to the job position. At the bottom of each job position card are four icons, and corresponding tracking links, that can be used to share the job position, keeping track of applicants in the *Referrals* application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "The various sharing icons that appear for each job." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "Link" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:86 +msgid "To share the job position with a customized tracking link, click the :guilabel:`Share Now` button with the :icon:`fa-chain` :guilabel:`(link)` icon above it. A :guilabel:`Link to Share` pop-up window appears with the tracking link. Click :guilabel:`Copy` to copy the link. After the link is copied, click the :guilabel:`Close` button to close the pop-up window. Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:93 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:95 +msgid "To share the job position using Facebook, click the :guilabel:`Share Now` button with the :icon:`fa-facebook` :guilabel:`(Facebook)` icon above it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:98 +msgid "If the user is already logged into Facebook, when the the :guilabel:`Share Now` button is clicked, a :guilabel:`Share on Facebook` page loads in a new tab, with the link populated in the main body of the new post in a pop-up window. If the user is *not* already logged in, a log-in screen loads, instead, prompting the user to log-in to Facebook first." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "Type in any additional information to add to the post, then share the job position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:107 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:109 +msgid "A job position can also be shared on X. Click the :guilabel:`Share Now` button with the :guilabel:`(X)` icon above it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "If the user is already signed-in to X, when the :guilabel:`Share Now` button is clicked, an X page loads in a new tab with a pre-populated message ready to post, in a draft pop-up window. If the user is *not* already signed-in, a sign-in screen loads instead, prompting the user to first sign-in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:117 +msgid "The default message is:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:119 +msgid "`Amazing job offer for (Job Position)! Check it live: (link to Job Position)`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:121 +msgid "Type in any additional information, or make any edits to the message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:125 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "To share a job position on LinkedIn, click the :guilabel:`Share Now` button with the :icon:`fa-linkedin` :guilabel:`(LinkedIn)` icon above it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:130 +msgid "If the user is already logged into LinkedIn, when the :guilabel:`Share Now` button is clicked, a new tab loads in LinkedIn, with a link to the job position at the top. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to LinkedIn first." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:134 +msgid "The job position can be shared either in a public post, or in a private message to an individual (or group of individuals)." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:137 +msgid "Type in any additional information, or make any edits to the message or post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:143 +msgid "Email a friend" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:145 +msgid "Another way to share job opportunities is to share the entire current list of open job positions, instead of one job position at a time. To do this, navigate to the :menuselection:`Referrals` main dashboard. Click the :guilabel:`Email a friend` button at the bottom of the screen. A :guilabel:`Send Job Offer by Mail` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:150 +msgid "Enter the email address in the :guilabel:`Email` field. The email can be sent to multiple recipients by separating each email address with a comma followed by a single space. The :guilabel:`Subject` is pre-configured with :guilabel:`Job for you`, but can be edited." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:154 +msgid "The email :guilabel:`Body` is also populated with pre-configured text. The text that appears is:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "`Hello,`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:158 +msgid "`There are some amazing job offers in my company! Have a look, they can be interesting for you\\:`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "`See Job Offers`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:162 +msgid "The :guilabel:`See Job Offers` text is a tracking link to a complete list of all job positions currently being recruited for. Add any additional text and make any edits to the message body, if necessary. Then, click :guilabel:`Send Mail` to send the email. This sends the message, and closes the window." msgstr "" #: ../../content/applications/hr/time_off.rst:5 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 msgid "Odoo's *Time Off* application serves as a centralized hub for all time-off-related information. This application manages requests, balances, allocations, approvals, and reports." msgstr "" -#: ../../content/applications/hr/time_off.rst:8 -msgid "Users can :ref:`request time off `, and see an overview of their requests and time off balances. Managers can :ref:`allocate time off ` to individuals, teams, or the whole company, and :ref:`approve time off requests `." +#: ../../content/applications/hr/time_off.rst:10 +msgid "Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see an overview of their requests and time off balances. Managers can :ref:`allocate time off ` to individuals, teams, or the whole company, and :ref:`approve time off requests `." msgstr "" -#: ../../content/applications/hr/time_off.rst:12 +#: ../../content/applications/hr/time_off.rst:15 msgid "Detailed :ref:`reports ` can be run to see how much time off (and what kinds of time off) are being used, :ref:`accrual plans ` can be created, and :ref:`public holidays ` can be set." msgstr "" -#: ../../content/applications/hr/time_off.rst:17 +#: ../../content/applications/hr/time_off.rst:20 msgid "Be advised, only users with specific access rights can see all aspects of the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:20 +#: ../../content/applications/hr/time_off.rst:23 msgid "All users can access the :guilabel:`My Time Off` and :guilabel:`Overview` sections of the *Time Off* application. All other sections require specific access rights." msgstr "" -#: ../../content/applications/hr/time_off.rst:23 +#: ../../content/applications/hr/time_off.rst:26 msgid "To better understand how access rights affect the *Time Off* application, refer to the :doc:`employees/new_employee` document, specifically the section about configuring the work information tab." msgstr "" -#: ../../content/applications/hr/time_off.rst:30 +#: ../../content/applications/hr/time_off.rst:33 msgid "In order to allocate time off to employees, and for employees to request and use their time off, the various time off types must be configured first, then allocated to employees (if allocation is required)." msgstr "" -#: ../../content/applications/hr/time_off.rst:37 +#: ../../content/applications/hr/time_off.rst:40 msgid "Time off types" msgstr "" -#: ../../content/applications/hr/time_off.rst:39 +#: ../../content/applications/hr/time_off.rst:42 msgid "To view the currently configured time off types, navigate to :menuselection:`Time Off app --> Configuration --> Time Off Types`. The time off types are presented in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:42 +#: ../../content/applications/hr/time_off.rst:45 msgid "The *Time Off* application comes with four pre-configured time off types: :guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, and :guilabel:`Compensatory Days`. These can be modified to suit business needs or used as-is." msgstr "" -#: ../../content/applications/hr/time_off.rst:47 +#: ../../content/applications/hr/time_off.rst:50 msgid "Create time off type" msgstr "" -#: ../../content/applications/hr/time_off.rst:49 +#: ../../content/applications/hr/time_off.rst:52 msgid "To create a new time off type, navigate to :menuselection:`Time Off app --> Configuration --> Time Off Types`. From here, click the :guilabel:`New` button to reveal a blank time off type form." msgstr "" -#: ../../content/applications/hr/time_off.rst:52 +#: ../../content/applications/hr/time_off.rst:55 msgid "Enter the name for the particular type of time off in the blank line at the top of the form, such as `Sick Time` or `Vacation`. Then, enter the following information on the form." msgstr "" -#: ../../content/applications/hr/time_off.rst:56 +#: ../../content/applications/hr/time_off.rst:59 msgid "The only **required** fields on the time off type form are the name of the :guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the :guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests` and :guilabel:`Allocation Requests` sections **must** be configured." msgstr "" -#: ../../content/applications/hr/time_off.rst:62 +#: ../../content/applications/hr/time_off.rst:65 msgid "Time Off Requests section" msgstr "" -#: ../../content/applications/hr/time_off.rst:64 +#: ../../content/applications/hr/time_off.rst:67 msgid ":guilabel:`Approval`: select what specific kind of approval is required for the time off type. The options are:" msgstr "" -#: ../../content/applications/hr/time_off.rst:67 +#: ../../content/applications/hr/time_off.rst:70 msgid ":guilabel:`No Validation`: no approvals are required when requesting this type of time off. The time off request is automatically approved." msgstr "" -#: ../../content/applications/hr/time_off.rst:69 +#: ../../content/applications/hr/time_off.rst:72 msgid ":guilabel:`By Time Off Officer`: only the specified :ref:`Time Off Officer `, set on this form in the :guilabel:`Notified Time Off Officer` field, is required to approve the time off request. This option is selected by default." msgstr "" -#: ../../content/applications/hr/time_off.rst:72 +#: ../../content/applications/hr/time_off.rst:75 msgid ":guilabel:`By Employee's Approver`: only the employee's specified approver for time off, which is set on the *Work Information* tab on the :ref:`employee's form `, is required to approve the time off request." msgstr "" -#: ../../content/applications/hr/time_off.rst:75 +#: ../../content/applications/hr/time_off.rst:78 msgid ":guilabel:`By Employee's Approver and Time Off Officer`: both the employee's :ref:`specified time off approver` and the :ref:`Time Off Officer ` are required to approve the time off request." msgstr "" -#: ../../content/applications/hr/time_off.rst:80 +#: ../../content/applications/hr/time_off.rst:83 msgid "Allocation Requests section" msgstr "" -#: ../../content/applications/hr/time_off.rst:82 +#: ../../content/applications/hr/time_off.rst:85 msgid ":guilabel:`Requires allocation`: if the time off must be allocated to employees, select :guilabel:`Yes`. If the time off can be requested without time off being previously allocated, select :guilabel:`No Limit`. If :guilabel:`No Limit` is selected, the following options do not appear on the form." msgstr "" -#: ../../content/applications/hr/time_off.rst:86 +#: ../../content/applications/hr/time_off.rst:89 msgid ":guilabel:`Employee Requests`: select :guilabel:`Extra Days Requests Allowed` if the employee is able to request more time off than was allocated." msgstr "" -#: ../../content/applications/hr/time_off.rst:89 +#: ../../content/applications/hr/time_off.rst:92 msgid "If employees should **not** be able to make requests for more time off than what was allocated, select the :guilabel:`Not Allowed` option." msgstr "" -#: ../../content/applications/hr/time_off.rst:93 +#: ../../content/applications/hr/time_off.rst:96 msgid "Ten days are allocated to the employee for this particular type of time off, and the :guilabel:`Extra Days Requests Allowed` option is enabled. The employee wants to take a vacation for twelve days. They may submit a request for two additional days, since the :guilabel:`Extra Days Requests Allowed` option is enabled." msgstr "" -#: ../../content/applications/hr/time_off.rst:99 +#: ../../content/applications/hr/time_off.rst:102 msgid "It is important to note that requesting additional time off does **not** guarantee that time off is granted." msgstr "" -#: ../../content/applications/hr/time_off.rst:102 +#: ../../content/applications/hr/time_off.rst:105 msgid ":guilabel:`Approval`: select the type of approvals required for the allocation of this particular time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:105 +#: ../../content/applications/hr/time_off.rst:108 msgid ":guilabel:`Approved by Time Off Officer` indicates the :ref:`Time Off Officer ` set on this form must approve the allocation." msgstr "" -#: ../../content/applications/hr/time_off.rst:107 +#: ../../content/applications/hr/time_off.rst:110 msgid ":guilabel:`No validation needed` indicates that no approvals are required." msgstr "" -#: ../../content/applications/hr/time_off.rst:110 +#: ../../content/applications/hr/time_off.rst:113 msgid "Configuration section" msgstr "" -#: ../../content/applications/hr/time_off.rst:114 +#: ../../content/applications/hr/time_off.rst:117 msgid ":guilabel:`Notified Time Off Officer`: select the person who is notified and responsible for approving requests and allocations for this specific type of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:116 +#: ../../content/applications/hr/time_off.rst:119 msgid ":guilabel:`Take Time Off in`: select the format the time off is requested in from the drop-down menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:119 +#: ../../content/applications/hr/time_off.rst:122 msgid "The options are:" msgstr "" -#: ../../content/applications/hr/time_off.rst:121 +#: ../../content/applications/hr/time_off.rst:124 msgid ":guilabel:`Day`: if time off can only be requested in full day increments (8 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:122 +#: ../../content/applications/hr/time_off.rst:125 msgid ":guilabel:`Half Day`: if time off can only be requested in half day increments (4 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:123 +#: ../../content/applications/hr/time_off.rst:126 msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." msgstr "" -#: ../../content/applications/hr/time_off.rst:127 +#: ../../content/applications/hr/time_off.rst:130 msgid ":guilabel:`Deduct Extra Hours`: enable this option if the time off request should factor in any extra time accrued by the employee" msgstr "" -#: ../../content/applications/hr/time_off.rst:131 +#: ../../content/applications/hr/time_off.rst:134 msgid "If an employee works two extra hours for the week, and requests five hours of time off, the request would be for three hours, since the two extra worked hours are used first, and deducted from the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:135 +#: ../../content/applications/hr/time_off.rst:138 msgid ":guilabel:`Allow To Attach Supporting Document`: enable this option to allow the employee to attach documents to the time off request. This is useful in situations where documentation is required, such as long-term medical leave." msgstr "" -#: ../../content/applications/hr/time_off.rst:138 +#: ../../content/applications/hr/time_off.rst:141 msgid ":guilabel:`Kind of Time Off`: select from the drop-down menu the type of time off this is, either :guilabel:`Worked Time` or :guilabel:`Absence`. :guilabel:`Worked Time` indicates that the time off taken counts toward worked time for any type of accrual the employee is working towards, whereas :guilabel:`Absence` does not count toward any type of accrual." msgstr "" -#: ../../content/applications/hr/time_off.rst:142 +#: ../../content/applications/hr/time_off.rst:145 msgid ":guilabel:`Company`: if multiple companies are created in the database, and this time off type only applies to one company, select the company from the drop-down menu. If this field is left blank, the time off type applies to all companies in the database. This field **only** appears in a multi-company database." msgstr "" -#: ../../content/applications/hr/time_off.rst:148 +#: ../../content/applications/hr/time_off.rst:151 msgid "Negative Cap section" msgstr "" -#: ../../content/applications/hr/time_off.rst:150 +#: ../../content/applications/hr/time_off.rst:153 msgid "Enable the :guilabel:`Allow Negative Cap` option if employees are able to request more time off than they currently have, allowing a negative balance. If enabled, an :guilabel:`Amount in Negative` field appears. In this field, enter the maximum amount of negative time allowed, in days." msgstr "" -#: ../../content/applications/hr/time_off.rst:155 +#: ../../content/applications/hr/time_off.rst:158 msgid "Sara currently has three days of the time off type `Vacation`. She is planning a trip that requires five days of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:158 +#: ../../content/applications/hr/time_off.rst:161 msgid "The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option enabled, and the :guilabel:`Amount in Negative` is set to five." msgstr "" -#: ../../content/applications/hr/time_off.rst:161 +#: ../../content/applications/hr/time_off.rst:164 msgid "These settings allow Sara to submit a request for five days of the `Vacation` time off type. If approved, her `Vacation` time off balance will be negative two (-2) days." msgstr "" @@ -9763,43 +10223,43 @@ msgid "The top half of the time off type form, with all the information filled o "off." msgstr "" -#: ../../content/applications/hr/time_off.rst:170 +#: ../../content/applications/hr/time_off.rst:173 msgid "Payroll section" msgstr "" -#: ../../content/applications/hr/time_off.rst:172 +#: ../../content/applications/hr/time_off.rst:175 msgid "If the time off type should create :doc:`../hr/payroll/work_entries` in the *Payroll* application, select the :guilabel:`Work Entry Type` from the drop-down list." msgstr "" -#: ../../content/applications/hr/time_off.rst:176 +#: ../../content/applications/hr/time_off.rst:179 msgid "Timesheets section" msgstr "" -#: ../../content/applications/hr/time_off.rst:179 +#: ../../content/applications/hr/time_off.rst:182 msgid "The :guilabel:`Timesheets` section only appears if the user is in developer mode. Refer to the :ref:`developer-mode` document for details on how to access the developer mode." msgstr "" -#: ../../content/applications/hr/time_off.rst:182 +#: ../../content/applications/hr/time_off.rst:185 msgid "When an employee takes time off, and is also using timesheets, Odoo creates entries in the *Timesheets* application for the time off. This section defines how they are entered." msgstr "" -#: ../../content/applications/hr/time_off.rst:185 +#: ../../content/applications/hr/time_off.rst:188 msgid ":guilabel:`Project`: select the project that the time off type entries appear in." msgstr "" -#: ../../content/applications/hr/time_off.rst:186 +#: ../../content/applications/hr/time_off.rst:189 msgid ":guilabel:`Task`: select the task that appears in the timesheet for this time off type. The default options are: :guilabel:`Time Off`, :guilabel:`Meeting`, or :guilabel:`Training`." msgstr "" -#: ../../content/applications/hr/time_off.rst:190 +#: ../../content/applications/hr/time_off.rst:193 msgid "Display Option section" msgstr "" -#: ../../content/applications/hr/time_off.rst:192 +#: ../../content/applications/hr/time_off.rst:195 msgid ":guilabel:`Color`: select a color to be used in the *Time Off* application dashboard." msgstr "" -#: ../../content/applications/hr/time_off.rst:193 +#: ../../content/applications/hr/time_off.rst:196 msgid ":guilabel:`Cover Image`: select an icon to be used in the *Time Off* application dashboard." msgstr "" @@ -9808,63 +10268,63 @@ msgid "The lower half of the time off type form, with all the information filled "off." msgstr "" -#: ../../content/applications/hr/time_off.rst:203 +#: ../../content/applications/hr/time_off.rst:206 msgid "Accrual plans" msgstr "" -#: ../../content/applications/hr/time_off.rst:205 +#: ../../content/applications/hr/time_off.rst:208 msgid "Some time off is earned through an accrual plan, meaning that for every specified amount of time an employee works (hour, day, week, etc), they earn or *accrue* a specified amount of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:209 +#: ../../content/applications/hr/time_off.rst:212 msgid "If an employee accrues a vacation day for every week they work, they would earn 0.2 vacation days for each hour they work. At the end of a forty hour work week, they would earn one whole vacation day (8 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:214 +#: ../../content/applications/hr/time_off.rst:217 msgid "Create accrual plan" msgstr "" -#: ../../content/applications/hr/time_off.rst:216 +#: ../../content/applications/hr/time_off.rst:219 msgid "To create a new accrual plan, navigate to :menuselection:`Time Off app --> Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, which reveals a blank accrual plan form." msgstr "" -#: ../../content/applications/hr/time_off.rst:221 +#: ../../content/applications/hr/time_off.rst:224 msgid ":guilabel:`Name`: enter the accrual plan name." msgstr "" -#: ../../content/applications/hr/time_off.rst:222 +#: ../../content/applications/hr/time_off.rst:225 msgid ":guilabel:`Accrued Gain Time`: select when the employee begins to accrue time off, either :guilabel:`At the start of the accrual period` or :guilabel:`At the end of the accrual period`." msgstr "" -#: ../../content/applications/hr/time_off.rst:224 +#: ../../content/applications/hr/time_off.rst:227 msgid ":guilabel:`Carry-Over Time`: select when the employee received previously earned time. The options are:" msgstr "" -#: ../../content/applications/hr/time_off.rst:227 +#: ../../content/applications/hr/time_off.rst:230 msgid ":guilabel:`At the start of the year`: select this if the accrual rolls over on January 1 of the upcoming year." msgstr "" -#: ../../content/applications/hr/time_off.rst:229 +#: ../../content/applications/hr/time_off.rst:232 msgid ":guilabel:`At the allocation date`: select this if the accrual rolls over as soon as time is allocated to the employee." msgstr "" -#: ../../content/applications/hr/time_off.rst:231 +#: ../../content/applications/hr/time_off.rst:234 msgid ":guilabel:`Other`: select this option if neither of the other two options are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. Select the date using the two drop-down menus, one for the day and one for the month." msgstr "" -#: ../../content/applications/hr/time_off.rst:235 +#: ../../content/applications/hr/time_off.rst:238 msgid ":guilabel:`Based on worked time`: enable this option if time off accrual is determined by the employee's worked hours. Days **not** considered as worked time do **not** contribute to the accrual plan in Odoo." msgstr "" -#: ../../content/applications/hr/time_off.rst:238 +#: ../../content/applications/hr/time_off.rst:241 msgid ":guilabel:`Milestone Transition`: this selection determines when employees move up to a new milestone. If they qualify to change milestones in the middle of a pay period, select if the employee changes milestones :guilabel:`Immediately` or :guilabel:`After this accrual's period` (after the current pay period)." msgstr "" -#: ../../content/applications/hr/time_off.rst:244 +#: ../../content/applications/hr/time_off.rst:247 msgid "The :guilabel:`Milestone Transition` field is **only** visible after a minimum of two :ref:`rules ` have been configured on the accrual plan." msgstr "" -#: ../../content/applications/hr/time_off.rst:247 +#: ../../content/applications/hr/time_off.rst:250 msgid ":guilabel:`Company`: using the drop-down menu, select the company the accrual plan applies to. If left blank, the accrual plan can be used for all companies. This field only appears in a multi-company database." msgstr "" @@ -9872,75 +10332,75 @@ msgstr "" msgid "An accrual plan form with all the entries filled out." msgstr "" -#: ../../content/applications/hr/time_off.rst:260 +#: ../../content/applications/hr/time_off.rst:263 msgid "Rules must be created in order for employees to accrue time off from the accrual plan." msgstr "" -#: ../../content/applications/hr/time_off.rst:262 +#: ../../content/applications/hr/time_off.rst:265 msgid "To create a new rule, click the :guilabel:`New Milestone` button in the gray :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:265 +#: ../../content/applications/hr/time_off.rst:268 msgid "Fill out the following fields on the form:" msgstr "" -#: ../../content/applications/hr/time_off.rst:267 +#: ../../content/applications/hr/time_off.rst:270 msgid ":guilabel:`Employee accrue`: select the parameters for earned time off in this section." msgstr "" -#: ../../content/applications/hr/time_off.rst:269 +#: ../../content/applications/hr/time_off.rst:272 msgid "First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment of accrued time using the drop-down menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:272 +#: ../../content/applications/hr/time_off.rst:275 msgid "Next, enter the numerical amount of the selected parameter that is accrued. The numerical format is `X.XXXX`, so that partial days or hours can also be configured." msgstr "" -#: ../../content/applications/hr/time_off.rst:275 +#: ../../content/applications/hr/time_off.rst:278 msgid "Last, select how often the time is accrued using the drop-down menu. The default options are :guilabel:`Hourly`, :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, :guilabel:`Twice a year`, and :guilabel:`Yearly`." msgstr "" -#: ../../content/applications/hr/time_off.rst:279 +#: ../../content/applications/hr/time_off.rst:282 msgid "Depending on which option is selected, additional fields may appear. For example, if :guilabel:`Twice a month` is selected, two additional fields appear, to specify the two days of each month that the milestone occurs." msgstr "" -#: ../../content/applications/hr/time_off.rst:282 +#: ../../content/applications/hr/time_off.rst:285 msgid ":guilabel:`Cap accrued time`: if there is a maximum amount of days the employee can accrue with this plan, enable this option." msgstr "" -#: ../../content/applications/hr/time_off.rst:285 +#: ../../content/applications/hr/time_off.rst:288 msgid "When enabled, two additional fields appear beneath it. Select the type of time period from the drop-down menu, either :guilabel:`Days` or :guilabel:`Hours`." msgstr "" -#: ../../content/applications/hr/time_off.rst:288 +#: ../../content/applications/hr/time_off.rst:291 msgid "Then, enter a numerical value in the field to specify the maximum amount of time that can be accrued." msgstr "" -#: ../../content/applications/hr/time_off.rst:290 +#: ../../content/applications/hr/time_off.rst:293 msgid ":guilabel:`Milestone reached`: enter the number and value of the time period that must pass before the employee starts to accumulate time off. The first value is numerical; enter a number in the first field." msgstr "" -#: ../../content/applications/hr/time_off.rst:294 +#: ../../content/applications/hr/time_off.rst:297 msgid "Then, select the type of time period using the drop-down menu in the second field. The options are: :guilabel:`Days`, :guilabel:`Months`, or :guilabel:`Years`." msgstr "" -#: ../../content/applications/hr/time_off.rst:296 +#: ../../content/applications/hr/time_off.rst:299 msgid ":guilabel:`Carry over`: select how any unused time off is handled. The options are either:" msgstr "" -#: ../../content/applications/hr/time_off.rst:298 +#: ../../content/applications/hr/time_off.rst:301 msgid ":guilabel:`None. Accrued time reset to 0`: any unused time off is gone." msgstr "" -#: ../../content/applications/hr/time_off.rst:299 +#: ../../content/applications/hr/time_off.rst:302 msgid ":guilabel:`All accrued time carried over`: all unused time off is rolled over to the next calendar year." msgstr "" -#: ../../content/applications/hr/time_off.rst:301 +#: ../../content/applications/hr/time_off.rst:304 msgid ":guilabel:`Carry over with a maximum`: unused time off is rolled over to the next calendar year, but there is a cap. An :guilabel:`Up to` field appears if this is selected. Enter the maximum number of :guilabel:`Days` that can roll over to the following year. Any time off beyond this parameter is lost." msgstr "" -#: ../../content/applications/hr/time_off.rst:306 +#: ../../content/applications/hr/time_off.rst:309 msgid "Once the form is completed, click :guilabel:`Save & Close` to save the form and close the modal, or click :guilabel:`Save & New` to save the form and create another milestone. Add as many milestones as desired." msgstr "" @@ -9948,84 +10408,84 @@ msgstr "" msgid "A milestone form with all the entries filled out." msgstr "" -#: ../../content/applications/hr/time_off.rst:317 +#: ../../content/applications/hr/time_off.rst:320 msgid "Public holidays" msgstr "" -#: ../../content/applications/hr/time_off.rst:319 +#: ../../content/applications/hr/time_off.rst:322 msgid "To observe public or national holidays, and provide extra days off as holidays to employees, configure the observed *public holidays* in Odoo." msgstr "" -#: ../../content/applications/hr/time_off.rst:322 +#: ../../content/applications/hr/time_off.rst:325 msgid "It is important to configure these days in Odoo, so employees are aware of the days they have off, and do not request time off on days that are already set as a public holiday (non-working days)." msgstr "" -#: ../../content/applications/hr/time_off.rst:325 +#: ../../content/applications/hr/time_off.rst:328 msgid "Additionally, all public holidays configured in the *Time Off* app are also reflected in any app that uses working schedules, such as *Calendar*, *Planning*, *Manufacturing*, and more." msgstr "" -#: ../../content/applications/hr/time_off.rst:328 +#: ../../content/applications/hr/time_off.rst:331 msgid "Due to Odoo's integration with other apps that use working schedules, it is considered best practice to ensure *all* public holidays are configured." msgstr "" -#: ../../content/applications/hr/time_off.rst:332 +#: ../../content/applications/hr/time_off.rst:335 msgid "Create public holiday" msgstr "" -#: ../../content/applications/hr/time_off.rst:334 +#: ../../content/applications/hr/time_off.rst:337 msgid "To create a public holiday, navigate to :menuselection:`Time Off app --> Configuration --> Public Holidays`." msgstr "" -#: ../../content/applications/hr/time_off.rst:337 +#: ../../content/applications/hr/time_off.rst:340 msgid "All currently configured public holidays appear in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:339 +#: ../../content/applications/hr/time_off.rst:342 msgid "Click the :guilabel:`New` button, and a new line appears at the bottom of the list." msgstr "" -#: ../../content/applications/hr/time_off.rst:341 -#: ../../content/applications/hr/time_off.rst:403 +#: ../../content/applications/hr/time_off.rst:344 +#: ../../content/applications/hr/time_off.rst:406 msgid "Enter the following information on that new line:" msgstr "" -#: ../../content/applications/hr/time_off.rst:343 +#: ../../content/applications/hr/time_off.rst:346 msgid ":guilabel:`Name`: enter the name of the holiday." msgstr "" -#: ../../content/applications/hr/time_off.rst:344 +#: ../../content/applications/hr/time_off.rst:347 msgid ":guilabel:`Company`: if in a multi-company database, the current company populates this field by default. It is not possible to edit this field." msgstr "" -#: ../../content/applications/hr/time_off.rst:348 +#: ../../content/applications/hr/time_off.rst:351 msgid "The :guilabel:`Company` field is hidden by default. To view this field, click the two dots in the top-right corner of the list, to the far-right of the column titles, and activate the :guilabel:`Company` selection from the drop-down menu that appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:352 +#: ../../content/applications/hr/time_off.rst:355 msgid ":guilabel:`Start Date`: using the date and time picker, select the date and time that the holiday starts. By default, this field is configured for the current date. The start time is set according to the start time for the company (according to the :ref:`working schedules `). If the user's computer is set to a different time zone, the start time is adjusted according to the difference in the time zone, compared to the company's time zone." msgstr "" -#: ../../content/applications/hr/time_off.rst:357 +#: ../../content/applications/hr/time_off.rst:360 msgid ":guilabel:`End Date`: using the date and time picker, select the date and time that the holiday ends. By default, this field is configured for the current date, and the time is set to the end time for the company (according to the :ref:`working schedules `). If the user's computer is set to a different time zone, the start time is adjusted according to the difference in the time zone, compared to the company's time zone." msgstr "" -#: ../../content/applications/hr/time_off.rst:364 +#: ../../content/applications/hr/time_off.rst:367 msgid "A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an eight hour work day and one hour lunch break." msgstr "" -#: ../../content/applications/hr/time_off.rst:367 +#: ../../content/applications/hr/time_off.rst:370 msgid "For a user in New York, with a computer time zone set to Eastern Standard Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, accounting for the three hour time zone difference." msgstr "" -#: ../../content/applications/hr/time_off.rst:371 +#: ../../content/applications/hr/time_off.rst:374 msgid "Similarly, a user located in Los Angeles, with a computer time zone set to Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." msgstr "" -#: ../../content/applications/hr/time_off.rst:374 +#: ../../content/applications/hr/time_off.rst:377 msgid ":guilabel:`Working Hours`: if the holiday should only apply to employees who have a specific set of working hours, select the working hours from the drop-down menu. If left blank, the holiday applies to all employees." msgstr "" -#: ../../content/applications/hr/time_off.rst:377 +#: ../../content/applications/hr/time_off.rst:380 msgid ":guilabel:`Work Entry Type`: if using the *Payroll* application, this field defines how the :ref:`work entries ` for the holiday appear. Select the work entry type from the drop-down menu." msgstr "" @@ -10033,59 +10493,59 @@ msgstr "" msgid "The list of public holidays in the configuration menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:386 +#: ../../content/applications/hr/time_off.rst:389 msgid "Mandatory days" msgstr "" -#: ../../content/applications/hr/time_off.rst:388 +#: ../../content/applications/hr/time_off.rst:391 msgid "Some companies have special days where specific departments, or the entire staff, is required to be present, and time off is not allowed on those specific days." msgstr "" -#: ../../content/applications/hr/time_off.rst:391 +#: ../../content/applications/hr/time_off.rst:394 msgid "These types of days are called *mandatory days* in Odoo. These can be configured to be company-wide, or department specific. When configured, employees in the specified department or company are unable to submit time off requests for these mandatory days." msgstr "" -#: ../../content/applications/hr/time_off.rst:396 +#: ../../content/applications/hr/time_off.rst:399 msgid "Create mandatory days" msgstr "" -#: ../../content/applications/hr/time_off.rst:398 +#: ../../content/applications/hr/time_off.rst:401 msgid "No mandatory days are configured in Odoo by default. To create a mandatory day, navigate to :menuselection:`Time Off app --> Configuration --> Mandatory Days`." msgstr "" -#: ../../content/applications/hr/time_off.rst:401 +#: ../../content/applications/hr/time_off.rst:404 msgid "Click the :guilabel:`New` button in the top-left corner, and a blank line appears in the list." msgstr "" -#: ../../content/applications/hr/time_off.rst:405 +#: ../../content/applications/hr/time_off.rst:408 msgid ":guilabel:`Name`: enter the name of the mandatory day." msgstr "" -#: ../../content/applications/hr/time_off.rst:406 +#: ../../content/applications/hr/time_off.rst:409 msgid ":guilabel:`Company`: if in a multi-company database, this field is visible, and the current company populates this field by default. Using the drop-down menu, select the company the mandatory day is for." msgstr "" -#: ../../content/applications/hr/time_off.rst:409 +#: ../../content/applications/hr/time_off.rst:412 msgid ":guilabel:`Departments`: this column is hidden by default. First, click the :guilabel:`(optional columns)` icon in the top-right corner, next to :guilabel:`Colors`, and then click the checkbox next to :guilabel:`Departments` to reveal that column." msgstr "" -#: ../../content/applications/hr/time_off.rst:413 +#: ../../content/applications/hr/time_off.rst:416 msgid "Next, select the desired departments from the drop-down menu. Multiple departments can be selected, and there is no limit to the amount of departments that can be added." msgstr "" -#: ../../content/applications/hr/time_off.rst:416 +#: ../../content/applications/hr/time_off.rst:419 msgid "If this field is left blank, the mandatory day applies to the entire company." msgstr "" -#: ../../content/applications/hr/time_off.rst:417 +#: ../../content/applications/hr/time_off.rst:420 msgid ":guilabel:`Start Date`: using the calendar picker, select the date the mandatory day starts." msgstr "" -#: ../../content/applications/hr/time_off.rst:418 +#: ../../content/applications/hr/time_off.rst:421 msgid ":guilabel:`End Date`: using the calendar picker, select the date the mandatory day ends. If creating a single mandatory day, the end date should be the same as the start date." msgstr "" -#: ../../content/applications/hr/time_off.rst:420 +#: ../../content/applications/hr/time_off.rst:423 msgid ":guilabel:`Color`: if desired, select a color from the available presented options. If no color is desired, select the `No color` option, represented by a white box with a red line diagonally across it. The selected color appears on the main *Time Off* application dashboard, in both the calendar and in the legend." msgstr "" @@ -10093,83 +10553,83 @@ msgstr "" msgid "The Mandatory Days section with three configured days." msgstr "" -#: ../../content/applications/hr/time_off.rst:432 +#: ../../content/applications/hr/time_off.rst:435 msgid "Allocate time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:434 +#: ../../content/applications/hr/time_off.rst:437 msgid "Once time off types and accrual plans have been configured, the next step is to allocate, or give, time off to employees. This section is only visible to users who have either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:438 +#: ../../content/applications/hr/time_off.rst:441 msgid "To create a new allocation, navigate to :menuselection:`Time Off app --> Management --> Allocations`." msgstr "" -#: ../../content/applications/hr/time_off.rst:441 +#: ../../content/applications/hr/time_off.rst:444 msgid "This presents a list of all current allocations, including their respective statuses." msgstr "" -#: ../../content/applications/hr/time_off.rst:443 +#: ../../content/applications/hr/time_off.rst:446 msgid "Click :guilabel:`New` to allocate time off, and a blank allocation form appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:445 +#: ../../content/applications/hr/time_off.rst:448 msgid "After entering a name for the allocation on the first blank field of the form, enter the following information:" msgstr "" -#: ../../content/applications/hr/time_off.rst:448 +#: ../../content/applications/hr/time_off.rst:451 msgid ":guilabel:`Time Off Type`: using the drop-down menu, select the type of time off that is being allocated to the employees." msgstr "" -#: ../../content/applications/hr/time_off.rst:450 +#: ../../content/applications/hr/time_off.rst:453 msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`. If the allocation is **not** based on an accrual plan, select :guilabel:`Regular Allocation`." msgstr "" -#: ../../content/applications/hr/time_off.rst:453 +#: ../../content/applications/hr/time_off.rst:456 msgid ":guilabel:`Accrual Plan`: if :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu, select the accrual plan with which the allocation is associated. An accrual plan **must** be selected for an :guilabel:`Accrual Allocation`." msgstr "" -#: ../../content/applications/hr/time_off.rst:457 +#: ../../content/applications/hr/time_off.rst:460 msgid ":guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start Date`." msgstr "" -#: ../../content/applications/hr/time_off.rst:462 +#: ../../content/applications/hr/time_off.rst:465 msgid "The current date populates the first date field by default. To select another date, click on the pre-populated date to reveal a popover calendar window. Navigate to the desired start date for the allocation, and click on the date to select it." msgstr "" -#: ../../content/applications/hr/time_off.rst:466 +#: ../../content/applications/hr/time_off.rst:469 msgid "If the allocation expires, select the expiration date in the next date field. If the time off does *not* expire, leave the second date field blank. `No Limit` appears in the field if no date is selected." msgstr "" -#: ../../content/applications/hr/time_off.rst:470 +#: ../../content/applications/hr/time_off.rst:473 msgid "If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this second field is labeled :guilabel:`Run until`." msgstr "" -#: ../../content/applications/hr/time_off.rst:472 +#: ../../content/applications/hr/time_off.rst:475 msgid ":guilabel:`Allocation`: enter the amount of time that is being allocated to the employees. This field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the selected :ref:`Time Off Type ` is configured (in hours or days)." msgstr "" -#: ../../content/applications/hr/time_off.rst:475 +#: ../../content/applications/hr/time_off.rst:478 msgid ":guilabel:`Mode`: using the drop-down menu, select how the allocation is assigned. This selection determines who receives the time off allocation. The options are :guilabel:`By Employee`, :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`." msgstr "" -#: ../../content/applications/hr/time_off.rst:479 +#: ../../content/applications/hr/time_off.rst:482 msgid "Depending on what is selected for the :guilabel:`Mode`, this following field is labeled either: :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`." msgstr "" -#: ../../content/applications/hr/time_off.rst:482 +#: ../../content/applications/hr/time_off.rst:485 msgid "Using the drop-down menu, indicate the specific employees, company, department, or employee tags who are receiving this time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:485 +#: ../../content/applications/hr/time_off.rst:488 msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`." msgstr "" -#: ../../content/applications/hr/time_off.rst:487 +#: ../../content/applications/hr/time_off.rst:490 msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`." msgstr "" -#: ../../content/applications/hr/time_off.rst:488 +#: ../../content/applications/hr/time_off.rst:491 msgid ":guilabel:`Add a reason...`: if any description or note is necessary to explain the time off allocation, enter it in this field at the bottom of the form." msgstr "" @@ -10178,136 +10638,55 @@ msgid "A new allocation form with all the fields filled out for the annual two w "granted to all employees." msgstr "" -#: ../../content/applications/hr/time_off.rst:499 -msgid "Request time off" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:501 -msgid "Once an employee has been allocated time off, a request to use the time off can be submitted. Time off can be requested in one of two ways, either from the :ref:`dashboard ` or from the :ref:`My Time Off ` view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:505 -msgid "To create a new request for time off, click the :guilabel:`New` button on either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time Off` list view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:509 -msgid "Both :guilabel:`New` buttons allow the user to request time off, but when requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request form appears in a modal. When requested from the :guilabel:`My Time Off` list view, the screen navigates to a new time off request page, instead." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:514 -msgid "Enter the following information on the :guilabel:`New Time Off` request form:" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:516 -msgid ":guilabel:`Time Off Type`: select the type of time off being requested from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:517 -msgid ":guilabel:`Dates`: enter the dates that the time off falls under. There are two fields to populate, the start and end dates. Click on either date field and a popover calendar appears." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:520 -msgid "Click on the start date, then click on the end date. The selected start and end dates are circled, and the dates between them are highlighted (if applicable)." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:523 -msgid "If the time off requested is for a single day, click on the start date, then click the same date again for the end date." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:526 -msgid "When the correct dates are selected/highlighted, click the :guilabel:`Apply` button." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:528 -msgid "The selected dates now populate the two portions of the :guilabel:`Dates` field." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:530 -msgid "If the selected :guilabel:`Time Off Type` is configured to have the time off taken in hours, the following two fields also appear:" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:533 -msgid ":guilabel:`Half Day`: if the time off request is for a half day, check this box. When this is selected, the second date field disappears, and is replaced with a drop-down menu. From that drop-down menu, select either :guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the day is being requested." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:537 -msgid ":guilabel:`Custom Hours`: if the time off requested is not a whole or half day, check this box. A :guilabel:`From` and :guilabel:`To` field appears beneath this option, if selected. Using the drop-down menu, select the start and end time for the time off request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:541 -msgid ":guilabel:`Duration`: this field updates automatically once the :guilabel:`Date` section is completed. If the :guilabel:`Date` section is modified, this section automatically updates to reflect the total time off requested. This field is in either hours or days, depending on how the selected :guilabel:`Time Off Type` is configured." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:545 -msgid ":guilabel:`Description`: enter a description for the time off request. This should include any details that managers and approvers may need in order to approve the request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:547 -msgid ":guilabel:`Supporting Document`: this field only appears if the :guilabel:`Time Off Type` selected allows for the attachments of documents. Click the :guilabel:`Attach File` button, and a file explorer window appears." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:551 -msgid "Navigate to the desired files to attach, select them, then click the :guilabel:`Open` button. The files then appear on the time off request form. Multiple documents can be attached, if necessary." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:554 -#: ../../content/applications/hr/time_off.rst:604 -msgid "If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button to save the information and submit the request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:557 -msgid "If the form was completed from the :guilabel:`My Time Off` list view, the information is automatically saved as it is entered. However, the form can be saved manually at any time by clicking the *save manually* button, represented by a :guilabel:`(cloud upload)` icon." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:-1 -msgid "A time off request form filled out for an employee home sick for two days with the flu." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:568 +#: ../../content/applications/hr/time_off.rst:502 msgid "Request allocation" msgstr "" -#: ../../content/applications/hr/time_off.rst:570 +#: ../../content/applications/hr/time_off.rst:504 msgid "If an employee has used all their time off, or is going to run out of time off, they can request an allocation for additional time. Allocations can be requested in one of two ways, either from the :ref:`Dashboard ` or the :ref:`My Allocations ` view." msgstr "" -#: ../../content/applications/hr/time_off.rst:574 +#: ../../content/applications/hr/time_off.rst:508 msgid "To create a new allocation request, click either the :guilabel:`New Allocation Request` button on the main *Time Off* dashboard, or the :guilabel:`New` button in the :guilabel:`My Allocations` list view. Both buttons open a new allocation request form." msgstr "" -#: ../../content/applications/hr/time_off.rst:579 +#: ../../content/applications/hr/time_off.rst:513 msgid "Both :guilabel:`New` buttons open a :guilabel:`New Allocation` request form, but when requested from the :guilabel:`Dashboard`, the form appears in a modal. When requested from the :guilabel:`My Allocations` list view, the screen navigates to a new allocation request page, instead." msgstr "" -#: ../../content/applications/hr/time_off.rst:584 +#: ../../content/applications/hr/time_off.rst:518 msgid "Enter the following information on the :guilabel:`New Allocation` request form:" msgstr "" -#: ../../content/applications/hr/time_off.rst:586 +#: ../../content/applications/hr/time_off.rst:520 msgid ":guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the drop-down menu. After a selection is made, the title updates with the time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:588 +#: ../../content/applications/hr/time_off.rst:522 msgid ":guilabel:`Validity Period`: this field **only** appears if requesting an allocation with a time off type that has the :guilabel:`Take Time Off in` field :ref:`configured ` to either :guilabel:`Day` or :guilabel:`Half Day`. This field does **not** appear if the :guilabel:`Take Time Off in` field is set to :guilabel:`Hours`." msgstr "" -#: ../../content/applications/hr/time_off.rst:593 +#: ../../content/applications/hr/time_off.rst:527 msgid "Using the calendar selector, select a start and end date the allocation is valid for. By default, the current date populates the first field, and :guilabel:`No Limit` populates the second field." msgstr "" -#: ../../content/applications/hr/time_off.rst:596 +#: ../../content/applications/hr/time_off.rst:530 msgid "Adjust both of these dates, if desired." msgstr "" -#: ../../content/applications/hr/time_off.rst:597 +#: ../../content/applications/hr/time_off.rst:531 msgid ":guilabel:`Allocation`: enter the amount of time being requested in this field. The format is presented in either days or hours, depending on how the time off type is configured. Once this field is populated, the name of the allocation request is updated to include the amount of time being requested." msgstr "" -#: ../../content/applications/hr/time_off.rst:601 +#: ../../content/applications/hr/time_off.rst:535 msgid ":guilabel:`Add a reason...`: enter a description for the allocation request. This should include any details that managers and approvers may need in order to approve the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:607 +#: ../../content/applications/hr/time_off.rst:538 +msgid "If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:541 msgid "If the form was completed from the :guilabel:`My Allocations` list view, the information is automatically saved as it is entered. However, the form can be saved manually at any time by clicking the *save manually* button, represented by a :guilabel:`(cloud upload)` icon." msgstr "" @@ -10316,52 +10695,52 @@ msgid "An allocation request form filled out for an employee requesting an addit "sick time." msgstr "" -#: ../../content/applications/hr/time_off.rst:619 +#: ../../content/applications/hr/time_off.rst:553 msgid "Management" msgstr "" -#: ../../content/applications/hr/time_off.rst:621 +#: ../../content/applications/hr/time_off.rst:555 msgid "Time off and allocation requests typically undergo an approval process before being granted. Requests either need one or two approvals, if any, depending on how the specific type of time off is configured. These are all housed under the :guilabel:`Management` section of the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:626 +#: ../../content/applications/hr/time_off.rst:560 msgid "Only users who can approve allocation and time off requests have the :guilabel:`Management` section visible in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:632 +#: ../../content/applications/hr/time_off.rst:566 msgid "Manage time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:634 +#: ../../content/applications/hr/time_off.rst:568 msgid "To view time off requests that need approval, navigate to :menuselection:`Time Off app --> Management --> Time Off`. The only time off requests visible on this list are for employees the user has either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:639 +#: ../../content/applications/hr/time_off.rst:573 msgid "The default filter in the :guilabel:`Time Off` list is `Waiting For Me`. This only presents time off requests that need to be approved for current employees on the user's team, with a status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." msgstr "" -#: ../../content/applications/hr/time_off.rst:643 +#: ../../content/applications/hr/time_off.rst:577 msgid "The left side of the screen has various grouping options to narrow down the presented time off requests. Since only time off requests that need to be approved are shown, the only status options are :guilabel:`All`, :guilabel:`To Approve`, and :guilabel:`Second Approval`. The various departments the user is a member of, and manages employees under, also appear on the left side of the screen, under :guilabel:`Departments`." msgstr "" -#: ../../content/applications/hr/time_off.rst:650 +#: ../../content/applications/hr/time_off.rst:584 msgid "If there are no requests that fall under one of the status options or departments, that status or department is **not** visible on the left-side menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:653 +#: ../../content/applications/hr/time_off.rst:587 msgid "To display time off requests for specific departments only, click on the :guilabel:`Department` on the left-hand side. Only requests within the selected department are then presented." msgstr "" -#: ../../content/applications/hr/time_off.rst:656 -#: ../../content/applications/hr/time_off.rst:721 +#: ../../content/applications/hr/time_off.rst:590 +#: ../../content/applications/hr/time_off.rst:657 msgid "The status column displays the status of each request, with the status highlighted in a specific color." msgstr "" -#: ../../content/applications/hr/time_off.rst:659 +#: ../../content/applications/hr/time_off.rst:593 msgid "The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are highlighted in yellow and are the only ones that appear in the list by default. If the `Waiting For Me` filter is removed, then all statuses appear. :guilabel:`Approved` requests are highlighted in green, :guilabel:`To Submit` (drafts) requests are highlighted in blue, and the :guilabel:`Refused` requests are highlighted in gray." msgstr "" -#: ../../content/applications/hr/time_off.rst:665 +#: ../../content/applications/hr/time_off.rst:599 msgid "To approve a time off request, click the :guilabel:`👍 Approve` button at the end of the line. To validate a time off request that has already been approved, and is waiting on a second approval, click the :guilabel:`✔️ Validate` button at the end of the line. To refuse a request, click the :guilabel:`✖️ Refuse` button at the far end of the line." msgstr "" @@ -10369,63 +10748,63 @@ msgstr "" msgid "Time off requests with the filter, groupings, and status sections highlighted." msgstr "" -#: ../../content/applications/hr/time_off.rst:674 +#: ../../content/applications/hr/time_off.rst:608 msgid "For more details, click anywhere on the time off request line (except for the :guilabel:`👍 Approve`, :guilabel:`✔️ Validate`, and :guilabel:`✖️ Refuse` buttons) to load the time off request form. Depending on the rights of the user, changes can be made." msgstr "" -#: ../../content/applications/hr/time_off.rst:678 +#: ../../content/applications/hr/time_off.rst:612 msgid "To modify the request, make any desired changes to the form. All changes are automatically saved." msgstr "" -#: ../../content/applications/hr/time_off.rst:680 +#: ../../content/applications/hr/time_off.rst:614 msgid "It is also possible to approve or refuse the request from this form. Click the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button to refuse the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:684 +#: ../../content/applications/hr/time_off.rst:620 msgid "Manage allocations" msgstr "" -#: ../../content/applications/hr/time_off.rst:686 +#: ../../content/applications/hr/time_off.rst:622 msgid "To view allocations that need approval, navigate to :menuselection:`Time Off app --> Management --> Allocations`. The only allocations visible on this list are for employees the user has either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:691 +#: ../../content/applications/hr/time_off.rst:627 msgid "The default filters that are configured to be in place when navigating to the :guilabel:`Allocations` list are :guilabel:`My Team` and :guilabel:`Active Employee`. This *only* presents employees on the user's team (who they manage) and active employees. Inactive users are not shown." msgstr "" -#: ../../content/applications/hr/time_off.rst:696 +#: ../../content/applications/hr/time_off.rst:632 msgid "The left side of the screen has various grouping options to narrow down the presented allocation requests." msgstr "" -#: ../../content/applications/hr/time_off.rst:699 +#: ../../content/applications/hr/time_off.rst:635 msgid "The :guilabel:`Status` options are :guilabel:`To Approve`, :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific :guilabel:`Status` to view only requests with that status. To view all allocation requests, click :guilabel:`All`." msgstr "" -#: ../../content/applications/hr/time_off.rst:703 +#: ../../content/applications/hr/time_off.rst:639 msgid "It is also possible to display allocation requests by department. Click on the :guilabel:`Department` in the left side of the screen to only present allocations for that specific department." msgstr "" -#: ../../content/applications/hr/time_off.rst:708 +#: ../../content/applications/hr/time_off.rst:644 msgid "The groupings on the left side only present allocation requests that fall under the default filters of :guilabel:`My Team` and :guilabel:`Active Employee`. Only the statuses for allocation requests that fall under those filters are presented on the left side." msgstr "" -#: ../../content/applications/hr/time_off.rst:712 +#: ../../content/applications/hr/time_off.rst:648 msgid "For example, if there are no requests with a status of :guilabel:`To Submit`, that status option does not appear in the left-hand side." msgstr "" -#: ../../content/applications/hr/time_off.rst:715 +#: ../../content/applications/hr/time_off.rst:651 msgid "All departments for the user's employees appear in the list. If there are no allocation requests that fall under that department matching the pre-configured filters, the list is blank." msgstr "" -#: ../../content/applications/hr/time_off.rst:718 +#: ../../content/applications/hr/time_off.rst:654 msgid "It is always possible to remove any of the pre-configured filters, by clicking the :guilabel:`✖️ (remove)` icon on the specific filter to remove it." msgstr "" -#: ../../content/applications/hr/time_off.rst:724 +#: ../../content/applications/hr/time_off.rst:660 msgid "The :guilabel:`To Approve` requests are highlighted in yellow, :guilabel:`Approved` requests are highlighted in green, and the :guilabel:`Refused` requests are highlighted in gray." msgstr "" -#: ../../content/applications/hr/time_off.rst:727 +#: ../../content/applications/hr/time_off.rst:663 msgid "To approve an allocation request, click the :guilabel:`✔ Validate` button at the end of the line. To refuse a request, click the :guilabel:`✖️ Refuse` button." msgstr "" @@ -10433,59 +10812,59 @@ msgstr "" msgid "Allocations with the filter, groupings, and status sections highlighted." msgstr "" -#: ../../content/applications/hr/time_off.rst:734 +#: ../../content/applications/hr/time_off.rst:670 msgid "If more details are needed, click anywhere on the allocation request line (except for the :guilabel:`✔ Validate` and :guilabel:`✖️ Refuse` buttons) to view the request in detail." msgstr "" -#: ../../content/applications/hr/time_off.rst:737 +#: ../../content/applications/hr/time_off.rst:673 msgid "Depending on the rights of the user, changes can be made to the allocation request form that appears. To modify the request, make any desired changes to the form. All changes are automatically saved." msgstr "" -#: ../../content/applications/hr/time_off.rst:741 +#: ../../content/applications/hr/time_off.rst:677 msgid "It is also possible to approve or refuse the request from this form. Click the :guilabel:`Validate` button to approve, or the :guilabel:`Refuse` button to refuse the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:747 +#: ../../content/applications/hr/time_off.rst:683 msgid "To view a color-coded schedule of the user's time off, and/or of the team managed by them, navigate to :menuselection:`Time Off app --> Overview`. This presents a calendar with the default filter of `My Team`, in a month view." msgstr "" -#: ../../content/applications/hr/time_off.rst:751 +#: ../../content/applications/hr/time_off.rst:687 msgid "To change the time period displayed, click on the :guilabel:`Month` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Year` to present the calendar in that corresponding view." msgstr "" -#: ../../content/applications/hr/time_off.rst:755 +#: ../../content/applications/hr/time_off.rst:691 msgid "To navigate forward or backward in time, in the selected increment (:guilabel:`Month`, :guilabel:`Week`, etc.), click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` to move either forward or backward in that specified amount of time." msgstr "" -#: ../../content/applications/hr/time_off.rst:759 +#: ../../content/applications/hr/time_off.rst:695 msgid "For example, if :guilabel:`Month` is selected, the arrows adjust the view by one month." msgstr "" -#: ../../content/applications/hr/time_off.rst:761 +#: ../../content/applications/hr/time_off.rst:697 msgid "To return to a view containing the current day, click the :guilabel:`Today` button at any time." msgstr "" -#: ../../content/applications/hr/time_off.rst:763 +#: ../../content/applications/hr/time_off.rst:699 msgid "Team members are listed alphabetically on individual lines, and their requested time off, regardless of the status (*validated* or *to approve*), is visible on the calendar." msgstr "" -#: ../../content/applications/hr/time_off.rst:766 +#: ../../content/applications/hr/time_off.rst:702 msgid "Each employee is color-coded. The employee's color is selected at random, and does *not* correspond to the type of time off they requested." msgstr "" -#: ../../content/applications/hr/time_off.rst:769 +#: ../../content/applications/hr/time_off.rst:705 msgid "The status of the time off is represented by the color detail of the request, either appearing solid (*validated*) or striped (*to approve*)." msgstr "" -#: ../../content/applications/hr/time_off.rst:772 +#: ../../content/applications/hr/time_off.rst:708 msgid "The number of days or hours requested is written on the request (if there is enough space)." msgstr "" -#: ../../content/applications/hr/time_off.rst:774 +#: ../../content/applications/hr/time_off.rst:710 msgid "At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph shows how many people are projected to be out on any given day. The number on each individual bar represents the number of employees out for those highlighted days." msgstr "" -#: ../../content/applications/hr/time_off.rst:778 +#: ../../content/applications/hr/time_off.rst:714 msgid "Click on a time off entry to view the details for the specific time off entry. The total number of hours or days are listed, along with the start and end time of the time off. To view the details of the time off request in a modal, click the :guilabel:`View` button." msgstr "" @@ -10493,47 +10872,47 @@ msgstr "" msgid "Overview of the user's team, with time off requests shown." msgstr "" -#: ../../content/applications/hr/time_off.rst:787 +#: ../../content/applications/hr/time_off.rst:723 msgid "My time" msgstr "" -#: ../../content/applications/hr/time_off.rst:789 +#: ../../content/applications/hr/time_off.rst:725 msgid "The :guilabel:`My Time` section of the *Time Off* application contains the time off dashboard, as well as the user's time off requests and allocations." msgstr "" -#: ../../content/applications/hr/time_off.rst:795 +#: ../../content/applications/hr/time_off.rst:731 msgid "Dashboard" msgstr "" -#: ../../content/applications/hr/time_off.rst:797 +#: ../../content/applications/hr/time_off.rst:733 msgid "All users have access to the time off dashboard, which is the default view in the *Time Off* application. The dashboard can also be accessed at any point in the application by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." msgstr "" -#: ../../content/applications/hr/time_off.rst:801 +#: ../../content/applications/hr/time_off.rst:737 msgid "The current year is displayed, and the current day is highlighted in red." msgstr "" -#: ../../content/applications/hr/time_off.rst:803 +#: ../../content/applications/hr/time_off.rst:739 msgid "To change the view, click on the :guilabel:`Year` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month` to present the calendar in that corresponding view." msgstr "" -#: ../../content/applications/hr/time_off.rst:807 +#: ../../content/applications/hr/time_off.rst:743 msgid "To change the presented dates, click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` icons to the left of the :guilabel:`Year` button. The calendar view adjusts in increments of the presented view." msgstr "" -#: ../../content/applications/hr/time_off.rst:811 +#: ../../content/applications/hr/time_off.rst:747 msgid "For example, if :guilabel:`Year` is selected, the arrows adjust the view by one year." msgstr "" -#: ../../content/applications/hr/time_off.rst:813 +#: ../../content/applications/hr/time_off.rst:749 msgid "To change the view at any point to a view that includes the current date, click the :guilabel:`Today` button." msgstr "" -#: ../../content/applications/hr/time_off.rst:816 +#: ../../content/applications/hr/time_off.rst:752 msgid "Above the calendar view is a summary of the user's time off balances. Every time off type that has been allocated appears in its own summary box. Each summary lists the type of time off, the corresponding icon, the current available balance (in hours or days), and an expiration date (if applicable)." msgstr "" -#: ../../content/applications/hr/time_off.rst:821 +#: ../../content/applications/hr/time_off.rst:757 msgid "To view the full details of a time off balance, click the :guilabel:`? (question mark)` icon at the end of the :guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete details are presented in a popover window, including the :guilabel:`Allocated` time, future :guilabel:`Accrual` time, :guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and the currently :guilabel:`Available` time off." msgstr "" @@ -10541,91 +10920,91 @@ msgstr "" msgid "A view of the complete time off balance details in the popover window." msgstr "" -#: ../../content/applications/hr/time_off.rst:831 +#: ../../content/applications/hr/time_off.rst:767 msgid "A user is also able to see how much time off they will have accrued in the future. On the right side of the time off summary blocks, there is a :guilabel:`Balance at the (date)` field. Click on the date, and a calendar selector popover appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:835 +#: ../../content/applications/hr/time_off.rst:771 msgid "The current date is the default date selected. Navigate to the desired date, and Odoo displays the time off balances the user will have on that date. This takes into account all time off currently planned and approved. To return to the current date, click the :guilabel:`Today` button to the right of the date field." msgstr "" -#: ../../content/applications/hr/time_off.rst:840 +#: ../../content/applications/hr/time_off.rst:776 msgid "On the right side of the calendar, the various time off types are displayed, with their corresponding colors. The :guilabel:`Legend` explains how the various statuses for time off requests are presented." msgstr "" -#: ../../content/applications/hr/time_off.rst:844 +#: ../../content/applications/hr/time_off.rst:780 msgid "Time off that has been validated appears in a solid color (in the color specified in the :guilabel:`Time Off Type` section above the :guilabel:`Legend`). Time off requests that still need to be approved appear with white stripes in the color. Refused time off requests have a colored line through the dates." msgstr "" -#: ../../content/applications/hr/time_off.rst:849 -msgid "New time off requests can be made from the dashboard. Click the :guilabel:`New` button at the top of the dashboard, and a :ref:`New Time Off ` modal appears." +#: ../../content/applications/hr/time_off.rst:785 +msgid "New time off requests can be made from the :guilabel:`Dashboard`. Click the :guilabel:`New` button at the top of the dashboard, and a :doc:`New Time Off <../hr/time_off/request_time_off>` pop-up window appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:852 -msgid "New allocation requests can also be made from the dashboard. Click the :guilabel:`New Allocation Request` button at the top of the dashboard to request more time off, and a :ref:`New Allocation ` modal appears." +#: ../../content/applications/hr/time_off.rst:789 +msgid "New allocation requests can also be made from the :guilabel:`Dashboard`. Click the :guilabel:`New Allocation Request` button at the top of the :guilabel:`Dashboard` to request more time off, and a :ref:`New Allocation ` modal appears." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 msgid "Time off dashboard view with the legend, time off summaries, and view buttons highlighted." msgstr "" -#: ../../content/applications/hr/time_off.rst:863 +#: ../../content/applications/hr/time_off.rst:800 msgid "My time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:865 +#: ../../content/applications/hr/time_off.rst:802 msgid "To view a list of all the user's time off requests, navigate to :menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time off requests, both past and present, appear in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:868 +#: ../../content/applications/hr/time_off.rst:805 msgid "The list includes the following information for each request: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Duration`, and the :guilabel:`Status`." msgstr "" -#: ../../content/applications/hr/time_off.rst:872 -msgid "A new time off request can be made from this view. Click the :guilabel:`New` button to :ref:`request time off `." +#: ../../content/applications/hr/time_off.rst:809 +msgid "A new time off request can be made from this view. Click the :guilabel:`New` button to :doc:`request time off <../hr/time_off/request_time_off>`." msgstr "" -#: ../../content/applications/hr/time_off.rst:878 +#: ../../content/applications/hr/time_off.rst:815 msgid "My allocations" msgstr "" -#: ../../content/applications/hr/time_off.rst:880 +#: ../../content/applications/hr/time_off.rst:817 msgid "To view a list of all the user's allocations, navigate to :menuselection:`Time Off app --> My Time --> My Allocations`. All allocations and requested allocations appear in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:883 +#: ../../content/applications/hr/time_off.rst:820 msgid "The information presented on the :guilabel:`My Allocations` page includes: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Amount`, :guilabel:`Allocation Type`, and :guilabel:`Status`." msgstr "" -#: ../../content/applications/hr/time_off.rst:887 +#: ../../content/applications/hr/time_off.rst:824 msgid "A new allocation request can be made from this view, as well. Click the :guilabel:`New` button to :ref:`request an allocation `." msgstr "" -#: ../../content/applications/hr/time_off.rst:895 +#: ../../content/applications/hr/time_off.rst:832 msgid "The reporting feature allows users to view time off for their team, either by employee or type of time off. This allows users to see which employees are taking time off, how much time off they are taking, and what time off types are being used." msgstr "" -#: ../../content/applications/hr/time_off.rst:899 +#: ../../content/applications/hr/time_off.rst:836 msgid "Any report can be added to a spreadsheet through the *Insert in Spreadsheet* button that appears in the top-left of a report. If the *Documents* application is installed, an option to add the report to a spreadsheet appears. If not, the report can be added to a *Dashboard*." msgstr "" -#: ../../content/applications/hr/time_off.rst:904 +#: ../../content/applications/hr/time_off.rst:841 msgid "By employee" msgstr "" -#: ../../content/applications/hr/time_off.rst:906 +#: ../../content/applications/hr/time_off.rst:843 msgid "To view a report of employee time off requests, navigate to :menuselection:`Time Off app --> Reporting --> by Employee`." msgstr "" -#: ../../content/applications/hr/time_off.rst:909 +#: ../../content/applications/hr/time_off.rst:846 msgid "The default report presents the current year's data in a list view, displaying all the employees in alphabetical order. Each employee's line is collapsed by default. To expand a line, click anywhere on the line." msgstr "" -#: ../../content/applications/hr/time_off.rst:913 +#: ../../content/applications/hr/time_off.rst:850 msgid "The view expands, and has the time off requests organized by time off type. Click anywhere on a time off type line to expand it, and view all the individual time off requests that fall under that type." msgstr "" -#: ../../content/applications/hr/time_off.rst:916 +#: ../../content/applications/hr/time_off.rst:853 msgid "The information shown in the list includes: the :guilabel:`Employee` name, :guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." msgstr "" @@ -10633,7 +11012,7 @@ msgstr "" msgid "Report of time off, shown by each employee in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:924 +#: ../../content/applications/hr/time_off.rst:861 msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that specific way. The various options are a :guilabel:`List` (the default view), :guilabel:`Graph`, :guilabel:`Pivot` table, or :guilabel:`Calendar` view." msgstr "" @@ -10641,20 +11020,19 @@ msgstr "" msgid "The various other views highlighted, for the employee time off report." msgstr "" -#: ../../content/applications/hr/time_off.rst:933 -#: ../../content/applications/hr/time_off.rst:960 +#: ../../content/applications/hr/time_off.rst:870 msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." msgstr "" -#: ../../content/applications/hr/time_off.rst:938 +#: ../../content/applications/hr/time_off.rst:875 msgid "By type" msgstr "" -#: ../../content/applications/hr/time_off.rst:940 +#: ../../content/applications/hr/time_off.rst:877 msgid "To view a list of all time off, organized by time off type, navigate to :menuselection:`Time Off app --> Reporting --> by Type`. This shows all time off requests in a default bar chart." msgstr "" -#: ../../content/applications/hr/time_off.rst:943 +#: ../../content/applications/hr/time_off.rst:880 msgid "Hover over a bar to view the :guilabel:`Duration (Days)` of that specific time off type." msgstr "" @@ -10663,14 +11041,110 @@ msgid "The various time off types, and how many days requested, in a bar chart. "highlighted in a red box." msgstr "" -#: ../../content/applications/hr/time_off.rst:950 +#: ../../content/applications/hr/time_off.rst:887 msgid "Click on a bar to go to a detailed list view of all the time off requests for that time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:952 +#: ../../content/applications/hr/time_off.rst:889 msgid "Each request is listed, with the following information displayed: the :guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the :guilabel:`Description`." msgstr "" -#: ../../content/applications/hr/time_off.rst:956 +#: ../../content/applications/hr/time_off.rst:893 msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that way. The various options are a :guilabel:`Graph` (the default view), :guilabel:`List`, or :guilabel:`Pivot` table." msgstr "" + +#: ../../content/applications/hr/time_off.rst:897 +msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports, and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:902 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "Once time off has been allocated to an employee, a request to use it can be submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "Time off can be requested in one of two ways: either from the main *Time Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view (:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "To create a new request for time off, click the :guilabel:`New` button on either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "Both :guilabel:`New` buttons allow the user to request time off, but when requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request form appears in a pop-up window. When requested from the :guilabel:`My Time Off` list view, the screen navigates to a new time off request page, instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "Enter the following information on the :guilabel:`New Time Off` request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid ":guilabel:`Time Off Type`: select the type of time off being requested from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid ":guilabel:`Dates`: enter the dates that the time off falls under. There are two fields to populate: the start and end dates. Click on either date field and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "Click on the start date, then click on the end date. The selected start and end dates are circled, and the dates between them are highlighted (if applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "If only requesting time off for a single day, click on the start date, then click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "The selected dates now populate the two portions of the :guilabel:`Dates` field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "If the selected :guilabel:`Time Off Type` is configured to have the time off taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid ":guilabel:`Half Day`: if the time off request is for a half day, tick this checkbox. When this is selected, the second date field disappears, and is replaced with a drop-down menu. From that drop-down menu, select either :guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid ":guilabel:`Custom Hours`: if the time off requested is not a whole or half day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` field appears beneath this option. Using the drop-down menu, select the start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid ":guilabel:`Duration`: this field updates automatically once the :guilabel:`Date` section is completed. If the :guilabel:`Date` section is modified, this section automatically updates to reflect the total time off requested. This field is in either hours or days, depending on how the selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid ":guilabel:`Description`: enter a description for the time off request. This should include any details that managers and approvers may need to approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid ":guilabel:`Supporting Document`: this field only appears if the :guilabel:`Time Off Type` selected allows for the attachment of documents. Click the :guilabel:`Attach File` button, and a file explorer window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "Navigate to the desired files that should be attached, select them, then click The :guilabel:`Open` button. The files then appear on the time off request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button to save the information, and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "If the form was completed from the :guilabel:`My Time Off` list view, the information is automatically saved as it is entered. However, the form can be saved manually at any time by clicking the :icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "A time off request form filled out for an employee home sick for two days with the flu." +msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 5a2250c41..6ad767252 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 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 \n" "Language-Team: LANGUAGE \n" @@ -17,7 +17,7 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../content/applications/inventory_and_mrp.rst:5 -msgid "Inventory & MRP" +msgid "Supply Chain" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode.rst:8 @@ -502,7 +502,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:195 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:20 msgid "Location" msgstr "" @@ -1139,14 +1139,16 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:14 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:53 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:21 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:35 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:38 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:19 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:36 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:36 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:16 @@ -1161,16 +1163,23 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:21 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:104 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:15 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:46 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:65 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:45 #: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:13 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:32 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:23 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:41 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:52 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:24 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:40 #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:11 #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:15 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:26 @@ -2624,6 +2633,8 @@ msgid "When no route is selected, Odoo selects the :guilabel:`Route` specified i msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:170 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:182 msgid "Manual" msgstr "" @@ -2668,10 +2679,10 @@ msgid "The current date is February 20th, and the *delivery date* on a sales ord msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:214 -msgid "The :ref:`vendor lead time ` is four days, and the :ref:`purchase security lead time ` is one day." +msgid "The :ref:`vendor lead time ` is four days, and the :ref:`purchase security lead time ` is one day." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:217 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:218 msgid "When the :guilabel:`Visibility Days` field of the reordering rule is set to zero, the product appears on the replenishment dashboard five days before the delivery date, which, in this case, is February 27th." msgstr "" @@ -2679,27 +2690,27 @@ msgstr "" msgid "Graphic representing when the need appears on the replenishment dashboard: Feb 27th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:225 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:226 msgid "To see the product on the replenishment dashboard for the current date, February 20, set the :guilabel:`Visibility Days` to `7.00`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:228 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:229 msgid "To determine the amount of visibility days needed to see a product on the replenishment dashboard, subtract *today's date* from the *date the need appears* on the replenishment dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:231 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:232 msgid "Visibility~days = Need~appears~date - Today's~date" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:236 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:237 msgid "Referring to the example above, today's date is February 20th, and the need for the product appears on February 27th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:239 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:240 msgid "(February 27 - February 20 = 7 days)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:241 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:242 msgid "Incorrectly setting the :guilabel:`Visibility Days` fewer than seven days in this case results in the need **not** appearing on the replenishment dashboard." msgstr "" @@ -2707,27 +2718,27 @@ msgstr "" msgid "Show the replenishment dashboard with the correct and incorrect visibility days set." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:251 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:252 msgid "Route" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:253 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:254 msgid "Odoo allows for multiple routes to be selected under the :guilabel:`Inventory` tab on each product form. For instance, it is possible to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling the functionality of both routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:257 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:258 msgid "Odoo also enables users to set a preferred route for a product's reordering rule. This is the route that the rule defaults to, if multiple are selected. To select a preferred route, begin by navigating to :menuselection:`Inventory app --> Configuration --> Reordering Rules`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:261 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:262 msgid "By default, the :guilabel:`Route` column is hidden on the :guilabel:`Reordering Rules` page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:263 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:264 msgid "Reveal the :guilabel:`Route` column by selecting the :guilabel:`(slider)` icon to the far-right of the column titles, and checking the :guilabel:`Route` option from the drop-down menu that appears." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:266 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:267 msgid "Click inside of the column on the row of a reordering rule, and a drop-down menu shows all available routes for that rule. Select one to set it as the preferred route." msgstr "" @@ -2735,7 +2746,7 @@ msgstr "" msgid "Select a preferred route from the drop-down." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:274 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:275 msgid "If multiple routes are enabled for a product but no preferred route is set for its reordering rule, the product is reordered using the selected route that is listed first on the :guilabel:`Inventory` tab of the product form." msgstr "" @@ -3163,7 +3174,7 @@ msgid "Product tracking" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:3 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:100 msgid "Assign serial numbers" msgstr "" @@ -3177,7 +3188,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:21 msgid ":doc:`serial_numbers`" msgstr "" @@ -3198,42 +3209,42 @@ msgid "in the :ref:`Open: Stock move window ` for a product tracked by lot/serial numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:24 msgid "when making an inventory adjustment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:32 msgid "Display the Detailed Operations smart button and bulleted list icon on a receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:32 msgid "Display the **Detailed Operations** smart button and bulleted list icon on a receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:37 msgid "To assign serial numbers to products, activate the :guilabel:`Lots and Serial Numbers` feature in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:40 msgid "Then, in the :guilabel:`Inventory` tab of an item's product form, set the :guilabel:`Tracking` field to :guilabel:`By Unique Serial Number`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:44 msgid ":ref:`Enable serial numbers `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:45 msgid ":ref:`Track products by serial numbers `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:49 msgid "Next, enable creating new serial numbers by going to :menuselection:`Inventory app --> Configuration --> Operations Types`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:52 msgid "From the :guilabel:`Operations Types` page, select the desired operation type (e.g. :guilabel:`Receipts`, :guilabel:`Delivery Orders`, or :guilabel:`Manufacturing`), and select the :guilabel:`Create New` option in the :guilabel:`Lots/Serial Numbers` section of the operation type's configuration page." msgstr "" @@ -3241,15 +3252,15 @@ msgstr "" msgid "Show \"Create New\" option is selected on the Receipts operation type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:64 msgid "Detailed Operations" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:66 msgid "Serial numbers can be assigned to products when entering stock for the first time, from the :guilabel:`Detailed Operations` page on the receipt. Receipts can be accessed by navigating to :menuselection:`Inventory app --> Operations --> Receipts`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:71 msgid "Serial numbers can **not** be assigned to products on a request for quotation (RfQ) or purchase order (PO) — **only** on a receipt." msgstr "" @@ -3257,19 +3268,19 @@ msgstr "" msgid "Show the purchase order and the Receipt smart button" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:78 msgid "Screenshot of a \"Purchase Order\" with the \"Receipt\" smart button at the top." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:80 msgid "To record an item's serial number before receiving the item, follow the steps in the next sections to assign serial numbers, but do **not** click the receipt's :guilabel:`Validate` button, until the products are received from the vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:84 msgid "Assign a single serial number to a product by clicking the :guilabel:`Detailed Operations` smart button on a receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:87 msgid "In the :guilabel:`Lot/Serial Number Name` column, manually type in the serial number for a single product." msgstr "" @@ -3277,11 +3288,11 @@ msgstr "" msgid "Add a line on the Detailed Operations page to assign serial numbers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:94 msgid "When finished, click the receipt's breadcrumbs, and the assigned serial numbers are automatically saved." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:102 msgid "To generate new serial numbers in a sequence, click the :guilabel:`+ (plus)` icon in the :ref:`product line `." msgstr "" @@ -3289,11 +3300,11 @@ msgstr "" msgid "Show the plus icon in the product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:110 msgid "If the icon is not visible, ensure the :guilabel:`Create New` option is selected in the :ref:`receipt's configuration page `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:113 msgid "Doing so opens the :guilabel:`Assign Serial Numbers` pop-up window. The :guilabel:`Number of SN` field is auto-filled based on the product quantity requiring serial numbers. Manually input the first serial number in the :guilabel:`First SN` field, and click :guilabel:`Assign Serial Numbers` to generate a sequence of serial numbers based on the first serial number entered." msgstr "" @@ -3301,19 +3312,19 @@ msgstr "" msgid "Show Assign Serial numbers pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:125 msgid "Stock move pop-up window" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:125 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:127 msgid "For various methods of assigning serial numbers in bulk, click the :guilabel:`⦙≣ (bulleted list)` icon in the :ref:`product line ` of a receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:132 msgid "Add a line" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:134 msgid "In the :guilabel:`Open: Stock move` pop-up window that appears, manually input the serial numbers in the :guilabel:`Lot/Serial Number` column." msgstr "" @@ -3321,11 +3332,11 @@ msgstr "" msgid "Add a line on the Stock move pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:142 msgid "Generate Serials" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:142 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:144 msgid "Assign multiple serial numbers at once by clicking the :guilabel:`Generate Serials/Lots` button in the :guilabel:`Open: Stock move` pop-up window." msgstr "" @@ -3333,31 +3344,31 @@ msgstr "" msgid "Show generate serials button." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:151 msgid "Doing so opens the :guilabel:`Generate Serial numbers` pop-up window, where the first serial number is entered in the :guilabel:`First SN` field to generate a sequence of serial numbers, based on the first serial number entered." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:153 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:155 msgid "For more details on how to fill in this pop-up window, :ref:`refer to this section `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:157 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:159 msgid "Import Serials" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:159 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:161 msgid "Assign multiple serial numbers at once by clicking the :guilabel:`Import Serials/Lots` button in the :guilabel:`Open: Stock move` pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:165 msgid "If the button is not visible, ensure the :guilabel:`Create New` option is selected in the :ref:`receipt's configuration page `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:168 msgid "Doing so opens the :guilabel:`Import Lots` pop-up window. Enter each serial number on a separate line in the :guilabel:`Lots/Serial numbers` text field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:170 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:172 msgid "Copy/paste serial numbers from an existing excel spreadsheet and add them to the :guilabel:`Lots/Serial numbers` text field." msgstr "" @@ -3365,23 +3376,24 @@ msgstr "" msgid "Show excel sheet to copy serial numbers from." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:179 msgid "Tick the :guilabel:`Keep current lines` checkbox to add serial numbers to the list of products, and serial numbers in the :guilabel:`Lot/Serial Number` table, in the :guilabel:`Open: Stock move` pop-up window. To replace the serial numbers in the list, leave the :guilabel:`Keep current lines` option unchecked." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:182 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:184 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:146 msgid "Finally, click :guilabel:`Generate`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:187 msgid "For a receipt with a :guilabel:`Demand` of `3.00` products, one product has already been assigned a serial number in the :guilabel:`Open: Stock move` pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:188 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:190 msgid "So, in the :guilabel:`Import Lots` pop-up window, two serial numbers, `124` and `125` are assigned to the remaining products by entering the following in the :guilabel:`Lots/Serial numbers` input field:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:197 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:199 msgid "The :guilabel:`Keep current lines` option is selected to add these two serial numbers **in addition** to the serial number, `123`, that has already been assigned." msgstr "" @@ -3410,7 +3422,7 @@ msgid ":doc:`lots`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:21 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:22 msgid "Enable lots & serial numbers" msgstr "" @@ -3461,6 +3473,7 @@ msgid "Serial numbers can contain many different types of characters: numbers, l msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:67 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:343 msgid "Traceability" msgstr "" @@ -3737,6 +3750,7 @@ msgid "To sell perishable products with expiration dates, the :guilabel:`Removal msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:226 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:189 msgid ":doc:`../../warehouses_storage/removal_strategies`" msgstr "" @@ -3760,31 +3774,31 @@ msgstr "" msgid "Group by expiration dates on lots and serial numbers page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:245 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:247 msgid "Expiration alerts" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:247 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:249 msgid "To see expiration alerts, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:249 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:251 msgid "Then, click into a :guilabel:`Lot/Serial Number` with perishable products. Doing so reveals the serial number detail form. On the serial number detail form, click the :guilabel:`Dates` tab to see all expiration information related to the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:253 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:255 msgid "To edit the form, click :guilabel:`Edit` in the upper-left corner of the form, then change the :guilabel:`Expiration Date` to today's date (or earlier), and click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:257 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:259 msgid "After saving, the lot number form displays a red :guilabel:`Expiration Alert` at the top of the form to indicate that the products in this lot are either expired or expiring soon. From here, click back to the :guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:261 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:263 msgid "To see the new expiration alert, or any expiration alerts for products that are expired (or will expire soon), remove all of the search filters from the :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:265 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:267 msgid "Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." msgstr "" @@ -3793,294 +3807,396 @@ msgid "Expiration alert for product past the expiration date." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:3 -msgid "Use lots to manage groups of products" +msgid "Lot numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:5 -msgid "*Lots* are one of the two ways to identify and track products in Odoo. A lot usually indicates a specific batch of an item that was received, is currently stored, or was shipped from a warehouse, but can also pertain to a batch of products manufactured in-house, as well." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:10 +msgid "*Lots* are one of the two ways to identify and track products in Odoo. They typically represent a specific batch of products that were received, stored, shipped, or manufactured in-house." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:9 -msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps to identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their lifecycles." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:13 +msgid "Manufacturers assign lot numbers to groups of products sharing common properties, facilitating end-to-end traceability through their lifecycles." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:14 -msgid "Lots are useful for products that are manufactured or received in large quantities (such as clothes or food), and can be used to trace a product back to a group. This is especially useful when managing product recalls or expiration dates." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:16 +msgid "Lots are useful for managing large quantities of manufactured or received products, aiding in tracing items back to their group, particularly for product recalls or :doc:`expiration dates `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 -msgid "To track products using lots, the *Lots & Serial Numbers* feature must be enabled. Go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:26 +msgid "To track products using lots, enable the *Lots & Serial Numbers* feature. Go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and tick the checkbox next to :guilabel:`Lots & Serial Numbers`. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:36 -msgid "Track products by lots" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:32 +msgid ":doc:`Tracking expiration dates `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:38 -msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be configured to be tracked using lots. To do this, go to the :menuselection:`Inventory app --> Products --> Products`, and choose a product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:33 +msgid ":ref:`Print GS1 barcodes for lots and serial numbers `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:42 -msgid "Once on the product form, click :guilabel:`Edit` to make changes to the form. Then, click the :guilabel:`Inventory` tab. In the :guilabel:`Traceability` section, click :guilabel:`By Lots`. Then, click :guilabel:`Save` to save changes. Existing or new lot numbers can now be assigned to newly-received or manufactured batches of this product." +msgid "Track by lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:44 +msgid "Once the :guilabel:`Lots & Serial Numbers` feature is activated, configure individual products to be tracked using lots. To do this, go to :menuselection:`Inventory app --> Products --> Products`, and choose a product to configure." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:48 -msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed to assign lot numbers to the existing stock." +msgid "On the product form, go to the :guilabel:`Inventory` tab. In the :guilabel:`Traceability` section, select the :guilabel:`By Lots` option in the :guilabel:`Tracking` field. Now, new or existing lot numbers can be assigned to newly-received or manufactured batches of this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:49 +msgid ":doc:`expiration_dates`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:56 +msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, a warning message appears. Use an :doc:`inventory adjustment ` to assign lot numbers to existing products in stock." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 msgid "Enabled tracking by lots feature on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:56 -msgid "Create new lots for products already in stock" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:65 +msgid "Assign lots for shipping and receiving" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:58 -msgid "New lots can be created for products already in stock with no assigned lot number. To do this, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a separate page where a new :guilabel:`Lot/Serial Number` is generated automatically." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:67 +msgid "Assign new lot numbers to :ref:`incoming goods ` on the receipt form. When shipping :ref:`outgoing goods `, select products with specific lot numbers on the delivery order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:64 -msgid "While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:68 -msgid "Once the new :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:72 -msgid "This form also provides the option to adjust the :guilabel:`Quantity`, assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and assign this specific lot or serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:75 +msgid "On receipts" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:77 -msgid "A detailed description of this specific lot or serial number can also be added in the :guilabel:`Description` tab below." +msgid "Assigning new or existing lot numbers to incoming goods can be done directly on receipts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:80 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:83 -msgid "When all desired configurations are complete, click the :guilabel:`Save` button to save all changes." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:79 +msgid "To begin, go to the :menuselection:`Purchase` app to `create and confirm `_ a |PO| for products tracked by lot numbers. Then, click the :guilabel:`Receipt` smart button that appears at the top of the page to navigate to the warehouse receipt form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 -msgid "New lot number creation form with assigned product." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:85 +msgid "Alternatively, navigate to an existing receipt by going to the :menuselection:`Inventory` app, clicking the :guilabel:`Receipts` Kanban card, and choosing the desired receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:86 -msgid "After a new lot number has been created, saved, and assigned to the desired product, navigate back to the product form in the :menuselection:`Inventory` app, by going to :menuselection:`Products --> Products`, and selecting the product to which this newly-created lot number was just assigned." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:89 +msgid "Clicking :guilabel:`Validate` before assigning a lot number triggers an error, indicating that a lot number **must** be assigned before validating the receipt." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:90 -msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new lot number. When additional quantity of this product is received or manufactured, this new lot number can be selected and assigned to it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:95 -msgid "Manage lots for shipping and receiving" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:97 -msgid "Lot numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, lot numbers are assigned directly on the purchase order form. For outgoing goods, lot numbers are assigned directly on the sales order form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:104 -msgid "Manage lots on receipts" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:106 -msgid "Assigning lot numbers to **incoming** goods can be done directly from the purchase order (PO)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:108 -msgid "To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:111 -msgid "On this :abbr:`RFQ (request for quotation)`, fill out the necessary information by adding a :guilabel:`Vendor`, and adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` (under the :guilabel:`Products` tab)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:115 -msgid "Choose the desired quantity of the product to order by changing the number in the :guilabel:`Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:118 -msgid "Once the :abbr:`RFQ (request for quotation)` has been filled out, click :guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is confirmed, it becomes a :guilabel:`Purchase Order`, and a :guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:124 -msgid "Clicking :guilabel:`Validate` before assigning a lot number to the ordered product quantities will result in a :guilabel:`User Error` pop-up. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a lot number being assigned." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 msgid "Add lot/serial number user error popup." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:133 -msgid "From here, click the :guilabel:`Additional Options` menu, represented by a :guilabel:`hamburger (four horizontal lines)` icon, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:137 -msgid "In this pop-up, configure a number of different fields, including the assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:140 -msgid "There are two ways to assign lot numbers: **manually** and **copy/paste**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:142 -msgid "**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the location the products will be stored in under the :guilabel:`To` column. Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` quantity." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 -msgid "Assign lot number detailed operations popup." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:151 -msgid "If quantities should be processed in multiple locations and lots, click :guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for additional quantities. Repeat until the :guilabel:`Quantity Done` matches the :guilabel:`Demand`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:155 -msgid "**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with all of the lot numbers received from the supplier (or manually chosen to assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column. From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the lot number lines." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 -msgid "List of lot numbers copied on excel spreadsheet." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:165 -msgid "Once all product quantities have been assigned a lot number, click :guilabel:`Confirm` to close the pop-up. Then, click :guilabel:`Validate`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:168 -msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #` assigned, and more." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:174 -msgid "Manage lots on delivery orders" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:176 -msgid "Assigning lot numbers to **outgoing** goods can be done directly from the sales order (SO)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:178 -msgid "To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app --> Create`. Doing so reveals a new, blank quotation form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:181 -msgid "On this blank quotation form, fill out the necessary information by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:185 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:195 -msgid "Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:187 -msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, it becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:191 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:201 -msgid "Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific :abbr:`SO (sales order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:194 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:204 -msgid "From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:198 -msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with the full :guilabel:`Reserved` quantity taken from that specific lot (if there is enough stock in that particular lot)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:202 -msgid "If there is insufficient stock in that lot, or if partial quantities of the :guilabel:`Demand` should be taken from multiple lots, change the quantity in the :guilabel:`Done` column to only include that specific part of the total quantity." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:207 -msgid "The lot automatically chosen for delivery orders varies, depending on the selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will also depend on the quantity ordered, and if there is enough quantity in one lot to fulfill the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:213 -msgid ":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:215 -msgid "Then, click :guilabel:`Add a line`, select an additional (different) :guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click the :guilabel:`Validate` button to deliver the products." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:96 +msgid "On the receipt form, on the product line in the :guilabel:`Operations` tab, select the |list| icon to the right of the product that is tracked by lot numbers." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 -msgid "Detailed operations popup for source lot number on sales order." +msgid "Show the bulleted list icon on the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:103 +msgid "Doing so opens the :guilabel:`Open: Stock move` pop-up window, where the :guilabel:`Lot/Serial Number` and :guilabel:`Quantity` are assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:106 +msgid "The two ways to assign lot numbers: **manually** and **importing**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:109 +msgid "Manual assignment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:111 +msgid "To manually assign lot numbers, click :guilabel:`Add a line`. Input the :guilabel:`Lot/Serial Number`, :guilabel:`Store To` location for the lot, :guilabel:`Quantity`, and :guilabel:`Destination Package`, if any." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:116 +msgid "To assign multiple lot numbers, or store to multiple locations, click :guilabel:`Add a line`, and type a new :guilabel:`Lot/Serial Number` for additional quantities. Repeat until the total in the :guilabel:`Quantity` column matches the :guilabel:`Demand` at the top." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Assign lot number detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:125 +msgid "Import lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:127 +msgid "In the :guilabel:`Open: Stock move` pop-up window, click :guilabel:`Import Serials/Lots`, then paste the bulk lot numbers, in the :guilabel:`Lots/Serial numbers` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:134 +msgid "List of lot numbers copied on excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:134 +msgid "List of lot numbers copied on *Google* spreadsheets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:140 +msgid "Lot numbers copied to the lot number line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:140 +msgid "Lot numbers pasted to the \"Lots/Serial numbers\" field, in the **Import Lots** pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:142 +msgid "Tick the :guilabel:`Keep current lines` checkbox to generate *additional* lot numbers in the :guilabel:`Open: Stock move` pop-up window. To replace the lot numbers in the list, leave the :guilabel:`Keep current lines` option unticked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:148 +msgid "Once all product quantities have been assigned a lot number, click :guilabel:`Save` to close the pop-up window. Then, click :guilabel:`Validate` on the receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:152 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:200 +msgid ":ref:`Traceability report for lot numbers `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:157 +msgid "On delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:159 +msgid "Odoo makes it possible to specify which lot numbers for a product are chosen for outgoing shipment on a delivery order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:162 +msgid "To begin, create or select an existing quotation from the :menuselection:`Sales` app. After confirming the |SO|, the :guilabel:`Delivery` smart button becomes available. Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:167 +msgid "Alternatively, navigate to delivery orders by going to the :menuselection:`Inventory` app, and clicking the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:170 +msgid "Clicking the :guilabel:`Delivery` smart button opens the the delivery order form, where lot numbers are picked for delivery. In the :guilabel:`Operations` tab, click the |list| icon to the right of the product that is tracked by lot numbers. Clicking that icon reveals a :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:175 +msgid "In the pop-up window, the chosen lot number and its storage location is displayed in the :guilabel:`Pick From` column, with the with the full :guilabel:`Quantity` taken from that specific lot (if there is enough stock in that particular lot)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:179 +msgid "If there is insufficient stock in that lot, or if partial quantities of the :guilabel:`Demand` should be taken from multiple lots, change the :guilabel:`Quantity` directly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:183 +msgid "The lot automatically chosen for delivery orders varies, depending on the selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It also depends on the ordered quantity, and whether the lot's on-hand quantity is enough to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:191 +msgid "Repeat the above steps to select enough lots to fulfill the :guilabel:`Demand`, and click :guilabel:`Save` to close the pop-up window. Lastly, click the :guilabel:`Validate` button on the |DO| to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Popup for source lot number on sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:203 +msgid "Lot management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:205 +msgid "Manage and view existing lot numbers for products in the :guilabel:`Lot/Serial Numbers` dashboard by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:208 +msgid "By default, lot numbers are grouped by product, and selecting the drop-down menu for each product displays the existing lot numbers. Select a lot number to :ref:`modify or add details ` linked to the lot. Lot numbers can also be :ref:`created ` from this page, by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:218 +msgid "Show the \"Lot/Serial Number\" dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:218 +msgid "Display lot numbers, grouped by products, on the **Lot/Serial Number** dashboard." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:223 -msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." +msgid "Modify lot" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:228 -msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order, if the product quantities shared the same lot number." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:225 +msgid "Clicking a lot from the :guilabel:`Lot/Serial Number` dashboard reveals a separate page where additional information can be provided about the lot." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:232 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:229 +msgid "Odoo automatically generates a new :guilabel:`Lot/Serial Number` to follow the most recent number. However, it can be edited, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number to any desired one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:233 +msgid "On the lot number form, the following fields can be modified:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:235 +msgid ":guilabel:`Lot/Serial Number`: change the lot number linked to the :guilabel:`Product`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:236 +msgid ":guilabel:`Internal Reference`: records an alternative lot/serial number used within the warehouse that differs from the one used by the supplier manufacturer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:238 +msgid ":guilabel:`Company`: specify the company where the lot number is available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:239 +msgid ":guilabel:`Description`: add extra details about the lot or serial number in this text field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:242 +msgid "On existing lots, the :guilabel:`Product` and :guilabel:`On Hand Quantity` fields **cannot** be modified, as the lot numbers are linked with existing stock moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Show the lot number form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:250 +msgid ":doc:`Set expiration dates for lots `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:253 +msgid "Add property" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:255 +msgid "To add custom fields to lots for enhanced traceability, there are two methods of adding properties on a lot number form:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:258 +msgid "Click the :icon:`fa-cog` :guilabel:`(cog)` icon at the top-left of the page, then select :icon:`fa-cogs` :guilabel:`Add Properties` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:260 +msgid "Click the :icon:`fa-plus` :guilabel:`Add a Property` button, located below the existing fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:262 +msgid "Name and :doc:`configure the new field <../../../../productivity/knowledge/properties>`. Once finished, enter the property value in the new field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:266 +msgid "The new property, `Wood type`, is added. The value is recorded as `Cherry wood`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "Show the \"Add Properties\" button on a lot number form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:273 +msgid ":doc:`Configuring custom properties <../../../../productivity/knowledge/properties>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:278 +msgid "Reserve lot number for a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:280 +msgid "To create a lot number for a product, begin by going to :menuselection:`Inventory app --> Products --> Lot/Serial Numbers`, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:284 +msgid "Creating a lot number reserves it for a product but **does not** assign it. To assign lot numbers, refer to the section on :ref:`assigning lot numbers on receipts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:289 +msgid "While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field on the lot form, and changing the generated number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:293 +msgid "Once the new :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:298 +msgid "The lot number, `000001`, is created for the product, `Drawer Black`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "New lot number creation form with assigned product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:304 +msgid "After a new lot number has been created, saved, and assigned to the desired product, the lot number is saved as an existing lot number linked to the product, and can be selected when :ref:`assigning lot numbers to products on a receipt `, or when making an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:310 +msgid "After creating the lot number, `000001` appears as an option for `Drawer Black` when assigning lot numbers on the :guilabel:`Inventory Adjustment` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "Show how to assign lot numbers on the Inventory Adjustment page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:318 msgid "Manage lots for different operations types" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:234 -msgid "In Odoo, the creation of new lots is only allowed upon **receiving** products from a purchase order, by default. **Existing** lot numbers cannot be used." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:320 +msgid "By default, new lots can only be created when receiving products, and existing lot numbers cannot be used. For sales orders, only existing lot numbers can be utilized, and new ones cannot be created on the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:237 -msgid "For sales orders, the opposite is true: new lot numbers cannot be created on the delivery order, only existing lot numbers can be used." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:324 +msgid "To change the ability to use new (or existing) lot numbers on any operation type, go to the :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired operation type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:240 -msgid "To change the ability to use new (or existing) lot numbers on any operation type, go to the :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:244 -msgid "For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:249 -msgid "For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. Be sure to click the :guilabel:`Save` button to save all changes." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:328 +msgid "On the operation type form, under the :guilabel:`Lots/Serial Numbers` section, tick the :guilabel:`Create New` checkbox to enable new lot numbers to be created during this operation type. Choose :guilabel:`Use Existing ones` if only existing lot numbers can be selected." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 msgid "Enabled traceability setting on operations type form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:258 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:337 msgid "For inter-warehouse transfers involving products tracked by lots, it can be useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for warehouse receipts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:262 -msgid "Lots traceability" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:345 +msgid "Manufacturers and companies can refer to traceability reports to see the entire lifecycle of a product: where it came from, when it arrived, where it was stored, who it went to (and when)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:264 -msgid "Manufacturers and companies can refer to traceability reports to see the entire lifecycle of a product: where (and when) it came from, where it was stored, and who (and when) it went to." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:267 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:348 msgid "To see the full traceability of a product, or group by lots, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :menuselection:`Lots/Serial Numbers` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:271 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:352 msgid "From here, products with lot numbers assigned to them will be listed by default, and can be expanded to show the lot numbers those products have assigned to them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:274 -msgid "To group by lots (or serial numbers), begin by removing any filters in the search bar. Then, click the :guilabel:`Group By` drop-down, select :guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from the drop-down menu. Then, click :guilabel:`Apply`." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:355 +msgid "To group by lots, begin by removing any filters in the :guilabel:`Search...` bar. Then, click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon to open a drop-down menu of :guilabel:`Filters`, :guilabel:`Group By` options, and :guilabel:`Favorites`. Under the :guilabel:`Group By` section, click the :guilabel:`Add Custom Group` option, and select :guilabel:`Lot/Serial Number` from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:278 -msgid "Doing so displays all existing lots and serial numbers, and can be expanded to show all quantities of products with that assigned number." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:361 +msgid "Doing so reorganizes all the records on the page to display all existing lots and serial numbers, and can be expanded to show all quantities of products with that assigned number." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 msgid "Lots and serial numbers traceability report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:286 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:369 +msgid "Traceability report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:371 +msgid "To view a full stock moves report for a lot number, select the lot number line from the :guilabel:`Lots/Serial Number` dashboard. On the lot number form, click the :guilabel:`Traceability` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Show the Traceability Report for a lot, that displays the stock moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:380 msgid ":doc:`differences`" msgstr "" @@ -4435,6 +4551,103 @@ msgstr "" msgid "Packaging can be used in conjunction with Odoo :ref:`Barcode `. When receiving products from suppliers, scanning the packaging barcode automatically adds the number of units in the packaging to the internal count of the product." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:3 +msgid "Reassign lot/serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:5 +msgid "Changing a product's tracking settings to use lots or serial numbers, *after* storing products in Odoo without them, can lead to inconsistent records. Follow this documentation to learn how to use an inventory adjustment to assign lot or serial numbers to products that were not originally assigned lots." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:-1 +msgid "Warning message: products in stock have no lot/serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:15 +msgid "This document outlines the process of using two inventory adjustments: one to remove incorrect records *without* lot numbers, and another to save the quantities *with* the lot numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:19 +msgid ":doc:`Set up and use lot numbers `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:20 +msgid ":doc:`Set up serial numbers `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:21 +msgid ":doc:`Use serial numbers `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:24 +msgid "Change on-hand quantity to zero" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:26 +msgid "To change the product's settings to track by lots or serial numbers, begin by navigating to :menuselection:`Inventory app --> Products --> Products`, and select the intended product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:29 +msgid "Next, click the product's :guilabel:`On Hand` smart button to open the :guilabel:`Update Quantity` page. In the :guilabel:`On Hand Quantity` column, change the value to zero." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:33 +msgid "If the product is stored in multiple locations, make sure the **total** on hand quantity at **all** locations is zero." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:-1 +msgid "Show the Inventory Adjustments model, highlighting the \"On Hand Quantity\" field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:41 +msgid "Change traceability setting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:43 +msgid "Return to the product form (:menuselection:`Inventory app --> Products --> Products`), and switch to the :guilabel:`Inventory` tab. In the :guilabel:`Traceability` section, change the :guilabel:`Tracking` option from :guilabel:`No Tracking` to :guilabel:`By Lots` or :guilabel:`By Unique Serial Number`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:-1 +msgid "Enable lots and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:56 +msgid "Restore on-hand quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:58 +msgid "After manually changing the on-hand quantity to zero and changing the :guilabel:`Tracking` setting to lots or serial numbers, restore the quantities by clicking the :guilabel:`On Hand` smart button from the desired product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:62 +msgid "On the :guilabel:`Update Quantity` page, because the on-hand quantity had been previously changed to zero, a :guilabel:`No Stock On Hand` warning appears on the page. From here, click the :guilabel:`New` button in the top-left corner. Doing so reveals a new, modifiable line on the :guilabel:`Update Quantity` page. Then, input a desired lot number in the :guilabel:`Lot/Serial Number` field, and adjust the :guilabel:`On Hand Quantity` to its original value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:69 +msgid ":doc:`../../warehouses_storage/inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:-1 +msgid "Fill in the \"Lot/Serial Number\" and \"On Hand Quantity\" field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:76 +msgid "To find the original quantity, and adjust the :guilabel:`On Hand Quantity` accordingly, after assigning a new lot or serial number, click the :icon:`fa-pencil` :guilabel:`(pencil)` icon in the :guilabel:`On Hand Quantity` column. Then, click the :icon:`fa-history` :guilabel:`History` button on the far-right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:-1 +msgid "Show the \"History\" button on the Inventory Adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:85 +msgid "The inventory adjustment that changed the on-hand quantity to zero is displayed in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/reassign.rst:0 +msgid "Show the history entry." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:3 msgid "Use serial numbers to track products" msgstr "" @@ -4511,6 +4724,10 @@ msgstr "" msgid "A detailed description of this specific lot/serial number can also be added in the :guilabel:`Description` tab below." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:83 +msgid "When all desired configurations are complete, click the :guilabel:`Save` button to save all changes." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 msgid "New serial number created for existing product stock." msgstr "" @@ -4627,10 +4844,22 @@ msgstr "" msgid "To create an :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing so reveals a new, blank quotation form. On this blank quotation form, fill out the necessary information, by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab), by clicking :guilabel:`Add a product`." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:195 +msgid "Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:197 msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, the quotation becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:201 +msgid "Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:204 +msgid "From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:208 msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with each product of the total :guilabel:`Reserved` quantity listed with their unique serial numbers (most likely listed in sequential order)." msgstr "" @@ -4878,6 +5107,8 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:94 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:79 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:80 msgid "Create purchase order" msgstr "" @@ -5082,12 +5313,12 @@ msgid "After cancelling the shipping request, you can change the carrier you wan msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:50 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:160 msgid ":doc:`invoicing`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:51 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:161 msgid ":doc:`multipack`" msgstr "" @@ -5218,7 +5449,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:43 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:124 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:24 msgid ":doc:`../setup_configuration/third_party_shipper`" msgstr "" @@ -5348,8 +5579,6 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:35 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:48 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:93 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:130 msgid "Create a sales order" msgstr "" @@ -5401,11 +5630,11 @@ msgstr "" msgid "Print shipping labels" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:8 msgid "Integrate Odoo with :doc:`third-party shipping carriers <../setup_configuration/third_party_shipper>` to automatically generate shipping labels that includes prices, destination addresses, tracking numbers, and barcodes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:15 msgid "To generate labels for a third-party shipping carrier, first :doc:`install the third-party shipping connector <../setup_configuration/third_party_shipper>`. Then, configure and activate the :ref:`delivery method `, being sure to set the :guilabel:`Integration Level` to :guilabel:`Get Rate and Create Shipment` to generate shipping labels. Finally, provide the company's :ref:`source address ` and :ref:`product weights `." msgstr "" @@ -5413,27 +5642,51 @@ msgstr "" msgid "Set the \"Get Rate and Create Shipment\" option." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:33 +msgid "Labels for multi-step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:35 +msgid "For companies using :doc:`two <../daily_operations/receipts_delivery_two_steps>` or :doc:`three step delivery <../daily_operations/delivery_three_steps>`, labels can be triggered to print after validating the picking or packing operation. To do that, go to :menuselection:`Inventory app --> Configuration --> Operations Types`, and choose the desired operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:40 +msgid "On the :guilabel:`Operation Type` configuration page, tick the :guilabel:`Print Label` checkbox. Enabling this feature ensures that the third-party shipping label is printed upon validating this operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:45 +msgid "For :doc:`two-step delivery <../daily_operations/receipts_delivery_two_steps>`, where products are placed directly in packages during picking, companies can print shipping labels during picking instead of delivery. Odoo allows users to enable the :guilabel:`Print Label` feature on the `Pick` operation itself to achieve this flexibility." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:0 +msgid "Enable the \"Print Label\" feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:55 msgid "Print tracking labels" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:32 -msgid "Tracking labels are generated after the delivery order (DO) is validated." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:57 +msgid "Tracking labels are printed when specific operations are validated. By default, validating a delivery order (DO) generates a tracking label in the chatter." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:34 -msgid "When both the *Sales* and *Inventory* apps are installed, begin on the :menuselection:`Sales app`, and proceed to the desired quotation to :ref:`add the shipping cost `, confirm the sales order, and validate the |DO|." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:61 +msgid "For companies using two or three step delivery, refer to the :ref:`printing labels for multi-step delivery ` section to learn how to print the label after validating a picking or packing operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:38 -msgid "If only the *Inventory* app is installed, create :abbr:`DOs (Delivery Orders)` directly in the :menuselection:`Inventory` app , :ref:`add the third-party carrier ` in the :guilabel:`Carrier` field, and validate the |DO|." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:65 +msgid "When both the *Sales* and *Inventory* apps are installed, begin in the :menuselection:`Sales` app, and proceed to the desired quotation or sales order (SO). There, and :ref:`add the shipping cost ` to the order. Then, navigate to the linked |DO| — or another operation type when using multi-step delivery — to validate the operation and print the label." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:71 +msgid "If only the *Inventory* app is installed, create :abbr:`DOs (Delivery Orders)` directly in the :menuselection:`Inventory` app, :ref:`add the third-party carrier ` in the :guilabel:`Carrier` field, and validate the |DO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:79 msgid "Add shipping on quotation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:81 msgid "To generate a tracking label for an order, begin by creating a quotation in :menuselection:`Sales app --> Orders --> Quotations`, clicking :guilabel:`New`, and filling out the quotation form. Then, click the :guilabel:`Add Shipping` button in the bottom-right corner of the quotation." msgstr "" @@ -5441,15 +5694,19 @@ msgstr "" msgid "Show the \"Add Shipping\" button on the quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:56 -msgid "In the resulting pop-up window, select the intended carrier from the :guilabel:`Shipping Method` drop-down menu. Clicking :guilabel:`Get Rate` displays the shipping cost for the customer, via the third-party carrier in the :guilabel:`Cost` field." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:89 +msgid "In the resulting pop-up window, select the intended carrier from the :guilabel:`Shipping Method` drop-down menu. The :guilabel:`Total Order Weight` field is automatically populated, based on the :ref:`weight of products in the order `. Modify this field to overwrite the predicted weight, and use this weight to estimate the cost of shipping." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:94 +msgid "Next, click :guilabel:`Get Rate` to display the shipping cost for the customer, via the third-party carrier in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:98 msgid "If clicking :guilabel:`Get Rate` results in an error, ensure the :ref:`warehouse's address ` and :ref:`weight of products in the order ` are properly configured." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:102 msgid "Click :guilabel:`Add` to add the cost to the quotation, which is listed as the :ref:`configured delivery product `. Finally, click :guilabel:`Confirm` on the quotation, and click the :guilabel:`Delivery` smart button to access the |DO|." msgstr "" @@ -5457,39 +5714,39 @@ msgstr "" msgid "Show \"Get rate\" pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:75 -msgid "For users who do not have the *Sales* app installed, the shipping carrier is specified in a delivery order's :guilabel:`Carrier` field of the :guilabel:`Additional Info` tab." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:112 +msgid "For users who do not have the *Sales* app installed, specify the :guilabel:`Carrier` by going to the :menuselection:`Inventory` app, navigating to the |DO|, and going to the :guilabel:`Additional Info` tab." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:0 msgid "Show the \"Additional Info\" tab of a delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:123 msgid "Validate delivery order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:125 msgid "On a delivery order form, navigate to the :guilabel:`Additional Info` tab to ensure the third-party shipping carrier has been added to the :guilabel:`Carrier` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:129 msgid "If the *Sales* app is not installed, the third-party carrier is set in the :guilabel:`Carrier` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:132 msgid "After the items in the order have been packed, click :guilabel:`Validate` to get the shipping carrier's tracking number, and generate the shipping label." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:136 msgid "Create or select an existing delivery order by going to the :menuselection:`Inventory` app, and selecting the :guilabel:`Delivery Orders` card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:139 msgid "The :guilabel:`Tracking Reference` number is generated in the :guilabel:`Additional Info` tab of the delivery order. Click the :guilabel:`Tracking` smart button to access the tracking link from the shipping carrier's website." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:143 msgid "The tracking label is found in PDF format in the chatter." msgstr "" @@ -5497,12 +5754,12 @@ msgstr "" msgid "Show generated shipping label in the chatter." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:150 msgid "For multi-package shipping, one label is generated per package. Each label appears in the chatter." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:119 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:157 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:157 msgid "Sample label generated from Odoo's shipping connector with FedEx." msgstr "" @@ -5618,19 +5875,216 @@ msgstr "" msgid "It is also possible to ship out some of the items while creating another backorder for the rest. To do so, simply follow the same steps used to create the first backorder." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:3 +msgid "Printable delivery PDFs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:5 +msgid "Automatically print delivery-related PDFs documents and labels in Odoo, containing package recipient details, contents, or handling instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:8 +msgid "The following PDFs can be configured to print upon validating an *Inventory* operation (e.g. receipt, picking, delivery orders, quality checks):" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:11 +msgid ":ref:`Delivery slip `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:12 +msgid ":ref:`Return slip `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:13 +msgid ":ref:`Product labels of items in the order `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:14 +msgid ":ref:`Lot and serial number labels `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:15 +msgid "Carrier labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:16 +msgid "Export documents" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:17 +msgid "Package Content" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:18 +msgid "Package label" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:22 +msgid "To automatically print these forms, navigate to :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired operation type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:25 +msgid "In the :guilabel:`Hardware` tab, tick each of the desired options available in the :guilabel:`Print on Validation` section to download the PDF of those selected documents automatically after validating the :guilabel:`Operation Type`. For details on what each of the checkbox options do, jump to the related section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 +msgid "Show the *Print on Validation* option in the \"Pick\" *Operation Type*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:36 +msgid "Delivery slip" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:38 +msgid "A *delivery slip* contains recipient and package details, usually placed inside (or attached to) the package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:42 +msgid ":ref:`Picking list `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:43 +msgid ":doc:`Tracking label `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:45 +msgid "After :ref:`enabling the Delivery Slip setting ` in the :guilabel:`Hardware` tab configuration options, clicking :guilabel:`Validate` on the desired operation type downloads a PDF of the delivery slip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:49 +msgid "The delivery slip shows products, quantities, the delivery order reference number, and the total order weight." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 +msgid "Example delivery slip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:58 +msgid "Return slip" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:60 +msgid "Print a *return slip* to include in a delivery for customer return packages. It identifies the return, links to the sales order, and includes item details and customer information. It can also include specific return instructions for the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:64 +msgid "After :ref:`enabling the Return Slip setting ` in the :guilabel:`Hardware` tab configuration options, clicking :guilabel:`Validate` on the desired operation type downloads a PDF of the return slip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:68 +msgid "The return slip displays the company's return address, along with barcodes for both the order and the return operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:-1 +msgid "Example return slip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:77 +msgid "Product labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:79 +msgid "Print *product labels* to affix to items in an order, providing essential information, such as product name, barcode, and price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:82 +msgid "After navigating to the intended operation type (:menuselection:`Inventory app --> Configuration --> Operations Types`), in the :guilabel:`Hardware` tab, tick the :guilabel:`Product Labels` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:137 +msgid "Doing so makes the :guilabel:`Print label as:` drop-down menu visible, where each product label can be printed as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:88 +msgid ":guilabel:`2 x 7 with price`: PDF displays product name, barcode, and price, fitting two rows and seven columns of product labels per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 +msgid "Example 2 x 7 with price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:97 +msgid ":guilabel:`4 x 7 with price`: displays product name, barcode, and price, fitting four rows and seven columns of product labels per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 +msgid "Example 4 x 7 with price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:106 +msgid ":guilabel:`4 x 12`: displays product name and barcode. Fits four rows and twelve columns of product labels per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 +msgid "Example 4 x 12." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:115 +msgid ":guilabel:`4 x 12 with price`: displays product name, barcode, and price. Fits four rows and twelve columns of product labels per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:117 +msgid ":guilabel:`ZPL Labels`: prints labels in the Zebra Programming Language (ZPL) containing the product name and barcode. Readable for Zebra printers to automatically print labels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:119 +msgid ":guilabel:`ZPL Labels with price`: prints labels in the :abbr:`ZPL (Zebra Programming Language)` containing the product name, barcode, and price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:123 +msgid "Product labels can be manually printed from any delivery order, by clicking the :guilabel:`Print Labels` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:128 +msgid "Lot/SN Labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:130 +msgid "Print *lot/SN labels* to affix to items in an order, providing essential information, such as product name, lot or serial number, and the barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:133 +msgid "To automatically print this PDF, navigate to the intended operation type's options page (:menuselection:`Inventory app --> Configuration --> Operations Types`). Then, in the :guilabel:`Hardware` tab, tick the :guilabel:`Lot/SN Labels` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:140 +msgid ":guilabel:`4 x 12 - One per lot/SN`: PDF with labels for unique lot/serial numbers in the order, including product name, lot/serial number, and barcode. Fits four rows and twelve columns per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:0 +msgid "Order with only one unique set of lot/serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:150 +msgid "Labels for an order with only one unique set of lot/serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:152 +msgid ":guilabel:`4 x 12 - One per unit`: PDF with labels matching the quantity of items, displaying the product name, lot/serial number, and barcode. Fits four rows and twelve columns per page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:154 +msgid ":guilabel:`ZPL Labels - One per lot/SN`: prints labels in :abbr:`ZPL (Zebra Programming Language)`, containing the product name, lot/serial number, and barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/print_on_validation.rst:156 +msgid ":guilabel:`ZPL Labels - One per unit`: prints labels with the quantity of items in :abbr:`ZPL (Zebra Programming Language)`, containing the product name, lot/serial number, and barcode." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:3 msgid "Scheduled delivery dates" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:10 msgid "Accurately forecasting delivery dates is vital for fulfilling customer expectations. In Odoo, the *Inventory* app allows for comprehensive lead time configuration, allowing coordination and planning of manufacturing orders, deliveries, and receptions." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:10 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:15 msgid "Lead time types" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:17 msgid "Different lead times for different operations can impact various stages of the order fulfillment process. Here's a summary of the types of lead times in Odoo:" msgstr "" @@ -5638,43 +6092,51 @@ msgstr "" msgid "Show graphic of all lead times working together." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:19 -msgid ":ref:`Customer lead time `: The default time frame for fulfilling customer orders. The customer lead time is the number of days from the date the sales order (SO) is confirmed to the date the products are shipped from the warehouse. This is also known as *delivery lead time*." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:24 -msgid ":ref:`Sales security lead time `: moves the *scheduled delivery date* forward by a specified number of days. This serves as a buffer to allow the team ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the fulfillment process." +msgid ":ref:`Customer lead time `: default time frame for fulfilling customer orders. The customer lead time is the number of days from the date the sales order (SO) is confirmed to the date the products are shipped from the warehouse. This is also known as *delivery lead time*." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:29 -msgid ":ref:`Purchase lead time `: the number of days from the confirmation of a purchase order (PO) to the receipt of products. It provides insight on the time it takes for products to arrive at the warehouse, facilitating effective scheduling and planning of supplier deliveries." +msgid ":ref:`Sales security lead time `: moves the *scheduled delivery date* forward by a specified number of days. This serves as a buffer to allow ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the fulfillment process." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:34 -msgid ":ref:`Purchase security lead time `: advances the order deadline on a :abbr:`PO (Purchase Order)` by a specified number of days. This proactive approach of placing orders earlier mitigates the risk of vendor or shipping delays. Thus, for products that are set to replenish to order, the need appears on the *Replenishment report* earlier, according to the specified number of days." +msgid ":ref:`Purchase lead time `: number of days from the confirmation of a purchase order (PO) to the receipt of products. It provides insight on the time it takes for products to arrive at the warehouse, facilitating effective scheduling and planning of supplier deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:40 -msgid ":ref:`Manufacturing lead time `: the number of days needed to complete a manufacturing order (MO) from the date of confirmation. This lead time includes weekends (non-working hours in Odoo), and is used to forecast an approximate production date for a finished good." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:39 +msgid ":ref:`Purchase security lead time `: advances the order deadline on a :abbr:`PO (Purchase Order)` by a specified number of days. This proactive approach of placing orders earlier mitigates the risk of vendor or shipping delays. Thus, for products that are set to replenish to order, the need appears on the *Replenishment report* earlier, according to the specified number of days." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:45 -msgid ":ref:`Manufacturing security lead time `: moves the scheduled date of the :abbr:`MO (Manufacturing Order)` forward by a specified number of days. When used in conjunction with :ref:`replenish to order `, the security lead time makes the need appear earlier on the replenishment report." +msgid ":ref:`Days to Purchase `: days needed for the vendor to receive a request for quotation (RFQ) and confirm it. It advances the deadline to schedule a |RFQ| by a specified number of days." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:49 +msgid ":ref:`Manufacturing lead time `: number of days needed to complete a manufacturing order (MO) from the date of confirmation. This lead time includes weekends (non-working hours in Odoo), and is used to forecast an approximate production date for a finished good." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:54 +msgid ":ref:`Days to prepare manufacturing order `: number of days needed to replenish components, or manufacture sub-assemblies of the product. Either set one directly on the bill of materials (BoM), or click *Compute* to sum up purchase and manufacturing lead times of components in the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:60 +msgid ":ref:`Manufacturing security lead time `: moves the scheduled date of the :abbr:`MO (Manufacturing Order)` forward by a specified number of days. When used in conjunction with :ref:`replenish to order `, the security lead time makes the need appear earlier on the replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:69 msgid "Sales lead times" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:71 msgid "Customer lead times and sales security lead times can be configured to automatically compute an *expected delivery date* on a :abbr:`SO (Sales Order)`. The expected delivery date ensures a realistic *delivery dates* setting for shipments from the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:75 msgid "Odoo issues a warning message if the set delivery date is earlier than the expected date, as it may not be feasible to fulfill the order by that time, which would impact other warehouse operations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:79 msgid "A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is confirmed on July 11th. The product has a customer lead time of 14 days, and the business uses a sales security lead time of 1 day. Based on the lead time inputs, Odoo suggests a delivery date in 15 days, on July 26th." msgstr "" @@ -5682,19 +6144,19 @@ msgstr "" msgid "Set *Delivery Date* in a sales order. Enables delivery lead times feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:87 msgid "The following sections demonstrate how to automatically compute expected delivery dates." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:90 msgid "Customer lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:92 msgid "Set the customer lead time on each product form, by navigating to the products page. To do so, go to :menuselection:`Sales app --> Products --> Products`. From there, select the desired product, and switch to the :guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` field, fill in the number of calendar days required to fulfill the delivery order from start to finish." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:98 msgid "Set a 14-day customer lead time for the `Coconut-scented candle` by navigating to its product form. Then, in the :guilabel:`Inventory` tab, type `14.00` days into the :guilabel:`Customer Lead Time` field." msgstr "" @@ -5702,23 +6164,23 @@ msgstr "" msgid "Set *Customer Lead Time* on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:109 msgid "Sales security lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:111 msgid "*Sales security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:114 msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Sales`, and click the checkbox to enable the feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:117 msgid "Next, enter the desired number of calendar days. This security lead time is a buffer notifying the team to prepare for outgoing shipments earlier than the scheduled date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:121 msgid "Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes the :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. In that case, if a product is initially scheduled for delivery on April 6th, but with a one-day security lead time, the new scheduled date for the delivery order would be April 5th." msgstr "" @@ -5726,19 +6188,19 @@ msgstr "" msgid "View of the security lead time for sales configuration from the sales settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:131 msgid "Deliver several products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:133 msgid "For orders that include multiple products with different lead times, the lead times can be configured directly from the quotation itself. On a quotation, click the :guilabel:`Other Info` tab, and set the :guilabel:`Shipping Policy` to:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:121 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:137 msgid ":guilabel:`As soon as possible` to deliver products as soon as they are ready. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the shortest lead time among the products in the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:125 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:141 msgid ":guilabel:`When all products are ready` to wait to fulfill the entire order at once. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's date to the longest lead time among the products in the order." msgstr "" @@ -5746,27 +6208,27 @@ msgstr "" msgid "Show *Shipping Policy* field in the *Other Info* tab of a quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:134 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:150 msgid "In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the products have a lead time of 8 days and 5 days, respectively. Today's date is April 2nd." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:153 msgid "When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as possible`, the scheduled delivery date is 5 days from today: April 7th. On the other hand, selecting :guilabel:`When all products are ready` configures the scheduled date to be 8 days from today: April 10th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:160 msgid "Purchase lead times" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:146 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:162 msgid "Automatically determining the dates on which to place orders from suppliers can help simplify the procurement process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:165 msgid "Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO (Purchase Order)` deadline, based on the required date the product is needed in the warehouse. By working backwards from the receipt date, vendor lead times and purchase security lead times are taken into account, in order to determine the :abbr:`PO (Purchase Order)` deadline." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:170 msgid "This deadline is the date by which the order should be confirmed, in order to ensure timely arrival by the expected receipt date." msgstr "" @@ -5774,27 +6236,27 @@ msgstr "" msgid "Visualization of PO deadline and receipt date used with vendor lead times." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:162 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:178 msgid ":ref:`PO scheduling with reordering rules `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:181 msgid "Vendor lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:167 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:183 msgid "To set a vendor lead time for orders arriving in the warehouse from a vendor location, begin by navigating to a product form through :menuselection:`Purchase app --> Products --> Products`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:170 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:186 msgid "Next, select the desired product, and switch to the :guilabel:`Purchase` tab. In the editable vendor pricelist, click the :guilabel:`Add a line` button to add vendor details, such as the :guilabel:`Vendor` name, :guilabel:`Price` offered for the product, and lastly, the :guilabel:`Delivery Lead Time`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:192 msgid "Multiple vendors and lead times can be added to the vendor pricelist. The default vendor and lead time selected will be the entry at the top of the list." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:196 msgid "On the vendor pricelist of the product form, the :guilabel:`Delivery Lead Time` for the selected vendor is set to `10 days.`" msgstr "" @@ -5802,11 +6264,11 @@ msgstr "" msgid "Add delivery lead times to vendor pricelist on a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:187 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:203 msgid "By setting the vendor lead time, the expected arrival date of the item is automatically determined as the date of the :abbr:`PO (Purchase Order)` confirmation, plus the vendor lead time. This ensures that warehouse employees are notified, if the products do **not** arrive within the expected timeframe." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:193 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:209 msgid "On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product configured with a 10-day vendor lead time, Odoo automatically sets the :guilabel:`Receipt Date` to July 21st. The receipt date also appears as the :guilabel:`Scheduled Date` on the warehouse receipt form, accessible from the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase Order)`." msgstr "" @@ -5818,39 +6280,51 @@ msgstr "" msgid "Show expected *Scheduled Date* of arrival of the product from the vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:225 msgid "Purchase security lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:227 msgid "*Purchase security lead time* is set globally for the business in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:214 -msgid "On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for :guilabel:`Security Lead Time for Purchase`, and click the checkbox to enable the feature." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:230 +msgid "On the :guilabel:`Settings` page, under the :guilabel:`Advanced Scheduling` heading, tick the checkbox for :guilabel:`Security Lead Time for Purchase`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:217 -msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in supplier deliveries." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:233 +msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in supplier deliveries. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:221 -msgid "Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the :guilabel:`Scheduled Date` of receipt back by one day. In that case, if a product is initially scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for the receipt would be April 8th." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:237 +msgid "Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the :guilabel:`Scheduled Date` of receipt back by two days. In that case, if a product is initially scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for the receipt would be April 8th." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 msgid "Set security lead time for purchase from the Inventory > Configuration > Settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:233 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:249 +msgid "Days to purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:251 +msgid "To set up the *days to purchase* lead time, go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Advanced Scheduling` section, in the :guilabel:`Days to Purchase` field, specify the number of days required for the vendor to confirm a |RFQ| after receiving it from the company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 +msgid "Show \"Days to Purchase\" configuration in the Settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:263 msgid "Manufacturing lead times" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:235 -msgid "Lead times can help simplify the procurement process for consumable materials and components used in manufactured products with bills of materials." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:265 +msgid "Lead times can help simplify the procurement process for consumable materials and components used in manufactured products with bills of materials (BoMs)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:238 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:268 msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the deadline to begin the manufacturing process to complete the product by the scheduled delivery date, can be determined by configuring the manufacturing lead times and manufacturing security lead times." msgstr "" @@ -5858,103 +6332,135 @@ msgstr "" msgid "Visualization of the determination of planned MO date manufacturing lead times." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:247 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:277 msgid "Manufacturing lead time" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:249 -msgid "Configure the manufacturing lead time directly on the product form, by navigating to :menuselection:`Manufacturing app --> Products --> Products`, and select the desired product." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:279 +msgid "Manufacturing lead times for products are configured from a product's bill of materials (BoM) form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:252 -msgid "In the :guilabel:`Inventory` tab of the product, specify the calendar days needed to the manufacture the product in the :guilabel:`Manufacturing Lead Time` field." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:281 +msgid "To add a lead time to a |BoM|, navigate to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the desired |BoM| to edit." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:256 -msgid "Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly in the :guilabel:`Inventory` tab of the product." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:284 +msgid "On the |BoM| form, click the :guilabel:`Miscellaneous` tab. Change the value (in days) in the :guilabel:`Manuf. Lead Time` field to specify the calendar days needed to manufacture the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 -msgid "View of the manufacturing lead time configuration from the product form." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 +msgid "Manuf. Lead Time value specified on a product's Bill of Material form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:263 -msgid "Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the *expected delivery date*, indicated in the :guilabel:`Scheduled Date` field of the :abbr:`DO (Delivery Order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:266 -msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the :guilabel:`Scheduled Date` field on the :abbr:`MO (Manufacturing Order)`, is calculated as the *expected delivery date* subtracted by the manufacturing lead time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:270 -msgid "This ensures the manufacturing process begins on time, in order to meet the delivery date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:272 -msgid "However, it's important to note that lead times are based on calendar days. Lead times do **not** consider weekends, holidays, or *work center capacity* (:dfn:`the number of operations that can be performed at the work center simultaneously`)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:277 -msgid ":ref:`Manufacturing planning `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:278 -msgid ":ref:`Configure automatic MO scheduling with reordering rules `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:282 -msgid "A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is August 15th. The product requires 14 days to manufacture. So, the latest date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment date is August 1st." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:289 -msgid "Manufacturing security lead time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:291 -msgid "*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, locate the box for :guilabel:`Security Lead Time`, and click the checkbox to enable the feature." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:292 +msgid "If the selected |BoM| is a multi-level |BoM|, the manufacturing lead times of the components are added." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:295 -msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in the manufacturing process." +msgid "If the |BoM| product is subcontracted, the :guilabel:`Manuf. Lead Time` can be used to determine the date at which components should be sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:298 +msgid "Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the *expected delivery date*, indicated in the :guilabel:`Scheduled Date` field of the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:301 +msgid "The :abbr:`MO (Manufacturing Order)` deadline, which is the :guilabel:`Scheduled Date` field on the :abbr:`MO (Manufacturing Order)`, is calculated as the *expected delivery date* subtracted by the manufacturing lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:305 +msgid "This ensures the manufacturing process begins on time, in order to meet the delivery date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:307 +msgid "However, it is important to note that lead times are based on calendar days. Lead times do **not** consider weekends, holidays, or *work center capacity* (:dfn:`the number of operations that can be performed at the work center simultaneously`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:312 +msgid ":doc:`Manufacturing planning <../../../manufacturing/workflows/use_mps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:313 +msgid ":doc:`Schedule MOs with reordering rules <../../product_management/product_replenishment/reordering_rules>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:317 +msgid "A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is August 15th. The product requires 14 days to manufacture. So, the latest date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment date is August 1st." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:324 +msgid "Days to prepare manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:326 +msgid "Configure the days required to gather components to manufacture a product by going to its |BoM|. To do that, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the desired |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:330 +msgid "In the :guilabel:`Miscellaneous` tab of the |BoM|, specify the calendar days needed to obtain components of the product in the :guilabel:`Days to prepare Manufacturing Order` field. Doing so creates |MOs| in advance, and ensures there is enough time to either replenish components, or manufacture semi-finished products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:336 +msgid "Clicking :guilabel:`Compute`, located next to the :guilabel:`Days to prepare Manufacturing Order` field, calculates the longest lead time among all the components listed on the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:339 +msgid "*Purchase security lead times* that impact this specific |BoM| are also added to this value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:343 +msgid "A |BoM| has two components, one has a manufacturing lead time of two days, and the other has a purchase lead time of four days. The :guilabel:`Days to prepare Manufacturing Order` is four days." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:350 +msgid "Manufacturing security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:352 +msgid "*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, tick the checkbox for :guilabel:`Security Lead Time`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:356 +msgid "Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is set to account for potential delays in the manufacturing process. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:-1 msgid "View of the security lead time for manufacturing from the manufacturing app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:303 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:364 msgid "A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` set for August 15th. The manufacturing lead time is 7 days, and manufacturing security lead time is 3 days. So, the :guilabel:`Scheduled Date` on the :abbr:`MO (Manufacturing Order)` reflects the latest date to begin the manufacturing order. In this example, the planned date on the :abbr:`MO (Manufacturing Order)` is August 5th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:310 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:371 msgid "Global example" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:312 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:373 msgid "See the following example to understand how all the lead times work together to ensure timely order fulfillment:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:315 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:376 msgid "**Sales security lead time**: 1 day" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:316 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:377 msgid "**Manufacturing security lead time**: 2 days" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:317 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:378 msgid "**Manufacturing lead time**: 3 days" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:318 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:379 msgid "**Purchase security lead time**: 1 day" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:319 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:380 msgid "**Vendor lead time**: 4 days" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:321 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:382 msgid "The customer places an order for a manufactured product on September 1st, and the scheduled delivery date from the warehouse is on September 20th. Odoo uses lead times and automated reordering rules to schedule the necessary operations, based on the outgoing shipment delivery date, September 20th:" msgstr "" @@ -5962,27 +6468,27 @@ msgstr "" msgid "Show timeline of how lead times work together to schedule warehouse operations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:329 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:390 msgid "**September 1st**: Sales order created, confirmed by salesperson." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:331 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:392 msgid "**September 9th**: Deadline to order components to ensure they arrive in time when manufacturing begins (4-day supplier lead time)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:334 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:395 msgid "**September 13th**: Scheduled date of receipt for components. Initially, it was set to 9/14, but the 1-day purchase security lead time pushed the date earlier by 1 day." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:337 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:398 msgid "**September 14th**: Deadline to begin manufacturing. Calculated by subtracting the manufacturing lead time of 3 days, and the manufacturing security lead time of 2 days, from the expected delivery date of September 19th." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:341 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:402 msgid "**September 19th**: :guilabel:`Scheduled Date` on the delivery order form indicates the updated expected delivery date, which was originally set as September 20th. But the sales security lead time pushed the date forward by a day." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:345 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:406 msgid "Odoo's replenishment planning maps a business' order fulfillment process, setting pre-determined deadlines and raw material order dates, including buffer days for potential delays. This ensures products are delivered on time." msgstr "" @@ -6003,7 +6509,6 @@ msgid "Odoo is configured by default to :ref:`receive and deliver goods in one s msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Activate multi-step routes and storage locations in inventory settings." msgstr "" @@ -6113,313 +6618,370 @@ msgstr "" msgid "Process receipts and deliveries in one step" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:7 -msgid "By default, incoming shipments are configured to be received directly into stock, and outgoing shipments are configured to be delivered directly from stock to the customer; the default setting for warehouses in Odoo is one step receipts and deliveries." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:11 +msgid "In Odoo *Inventory*, both incoming and outgoing shipments are configured to process in one step, by default. This means purchases will be received directly into stock, and deliveries will be moved directly from stock to customers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:12 -msgid "Incoming and outgoing shipments do not need to be configured with the same steps. For example, products can be received in one step, but shipped in three steps." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:30 +msgid "Incoming and outgoing shipments do **not** need to be configured with the same amount of steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:15 -msgid "In the following example, one step will be used for both receipts and deliveries." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:18 +msgid "For example, a warehouse's settings can be configured so products can be received directly in one step, and delivered in three steps (pick + pack + ship)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:20 -msgid "Configure the warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:24 +msgid "To configure one-step receipts and deliveries for a warehouse, navigate to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select a warehouse to edit." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:22 -msgid "If another receiving or shipping configuration is set on the warehouse, they can easily be set back to the one step setting." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:25 -msgid "Begin by navigating to :menuselection:`Inventory --> Configuration --> Warehouses`, and click on the desired warehouse to edit. Next, on the :guilabel:`Warehouse Configuration` tab, under the :guilabel:`Shipments` section, select :guilabel:`Receive goods directly (1 step)` for :guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods directly (1 step)` for :guilabel:`Outgoing Shipments`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:27 +msgid "Under the :guilabel:`Warehouse Configuration` tab, set :guilabel:`Incoming Shipments` to :guilabel:`Receive goods directly (1 step)`, and set :guilabel:`Outgoing Shipments` to :guilabel:`Deliver goods directly (1 step)`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 -msgid "Set incoming and outgoing shipment options to receive and deliver in one step." +msgid "Incoming and outgoing shipments set to one-step on warehouse form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:36 -msgid "Receive goods directly (1 step)" +msgid "Since one-step receipt and delivery is the default for incoming and outgoing shipments in Odoo, the *Multi-Step Routes* feature is *not* required." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:39 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:69 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 -msgid "Create a purchase order" +msgid "However, for the :guilabel:`Shipments` settings to appear on a warehouse form, the feature **must** be enabled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:41 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:71 -msgid "On the main :menuselection:`Purchase` application dashboard, start by making a new quote by clicking :guilabel:`New`. Then, select (or create) a :guilabel:`Vendor` from the drop-down field, add a storable :guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` to finalize the quote as a new purchase order." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:41 +msgid "To enable *Multi-Step Routes*, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Warehouse` section, tick the checkbox next to :guilabel:`Multi-Step Routes`, and click :guilabel:`Save`. Doing so also activates the :guilabel:`Storage Locations` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:46 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:100 -msgid "A :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (purchase order)` form — click it to reveal the associated receipt for the purchase order." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:50 +msgid "Receive goods directly (1 step)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:52 +msgid "When products are received in one step, they will move from the vendor location to warehouse stock in the database immediately upon validation of a purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:58 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:81 +msgid "To create a |PO|, navigate to the :menuselection:`Purchase app`, and click :guilabel:`New`. This opens a blank :guilabel:`Request for Quotation` (RfQ) form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:61 +msgid "Add a vendor in the :guilabel:`Supplier` field. Then, fill out the various fields on the |RfQ|, as necessary." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 -msgid "Receipt smart button appears on the confirmed purchase order." +msgid "Filled out new request for quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:54 -msgid "Purchase order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Receipts` kanban card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 -msgid "Receipt kanban card's 1 to Process smart button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:68 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:91 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 -msgid "Process the receipt" +msgid "Under the :guilabel:`Products` tab, click :guilabel:`Add a product`, and select a product to add to the |RfQ|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:65 -msgid "When viewing the receipt (associated with the purchase order above), click :guilabel:`Validate` to then complete the receipt." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:94 +msgid "Once ready, click :guilabel:`Confirm Order`. This moves the |RfQ| to the :guilabel:`Purchase Order` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:97 +msgid "Once the |PO| is confirmed, a :guilabel:`Receipt` smart button appears at the top of the form. Clicking the smart button opens the warehouse receipt (WH/IN) form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 -msgid "Validate the purchase order via the Validate smart button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:73 -msgid "If :guilabel:`Storage Locations` are activated, clicking the :guilabel:`≣ (bullet list)` details icon next to the :guilabel:`🗑️ (trash)` delete icon enables the :guilabel:`Detailed Operations` screen to pop-up. This allows the location(s) to be specified for the received product(s)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 -msgid "Select the Storage Location for the products being received in the Detailed Operations\n" -"pop-up." +msgid "Receipt smart button on confirmed purchase order form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:82 -msgid "Once the receipt is validated, the product leaves the :guilabel:`Supplier Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives here, it will be available for manufacturing, sales, etc. Then, the status of the document will change to :guilabel:`Done`, thus completing the reception process in one step." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:113 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:171 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:249 +msgid "Process receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:84 +msgid "From the warehouse receipt form, the products ordered can be received into the warehouse. To receive the products, click :guilabel:`Validate`. Once validated, the receipt moves to the :guilabel:`Done` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 +msgid "Validated warehouse receipt in Done stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:123 +msgid "Click back to the |PO| (via the breadcrumbs, at the top of the form) to view the |PO| form. On the product line, the quantity in the :guilabel:`Received` column now matches the ordered :guilabel:`Quantity`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:99 msgid "Deliver goods directly (1 step)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:95 -msgid "Start my navigating to the main :menuselection:`Sales` app dashboard, and make a new quote by clicking :guilabel:`New`. Then select (or create) a :guilabel:`Customer` from the drop-down field, add a storable :guilabel:`Product` that is in stock to the order lines, and click :guilabel:`Confirm` to finalize the quotation as a sales order." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:101 +msgid "When products are delivered in one step, they will move from warehouse stock to the customer location in the database immediately upon validation of a sales order (SO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:103 -msgid "A :guilabel:`Delivery` smart button will appear in the top-right corner of the :abbr:`SO (Sales Order)` form — click it to reveal the associated delivery order for the sales order." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:156 +msgid "Create sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:158 +msgid "To create a |SO|, navigate to the :menuselection:`Sales app`, and click :guilabel:`New`. This opens a blank sales quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:161 +msgid "Add a customer in the :guilabel:`Customer` field. Then, fill out the various fields on the sales quotation form, as necessary." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 -msgid "The Delivery smart button appears after the sales order is confirmed." +msgid "Filled out new sales quotation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:111 -msgid "Delivery orders can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Delivery Orders` kanban card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 -msgid "Delivery Orders kanban card's 1 to Process smart button." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:117 +msgid "Under the :guilabel:`Product` tab, click :guilabel:`Add a product`, and select a product to add to the sales order quotation." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:120 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 -msgid "Process the delivery" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:171 +msgid "Once ready, click :guilabel:`Confirm`. This moves the quotation to the :guilabel:`Sales Order` stage." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:122 -msgid "When viewing the delivery order (associated with the sales order above), click :guilabel:`Validate` to then complete the delivery." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:174 +msgid "Once the |SO| is confirmed, a :guilabel:`Delivery` smart button appears at the top of the form. Clicking the smart button opens the warehouse delivery (WH/OUT) form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 -msgid "Validate the delivery order." +msgid "Delivery smart button on confirmed sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:129 -msgid "Once the picking order is validated, the product leaves the :guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers location`. Then, the status of the document will change to :guilabel:`Done`, thus completing delivery in one step." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:131 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:207 +msgid "Process delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:133 +msgid "From the warehouse delivery form, the products ordered by the customer can be delivered from the warehouse. To deliver the products, change the value in the :guilabel:`Quantity` field to match the ordered quantity in the :guilabel:`Demand` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:225 +msgid "Once ready, click :guilabel:`Validate`. Once validated, the delivery order moves to the :guilabel:`Done` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:-1 +msgid "Validated delivery order in Done stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:144 +msgid "Click back to the |SO| (via the breadcrumbs, at the top of the form) to view the |SO| form. On the product line, the quantity in the :guilabel:`Delivered` column now matches the ordered :guilabel:`Quantity`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:229 +msgid ":doc:`shipments_deliveries`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:3 msgid "Process receipts and deliveries in two steps" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:7 -msgid "Depending on a company's business processes, multiple steps may be needed before receiving or shipping products. In the two-step receipt process, products are received in an input area, then transferred to stock. Two-step receipts work best when various storage locations are being used, such as locked or secured areas, freezers and refrigerators, or various shelves." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:12 -msgid "Products can be sorted according to where they are going to be stored, and employees can stock all the products going to a specific location. The products are not available for further processing until they are transferred into stock." +msgid "Depending on a company's needs, receiving and shipping products in and out of the warehouse might require multi-step operations. In Odoo *Inventory*, this can be done using *Multi-Step Routes*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:16 -msgid "In the two-step delivery process, products that are part of a delivery order are picked from the warehouse according to their removal strategy, and brought to an output location before being shipped." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:15 +msgid "In the two-step receipt process, products are received in an input area, then transferred to stock. This kind of process for incoming shipments might be beneficial for warehouses with specific storage locations, such as freezers and refrigerators, secured locked areas, or special aisles and shelves." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:20 -msgid "One situation where this would be useful is when using either a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy, where the products that are being picked need to be selected based on their receipt date or expiration date." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:19 +msgid "Products can be sorted according to where they are going to be stored, and employees can stock all the products going to a specific location. The products are *not* available for further processing, until they are transferred into stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:25 -msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step `, so the settings need to be changed in order to utilize two-step receipts and deliveries. Incoming and outgoing shipments do not need to be set to have the same steps. For example, products can be received in two steps, but shipped in one step. In the following example, two steps will be used for both receipts and deliveries." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:23 +msgid "In the two-step delivery process, products are first picked from their respective location in the warehouse, then transferred to an output location before being shipped to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:26 +msgid "This might be beneficial for companies using a First In, First Out (FIFO), Last In, First Out (LIFO), or First Expired, First Out (FEFO) removal strategy." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:32 -msgid "Configure multi-step routes" +msgid "For example, a warehouse's settings can be configured so products can be received in two steps (input + stock), and delivered in three steps (pick + pack + ship)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:34 -msgid "First, make sure the :guilabel:`Multi-Step Routes` option is enabled in :menuselection:`Inventory --> Configuration --> Settings`, under the :guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` the changes." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:38 +msgid "In Odoo *Inventory*, both incoming and outgoing shipments are configured to process in one step, by default. To change these settings, the *Multi-Step Routes* feature must be enabled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:39 -msgid "Activating the :guilabel:`Multi-Step Routes` setting will also activate the :guilabel:`Storage Locations` feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:46 -msgid "Next, the warehouse needs to be configured for two-step receipts and deliveries. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click on the warehouse to change the warehouse settings." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 +msgid "Enabled Multi-Step Routes feature in Inventory app settings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:50 -msgid "Then, select :guilabel:`Receive goods in input and then stock (2 steps)` for :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and then deliver (2 steps)` for :guilabel:`Outgoing Shipments`." +msgid "Next, configure a warehouse for two-step receipts and deliveries. Navigate to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select a warehouse to edit." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:53 +msgid "Under the :guilabel:`Warehouse Configuration` tab, set :guilabel:`Incoming Shipments` to :guilabel:`Receive goods in input and then stock (2 steps)`, and set :guilabel:`Outgoing Shipments` to :guilabel:`Send goods in output and then deliver (2 steps)`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Set incoming and outgoing shipment options to receive and deliver in two steps." +msgid "Incoming and outgoing shipments set to two-step on warehouse form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:59 -msgid "Activating two-step receipts and deliveries will create new *input* and *output* locations, which by default, are labeled :guilabel:`WH/Input` and :guilabel:`WH/Output`, respectively, on the :guilabel:`Locations` dashboard. To rename these locations, go to :menuselection:`Configuration --> Locations`, and select the :guilabel:`Location` to change. On the location form, update the :guilabel:`Location Name`, and make any other changes (if necessary)." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:62 +msgid "Selecting two-step receipts and deliveries automatically creates new *Input* and *Output* warehouse locations in the database, named `WH/Input` and `WH/Output`, respectively." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:66 -msgid "Process a receipt in two steps (input + stock)" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:65 +msgid "To rename or edit these locations, navigate to :menuselection:`Inventory app --> Configuration --> Locations`, and select the desired location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:77 -msgid "For businesses with multiple warehouses that have different step configurations, the :guilabel:`Deliver To` field on the :abbr:`PO (Purchase Order)` form may need to be specified as the correct *input location* connected to the two-step warehouse, which can be done by selecting the warehouse from the drop-down selection that includes the `Receipts` label at the end of the name." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:68 +msgid "On the location's form, change the :guilabel:`Location Name`, and make any other necessary changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:83 -msgid "After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button appears at the top of the :abbr:`PO (Purchase Order)` form. Click it to reveal the new receipt (WH/IN) operation." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:72 +msgid "Process receipt in two steps (input + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:74 +msgid "When products are received in two steps, they first move from the vendor location to an input location. Then, they move from the input location to warehouse stock in the database, upon validation of a purchase order (PO), and a subsequent internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:84 +msgid "Add a vendor in the :guilabel:`Vendor` field. Then, fill out the various fields on the |RfQ|, as necessary." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 -msgid "After confirming a purchase order, a Receipt smart button will appear." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:93 -msgid "Once the purchase order is confirmed, a receipt is generated and ready to process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:95 -msgid "Navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Receipts` task card on the :guilabel:`Inventory Overview` dashboard. This reveals a list of all receipts to process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:98 -msgid "Click on the :guilabel:`Receipt` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to :guilabel:`WH/Input`." +msgid "Filled out new Request for Quotation from vendor." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Receipt form for product move to WH/Input." +msgid "Delivery smart button for validated purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:106 -msgid "Process the internal transfer" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:105 +msgid "For businesses with multiple warehouses that have different step configurations, the :guilabel:`Deliver To` field on the |PO| form **must** be specified as the correct *input location* connected to the two-step warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:109 +msgid "This can be done by selecting the warehouse from the drop-down menu that includes the `Receipts` label at the end of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:115 +msgid "From the warehouse receipt form, the products ordered can be received into the warehouse. To receive the products, click :guilabel:`Validate`. Once validated, the receipt moves to the :guilabel:`Done` stage, and the products move to the :guilabel:`WH/Input` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 +msgid "Receipt form for products ordered from vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:128 +msgid "Process internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:130 msgid "Once the receipt is validated, an internal transfer is created and ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:110 -msgid "Click back to the :guilabel:`Inventory Overview` in the breadcrumbs, and locate the :guilabel:`Internal Transfers` task card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:113 -msgid "Click the :guilabel:`# To Process` button to reveal a list of all internal transfers to process, and select the transfer associated with the previously validated receipt." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:116 -msgid "Click :guilabel:`Validate` to complete the transfer and move the product from :guilabel:`WH/Input` to :guilabel:`WH/Stock`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:119 -msgid "Once the transfer is validated, the product enters inventory and is available for customer deliveries or manufacturing orders." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Validate the internal transfer to move the item to stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:127 -msgid "Process a delivery order in two steps (pick + ship)" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:132 -msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`New`. Select (or create) a :guilabel:`Customer`, add a storable :guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." +msgid "To view the internal transfer, navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Internal Transfers` task card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:136 -msgid "After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart button will appear in the top, above the :abbr:`SO (Sales Order)` form. Click the :guilabel:`Delivery` smart button to reveal the associated receipt." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:135 +msgid "Click the :guilabel:`# To Process` button on the task card to reveal a list of all internal transfers to process, and select the transfer associated with the previously validated receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:138 +msgid "Once ready, click :guilabel:`Validate` to complete the transfer, and move the product from :guilabel:`WH/Input` to :guilabel:`WH/Stock`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 +msgid "Once the transfer is validated, the products enter inventory, and are available for customer deliveries or manufacturing orders." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Delivery smart button on sales order form." +msgid "Internal transfer form for products ordered from vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:145 -msgid "Sales order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Pick` Kanban card." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:149 +msgid "Process delivery order in two steps (pick + ship)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:150 -msgid "Process the picking" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:152 -msgid "Once the sales order is confirmed, a picking order is generated and ready to process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:154 -msgid "Navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Pick` task card on the :guilabel:`Inventory Overview` dashboard. This reveals a list of all pickings to process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:157 -msgid "Click on the picking (WH/PICK) operation associated with the sales order to reveal the picking order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:160 -msgid "Click :guilabel:`Check Availability` on the picking order form. If the product is in stock, Odoo automatically reserves the product. Quantities can also be manually set by changing the value in the :guilabel:`Quantity` column to match the value in the :guilabel:`Demand` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:164 -msgid "Once ready, click :guilabel:`Validate` to complete the picking and move the product from :guilabel:`WH/Stock` to :guilabel:`WH/Output.`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:151 +msgid "When products are delivered in two steps, they move from warehouse stock to an output location. Then, they move from the output location to a customer location in the database, upon validation of a picking order, and a subsequent delivery order (DO)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Picking operation form moving product to WH/Output." +msgid "Filled out new sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:174 -msgid "Once the picking has been processed, the delivery order is generated, and can be processed." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:168 +msgid "Under the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select a product to add to the sales order quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:176 -msgid "Navigate back to the original sales order by going to :menuselection:`Sales app`, and selecting the associated sales order." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 +msgid "Delivery smart button on validated sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:179 -msgid "The :guilabel:`Delivery` smart button now indicates there are two transfers. Click the :guilabel:`Delivery` smart button to reveal each transfer tied to this sales order: the completed picking, and the new delivery (WH/OUT) operation. Click the delivery operation to open the delivery order." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:182 +msgid "Process picking" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:184 -msgid "Once ready, click :guilabel:`Validate` to complete the delivery." +msgid "Once the sales order is confirmed, a picking order is generated and ready to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:186 +msgid "To complete the picking, navigate to the :guilabel:`Inventory app`, and locate the :guilabel:`Pick` task card on the :guilabel:`Inventory Overview` dashboard. Alternatively, the picking order can also be accessed via the :guilabel:`Delivery` smart button at the top of the sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:190 +msgid "From the :guilabel:`Inventory Overview` page, click the :guilabel:`# To Process` button on the :guilabel:`Pick` task card. This reveals a list of all pickings to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:193 +msgid "Click on the picking (WH/PICK) operation associated with the sales order to reveal the picking order." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Delivery operation form moving product to customer location." +msgid "Picking order form for products included in sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:200 +msgid "Manually set the quantity by changing the value in the :guilabel:`Quantity` column, to match the value in the :guilabel:`Demand` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:203 +msgid "Once ready, click :guilabel:`Validate` to complete the picking, and move the product from :guilabel:`WH/Stock` to :guilabel:`WH/Output.`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:209 +msgid "Once the picking is validated, a delivery order is created, and ready to process. Clicking the :guilabel:`Delivery` smart button on the sales order form reveals the newly created delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:212 +msgid "Alternatively, to view the delivery order, navigate back to the :guilabel:`Inventory Overview` page, via the breadcrumbs, and locate the :guilabel:`Delivery Orders` task card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:215 +msgid "Click the :guilabel:`# To Process` button on the task card to reveal a list of all delivery orders to process, and select the order associated with the previously validated picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 +msgid "Delivery order form for products ordered by customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:222 +msgid "To deliver the products, change the value in the :guilabel:`Quantity` field to match the ordered quantity in the :guilabel:`Demand` field." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:3 @@ -6462,6 +7024,10 @@ msgstr "" msgid "Receive in three steps (input + quality + stock)" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 +msgid "Create a purchase order" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:50 msgid "To create a new :abbr:`RfQ (Request for Quotation)`, navigate to :menuselection:`Purchase app --> New`, which reveals a blank :abbr:`RfQ (Request for Quotation)` form page. On this page, select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`." msgstr "" @@ -6470,6 +7036,10 @@ msgstr "" msgid "A :guilabel:`Receipt` smart button will appear in the top right, and the receipt will be associated with the purchase order. Clicking on the :guilabel:`Receipt` smart button will show the receipt order." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 +msgid "After confirming a purchase order, a Receipt smart button will appear." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 msgid "Process a receipt" msgstr "" @@ -7467,7 +8037,7 @@ msgid "You need to write to xmlrequests@dhl.com along with your full Account det msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:3 -msgid "Set up Sendcloud shipping services in Odoo" +msgid "Sendcloud configuration" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:5 @@ -7495,15 +8065,15 @@ msgid "For new account creation, Sendcloud will ask for a :abbr:`VAT (Value-Adde msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:30 -msgid "Odoo integration of Sendcloud works on free Sendcloud plans *only* if a bank account is linked, since Sendcloud won't ship for free. To use shipping rules or individual custom carrier contacts, a paid plan of Sendcloud is required." +msgid "Odoo integration of Sendcloud works on free Sendcloud plans *only* if a bank account is linked, since Sendcloud won't ship for free. To use shipping rules, or individual custom carrier contacts, a paid plan of Sendcloud is **required**." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:37 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:174 msgid "Warehouse configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:39 msgid "Once logged into the Sendcloud account, navigate to :menuselection:`Settings --> Shipping --> Addresses`, and fill in the field for :guilabel:`Warehouse address`." msgstr "" @@ -7511,7 +8081,7 @@ msgstr "" msgid "Adding addresses in the Sendcloud settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:46 msgid "To allow Sendcloud to process returns as well, a :guilabel:`Return Address` is required. Under the :guilabel:`Miscellaneous section`, there is a field called :guilabel:`Address Name (optional)`. The Odoo warehouse name should be entered here, and the characters should be exactly the same." msgstr "" @@ -7551,23 +8121,23 @@ msgstr "" msgid ":guilabel:`Address`: `My Company (San Francisco)`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:63 msgid "Notice how the inputs for the :guilabel:`Warehouse` field, for both the Odoo configuration and the Sendcloud configuration, are the exact same." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:67 msgid "Generate Sendcloud credentials" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:67 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:69 msgid "In the Sendcloud account, navigate to :menuselection:`Settings --> Integrations` in the menu on the right. Next, search for :guilabel:`Odoo Native`. Then, click on :guilabel:`Connect`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:72 msgid "After clicking on :guilabel:`Connect`, the page redirects to the :guilabel:`Sendcloud API` settings page, where the :guilabel:`Public and Secret Keys` are produced. The next step is to name the :guilabel:`Integration`. The naming convention is as follows: `Odoo CompanyName`, with the user's company name replacing `CompanyName` (e.g. `Odoo StealthyWood`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:77 msgid "Then, check the box next to :guilabel:`Service Points` and select the shipping services for this integration. After saving, the :guilabel:`Public and Secret Keys` are generated." msgstr "" @@ -7575,87 +8145,91 @@ msgstr "" msgid "Configuring the Sendcloud integration and receiving the credentials." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:85 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:90 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:158 msgid "Setup in Odoo" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:86 -msgid "Install the Sendcloud shipping module" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:87 +msgid "To ensure seamless Sendcloud integration with Odoo, :ref:`install ` and :ref:`link ` the Sendcloud shipping connector to the Sendcloud account. Then, :ref:`configure Odoo fields `, so Sendcloud can accurately pull shipping data to generate labels." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:88 -msgid "After the Sendcloud account is set up and configured, it's time to configure the Odoo database. To get started, go to Odoo's :guilabel:`Apps` module, search for the :guilabel:`Sendcloud Shipping` integration, and install it." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:97 +msgid "Install Sendcloud shipping module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:99 +msgid "After the Sendcloud account is set up and configured, it's time to configure the Odoo database. To get started, go to Odoo's :guilabel:`Apps` module, search for the `Sendcloud Shipping` integration, and install it." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:-1 msgid "Sendcloud Shipping module in the Odoo Apps module." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:110 msgid "Sendcloud shipping connector configuration" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:112 msgid "Once installed, activate the :guilabel:`Sendcloud Shipping` module in :menuselection:`Inventory --> Configuration --> Settings`. The :guilabel:`Sendcloud Connector` setting is found under the :guilabel:`Shipping Connectors` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:116 msgid "After activating the :guilabel:`Sendcloud Connector`, click on the :guilabel:`Sendcloud Shipping Methods` link below the listed connector. Once on the :guilabel:`Shipping Methods` page, click :guilabel:`Create`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:121 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:115 msgid ":guilabel:`Shipping Methods` can also be accessed by going to :menuselection:`Inventory --> Configuration --> Delivery --> Shipping Methods`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:124 msgid "Fill out the following fields in the :guilabel:`New Shipping Method` form:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:126 msgid ":guilabel:`Shipping Method`: type `Sendcloud DPD`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:127 msgid ":guilabel:`Provider`: select :guilabel:`Sendcloud` from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:128 msgid ":guilabel:`Delivery Product`: set the product that was configured for this shipping method or create a new product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:130 msgid "In the :guilabel:`SendCloud Configuration` tab, enter the :guilabel:`Sendcloud Public Key`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:131 msgid "In the :guilabel:`SendCloud Configuration` tab, enter the :guilabel:`Sendcloud Secret Key`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:132 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:146 msgid "Manually :guilabel:`Save` the form by clicking the cloud icon next to the :guilabel:`Shipping Methods / New` breadcrumbs." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:135 msgid "After configuring and saving the form, follow these steps to load the shipping products:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:137 msgid "In the :guilabel:`SendCloud Configuration` tab of the :guilabel:`New Shipping Method` form, click on the :guilabel:`Load your SendCloud shipping products` link." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:139 msgid "Select the shipping products the company would like to use for deliveries and returns." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:140 msgid "Click :guilabel:`Select`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:143 msgid "Sample Sendcloud shipping products configured in Odoo:" msgstr "" @@ -7679,7 +8253,7 @@ msgstr "" msgid ":guilabel:`Maximum Weight`: `31.50`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:151 msgid ":guilabel:`Countries`: `Austria` `Belgium` `Bosnia` `Herzegovina` `Bulgaria` `Croatia` `Czech` `Republic` `Denmark` `Estonia` `Finland` `France` `Germany` `Greece` `Hungary` `Iceland` `Ireland` `Italy` `Latvia` `Liechtenstein` `Lithuania` `Luxembourg` `Monaco` `Netherlands` `Norway` `Poland` `Portugal` `Romania` `Serbia` `Slovakia` `Slovenia` `Spain` `Sweden` `Switzerland`" msgstr "" @@ -7712,64 +8286,88 @@ msgstr "" msgid "Example of shipping products configured in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:169 msgid "Sendcloud does not provide test keys when a company tests the sending of a package in Odoo. This means if a package is created, the configured Sendcloud account will be charged, unless the associated package is canceled within 24 hours of creation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:160 -msgid "Odoo has a built-in layer of protection against unwanted charges when using test environments. Within a test environment, if a shipping method is used to create labels, then those labels are immediately canceled after the creation — this occurs automatically. The test and production environment settings can be toggled back and forth from the :guilabel:`Smart Buttons`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:173 +msgid "Odoo has a built-in layer of protection against unwanted charges when using test environments. Within a test environment, if a shipping method is used to create labels, then those labels are immediately canceled after the creation — this occurs automatically. The test and production environment settings can be toggled back and forth from their respective smart buttons." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:166 -msgid "Generate a label with Sendcloud" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:181 +msgid "Shipping information" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:183 +msgid "To use Sendcloud to generate shipping labels, the following information **must** be filled out accurately and completely in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:186 +msgid "**Customer information**: when creating a quotation, ensure the selected :guilabel:`Customer` has a valid phone number, email address, and shipping address." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:189 +msgid "To verify, select the :guilabel:`Customer` field to open their contact page. Here, add their shipping address in the :guilabel:`Contact` field, along with their :guilabel:`Mobile` number and :guilabel:`Email` address." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:193 +msgid "**Product weight**: ensure all products in an order have a specified :guilabel:`Weight` in the :guilabel:`Inventory` tab of their product form. Refer to the :ref:`Product weight section ` of this article for detailed instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:197 +msgid "**Warehouse address**: ensure the warehouse name and address in Odoo match the :ref:`previously defined warehouse ` in the Sendcloud setup. For details on warehouse configuration in Odoo, refer to the :ref:`warehouse configuration section ` of the third-party shipping documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:204 +msgid "Generate labels with Sendcloud" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:206 msgid "When creating a quotation in Odoo, add shipping and a :guilabel:`Sendcloud shipping product`. Then, :guilabel:`Validate` the delivery. Shipping label documents are automatically generated in the chatter, which include the following:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:172 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:210 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:205 msgid ":guilabel:`Shipping label(s)` depending on the number of packages." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:211 msgid ":guilabel:`Return label(s)` if the Sendcloud connector is configured for returns." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:174 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:212 msgid ":guilabel:`Customs document(s)` should the destination country require them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:214 msgid "Additionally, the tracking number is now available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:179 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:217 msgid "When return labels are created, Sendcloud will automatically charge the configured Sendcloud account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:221 msgid "FAQ" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:186 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:224 msgid "Shipment is too heavy" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:188 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:226 msgid "If the shipment is too heavy for the Sendcloud service that is configured, then the weight is split to simulate multiple packages. Products will need to be put in different :guilabel:`Packages` to :guilabel:`Validate` the transfer and generate labels." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:192 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:230 msgid ":guilabel:`Rules` can also be set up in Sendcloud to use other shipping methods when the weight is too heavy. However, note that these rules will not apply to the shipping price calculation on the calculation on the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:197 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:235 msgid "Personal carrier contract" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:199 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:237 msgid "Use custom prices from a direct carrier contract, via CSV upload, by first logging into Sendcloud, navigating to :menuselection:`Settings --> Carriers --> My contracts`, and then selecting the intended contract." msgstr "" @@ -7777,11 +8375,11 @@ msgstr "" msgid "Navigate to the contracts section in Sendcloud." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:207 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:245 msgid "Under the :guilabel:`Contract prices` section, click :guilabel:`Download CSV` and fill out the contract prices in the :guilabel:`price` column of the CSV file template." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:249 msgid "Ensure the CSV file includes the correct prices to avoid any inaccuracies." msgstr "" @@ -7789,36 +8387,36 @@ msgstr "" msgid "Show sample contract CSV from Sendcloud, highlighting the price column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:217 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:255 msgid ":guilabel:`Upload` the completed CSV file to Sendcloud, then click :guilabel:`Save these prices`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:220 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:258 msgid "`Sendcloud: How to upload contract prices with carriers `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:224 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:262 msgid "Measuring volumetric weight" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:226 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:264 msgid "Many carriers have several measures for weight. There is the actual weight of the products in the parcel, and there is the *volumetric weight* (:dfn:`Volumetric weight is the volume that a package occupies when in transit. In other words it is the physical size of a package`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:231 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:269 msgid "Check to see if selected carrier(s) already have defined formulas to compute the volumetric weight." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:235 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:273 msgid "`Sendcloud: How to calculate & automate parcel volumetric weight `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:240 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:277 msgid "Unable to calculate shipping rate" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:242 -msgid "First, verify that product being shipped has a weight that is supported by the selected shipping method. If this is set, then verify that the destination country (from the customer address) is supported by the carrier. The country of origin (warehouse address) should also be supported by the carrier." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:279 +msgid "First, verify that the product being shipped has a weight that is supported by the selected shipping method. If this is set, then verify that the destination country (from the customer address) is supported by the carrier. The country of origin (warehouse address) should also be supported by the carrier." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:3 @@ -8821,7 +9419,7 @@ msgid "When picking in batches, orders are grouped and consolidated into a picki msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:15 -msgid ":ref:`Use Barcode app for pickings `" +msgid ":ref:`Use Barcode app for pickings `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:17 @@ -10221,7 +10819,7 @@ msgid "Once all changes have been made to the new inventory adjustment line, cli msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:94 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:160 msgid "If the :guilabel:`Counted Quantity` is greater than the :guilabel:`On Hand Quantity`, the value in the :guilabel:`Difference` column is **green**. If the :guilabel:`Counted Quantity` is less than the :guilabel:`On Hand Quantity`, the value in the :guilabel:`Difference` column is **red**. If the quantities match, and haven't been changed at all, no value appears in the :guilabel:`Difference` column." msgstr "" @@ -10245,23 +10843,27 @@ msgstr "" msgid "Once ready, click :guilabel:`Apply` to apply the inventory adjustment." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:121 +msgid "Applying an inventory adjustment simultaneously creates a :doc:`stock move line (SML) <../reporting/moves_history>` in the *Moves History* report for traceability." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:-1 msgid "Apply all option applies the inventory adjustment once a reason is specified." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:125 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:129 msgid "Count products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:131 msgid "Counting products is a recurring activity in a warehouse. Once a count is complete, go to :menuselection:`Inventory app --> Operations --> Inventory Adjustments` to update the :guilabel:`Counted Quantity` column for each product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:131 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:135 msgid "On each product line, identify whether the value in the :guilabel:`On Hand Quantity` column recorded in the database matches the newly-counted value. If the recorded value and the counted value do match, click the :guilabel:`Set` button (target icon) at the far right of the product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:139 msgid "Doing so copies the value from the :guilabel:`On Hand Quantity` column over to the :guilabel:`Counted Quantity` column, and sets the value of the :guilabel:`Difference` column to `0.00`. Subsequently, once applied, an inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the product's inventory adjustment history." msgstr "" @@ -10269,19 +10871,19 @@ msgstr "" msgid "Zero count inventory adjustment move." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:148 msgid "If the newly-counted value for a given product does **not** match the value in the :guilabel:`On Hand Quantity` recorded in the database, instead of clicking the :guilabel:`Set` button, record the real value in the field in the :guilabel:`Counted Quantity` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:148 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:152 msgid "To do so, click the field in the :guilabel:`Counted Quantity` column on the specific inventory adjustment line for the product whose count is being changed. This automatically assigns a :guilabel:`Counted Quantity` of `0.00`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:152 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:156 msgid "To change this value, type in a new value that matches the real, newly-counted value. Then, click away from the line. Doing so saves the adjustment, and automatically adjusts the value in the :guilabel:`Difference` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:162 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:166 msgid "Subsequently, once applied, a move with the difference between the :guilabel:`On Hand Quantity` and the :guilabel:`Counted Quantity` is recorded in the product's inventory adjustment history." msgstr "" @@ -10289,19 +10891,19 @@ msgstr "" msgid "Inventory Adjustments History dashboard detailing a list of prior product moves." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:170 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:174 msgid "Sometimes a count occurs, but cannot be applied in the database right away. In the time between the actual count and applying the inventory adjustment, product moves can occur. In that case, the on-hand quantity in the database can change and no longer be consistent with the counted quantity. As an extra precaution, Odoo asks for confirmation before applying the inventory adjustment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:177 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:181 msgid "Change inventory count frequency" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:179 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:183 msgid "By default, the *scheduled date* for inventory adjustments are always scheduled for the 31st of December of the current year. However, for some companies, it is crucial that they have an accurate inventory count at all times. In such cases, the default scheduled date can be modified." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:187 msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting, which includes a drop-down menu that is set to `31 December` by default." msgstr "" @@ -10309,32 +10911,32 @@ msgstr "" msgid "Adjust the next inventory count date with the Annual Inventory Day and Month setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:195 msgid "To change the day, click the :guilabel:`31`, and change it to a day within the range `1-31`, depending on the desired month of the year." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:194 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:198 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:117 msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:197 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:201 msgid "Once all desired changes have been made, click :guilabel:`Save` to save all changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:200 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:204 msgid "Plan big inventory counts" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:202 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:206 msgid "To plan big inventory counts, such as a full count of everything currently in stock, first navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:205 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:209 msgid "Then, select the desired products to be counted by clicking the checkbox on the far left of each product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:213 msgid "To request a count of **all** products currently in stock, click the checkbox at the very top of the table, in the header row next to the :guilabel:`Location` label. This selects **all** product lines." msgstr "" @@ -10342,35 +10944,35 @@ msgstr "" msgid "Request a count popup on inventory adjustments page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:217 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:221 msgid "Once all desired products have been selected, click the :guilabel:`Request a Count` button at the top of the page. This causes a :guilabel:`Request a Count` pop-up window to appear. From this pop-up, fill in the following information:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:221 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:225 msgid ":guilabel:`Inventory Date`: the planned date of the count." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:222 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:226 msgid ":guilabel:`User`: the user responsible for the count." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:223 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:227 msgid ":guilabel:`Accounting Date`: the date at which the inventory adjustment will be accounted." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:224 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:228 msgid ":guilabel:`Count`: to leave the on-hand quantity of each product line blank, select :guilabel:`Leave Empty`. To pre-fill the on-hand quantity of each product line with the current value recorded in the database, select :guilabel:`Set Current Value`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:228 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:232 msgid "Finally, once ready, click :guilabel:`Confirm` to request the count." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:231 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:235 msgid "In the Odoo *Barcode* app, users can only view inventory counts that are assigned to **them**, and are scheduled for **today** or **earlier**." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:235 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:239 msgid ":doc:`cycle_counts`" msgstr "" @@ -10379,147 +10981,192 @@ msgid "Create a second warehouse" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:5 -msgid "A *warehouse* is a physical building or space where items are stored. In Odoo, it is possible to set up multiple warehouses and transfer stored items between them." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:11 +msgid "In Odoo *Inventory*, a *warehouse* is a physical building or space where items are stored. By default, each Odoo database has one warehouse already pre-configured, with the address set as the company's address." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:8 -msgid "By default, the Odoo platform has one warehouse that is already configured, with the address set as the company's address. To create a second warehouse, select :menuselection:`Configuration --> Warehouses`, then click :guilabel:`Create` and configure the form as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:12 -msgid ":guilabel:`Warehouse`: the full name of the warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:13 -msgid ":guilabel:`Short Name`: the abbreviated code by which the warehouse is referred to; the short name for the default warehouse in Odoo is **WH**" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:9 +msgid "However, it is possible to set up multiple additional warehouses, and transfer stored items between them." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:15 -msgid ":guilabel:`Company`: the company that owns the warehouse; this can be set as the company that owns the Odoo database or the company of a customer or vendor" +msgid "To create a second warehouse, the *Storage Locations* feature must be enabled. To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Warehouse` section, tick the checkbox next to :guilabel:`Storage Locations`, and :guilabel:`Save` changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:17 -msgid ":guilabel:`Address`: the address where the warehouse is located" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:20 -msgid "The options below will only appear if the :guilabel:`Multi-Step Routes` checkbox is enabled in :menuselection:`Configuration --> Settings` under the :guilabel:`Warehouse` heading. For more information about routes and how they work in Odoo, see :ref:`Using Routes and Pull/Push Rules `." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 +msgid "Warning pop-up window for creating a second warehouse before enabling Storage Locations." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:25 -msgid ":guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and outgoing shipments should follow" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:97 +msgid "Creating a second warehouse without first enabling the *Storage Locations* feature triggers a :guilabel:`Warning` pop-up window. It indicates creating a second warehouse automatically activates the *Storage Locations* setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:27 -msgid ":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied from this warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:30 +msgid "Create new warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:28 -msgid ":guilabel:`Manufacture to Resupply`: allow for items to be manufactured in this warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:70 +msgid "To create a new warehouse, navigate to :menuselection:`Inventory app --> Configuration --> Warehouses`, and click :guilabel:`New`. Doing so opens a blank warehouse creation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:29 -msgid ":guilabel:`Manufacture`: select the route that should be followed when manufacturing goods inside the warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:35 +msgid "Fill out the following fields as necessary:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:31 -msgid ":guilabel:`Buy to Resupply`: check the box to allow for purchased products to be delivered to the warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:37 +msgid ":guilabel:`Warehouse`: the full name of the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:33 -msgid ":guilabel:`Resupply From`: select warehouses that can be used to resupply the warehouse being created" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:38 +msgid ":guilabel:`Short Name`: the abbreviated code used to identify the warehouse, i.e. `WH2` (the short name for the default warehouse in Odoo is `WH`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:40 +msgid ":guilabel:`Company`: the company that owns the warehouse. This can be set as the company that owns the Odoo database or the company of a customer or vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:42 +msgid ":guilabel:`Address`: the address where the warehouse is located. By default, this is set to the company's address in the database." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 -msgid "A filled out form for creating a new warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:41 -msgid "Creating a second warehouse will automatically enable the *Storage Locations* setting, which allows location tracking of products within a warehouse. To toggle this setting, navigate to :menuselection:`Configuration --> Settings` and click the checkbox under the :guilabel:`Warehouse` heading." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:46 -msgid "After filling out the form, click :guilabel:`Save` and the new warehouse will be created." +msgid "Filled out warehouse name and address settings on warehouse creation form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:49 -msgid "Add inventory to a new warehouse" +msgid "Under the :guilabel:`Warehouse Configuration` tab, configure the warehouse's main workflow in the :guilabel:`Shipments` section, and set available replenishment methods in the :guilabel:`Resupply` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:51 -msgid "If a new warehouse is created that has existing inventory in it, the inventory counts should be added to Odoo so that the stock listed in the Odoo database reflects what is in the physical warehouse. To add inventory to a new warehouse, navigate to :menuselection:`Inventory --> Operations --> Inventory Adjustments`, and then click :guilabel:`Create`. The inventory adjustment form can then be filled out as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:57 -msgid ":guilabel:`Inventory Reference`: the name or code that the inventory adjustment can be referred to by" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:54 +msgid "The :guilabel:`Shipments` and :guilabel:`Resupply` sections only appear if the :guilabel:`Multi-Step Routes` checkbox is enabled in :menuselection:`Inventory app --> Configuration --> Settings`, under the :guilabel:`Warehouse` heading. For more information about routes and how they work in Odoo, see :ref:`Using Routes and Pull/Push Rules `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:59 -msgid ":guilabel:`Locations`: the location(s) where the inventory is stored; include the new warehouse and any locations within it that inventory will be added to" +msgid "In the :guilabel:`Shipments` section, choose between one, two, or three-step processes for both incoming and outgoing shipments." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:61 -msgid ":guilabel:`Products`: include all products that will be added to inventory or leave blank to select any product during the next step" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:62 +msgid "In the :guilabel:`Resupply` section, edit the following settings:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:63 -msgid ":guilabel:`Include Exhausted Products`: include products with a quantity of zero; does not affect inventory adjustments for new warehouses since they have no existing inventory" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:64 +msgid ":guilabel:`Dropship Subcontractors`: enable this feature to coordinate with vendors, and have components dropshipped directly to subcontractors for manufacturing." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:65 -msgid ":guilabel:`Accounting Date`: the date used by accounting teams for bookkeeping related to the inventory" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:66 +msgid ":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied with goods from this warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:67 -msgid ":guilabel:`Company`: the company that owns the inventory; can be set as the user's company or as a customer or vendor" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:68 +msgid ":guilabel:`Manufacture to Resupply`: when products are manufactured, they can be delivered to this warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:69 -msgid ":guilabel:`Counted Quantities`: choose whether the counted quantities for products being added should default to stock on hand or zero; does not affect inventory adjustments for new warehouses since they have no existing inventory" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:70 +msgid ":guilabel:`Manufacture`: the route that should be followed when manufacturing goods inside the warehouse. Choose from one, two, and three-step production." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:72 +msgid ":guilabel:`Buy to Resupply`: when products are purchased, they can be delivered to this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:73 +msgid ":guilabel:`Resupply From`: Check the box next to the other warehouses from which this warehouse can replenish products. If the current warehouse does not have the stock, it can also pull products from these selected warehouses in the database. Automatic resupply routes will be created accordingly." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 -msgid "A filled out form for an inventory adjustment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:77 -msgid "Once the form is properly configured, click on :guilabel:`Start Inventory` to be taken to the next page where products can be added to the inventory adjustment. Add a new product by clicking on :guilabel:`Create` and then fill out the product line as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:81 -msgid ":guilabel:`Product`: the product being added to inventory" +msgid "Filled out Warehouse Configuration tab settings on warehouse creation form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:82 -msgid ":guilabel:`Location`: the location where the product is currently stored in the new warehouse; this can be set as the overall warehouse or a location within the warehouse" +msgid "Once ready, click :guilabel:`Save` to save the new warehouse's settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:84 -msgid ":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the serial number used to identify it" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:85 +msgid "Add inventory to a new warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:86 -msgid ":guilabel:`On Hand`: the total quantity of the product stored in the location for which inventory is being adjusted; this should be zero for a new location or warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:88 -msgid ":guilabel:`Counted`: the amount of the product that is being added to inventory" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:89 -msgid ":guilabel:`Difference`: the difference between the *On Hand* and *Counted* values; this will automatically update to reflect the value entered in the :guilabel:`Counted` column" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:87 +msgid "If a new warehouse is created to represent a real-world storage location with existing stock, update the warehouse's stock using an inventory adjustment." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:91 -msgid ":guilabel:`UoM`: the unit of measure used for counting the product" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:123 +msgid ":doc:`count_products`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 -msgid "Include a line for each product being added to inventory." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:93 +msgid "To perform an inventory adjustment, navigate to :menuselection:`Inventory app --> Operations --> Physical Inventory`, and click :guilabel:`New`. Doing so adds a new line at the bottom of the list of inventory adjustments." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:97 -msgid "After adding all the products already stored in the new warehouse, click :guilabel:`Validate Inventory` to complete the inventory adjustment. The values in the :guilabel:`On Hand` column will update to reflect those in the :guilabel:`Counted` column and the products added will appear in the inventory of the new warehouse." +msgid "Configure the line by filling out the following fields as necessary:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:99 +msgid ":guilabel:`Location`: the location where the product is currently stored in the new warehouse. This can be set as the overall warehouse, or a location within the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:101 +msgid ":guilabel:`Product`: the product being added to inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:102 +msgid ":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the serial number used to identify it, if the product is tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:104 +msgid ":guilabel:`On Hand Quantity`: the total quantity of the product stored in the location for which inventory is being adjusted. For a new warehouse or location where a count or a prior inventory adjustment has not taken place, this should be set to `0.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:107 +msgid ":guilabel:`UoM`: the unit of measure (UoM) used for counting the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:108 +msgid ":guilabel:`Counted Quantity`: the amount of the product being added to inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:109 +msgid ":guilabel:`Difference`: the difference between the on-hand and counted quantities. This automatically updates to reflect the value entered in the :guilabel:`Counted Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:111 +msgid ":guilabel:`Scheduled Date`: the date selected for the next inventory count for this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:112 +msgid ":guilabel:`User`: the user who recorded the inventory adjustment in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 +msgid "Filled out inventory adjustment line for product in new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:118 +msgid "Once each line for the products being added to the new warehouse is configured, click :guilabel:`Apply` on each line to apply the new inventory counts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:121 +msgid "The values in the :guilabel:`On Hand Quantity` column update to reflect those in the :guilabel:`Counted Quantity` column, and the products added appear in the new warehouse's stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:125 +msgid "If products tracked using a lot number or serial number are added without specifying the tracking number, a :guilabel:`Tracked Products in Inventory Adjustment` pop-up window appears upon clicking :guilabel:`Apply` on that product's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:129 +msgid "The pop-up indicates tracked products were added, but the lots/serial numbers were not defined. To apply the adjustment without the numbers, click :guilabel:`Apply`. To add the numbers before applying, click :guilabel:`Discard`, and add the numbers. Then, once ready, click :guilabel:`Apply` again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:0 +msgid "Tracked Products in Inventory Adjustment pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:139 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:118 +msgid ":doc:`warehouses_locations`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:3 @@ -10646,10 +11293,6 @@ msgstr "" msgid "Once all necessary changes have been made, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:123 -msgid ":doc:`count_products`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:124 msgid ":doc:`use_locations`" msgstr "" @@ -10722,99 +11365,136 @@ msgstr "" msgid "Scrap inventory" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:5 -msgid "In some cases, a product in inventory may be damaged or found to be defective. If it is not possible to repair or return the product, Odoo *Inventory* allows users to scrap it, ensuring that usable inventory counts remain accurate." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:8 +msgid "Sometimes, products in a company's warehouse stock might be found to be damaged or defective, past the point of being reparable. If it is not possible to repair the product, or return the product to a vendor, it can be scrapped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:10 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:25 -msgid "Scrap orders can be viewed by navigating to :menuselection:`Inventory --> Operations --> Scrap`. Each scrap order shows the date and time the order was created, along with the product and quantity that was scrapped." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:12 +msgid "Odoo *Inventory* allows users to scrap inventory, designating goods or materials that are no longer usable or sellable for disposal (or recycling)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:14 -msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`. Remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display virtual locations. Finally, select the :guilabel:`Virtual Locations/Scrap` location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:15 +msgid "Scrapping inventory in a database helps stock counts remain accurate, by removing scrapped products from physical inventory, and placing it in a virtual scrap location (*Virtual Locations/Scrap*)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:19 -msgid "By default, scrapping a product removes it from physical inventory, and places it in a virtual location titled *Virtual Locations/Scrap*. A virtual location is **not** a physical space, but rather a designation in Odoo that is used to track items that are no longer in physical inventory." +msgid "*Virtual locations* in Odoo are **not** real, physical spaces in a warehouse. Rather, they are designated locations in a database that provide tracking of items that shouldn't be counted in a physical inventory." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:23 -#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:30 -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:68 -msgid "Learn more" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:25 msgid "For more information about virtual locations, see the documentation about the different types of :ref:`locations `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:29 +msgid "To use locations in warehouse, including a virtual scrap location, the *Storage Locations* feature must first be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:32 +msgid "To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Tick the checkbox next to :guilabel:`Storage Locations` to enable the feature, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 +msgid "Enabled Storage Locations setting in Inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:41 msgid "Scrap from stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:31 -msgid "To scrap a product located in inventory, begin by navigating to :menuselection:`Inventory --> Operations --> Scrap`. On the :guilabel:`Scrap Orders` page, click :guilabel:`Create` to configure a new scrap order." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:43 +msgid "To create a new scrap order (SP) for an in-stock product, navigate to :menuselection:`Inventory app --> Operations --> Scrap`, and click :guilabel:`New`. This opens a new |SP| form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:35 -msgid "On the scrap order, select the product being scrapped from the :guilabel:`Product` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:46 +msgid "Click the drop-down menu in the :guilabel:`Product` field, and select the product that should be scrapped from inventory. In the :guilabel:`Quantity` field, change the value to the quantity of the product that should be scrapped (by default, this value is set to `1.00`)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 -msgid "A new scrap order." +msgid "Filled out new scrap order form with product details." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:45 -msgid "Finally, click :guilabel:`Validate` to scrap the product. The on-hand inventory count for the scrapped product updates to subtract the scrapped quantity." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:54 +msgid "The :guilabel:`Source Location` defaults to the location where the product is currently stored. The :guilabel:`Scrap Location` defaults to the designated scrap location (:guilabel:`Virtual Locations/Scrap`). Either of these locations can be changed by selecting a different location from their respective drop-down menus." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:49 -msgid "Scrap from a receipt, transfer, or delivery" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:59 +msgid "If the scrapping is tied to a specific existing operation, specify the operation in the :guilabel:`Source Document` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:51 -msgid "It is also possible to scrap products during the receipt, transfer, and delivery operations. This can be necessary if any products are found to be defective when receiving them into inventory, transferring them from one location to another, or preparing them for delivery." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:55 -msgid "To scrap a product during the receipt, transfer, or delivery operations, begin by navigating to the :menuselection:`Inventory` app. On the :guilabel:`Overview` page, select the :guilabel:`# TO PROCESS` button on the :guilabel:`Receipts`, :guilabel:`Internal Transfers`, or :guilabel:`Delivery Orders` card, depending on the type of operation the product is being scrapped from." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:61 -msgid "For the :guilabel:`Internal Transfers` card to appear on the :menuselection:`Overview` page of the :menuselection:`Inventory` app, the :guilabel:`Storage Locations` setting must be enabled. To do so, navigate to :menuselection:`Configuration --> Settings`, then enable the checkbox next to :guilabel:`Storage Locations` under the :guilabel:`Warehouse` heading." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:62 +msgid "The :guilabel:`Company` field displays the company whose warehouse this product belongs to. If a replenishment rule is set up for the product being scrapped, and if the product should be replenished, tick the checkbox for :guilabel:`Replenish Quantities`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:66 -msgid "Alternatively, a list of all delivery orders, receipts, and transfers can be viewed by navigating to :menuselection:`Inventory --> Operations --> Transfers`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:69 -msgid "Next, open a delivery order, receipt, or transfer from the corresponding page by clicking on it. A :guilabel:`Scrap` button appears at the top of the page. Click it to open the :guilabel:`Scrap` pop-up window." +msgid "Once ready, click :guilabel:`Validate` to complete the new |SP|. Once validated, a :guilabel:`Product Moves` smart button appears at the top of the form. Click the smart button to view the details of the scrap operation." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 -msgid "The scrap pop-up in the Inventory app." +msgid "Product Moves smart button on new scrap order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:78 -msgid "The :guilabel:`Scrap` button will only appear on a receipt that has been validated. This is because Odoo only allows products to be scrapped once they have been entered into inventory." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:75 +msgid "To view the all-time total quantities of scrapped items, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. Click the :guilabel:`x (remove)` button on the :guilabel:`Internal` filter in the :guilabel:`Search...` bar, to display virtual locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:81 -msgid "On the :guilabel:`Scrap` pop-up window, select the product being scrapped from the :guilabel:`Product` drop-down menu. Then, enter the quantity in the :guilabel:`Quantity` field." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:79 +msgid "Select the :guilabel:`Virtual Locations/Scrap` location. From the :guilabel:`Scrap` location's form, click the :guilabel:`Current Stock` smart button, at the top of the form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:84 -msgid "The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:82 +msgid "A list of all scrapped products, and their quantities, is displayed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:88 -msgid "Finally, click :guilabel:`Done` to scrap the product. After doing so, the :guilabel:`Scrap` pop-up window disappears and a :guilabel:`Scraps` smart button appears in the top right of the page. Click it to view all of the scrap orders created from that operation." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:0 +msgid "Current Stock list of all scrapped products in virtual scrap location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:89 +msgid "Scrap from an existing operation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:91 +msgid "Scrap orders (SPs) can *also* be created from existing operations, such as receipts, delivery orders, and internal transfers, before they are entered into, or removed from, stock for an operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:95 +msgid "To scrap a product during an operation, navigate to the :menuselection:`Inventory app`. From the :guilabel:`Inventory Overview`, click the :guilabel:`# To Process` button on an operation's task card (i.e. the :guilabel:`Receipts` task card)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 -msgid "The Scraps smart button." +msgid "# To Process button on Receipts task card on Inventory Overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:103 +msgid "Then, select an operation to process from the resulting list of existing orders. Doing so opens that operation's form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:106 +msgid "Click the :icon:`fa-cog` :guilabel:`(cog)` icon, and select :guilabel:`Scrap` from the resulting drop-down menu. This opens a :guilabel:`Scrap Products` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 +msgid "Scrap Products pop-up window on operation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:113 +msgid "From this pop-up window, click the drop-down menu in the :guilabel:`Product` field, and select the products from the operation that should be scrapped. Adjust the value in the :guilabel:`Quantity` field, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:117 +msgid "If the :guilabel:`Product` selected is tracked using a lot or serial number, a :guilabel:`Lot/Serial` field appears. Specify the tracking number in that field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:120 +msgid "The :guilabel:`Source Location` and :guilabel:`Scrap Location` can be changed, if needed. If a replenishment rule is set up for the product being scrapped, and if the product should be replenished, tick the checkbox for :guilabel:`Replenish Quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:124 +msgid "Once ready, click :guilabel:`Scrap Products`. A :guilabel:`Scraps` smart button appears at the top of the operation form. Click this smart button to view the details of all scrap orders created from this specific operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 +msgid "Scraps smart button showing all scrap orders from operation." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:3 @@ -10822,83 +11502,149 @@ msgid "Locations" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:5 -msgid "A *location* is a specific space within a warehouse. This can be a shelf, room, aisle, etc. There are three types of locations in Odoo:" +msgid "In Odoo *Inventory*, a *location* is a specific space within a warehouse. This can be a shelf, room, aisle, rack, bin, etc." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 -msgid "*Physical locations* are spaces within a warehouse owned by the user's company. These can be a an area where items are stored like an aisle or shelf, or an area where operations take place, like loading and unloading bays." +msgid "There are also external and virtual locations. For example, customer locations, and locations specifically designated as \"virtual\", instead of real, physical locations." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:11 -msgid "*Partner locations* are the same as physical locations except that they exist within the warehouse of a customer or vendor." +msgid "Locations allow for the storage of products in designated areas of the warehouse, to help track inventory accurately." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:13 -msgid "*Virtual locations* are locations that do not exist physically, but where items that are not in inventory can be placed. These can be items that have not yet entered inventory, like products that are on the way to a warehouse, or items that are no longer in inventory due to loss or other factors." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:19 -msgid "In order to use locations, the :guilabel:`Storage Locations` setting must be enabled. To do so, navigate to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the :guilabel:`Warehouse` heading, and enable the :guilabel:`Storage Locations` checkbox." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:24 -msgid "Create a new location inside a warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:26 -msgid "Starting from the :menuselection:`Inventory` app, select :menuselection:`Configuration --> Locations --> Create`. The new location form can then be configured as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:29 -msgid ":guilabel:`Location Name`: the name that will be used to reference the location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:30 -msgid ":guilabel:`Parent Location`: the location or warehouse that the new location exists within" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:31 -msgid ":guilabel:`Location Type`: choose the category that the location belongs to" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:32 -msgid ":guilabel:`Company`: the company that owns the warehouse that the location is inside of" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:33 -msgid ":guilabel:`Is a Scrap Location?`: check this box to allow for scrapped/damaged goods to be stored in this location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:35 -msgid ":guilabel:`Is a Return Location?`: check this box to allow products to be returned to this location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:37 -msgid ":guilabel:`Barcode`: the barcode number assigned to the location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:38 -msgid ":guilabel:`Removal Strategy`: the :doc:`strategy <../removal_strategies>` for how items should be taken from inventory" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:17 +msgid "To specify storage locations, the *Storage Locations* setting must be enabled. To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Tick the checkbox next to :guilabel:`Storage Locations` to enable the feature, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 -msgid "The form for creating a new location." +msgid "Enabled Storage Location setting in Inventory app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:48 -msgid "Create location hierarchies" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:26 +msgid "Once the :guilabel:`Storage Locations` feature is enabled, two additional internal link options appear below it: :guilabel:`Locations` and :guilabel:`Putaway Rules`. Click :guilabel:`Locations` to open a list of all existing locations in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:31 +msgid "Create a new location inside a warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:104 +msgid "To create a new location inside a warehouse, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. Doing so opens a list of all existing locations. Click :guilabel:`New` to open a new location creation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:108 +msgid "In the :guilabel:`Location Name` field, assign a name for the new location. In the :guilabel:`Parent Location` field, assign the location that this new location exists in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:41 +msgid "A new location `Gate 1` is created. Its parent location is `Dispatch Zone`. In the :guilabel:`Parent Location` for `Gate 1`, select `Dispatch Zone`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:44 +msgid "In the :guilabel:`Additional Information` section, fill out the necessary details for the new location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:47 +msgid "In the :guilabel:`Location Type` field, select which type of location this is. There are seven different types of locations to choose from:" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:50 -msgid "The *Parent Location* setting on the new location form allows for a location to exist within a warehouse or another location. Every location can serve as a parent location, and every parent location can have multiple locations within it, allowing for the creation of a virtually infinite hierarchical structure." +msgid ":guilabel:`Vendor Location`: virtual location representing the source location for products coming from vendors." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:56 -msgid "Location hierarchy could be organized so that a shelf is located within an aisle, which is located within a room, which is located within the overall warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:52 +msgid ":guilabel:`View`: virtual location used to create a hierarchical structure for a warehouse; aggregates its child locations. **Should not directly contain products**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:54 +msgid ":guilabel:`Internal Location`: physical location inside a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:55 +msgid ":guilabel:`Customer Location`: virtual location representing the destination location for products sent to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:57 +msgid ":guilabel:`Inventory Loss`: virtual location serving as a counterpart for inventory operations. Used to correct stock levels of physical inventory." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:59 -msgid "To create the location hierarchy in the example above, set the warehouse as the parent of the room, the room as the parent of the aisle, and the aisle as the parent of the shelf. This can be adapted to a hierarchy of any magnitude." +msgid ":guilabel:`Production`: virtual counterpart location for production operations. This location consumes components and produces finished products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:61 +msgid ":guilabel:`Transit Location`: counterpart location that should be used in inter-company or inter-warehouse operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 +msgid "Additional Information section of new location creation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:68 +msgid "Configure the remaining fields in the :guilabel:`Additional Information` section as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:70 +msgid ":guilabel:`Company`: the company whose warehouse the location is inside of. Leave this field blank if this location is shared between companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:72 +msgid ":guilabel:`Is a Scrap Location?`: tick this checkbox to allow for scrapped/damaged goods to be stored in this location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:74 +msgid ":guilabel:`Is a Return Location?`: tick this checkbox to allow products to be returned to this location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:76 +msgid ":guilabel:`Barcode`: the barcode assigned to the location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:77 +msgid ":guilabel:`Replenish Location`: tick this checkbox to get all quantities to replenish at this location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:80 +msgid "In the :guilabel:`Cyclic Counting` section, change the value in the :guilabel:`Inventory Frequency (Days)` field from the default `0`, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 +msgid "Cyclic Counting section of new location creation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:87 +msgid "When different than `0`, the inventory count dates for products stored at this location are automatically set at the defined frequency." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:90 +msgid "In the :guilabel:`Logistics` section, in the :guilabel:`Removal Strategy` field, click the drop-down menu and select the :doc:`removal strategy <../removal_strategies>` for how items should be removed from this location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:97 +msgid "Create location hierarchies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:99 +msgid "The *Parent Location* setting on the new location form allows for a location to exist within a warehouse, or below another location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:102 +msgid "Every location can serve as a parent location, and every parent location can have multiple locations within it, allowing for the creation of a hierarchical structure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:106 +msgid "Location hierarchy could be organized so that a small refrigerator is located on a specific shelf, which is located in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 +msgid "Location hierarchy of small refrigerator, on a shelf in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:113 +msgid "To create the location hierarchy in the example above (`WH/Stock/Shelf 2/Small Refrigerator`), set the warehouse stock as the parent of the shelf, and the shelf as the parent of the small refrigerator. This can be adapted to a hierarchy of any magnitude." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:5 @@ -11363,6 +12109,10 @@ msgstr "" msgid "The delivery orders card for the outgoing warehouse." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 +msgid "Process the receipt" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:99 msgid "Once the goods arrive at the incoming warehouse, the receipt created for that warehouse must be processed as well. Return to the :menuselection:`Inventory` dashboard and select the :guilabel:`X to Process` button on the :guilabel:`Receipts` card for the incoming warehouse, then the receipt created for the replenishment. On the receipt page, click the :guilabel:`Validate` button in the top left of the page to register the quantities received." msgstr "" @@ -11420,102 +12170,111 @@ msgid "After the scheduler runs, a delivery order and receipt will be created fo msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:3 -msgid "Manage Warehouses and Locations" +msgid "Manage warehouses and locations" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:9 msgid "Warehouse" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:11 -msgid "In Odoo, a *warehouse* is the actual building/place in which a company's items are stocked. Multiple warehouses can be set up in Odoo and the user can create moves between warehouses." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:15 +msgid "Multiple warehouses can be set up in Odoo, and stock moves can be created between warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:19 -msgid "A **Location** is a specific space within the warehouse. It can be a sublocation of the warehouse (a shelf, a floor, an aisle, and so on). Therefore, a location is part of one warehouse only and it is not possible to link one location to multiple warehouses. In Odoo, as many locations can be configured as needed under one warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:24 -msgid "There are three types of locations:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:22 +msgid "In Odoo *Inventory*, a *location* is a specific space within a warehouse. This can be a shelf, room, aisle, rack, bin, etc. Locations allow for the storage of products in designated areas of the warehouse, to help track inventory accurately." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:26 -msgid "The **Physical Locations** are internal locations that are part of the warehouses that the company owns. They can be the loading and unloading areas of the warehouse, a shelf, a department, etc." +msgid "A location is only part of *one* warehouse, and can **not** be linked to multiple warehouses. As many locations can be configured as needed under one warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:30 -msgid "The **Partner Locations** are spaces within a customer and/or vendor's warehouse. They work the same way as physical locations, with the only difference being that they are not owned by the user's company." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:29 +msgid "There are three types of locations in Odoo *Inventory*:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:34 -msgid "The **Virtual Locations** are places that do not exist, but in which products can be placed when they are not physically in an inventory yet (or anymore). They come in handy when recording lost products (**Inventory Loss**), or accounting for products that are on their way to the warehouse (**Procurements**)." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:31 +msgid "**Physical Locations**: internal locations within a single warehouse owned by the company. This can include shipping and loading docks, aisles, shelves, storage areas, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:39 -msgid "In Odoo, locations are structured hierarchically. Locations can be structured as a tree, dependent on a parent-child relationship. This gives more detailed levels of analysis of the stock operations and the organization of the warehouses." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:33 +msgid "**Partner Locations**: external locations, such as designated spaces in a customer or vendor's warehouse. They are similar to physical locations, but they are **not** owned by the user's company." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:46 -msgid "To activate locations, go to :menuselection:`Configuration --> Settings` and enable :guilabel:`Storage Locations`. Then, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:36 +msgid "**Virtual Locations**: this type of location does not exist as a physical space, but products can be \"stored\" here when they are not physically in an inventory yet. *Inventory Loss* and *Procurements* are examples of virtual locations, for products that are lost or in transit to the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 -msgid "Enable the storage location feature in Odoo Inventory settings." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:41 +msgid "Every location within a warehouse can serve as a parent location, and every parent location can have multiple locations within it, allowing for the creation of a hierarchical structure. This allows for more detailed levels of analysis of the stock operations and the organization of the warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:48 +msgid "For companies with one warehouse, no additional settings are required to activate before editing the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:51 +msgid "For companies with multiple warehouses, and to create locations within a warehouse, the *Storage Locations* feature must be enabled." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:54 -msgid "To manage several routes within the warehouses, also enable :guilabel:`Multi-Step Routes` and check :doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes`." +msgid "To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Tick the :guilabel:`Storage Locations` checkbox to enable the feature, and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:58 -msgid "Create a new warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:60 -msgid "To create a warehouse, go to :menuselection:`Configuration --> Warehouse Management --> Warehouses` and click on :guilabel:`Create`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 +msgid "Storage Locations feature enabled in the Inventory app settings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:63 -msgid "Then, fill out a :guilabel:`Warehouse Name` and a :guilabel:`Short Name`. The short name is five characters maximum." +msgid "To manage warehouse *routes*, such as two-and-three-step receipts and deliveries, enable the *Multi-Step Routes* feature from the *Inventory* app settings, as well. For more on routes, see :doc:`use_routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:68 +msgid "Create a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:73 +msgid "Begin by assigning a :guilabel:`Warehouse Name`, and a :guilabel:`Short Name`. The :guilabel:`Short Name` field is limited to a **five** character maximum." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 -msgid "Short name field of a warehouse on Odoo Inventory." +msgid "New warehouse creation form name configuration fields." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:71 -msgid "The :guilabel:`Short Name` appears on transfer orders and other warehouse documents. Odoo recommends using an understandable one like \"WH/[first letters of location]\"." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:81 +msgid "The :guilabel:`Short Name` appears on transfer orders and other warehouse documents. Odoo recommends using an understandable one like `WH/[first letters of location]`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:74 -msgid "Now, go back to the :guilabel:`Inventory` dashboard. There, new operations related to the newly created warehouse have been automatically generated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 -msgid "Inventory app dashboard displaying new transfer types for the recently created warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:82 -msgid "Adding a second warehouse will automatically activate the :guilabel:`Locations` setting." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:85 -msgid "Create a new location" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:84 +msgid "For example, a warehouse named `Warehouse #2` might have the :guilabel:`Short Name` `WH2` (the short name for the default warehouse in Odoo is `WH`)." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:87 -msgid "To create a location, go to :menuselection:`Configuration --> Warehouse Management --> Locations` and click on :guilabel:`Create`." +msgid "Once the warehouse is created, navigate back to the :menuselection:`Inventory` dashboard. New operations for the newly created warehouse are automatically generated there." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:90 -msgid "Then, fill out a :guilabel:`Location Name` and a :guilabel:`Parent Location` and click :guilabel:`Save`." +msgid "For more on creating new warehouses, see :doc:`create_a_second_warehouse`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 -msgid "Create a new warehouse location in Odoo Inventory." +msgid "Inventory app dashboard displaying new transfers for the new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:102 +msgid "Create a new location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:111 +msgid "For more on locations, see :doc:`use_locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 +msgid "New warehouse location creation form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:123 msgid "Inventory valuation" msgstr "" @@ -11731,115 +12490,227 @@ msgstr "" msgid "The Inventory Valuation fields are located on the Product Categories form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:21 msgid "Alternatively, automated inventory valuation is an integrated valuation method that updates the inventory value in real-time by creating journal entries whenever there are stock moves initiated between locations in a company's inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:26 msgid "Automated inventory valuation is a method recommended for expert accountants, given the extra steps involved in journal entry configuration. Even after the initial setup, the method will need to be periodically checked to ensure accuracy, and adjustments may be needed on an ongoing basis depending on the needs and priorities of the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:34 msgid "Types of accounting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:36 msgid "Accounting entries will depend on the accounting mode: *Continental* or *Anglo-Saxon*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:40 -msgid "Verify the accounting mode by activating the :ref:`developer-mode` and navigating to :menuselection:`Accounting --> Configuration --> Settings`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:39 +msgid "Verify the accounting mode by activating the :ref:`developer-mode` and navigating to :menuselection:`Accounting app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:43 -msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. *Interim Stock Accounts* are used for the input and output accounts, and are both *Asset Accounts* in the balance sheet." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:42 +msgid "Then, in the search bar, look for :guilabel:`Anglo-Saxon Accounting`, to see if the feature is enabled. If it is **not** enabled, Continental accounting mode is in use." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:48 -msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Additionally, a single *Expense* account is used for both input and output accounts in the balance sheet." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:0 +msgid "Show the Anglo-Saxon accounting mode feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:55 -msgid "Costing methods" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:49 +msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. So for **manual** valuation method, set the :guilabel:`Expense Account` to `Stock Valuation` for the current asset type; for **automatic** valuation method, set the the :guilabel:`Expense Account` to an *Expenses* or a *Cost of Revenue* type (e.g. `Cost of Production`, `Cost of Goods Sold`, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:57 -msgid "Below are the three costing methods that can be used in Odoo for inventory valuation." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:56 +msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Because of this, the :guilabel:`Expense Account` can be set to **either** *Expenses* or a *Cost of Revenue* type, however, it is more commonly set to an *Expenses* account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:59 -msgid "**Standard Price**: is the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:61 +msgid ":ref:`Details about configuring Expense and Stock accounts `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:63 -msgid "**Average Cost (AVCO)**: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:67 +msgid "Make changes to inventory valuation options by navigating to :menuselection:`Inventory app --> Configuration --> Product Categories`. In the :guilabel:`Inventory Valuation` section, select the desired :guilabel:`Costing Method` and :guilabel:`Inventory Valuation` options." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:66 -msgid "**First In First Out (FIFO)**: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it's highly sensitive to input data and human error." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:74 -msgid "Changing the costing method greatly impacts inventory valuation. It's highly recommended to consult an accountant first before making any adjustments here." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:78 -msgid "Configure automated inventory valuation in Odoo" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:80 -msgid "Make changes to inventory valuation options by navigating to :menuselection:`Inventory --> Configuration --> Product Categories`, and choose the category/categories where the automated valuation method should apply." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:72 msgid "It is possible to use different valuation settings for different product categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:87 -msgid "Under the :guilabel:`Inventory Valuation` heading are two labels: :guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the desired :guilabel:`Costing Method` using the drop-down menu (e.g. :guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to :guilabel:`Automated`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:-1 +msgid "Show inventory valuation configuration options." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:93 -msgid ":ref:`Using the inventory valuation`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:81 +msgid "Costing method" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:83 +msgid "From the product category's configuration page, choose the desired :guilabel:`Costing Method`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:85 +msgid ":guilabel:`Standard Price`: the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:89 +msgid ":guilabel:`Average Cost (AVCO)`: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:94 msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the :guilabel:`Cost` field for products in the respective product category creates a new record in the *Inventory Valuation* report to adjust the value of the product. The :guilabel:`Cost` amount will then automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:102 -msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:100 +msgid ":guilabel:`First In First Out (FIFO)`: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it is highly sensitive to input data and human error." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:108 -msgid "On the same screen, the :guilabel:`Account Stock Properties` fields will appear, as they are now required fields given the change to automated inventory valuation. These accounts are defined as follows:" +msgid "Changing the costing method greatly impacts inventory valuation. It is highly recommended to consult an accountant first before making any adjustments here." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:112 -msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products." +msgid ":doc:`using_inventory_valuation`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 -msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product." +msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo will generate a corresponding record in the *Inventory Valuation* report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:118 -msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:125 +msgid "Inventory valuation in Odoo can be set to be updated manually or automatically. While *Expense* accounts apply to both, the *Stock Input* and *Stock Output* accounts are only used for automated valuation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:124 -msgid "Access reporting data generated by inventory valuation" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:126 -msgid "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:131 -msgid "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:129 +msgid "Refer to the :ref:`Expense ` and :ref:`Stock input/output ` sections for details on configuring each account type." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:135 +msgid "Expense account" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:137 +msgid "To configure the *expense account*, go to the :guilabel:`Account Properties` section of the intended product category (:menuselection:`Inventory app --> Configuration --> Product Categories`). Then, choose an existing account from the :guilabel:`Expense Account` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:141 +msgid "To ensure the chosen account is the correct :guilabel:`Type,` click the |right arrow| icon to the right of the account. Then, set the account type based on the information below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:146 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:214 +msgid "Anglo-Saxon" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:150 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:177 +msgid "Automated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:152 +msgid "In Anglo-Saxon accounting for automated inventory valuation, set the :guilabel:`Expense Account` to the `Expenses` account. Then, click the |right arrow| icon to the right of the account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:156 +msgid "In the pop-up window, choose :guilabel:`Expenses` or :guilabel:`Cost of Revenue` from the :guilabel:`Type` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:0 +msgid "Show **Expense Account** field, and external link icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:165 +msgid "To configure the :guilabel:`Expense Account`, choose :guilabel:`Stock Valuation` from the field's drop-down menu. Verify the account's type by clicking the |right arrow| icon, and then ensure the :guilabel:`Type` is :guilabel:`Current Assets`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:0 +msgid "Show the **Expense Account** field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:232 +msgid "Continental" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:179 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:184 +msgid "Set the :guilabel:`Expense Account` to the :guilabel:`Expenses` or :guilabel:`Cost of Revenue` account type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:190 +msgid "Stock input/output (automated only)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:192 +msgid "To configure the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account`, go to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:196 +msgid "In the :guilabel:`Inventory Valuation` field, select :guilabel:`Automated`. Doing so makes the :guilabel:`Account Stock Properties` section appear. These accounts are defined as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:199 +msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:201 +msgid ":guilabel:`Stock Journal`: accounting journal where entries are automatically posted when a product's inventory valuation changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:203 +msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:207 +msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:216 +msgid "In Anglo-Saxon accounting, the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account` are set to *different* :guilabel:`Current Assets` accounts. This way, delivering products and invoicing the customer balance the *Stock Output* account, while receiving products and billing vendors balance the *Stock Input* account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:221 +msgid "To modify the account type, go to the click the |right arrow| icon to the right of the stock input/output account. In the pop-up window, choose :guilabel:`Current Assets` from the :guilabel:`Type` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:0 +msgid "Display account setup page, highlighting the **Type** field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:229 +msgid "The *Stock Input* account is set to `Stock Interim (Received)`, a *Current Asset* account type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:234 +msgid "In Continental accounting, the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account` are set to **the same** :guilabel:`Current Assets` account. That way, one account can be balanced when items are bought and sold." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:239 +msgid "The stock input and output accounts are both set to `Stock Interim (Received)`, a :guilabel:`Current Assets` account type. They can also be set to the `Stock Interim (Delivered)`, as long as the input and output accounts are assigned to the **same** account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:0 +msgid "Show the Stock Input and Output accounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:249 +msgid "Inventory valuation reporting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:251 +msgid "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:257 +msgid ":doc:`../../../../finance/accounting/get_started/cheat_sheet`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:259 +msgid "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:263 msgid "Access more specific information with the :guilabel:`Stock Valuation Account` drop-down menu, by selecting either the :guilabel:`General Ledger` to see an itemized view of all of the journal entries, or by selecting :guilabel:`Journal Items` to review all of the individualized journal entries that were submitted to the account. As well, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." msgstr "" @@ -11868,7 +12739,7 @@ msgid "To use Odoo to automatically generate a trail of inventory valuation entr msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:24 -msgid ":ref:`Set up inventory valuation `" +msgid ":doc:`Set up inventory valuation `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:26 @@ -12178,16 +13049,12 @@ msgstr "" msgid "Lots and serial numbers differentiate identical products and track information like arrival or expiration dates. To enable this feature, navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under the :guilabel:`Traceability` heading, check the box beside :guilabel:`Lots & Serial Numbers` to enable the feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:-1 -msgid "Enable lots and serial numbers." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:115 msgid "Next, ensure the intended product is tracked by lots or serial numbers by navigating to the product form through :menuselection:`Inventory --> Products --> Products`, and selecting the desired product. On the product form, switch to the :guilabel:`Inventory` tab, and under the :guilabel:`Tracking` field, select either the :guilabel:`By Unique Serial Number` or :guilabel:`By Lots` options." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:121 -msgid "After enabling the features, assign lot or serial numbers to products using an :doc:`inventory adjustment ` or during :ref:`product reception `." +msgid "After enabling the features, assign lot or serial numbers to products using an :doc:`inventory adjustment ` or during :ref:`product reception `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:126 @@ -12779,6 +13646,648 @@ msgstr "" msgid "The detailed operations shows which lots are being selected for the picking." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting.rst:5 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:3 +msgid "Inventory aging report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:7 +msgid "The inventory aging report evaluates all items in stock, providing insights into potentially sunken purchase costs and delays in profitability." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:10 +msgid "Create customized pivot tables to analyze product, operation types, month, or company breakdowns. This helps identify products in stock that are at risk of passing their expiration or viability dates, or instances of rot/decay for fast-expiring items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:13 +msgid "The *Reporting* menu in *Inventory* is only accessible to users with :doc:`admin access <../../../../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:18 +msgid "To access the inventory aging report, go to :menuselection:`Inventory app --> Reporting --> Inventory Aging`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:24 +msgid "Navigate the inventory aging report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:26 +msgid "By default, the :guilabel:`Inventory Aging` report displays a pivot table, with the month in columns, and product category in rows. The default filters, :guilabel:`Incoming` and :guilabel:`Has Remaining Qty`, show only products from receipts, and are currently in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:30 +msgid ":guilabel:`Remaining Qty` displays the number of on-hand items, and :guilabel:`Remaining Value` displays the total cost of purchasing these items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:33 +msgid "Clicking the :icon:`fa-plus-square` :guilabel:`(plus)` icon in each column or row reveals options to expand the pivot table and show a detailed breakdown of the :guilabel:`Remaining Qty` and :guilabel:`Remaining Value` by :guilabel:`Product`, :guilabel:`Product Category`, :guilabel:`Date`, or :guilabel:`Company`. Clicking the :icon:`fa-minus-square-o` :guilabel:`(minus)` icon collapses it back to its previous state." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:43 +msgid "Inventory aging report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:43 +msgid "Inventory aging report, showing each **Product** in rows and each reception **Date** in columns, to better monitor products with fast expiration dates. Each row shows the the total on-hand quantity and inventory valuation of items purchased on each day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:48 +msgid "Records in the :guilabel:`Inventory Aging` report are *stock valuation layers* (SVLs), representing product moves that impact stock valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:51 +msgid "Inventory adjustments do **not** create |SVLs|; only items purchased from vendors do." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:71 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:56 +msgid "After learning how to :ref:`navigate the inventory aging report `, it can be used to create and share different reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:59 +msgid "A few common reports that can be created using the :guilabel:`Inventory Aging` report are detailed below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:63 +msgid "Rotating stock report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:65 +msgid "To create a report to identify items that have been in stock for a while, follow these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:67 +msgid "Navigate to :menuselection:`Inventory app --> Reporting --> Inventory Aging`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:68 +msgid "On the :guilabel:`Inventory Aging` report, click the :icon:`fa-caret-down` :guilabel:`(caret down)` icon in the :guilabel:`Search...` bar to see a drop-down list of :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorite` options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:71 +msgid "Choose :guilabel:`Product` under the :guilabel:`Group By` section. Doing so expands the pivot table to show a product in each row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:73 +msgid "Click the :icon:`fa-plus-square` :guilabel:`(plus)` icon to the left of the date column. Hover over :guilabel:`Date` from the drop-down menu and choose :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, or :guilabel:`Day`. Doing so expands the columns to show the :guilabel:`Remaining Qty` and :guilabel:`Remaining Value` by the selected time period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:79 +msgid "For products that have a longer shelf life, choose longer time periods such as :guilabel:`Month` or :guilabel:`Quarter` when expanding columns by :guilabel:`Date`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:0 +msgid "Pivot table, highlighting the plus icon to expand columns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:86 +msgid "The report now displays the on-hand stock of items, and their total purchasing cost, for each time period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:90 +msgid "Inventory aging report, with the :guilabel:`Group By`: :guilabel:`Product` option selected, and with the :guilabel:`Date` column set to :guilabel:`Day`. It gives insight into how much raw fish sashimi products were purchased on each day, and how much it cost. This informs the business owners how much stock is at risk of rotting in stock, per day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/aging.rst:0 +msgid "Inventory aging report, showing product row items and day columns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:3 +msgid "Locations dashboard" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:7 +msgid "The *Locations* dashboard in the *Inventory* application provides an overview of on-hand storage locations for company products. Use this report to see where stock is stored, identify :ref:`misplaced items `, or view past inventory to see product locations on specific dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:16 +msgid "To access the locations report, the *Storage Locations* feature must be enabled. To do that, go to :menuselection:`Inventory app --> Configuration --> Settings`. In the :guilabel:`Warehouse` section, tick the checkbox for :guilabel:`Storage Locations`, and click :guilabel:`Save`. Then, access the locations dashboard by navigating to :menuselection:`Inventory app --> Reporting --> Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:24 +msgid "Navigate the locations dashboard" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:26 +msgid "By default, the :guilabel:`Locations` dashboard lists all on-hand products in stock (in the :guilabel:`Product` column), along with the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:29 +msgid ":guilabel:`Location`: current storage location. If a product is stored at `Shelf 1` and `Shelf 2`, the product is listed twice, showing quantities at each location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:31 +msgid ":guilabel:`Package`: the package that the product is stored in, if any." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:32 +msgid ":guilabel:`Lot/Serial Number`: if the product has a lot or serial number, it is specified here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:33 +msgid ":guilabel:`On Hand Quantity`: current quantity of products. Click the :icon:`fa-pencil` :guilabel:`(pencil)` icon to :doc:`modify the on-hand quantity <../inventory_management/count_products>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:36 +msgid ":guilabel:`Reserved Quantity`: on-hand quantity reserved for operations, such as pickings, delivery orders, or manufacturings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:38 +msgid ":guilabel:`Unit`: the unit of measure of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:52 +msgid "Click the buttons to the right of each row item to access additional information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:42 +msgid ":icon:`fa-history` :guilabel:`History`: access the stock move history of the product, displaying information about the quantity and description of why the product was moved from one location to another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:47 +msgid "View what the product is reserved for, by clicking the :icon:`fa-history` :guilabel:`History` button on the far-right of the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:50 +msgid "On the :guilabel:`Moves History` page, remove the :icon:`fa-filter` :guilabel:`Done` filter. Then, click the |down| icon to the right of the :guilabel:`Search...` bar to reveal filter options, and select the :guilabel:`To Do` filter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:0 +msgid "Display *Moves History* page of to-do deliveries that reserved the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:58 +msgid ":icon:`fa-refresh` :guilabel:`Replenishment`: access the :doc:`reordering rules <../../product_management/product_replenishment/reordering_rules>` page to replenish products at the specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:62 +msgid "In the upper-left corner of the page, click the the :guilabel:`New` button to make an :doc:`inventory adjustment <../inventory_management/count_products>` to record quantities of a certain product at a specific :guilabel:`Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:66 +msgid "To view products, quantities, and their locations for a specified date, click the :guilabel:`Inventory At Date` button (also located in the upper-left corner of the page). Select a date and time in the :guilabel:`Inventory at Date` field, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:73 +msgid "After learning how to :ref:`navigate the locations dashboard `, it can be used to create and share different reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:77 +msgid "A few common reports that can be created using the :guilabel:`Locations` dashboard are detailed below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:81 +msgid "Dead stock report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:83 +msgid "To get list of expired items, also referred to as *dead stock*, follow these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:143 +msgid "Go to :menuselection:`Inventory app --> Reporting --> Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:144 +msgid "Then, click the |down| icon to the right of the :guilabel:`Search...` bar to reveal a drop-down list of :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorite` options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:88 +msgid "Enable the :guilabel:`Internal Locations` and :guilabel:`Expiration Alerts` option under the :guilabel:`Filters` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:91 +msgid "The report now displays a list of expired products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:94 +msgid "This report can also be generated from the :ref:`Lot and Serials Numbers ` page, accessed by going to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:-1 +msgid "Show a list of products whose expiration dates have exceeded today." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:105 +msgid "Stranded inventory report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:107 +msgid "Businesses using multi-step flows in the *Inventory* or *Manufacturing* apps, may have *stranded* items, which are products not in their proper storage locations, due to human error. Use this report to periodically check transfer locations (e.g. *WH/Input*, *WH/Pre-Processing*) to ensure items are moved to their intended storage locations, and accurately recorded in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:112 +msgid "To get a list of items that might be sitting idly in storage, follow these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:115 +msgid "In the :guilabel:`Search...` bar, begin typing the name of the location where products are intended to be moved to, such as `WH/Input`, or `WH/Packing`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:117 +msgid "Select the :guilabel:`Search Location for:` [location name] option from the resulting drop-down menu that appears beneath the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:0 +msgid "Show search result for the location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:124 +msgid "The report now displays a list of products at the transit location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:127 +msgid "Searching `Input` in :guilabel:`Location` shows a list of products at a *WH/Input* location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:129 +msgid "The list shows `500` quantities of `Chicken`, which is alarming if not refrigerated soon after reception. The stranded inventory report helps identify items that have been idling in non-storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:0 +msgid "Show items stored at a specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:138 +msgid "Inventory discrepancy report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:140 +msgid "To generate a report of items that have been moved since the last :doc:`inventory audit <../inventory_management/cycle_counts>`, follow these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:146 +msgid "Enable the :guilabel:`Internal Locations` and :guilabel:`Conflicts` option from the :guilabel:`Filters` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:148 +msgid "The report now displays items whose quantities have changed since the last cycle count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:0 +msgid "Show items from the *Conflicts* filter in the report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:154 +msgid "Click the :icon:`fa-history` :guilabel:`History` button to view inventory transfers, including receipts and deliveries, that have occurred since the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:0 +msgid "Show *Moves History*, showing a delivery that occurred after an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:3 +msgid "Moves history dashboard" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:5 +msgid "The *Moves History* report in Odoo *Inventory* provides a detailed record of product movements (containing past and current locations), lot numbers, and reasons for movement. Reports can be generated for any time frame, making this report essential for analyzing stock levels, monitoring inventory turnover, and identifying any discrepancies in inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:9 +msgid "The reporting feature is only accessible to users with :doc:`admin access <../../../../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:14 +msgid "To access the stock report, go to :menuselection:`Inventory app --> Reporting --> Moves History`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:-1 +msgid "Display Moves History report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:23 +msgid "Navigate the moves history report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:25 +msgid "In the report, the columns represent:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:27 +msgid ":guilabel:`Date`: calendar date and time of the stock move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:28 +msgid ":guilabel:`Reference`: description of the reason for the stock move or quantity change, such as a receipt number (e.g. `WH/IN/00012`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:30 +msgid ":guilabel:`Product`: name of the product involved in the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:31 +msgid ":guilabel:`Lot/Serial Number`: specifies the lot or serial number of the tracked product being moved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:33 +msgid ":guilabel:`From`: source location of the moved product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:34 +msgid ":guilabel:`To`: destination location of the moved product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:35 +msgid ":guilabel:`Quantity`: number of products moved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:36 +msgid ":guilabel:`Unit`: unit of measure of the products moved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:37 +msgid ":guilabel:`Status`: indicates the move status, which can be :guilabel:`Done`, :guilabel:`Available` (ready for action), or :guilabel:`Partially Available` (insufficient quantities to complete the operation)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:66 +msgid "Search options" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:44 +msgid "Use the following search options to customize the :guilabel:`Moves History` report to display relevant information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:70 +msgid "Filters" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:72 +msgid "The :guilabel:`Filters` section allows users to search among pre-made and custom filters to find specific stock records." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:54 +msgid ":guilabel:`To Do`: show stock move records that are in progress. This includes lines with a :guilabel:`Status` column value of :guilabel:`Available` or :guilabel:`Partially Available`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:56 +msgid ":guilabel:`Done`: completed stock moves, with a :guilabel:`Status` of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:57 +msgid ":guilabel:`Incoming`: displays move records from vendor locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:58 +msgid ":guilabel:`Outgoing`: displays move records to customer locations, including customer returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:60 +msgid ":guilabel:`Internal`: displays move records from one internal location to another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:61 +msgid ":guilabel:`Manufacturing`: shows records where products were produced from the virtual, production :doc:`location <../inventory_management/use_locations>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:63 +msgid ":guilabel:`Date`: select this drop-down menu to access various date filter options and view stock moves from a specific month, quarter, or year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:65 +msgid ":guilabel:`Last 30 Days`: show records that occurred in the last thirty days." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:66 +msgid ":guilabel:`Last 3 Months`: show records from the last three months." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:113 +msgid "Group By" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:70 +msgid "The :guilabel:`Group By` section allows users to add pre-made and custom groupings to the search." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:73 +msgid ":guilabel:`Product`: group records by product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:74 +msgid ":guilabel:`Status`: group records by the three status types: :guilabel:`Done`, :guilabel:`Available`, and :guilabel:`Partially Available`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:76 +msgid ":guilabel:`Date`: group records by :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, or :guilabel:`Day`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:78 +msgid ":guilabel:`Transfers`: group records by operation number, e.g. `WH/OUT/00012`, `WH/MO/00211`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:80 +msgid ":guilabel:`Location`: group records by source location (the :guilabel:`From` column in this report)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:82 +msgid ":guilabel:`Category`: group records by product category. To configure these, go to :menuselection:`Inventory app --> Configuration --> Products: Product Categories`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:84 +msgid ":guilabel:`Batch Transfer`: group records by :doc:`batch <../advanced_operations_warehouse/batch_transfers>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:125 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:89 +msgid "To save the current applied filters and groups, so the same information can be easily accessed after closing this page, click :guilabel:`Save current search`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:92 +msgid "Optionally, tick the :guilabel:`Default filter` checkbox to make this current view the default filter when opening the :guilabel:`Moves History` report. Or tick the :guilabel:`Shared` checkbox to make the search option available to other users." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:134 +msgid "Lastly, click the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:137 +msgid ":doc:`../../../../essentials/search`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:3 +msgid "Stock report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:5 +msgid "Use the stock report in Odoo *Inventory* for a detailed list of all stored products, including those reserved, purchased and in transit, as well as those delivered to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:12 +msgid "To access the stock report, go to :menuselection:`Inventory app --> Reporting --> Stock`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:-1 +msgid "Show the stock report, accessible by going to Inventory > Reporting > Stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:19 +msgid "Navigate the stock report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:21 +msgid "On the stock report, the left sidebar includes several groupings to narrow down what is being shown. The default groupings are :guilabel:`Warehouses`, which filters products by specific warehouses, and :guilabel:`Category`, which shows products within a selected product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:26 +msgid "The :guilabel:`Warehouse` grouping is only available when there are multiple warehouses in the database. Refer to the :doc:`../inventory_management/create_a_second_warehouse` documentation for more details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:30 +msgid "In the report itself, the columns represent:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:32 +msgid ":guilabel:`Product`: name of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:33 +msgid ":guilabel:`Unit Cost`: average inventory valuation per unit, adjusted based on the cost to purchase and/or manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:35 +msgid ":guilabel:`Total Value`: Total inventory valuation of the product, calculated by multiplying unit cost by on-hand quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:39 +msgid ":ref:`Compute average cost inventory valuation per unit `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:40 +msgid ":doc:`Inventory valuation methods <../inventory_valuation/inventory_valuation_config>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:42 +msgid ":guilabel:`On Hand`: current quantity of products. Click the :icon:`fa-pencil` :guilabel:`(pencil)` icon to :doc:`modify the on-hand quantity <../inventory_management/count_products>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:45 +msgid ":guilabel:`Free to Use`: on-hand quantity that are **not** reserved for delivery or manufacturing orders, and are available to sell or use." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:47 +msgid ":guilabel:`Incoming`: items expected to arrive at the warehouse. Number of products is based on quantities in confirmed purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:49 +msgid ":guilabel:`Outgoing`: items expected to leave the warehouse or be consumed in manufacturing orders. Number of products is based on quantities in confirmed sales or manufacturing orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:54 +msgid ":guilabel:`History`: access the stock move history of the product, displaying information about the quantity and description of why the product was moved from one location to another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:56 +msgid ":guilabel:`Replenishment`: access the :doc:`reordering rules <../../product_management/product_replenishment/reordering_rules>` page for the product to create or manage methods of procuring the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:59 +msgid ":guilabel:`Locations`: break down of on-hand quantity at multiple storage locations. Only available when the product is stored in multiple locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:61 +msgid ":guilabel:`Forecast`: access the forecasted report to view on-hand, incoming, and outgoing quantities. Report also contains links to confirmed purchase, sales, or manufacturing orders. Only available when there are confirmed sales, purchase, or manufacturing orders for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:75 +msgid ":guilabel:`Published`: display products published on the website. Only available with the *Website* app installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:77 +msgid ":guilabel:`Available in POS`: display products available through the *Point of Sale* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:78 +msgid ":guilabel:`Available in Self`: display products available in self order through the *Point of Sale* app. Appears in the search because the :guilabel:`Available in Self Order` checkbox was ticked in the :guilabel:`Point of Sale` section of a product form's :guilabel:`Sales` tab. The option is only available when the :guilabel:`Available in POS` checkbox is ticked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:0 +msgid "In the Sales tab of a product form, showing *Available in Self Order* setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:87 +msgid ":guilabel:`Not available in Self`: display products available in *PoS*, but not available in self order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:91 +msgid "`Configure PoS products `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:93 +msgid ":guilabel:`Can be Sold`: display products that can be sold to customers. Appears in the search because the :guilabel:`Can be Sold` checkbox is ticked on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:95 +msgid ":guilabel:`Can be Purchased`: display products that can be bought from vendors. Appears in the search because the :guilabel:`Can be Purchased` checkbox is ticked on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:97 +msgid ":guilabel:`Can be Recurring`: show subscription products, indicated by ticking the :guilabel:`Recurring` checkbox on the product form. Only available with the *Subscription* app activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:100 +msgid ":guilabel:`Can be Rented`: show products that can be loaned to customers for a certain time. Appears in the search because the :guilabel:`Can be Rented` checkbox was ticked on the product form. Only available with the *Rental* app installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:103 +msgid ":guilabel:`Can be Subcontracted`: display products that can be produced by a :doc:`third-party manufacturer <../../../manufacturing/subcontracting/subcontracting_basic>`. Available only with the *Manufacturing* app installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:107 +msgid ":guilabel:`Can be Expensed`: show items that can be expensed. Only available with the *Expenses* app installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:111 +msgid ":doc:`../../product_management/product_tracking/type`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:115 +msgid "The :guilabel:`Group By` section allows users to add pre-made and custom groupings to the search results." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:118 +msgid ":guilabel:`Product Type`: group items by :doc:`product type <../../product_management/product_tracking/type>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:120 +msgid ":guilabel:`Product Category`: group items by product category. To configure these, go to :menuselection:`Inventory app --> Configuration --> Products: Product Categories`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:122 +msgid ":guilabel:`POS Product Category`: group items by :doc:`point of sale product categories <../../../../sales/point_of_sale/configuration>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:127 +msgid "To save the current applied filters and groupbys, so the same information can be easily accessed after closing this page, click :guilabel:`Save current search`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:130 +msgid "Optionally, tick the :guilabel:`Default filter` checkbox to make this current view the default filter when opening the stock report. Or tick the :guilabel:`Shared` checkbox to make the search option available to other users." +msgstr "" + #: ../../content/applications/inventory_and_mrp/maintenance.rst:8 msgid "Maintenance" msgstr "" @@ -14450,8 +15959,13 @@ msgstr "" msgid "Work order dependencies are configured on a product's |BOM|. To do so, navigate to :menuselection:`Manufacturing --> Products --> Bills of Materials`, then select a |BOM|, or create a new one by clicking :guilabel:`New`." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:94 +msgid "Learn more" +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:32 -msgid "For a complete guide on how to properly configure a new |BOM|, see the documentation on :ref:`creating a bill of materials `." +msgid "For a complete guide on how to properly configure a new |BOM|, see the documentation on :doc:`creating a bill of materials <../basic_setup/bill_configuration>`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:35 @@ -14546,96 +16060,284 @@ msgstr "" msgid "Bill of materials" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:7 -msgid "A *bill of materials* (or *BoM* for short) is a document that defines the quantity of each component required to make or deliver a finished product. It can also include various operations and the individual step guidelines needed to complete a production process." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:9 +msgid "A *bill of materials* (or *BoM* for short) documents specific components, along with their respective quantities, that are needed to produce or repair a product. In Odoo, |BoMs| as blueprints for manufactured goods and kits, and often include production operations and step-by-step guidelines, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:11 -msgid "In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:15 +msgid "BoM setup" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:14 -msgid "Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the manufacturing process and save time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:18 -msgid "Set up a bill of materials (BoM)" +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:17 +msgid "To create a |BOM|, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials` and click :guilabel:`New`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:20 -msgid "The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations or instructions, only components. In this case, the production is solely managed using *Manufacturing Orders*." +msgid "Next, set the :guilabel:`BoM Type` to :guilabel:`Manufacture this Product`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:23 -msgid "To create a :abbr:`BoM (Bill of Materials)` from the :guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills of Materials`. Then, click :guilabel:`Create`. Next, specify the :guilabel:`Product`." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:22 +msgid "Then, specify :ref:`required components ` and, if necessary, define any :ref:`manufacturing operations `." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:28 -msgid "A :abbr:`BoM (Bill of Materials)` can also be created directly from the product form, in which case the :guilabel:`Product` field is pre-filled." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:26 +msgid "Individual |BOMs| can also be quickly accessed or created by clicking the :guilabel:`Bill of Materials` smart button on any product form, as accessible through the *Sales*, *Inventory*, and *Manufacturing* apps, as well as through any internal links where a product is referenced (such as in a field or a line item)." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:31 -msgid "For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type` to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line` to specify the various components that make up the production of the final product and their respective quantities. New components can be created quickly through the :abbr:`BoM (Bill of Materials)`, or can be created beforehand in :menuselection:`Manufacturing --> Products --> Products --> Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM (Bill of Materials)`." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:35 +msgid "Show BoM for a product, with components listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:35 +msgid "BoM for `Drawer`, displaying the **Components** tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:38 +msgid ":doc:`../advanced_configuration/kit_shipping`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:39 +msgid ":doc:`../subcontracting/subcontracting_basic`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:44 +msgid "Components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:46 +msgid "In the :guilabel:`Components` tab of a |BOM|, specify components used to manufacture the product by clicking :guilabel:`Add a line`. From the :guilabel:`Components` drop-down menu, select from existing products or create a new product by typing the name and selecting either the :guilabel:`Create \" \"` option to quickly add the line item, or the :guilabel:`Create and edit...` option to add the component and continue to its configuration form." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 -msgid "Set up a Bill of Materials." +msgid "Add a component by selecting it from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:43 -msgid "Specify a bill of materials (BoM) for a product variant" +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:56 +msgid "Optionally, access additional fields by clicking the :icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon to the far-right of the :guilabel:`Components` tab. Tick the checkboxes for the following features to enable these columns:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:45 -msgid ":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product Variants*, with two setup options available to choose from." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:60 +msgid ":guilabel:`Apply on Variants`: specify which :doc:`product variant <../advanced_configuration/product_variants>` each component is used in. When the field is left blank, the component is used in all product variants." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:49 -msgid "In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, the product's variant attributes must already be configured on the product form." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:66 +msgid ":guilabel:`Consumed in Operation`: specify the operation using the component. Useful for determining :ref:`manufacturing readiness `." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:52 -msgid "The first method is to create one :abbr:`BoM (Bill of Materials)` per variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the :guilabel:`Product Variant`. The second method is to create one master :abbr:`BoM (Bill of Materials)` that contains all of the components, and specify which variant each component applies to using the :guilabel:`Apply on Variants` column." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:68 +msgid ":guilabel:`Manual Consumption`: tick the checkbox to force operators to check the :guilabel:`Consumed` checkbox on a manufacturing order (MO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 -msgid "Product Variants in the Bill of Materials." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:0 +msgid "Show a manufacturing order, highlighting the *Consumed* field." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:62 -msgid "Set up operations" +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:75 +msgid "Not doing so triggers the :guilabel:`Consumption Warning` error message, where the consumed component quantity must be manually inputted. Otherwise, the operation cannot be completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:64 -msgid "Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify instructions for production and register time spent on an operation. To use this feature, first enable the :guilabel:`Work Orders` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:69 -msgid "Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the :guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new operation. In the :guilabel:`Create Operations` box, give the operation a name, specify the :guilabel:`Work Center` and duration settings. Like components, Odoo gives the option to specify a product variant in the :guilabel:`Apply on Variants` field so the operation only applies to that variant. Finally, click :guilabel:`Save & Close`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:76 -msgid "Each operation is unique, as it is always exclusively linked to one :abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing Operations` feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 -msgid "Copy Existing Operations feature." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:0 +msgid "Show the consumption warning error message." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:85 -msgid "Add by-products to a bill of materials (BoM)" +msgid "Operations" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:87 -msgid "A *By-Product* is a residual product that is created during production in addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike the primary product, there can be more than one by-product on a :abbr:`BoM (Bill of Materials)`." +msgid "Add an *operation* to a |BOM| to specify instructions for production and register time spent on an operation. To use this feature, first enable the *Work Orders* feature by going to :menuselection:`Manufacturing app --> Configuration --> Settings`. In the :guilabel:`Operations` section, tick the :guilabel:`Work Orders` checkbox to enable the feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:91 -msgid "To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`By-Products` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:93 +msgid ":doc:`../advanced_configuration/work_order_dependencies`" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:94 -msgid "Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill of Materials)` by clicking on the :guilabel:`Operations` tab and clicking :guilabel:`Add a line`. Then, name the by-product and indicate the :guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM (Bill of Materials)` has configured operations, specify exactly which operation the by-product is produced from in the :guilabel:`Produced in Operation` field. Finally, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "\"Work Orders\" feature in the Settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:99 +msgid "Next, navigate to the |BOM| by going to :menuselection:`Manufacturing app --> Products --> Bill of Materials` and selecting the desired |BOM|. To add a new operation, go to the :guilabel:`Operations` tab, and click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:103 +msgid "Doing so opens the :guilabel:`Create Operations` pop-up window, where the various fields of the operation are configured:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:106 +msgid ":guilabel:`Operation`: name of the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:107 +msgid ":guilabel:`Work Center`: select existing locations to perform the operation, or create a new work center by typing the name and selecting the :guilabel:`Create \" \"` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:109 +msgid ":guilabel:`Apply on Variants`: specify if this operation is only available for certain product variants. If the operation applies to all product variants, leave this field blank." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:113 +msgid ":doc:`Configuring BoMs for product variants <../advanced_configuration/product_variants>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:115 +msgid ":guilabel:`Duration Computation`: choose how time spent on the operation is tracked. Opt for :guilabel:`Compute based on tracked time` to use the operation's time tracker or :guilabel:`Set duration manually` if operators can record and modify time themselves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:119 +msgid "Choosing the :guilabel:`Compute based on tracked time` option enables the :guilabel:`Based on last __ work orders` option, which automatically estimates the time to complete this operation based on the last few operations. Choosing :guilabel:`Set duration manually` enables the :guilabel:`Default Duration` field instead." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:123 +msgid ":guilabel:`Default Duration`: estimated amount of time to complete the operation; used for `planning manufacturing orders `_ and determining `work center availability `_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:126 +msgid ":guilabel:`Company`: specify the company the |BOM| is available in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:128 +msgid "Include operation details in the :guilabel:`Work Sheet` tab. Choose :guilabel:`PDF` to attach a file or :guilabel:`Google Slide` with *public* access to share a link. Select :guilabel:`Text` to type instructions in the :guilabel:`Description` text field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:133 +msgid "Type `/` for a list of formatting options and features, including ChatGPT." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:0 +msgid "Show ChatGPT feature to generate instructions for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "Fill out the Create Operations pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:143 +msgid "Finally, click :guilabel:`Save \\& Close` to close the pop-up window. To add more operations, click :guilabel:`Save & New` and repeat the same steps above to configure another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:147 +msgid "Each operation is unique, as it is always exclusively linked to one |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:150 +msgid "After creating an operation, click the :guilabel:`Copy Existing Operations` button to choose an operation to duplicate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:0 +msgid "Show Operation tab, highlighting the \"Copy Existing Operations\" field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:158 +msgid "Instructions" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:161 +msgid "To add detailed instructions to operations, the *Quality* app must be installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:163 +msgid "Add specific instructions to an existing operation by clicking the operation's :icon:`fa-list-ul` :guilabel:`(list)` icon in the :guilabel:`Instructions` column. The number in the :guilabel:`Instructions` column shows the number of existing detailed instructions there are for the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "Show the Instructions column, and list icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:172 +msgid "On the :guilabel:`Steps` dashboard, click :guilabel:`New` to open a blank quality control point form where the new manufacturing step can be created. Here, give the specific instruction a :guilabel:`Title` and set the :guilabel:`Type` to :guilabel:`Instructions`. In the :guilabel:`Instructions` tab of the form, write out the directions for the step in the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:178 +msgid "Further customizations can be made here on this form, beyond ordinary instructions, to also include specific types of quality control points that carry specific (or complex) conditions. For more details about quality control points refer the :doc:`Instruction check <../../quality/quality_check_types/instructions_check>` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "Show the page to add a quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:188 +msgid "Miscellaneous" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:190 +msgid "The :guilabel:`Miscellaneous` tab contains more |BoM| configurations to customize procurement, calculate costs, and define how components are consumed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:195 +msgid ":guilabel:`Manufacturing Readiness`: choosing :guilabel:`When components for the 1st operation are available` shows the :guilabel:`Component Status` as a **green** :guilabel:`Not Available`, when only the components that are consumed in the first operation are in stock. This indicates that although not all components are available, operators can at least begin with the first operation. Choosing :guilabel:`When all components are available` displays a **red** :guilabel:`Not Available` component status unless all components are in available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:203 +msgid "Specify which operation consumes each component on the |BoM| in the :ref:`Manual Consumption field `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:0 +msgid "Show the *Component Status* field on the manufacturing order dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:210 +msgid ":guilabel:`Version`: displays the current |BoM| version, visible with the Odoo *PLM* app installed for managing |BoM| changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:212 +msgid ":guilabel:`Flexible Consumption`: specifies if components used can deviate from the quantity defined on the |BoM|. Choose :guilabel:`Blocked` if operators **must** adhere strictly to the |BoM| quantity. Otherwise, choose :guilabel:`Allowed` or :guilabel:`Allowed with Warning`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:215 +msgid ":guilabel:`Routing`: select the preferred warehouse's manufacturing operation type for products produced in multiple warehouses. If left blank, this warehouse's `Manufacturing` operation type is used by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:218 +msgid ":guilabel:`Analytic Distribution`: select pre-created :doc:`analytic distribution models <../../../finance/accounting/reporting/analytic_accounting>` from the list to automatically record the cost of manufacturing products in the chosen journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:221 +msgid ":guilabel:`Manuf Lead Time`: define the number of days needed to complete a |MO| from the date of confirmation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:223 +msgid ":guilabel:`Days to prepare Manufacturing Order`: number of days needed to replenish components, or manufacture sub-assemblies of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:227 +msgid ":doc:`Analytic distribution <../../../finance/accounting/reporting/analytic_accounting>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:228 +msgid ":doc:`Lead times <../../inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "Show the *Miscellaneous* tab of the BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:236 +msgid "Add by-products to BoMs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:238 +msgid "A *by-product* is a residual product that is created during production in addition to the main product of a |BOM|. Unlike the primary product, there can be more than one by-product on a |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:241 +msgid "To add by-products to a |BOM|, first enable the *By-Products* feature in :menuselection:`Manufacturing app --> Configuration --> Settings`. In the :guilabel:`Operations` section, tick the checkbox for :guilabel:`By-Products` to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "\"By Products\" feature in the settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:249 +msgid "Once the feature is enabled, add by-products to a |BOM| by clicking the :guilabel:`By-products` tab. Click :guilabel:`Add a line`, and fill in the :guilabel:`By-product`, :guilabel:`Quantity`, and :guilabel:`Unit of Measure`. Optionally, specify a :guilabel:`Produced in Operation` for the by-product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:255 +msgid "The by-product, `Mush`, is created in the `Grind grapes` operation when producing `Red Wine`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:0 +msgid "Show sample by-product in the BoM." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:3 @@ -14662,15 +16364,40 @@ msgstr "" msgid "The Manufacturing route on the Inventory tab of a product page." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:28 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:30 +msgid "Lot/serial number tracking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:32 +msgid "The assignment of lots or serial numbers to newly manufactured products is optional. To optionally :doc:`assign lots or serial numbers <../../inventory/product_management/product_tracking/create_sn>` to newly manufactured products, go to the :guilabel:`Traceability` section in the :guilabel:`Inventory` tab. In the :guilabel:`Tracking` field, select :guilabel:`By Unique Serial Number` or :guilabel:`By Lots`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:38 +msgid "Doing so enables the *Lot/Serial Number* field on a manufacturing order, or the *Register Production* instruction on a work order card in the *Shop Floor* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:45 +msgid "\"Lot/Serial Number\" field on the MO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:45 +msgid "**Lot/Serial Number** field on the MO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:51 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:51 +msgid "**Register Production** option to generate lot/serial number on a work order card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:54 msgid "Configure a bill of materials (BoM)" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:56 msgid "Next, a |BOM| must be configured for the product so Odoo knows how it is manufactured. A |BOM| is a list of the components and operations required to manufacture a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:33 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:59 msgid "To create a |BOM| for a specific product, navigate to :menuselection:`Manufacturing --> Products --> Products`, then select the product. On the product page, click the :guilabel:`Bill of Materials` smart button at the top of the page, then select :guilabel:`New` to configure a new |BOM|." msgstr "" @@ -14678,11 +16405,11 @@ msgstr "" msgid "The Bill of Materials smart button on a product page." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:67 msgid "On the |BOM|, the :guilabel:`Product` field auto-populates with the product. In the :guilabel:`Quantity` field, specify the number of units that the BoM produces." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:44 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:70 msgid "Add a component to the |BOM| by selecting the :guilabel:`Components` tab and clicking :guilabel:`Add a line`. Select a component from the :guilabel:`Component` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. Continue adding components on new lines until all components have been added." msgstr "" @@ -14690,11 +16417,11 @@ msgstr "" msgid "The Components tab on a bill of materials." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:53 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:79 msgid "Next, select the :guilabel:`Operations` tab. Click :guilabel:`Add a line` and a :guilabel:`Create Operations` pop-up window appears. In the :guilabel:`Operation` field, specify the name of the operation being added (e.g. Assemble, Cut, etc.). Select the work center where the operation will be carried out from the :guilabel:`Work Center` drop-down menu. Finally, click :guilabel:`Save & Close` to finish adding operations, or :guilabel:`Save & New` to add more." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:60 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:86 msgid "The :guilabel:`Operations` tab only appears if the :guilabel:`Work Orders` setting is enabled. To do so, navigate to :menuselection:`Manufacturing --> Configuration --> Settings`, then enable the :guilabel:`Work Orders` checkbox." msgstr "" @@ -14702,8 +16429,8 @@ msgstr "" msgid "The Operations tab on a bill of materials." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:70 -msgid "The section above provides instructions for creating a basic |BOM| that allows a product to be manufactured in Odoo. However, it is by no means an exhaustive summary of all the options available when configuring a |BOM|. For more information about bills of materials, see the documentation on how to :ref:`create a bill of materials `." +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:96 +msgid "The section above provides instructions for creating a basic |BOM| that allows a product to be manufactured in Odoo. However, it is by no means an exhaustive summary of all the options available when configuring a |BOM|. For more information about bills of materials, see the documentation on how to :doc:`create a bill of materials `." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:3 @@ -15360,6 +17087,1242 @@ msgstr "" msgid "The *Real Duration* represents the total time spent working on the work order by all workers who worked on it. It includes time tracked in the *Shop Floor* module, as well as time tracked on the :guilabel:`Work Orders` tab of the |MO| itself." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:5 +msgid "Subcontracting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:9 +msgid "In manufacturing, *subcontracting* is the process of a company engaging a third-party manufacturer, or subcontractor, to manufacture products that are then sold by the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:12 +msgid "Subcontracting provides a variety of benefits for both the contracting company and the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:15 +msgid "For the contracting company, subcontracting allows them to sell a wide variety of manufactured products, without having to worry about investing in and maintaining the equipment and labor required to handle the manufacturing themselves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:19 +msgid "This helps contracting companies stay flexible throughout economic cycles, as they can easily increase or decrease their engagements with subcontractors, as necessitated by the current moment. It also means they are able to focus on tasks they excel at, while delegating more specialized work to subcontractors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:24 +msgid "On the other side of the relationship, subcontracting allows subcontractors to specialize in more niche areas of production, which might not be as profitable outside the bounds of a subcontracting engagement. In certain arrangements, it also provides them with the flexibility to choose which projects they accept or decline, and how many they work on at any given time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:29 +msgid "In Odoo, companies can configure their subcontracting workflows based on a variety of different factors, including how components are sourced, and what happens to finished products once they are manufactured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:54 +msgid "To enable subcontracting in Odoo, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Subcontracting` setting, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:-1 +msgid "The Subcontracting setting in the manufacturing app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:62 +msgid "With subcontracting enabled, a few different features become available in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:64 +msgid "On bills of materials (BoMs), the *BoM Type* field now includes a *Subcontracting* option. Enabling the *Subcontracting* |BoM| type designates the |BoM|'s product as a subcontracted product, which means Odoo knows that it is produced by a subcontractor, and not by the company that owns the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:68 +msgid "Two subcontracting routes become available in the *Inventory* app, and can be assigned to specific products, on the *Inventory* tab of their product pages:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:71 +msgid "*Resupply Subcontractor on Order*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:72 +msgid "*Dropship Subcontractor on Order*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:75 +msgid "Subcontracting workflows" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:77 +msgid "In Odoo, there are three subcontracting workflows, the main difference between them being *how* the subcontractor obtains the necessary components:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:80 +msgid "In the *basic* subcontracting workflow, the subcontractor is fully responsible for obtaining the components. This workflow is outlined in the :doc:`subcontracting/subcontracting_basic` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:83 +msgid "In the *Resupply Subcontractor on Order* workflow, the contracting company sends the components from their warehouse to the subcontractor. This workflow is outlined in the :doc:`subcontracting/subcontracting_resupply` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:86 +msgid "In the *Dropship Subcontractor on Order* workflow, the contracting company purchases the components from a vendor, and has them delivered directly to the subcontractor. This workflow is outlined in the :doc:`subcontracting/subcontracting_dropship` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:90 +msgid "In addition to how a subcontractor obtains components, it is also necessary to consider why a product is being subcontracted, as well as what happens to products once they are manufactured by the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:94 +msgid "In terms of why a product is being subcontracted, the two main reasons are to fulfill a customer order, or to replenish the quantity of stock on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:97 +msgid "In terms of what happens to products once they are manufactured, they can either be shipped to the contracting company, or dropshipped directly to an end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:100 +msgid "Each of the three subcontracting workflows described above can be configured to facilitate any of these possibilities, and the methods for doing so are outlined in their respective documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:104 +msgid "Subcontracted product valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:106 +msgid "The valuation of a subcontracted product depends upon a few different variables:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:108 +msgid "The cost of the required components, if provided by the contracting company; from here on referred to as `C`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:110 +msgid "The price paid to the subcontractor for the service of manufacturing the subcontracted product; from here on referred to as `M`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:112 +msgid "The cost of shipping components to the subcontractor, and having them shipped back to the contracting company; from here on referred to as `S`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:114 +msgid "The cost of dropshipping, if the components are shipped by the subcontractor to the end customer; from here on referred to as `D`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:116 +msgid "Any other associated costs, like import taxes, etc.; from here on referred to as `x`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:118 +msgid "Therefore, the total valuation of a subcontracted product (`P`) can be represented by the following equation:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:121 +msgid "P = C + M + S + D + x\n" +"\n" +"" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:124 +msgid "It is important to note that not every subcontracted product valuation will include all of these variables. For example, if the product is not dropshipped to the end customer, then there is no need to factor in the cost of dropshipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:3 +msgid "Basic subcontracting lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:8 +msgid "In Odoo, lead times are used to predict how long it takes to complete a certain action. For example, a *delivery lead time* can be set for a purchased product, which specifies the number of days it usually takes for the product's vendor to delivery the product to the purchasing company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:12 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:13 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:13 +msgid "For subcontracted products specifically, delivery lead times can be configured to take into account the amount of time required for the subcontractor to manufacture a product. Doing so allows the contracting company to better predict the delivery dates of subcontracted products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:17 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:31 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:23 +msgid "Like all lead times in Odoo, lead times for subcontracted products are only an estimate, and are based on how long actions are *expected* to take." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:20 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:34 +msgid "Unforeseen circumstances can impact the completion of these actions, which means that lead times should not be viewed as guarantees." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:26 +msgid "When using the :doc:`basic subcontracting ` workflow to manufacture a product, a company is not responsible for supplying the subcontractor with the necessary components. This means that the only factors affecting the delivery date of a product are the amount of time it takes the subcontractor to manufacture and deliver it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:31 +msgid "By assigning a product's subcontractor a delivery lead time that considers both of these factors, the *Expected Arrival* date displayed on purchase orders (POs) for the product more accurately reflects the amount of time required for both manufacturing and delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:36 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:54 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:44 +msgid "Product delivery lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:46 +msgid "To set a delivery lead time for a product's subcontractor, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a subcontracted product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:59 +msgid "Then, select the :guilabel:`Purchase` tab on the product's page. If the subcontractor has not already been added as a vendor, do so now by clicking :guilabel:`Add a line`, and selecting the subcontractor in the :guilabel:`Vendor` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:53 +msgid "Once the subcontractor has been added, enter the number of days it takes them to manufacture and deliver the product, in the :guilabel:`Delivery Lead Time` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:-1 +msgid "The Delivery Lead Time field for a subcontractor, on the Purchase tab of a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:53 +msgid "Multiple subcontractors can be added to the :guilabel:`Purchase` tab on a product's page, and a different :guilabel:`Delivery Lead Time` can be set for each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:57 +msgid "Lead time workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:59 +msgid "After setting a delivery lead time for a product's vendor, create an |RfQ| by navigating to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:62 +msgid "Specify the subcontractor in the :guilabel:`Vendor` field. Then, add the product in the :guilabel:`Products` tab by clicking :guilabel:`Add a product`, selecting the product in the :guilabel:`Product` column, and adding a quantity in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:66 +msgid "Once a product has been added, the :guilabel:`Expected Arrival` field on the |RfQ| auto-populates with a date that reflects the vendor's delivery lead time, as specified on the product's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:69 +msgid "If the date needs to be adjusted, click on the :guilabel:`Expected Arrival` field to open a calendar popover, and select the desired date. Make sure not to choose a date sooner than the one that was auto-populated, unless the subcontractor has confirmed that they are able to deliver the product by that date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:74 +msgid "Finally, click :guilabel:`Confirm Order` on the |RfQ| to turn it into a |PO|. At this point, the subcontractor should begin manufacturing the subcontracted product, before delivering it to the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:79 +msgid "Bike retailer *Mike's Bikes* works with a subcontractor — *Bike Friends* — to produce units of their *Tricycle* product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:82 +msgid "On average, Bike Friends requires three days to manufacture a tricycle, plus an additional two days to deliver it to Mike's Bikes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:85 +msgid "As a result, Mike's Bikes sets a delivery lead time of five days for tricycles manufactured by Bike Friends: three days for manufacturing, plus two days for delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:88 +msgid "On May 3rd, Mike's Bikes confirms a |PO| to purchase one tricycle from Bike Friends." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:90 +msgid "The :guilabel:`Expected Arrival` date listed on the |PO| is May 8th, five days after the :guilabel:`Confirmation Date`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:-1 +msgid "The Expected Arrival date on a PO for a subcontracted product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:97 +msgid "Bike Friends begins manufacturing the tricycle on May 3rd — the day that the |PO| is confirmed — and finishes on May 6th, three days later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/basic_subcontracting_lead_times.rst:100 +msgid "The tricycle is then shipped to Mike's Bikes the same day, and they receive it on May 8th, two days later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:3 +msgid "Dropship subcontracting lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:9 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:9 +msgid "In Odoo, lead times are used to predict how long it takes to complete a certain action. For example, a *delivery lead time* can be set for a purchased product, which specifies the number of days it usually takes for the product's vendor to deliver the product to the purchasing company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:17 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:17 +msgid "Certain subcontracted products require the contracting company to supply the subcontractor with manufacturing components. In this case, a *manufacturing lead time* can be used, in addition to the delivery lead time, to generate the date on which the subcontractor must receive the required components, in order to manufacture the product and deliver it on time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:22 +msgid "In cases where components are dropshipped to the subcontractor, an additional delivery lead time can be set for each component. This should be set to the amount of time it takes the vendor to deliver components to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:26 +msgid "Once a delivery lead time has been set on a component, dropship orders for the component display the date by which the order must be confirmed, so that it can be dropshipped to the subcontractor by the date on which manufacturing must begin." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:40 +msgid "When using the :doc:`Dropship Subcontractor on Order ` route, a company is responsible for purchasing the necessary components from a vendor, and having them dropshipped directly to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:44 +msgid "This means that, in addition to the amount of time it takes the subcontractor to manufacture and deliver the product, it is also necessary to consider how long it takes the component vendor to dropship the components to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:48 +msgid "By assigning a product's subcontractor a *delivery lead time*, specifying a *manufacturing lead time* on the product's BoM, and assigning the vendor of the components an additional *delivery lead time*, *Dropship Subcontractor* orders for the product's components display the deadline for confirming a dropship order to send the components to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:56 +msgid "To set a delivery lead time for a product's subcontractor, navigate to :guilabel:`Inventory app --> Products --> Products`, and select a subcontracted product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:71 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:61 +msgid "Product manufacturing lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:73 +msgid "Next, navigate to the product's |BoM| by clicking the :guilabel:`Bill of Materials` smart button at the top of the product's page. Then, select a BoM from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:76 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:66 +msgid "On the |BoM|, select the :guilabel:`Miscellaneous` tab. In the :guilabel:`Manuf. Lead Time` field, enter the same number of days that was entered in the :guilabel:`Delivery Lead Time` field of the |BoM|'s product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:-1 +msgid "The Manuf. Lead Time field on a product's BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:84 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:74 +msgid "While not all of these days are actually used for manufacturing by the subcontractor, setting the same number of days in each field tells Odoo that the subcontractor must receive the components and begin production by the start of the product's delivery lead time. This gives the subcontractor enough time to both manufacture and deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:90 +msgid "Component delivery lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:92 +msgid "From the product's BoM, navigate to each component by clicking on the component in the :guilabel:`Components` tab, and then clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` button to the right of the component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:96 +msgid "On the product page for each component, select the :guilabel:`Purchase` tab. If the vendor has not already been added, do so now by clicking :guilabel:`Add a line`, and selecting the subcontractor in the :guilabel:`Vendor` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:100 +msgid "Once the vendor has been added, enter the number of days it takes them to dropship the product to the subcontractor, in the :guilabel:`Delivery Lead Time` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:104 +msgid "Dropship subcontracting workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:82 +msgid "Create a request for quotation (RfQ) for the product by navigating to :menuselection:`Purchase app --> Orders --> Requests for Quotation`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:109 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:85 +msgid "Specify the subcontractor in :guilabel:`Vendor` field. Then, add the product in the :guilabel:`Products` tab by clicking :guilabel:`Add a product`, selecting the product in the :guilabel:`Product` column, and specifying a quantity in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:113 +msgid "In the :guilabel:`Expected Arrival` field, enter a date that provides enough time for the component vendor to dropship the components, and the subcontractor to manufacture and deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:117 +msgid "When a product is added to an |RfQ|, the :guilabel:`Expected Arrival` field auto-populates with a date that is today's date plus the delivery lead time of the product. However, this does not consider the time it takes to dropship the components to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:121 +msgid "When purchasing a product subcontracted using the *Dropship Subcontractor on Order* route, it is necessary to adjust this date to take into account the extra time needed for the components to be delivered to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:125 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:102 +msgid "Since production does not begin until they receive the components, leaving the date as is results in the finished product arriving *after* the date listed on the |RfQ|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:128 +msgid "Next, click :guilabel:`Confirm Order` to turn the |RfQ| into a |PO|. Doing so creates a second |RfQ| to purchase the components from the dropshipper, and have them sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:131 +msgid "Navigate to :menuselection:`Purchase app --> Orders --> Requests for Quotation`, and select the |RfQ| that lists the dropshipper in the :guilabel:`Vendor` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:134 +msgid "On the |RfQ|, the :guilabel:`Expected Arrival` field lists the date on which the subcontractor must receive the components, in order to deliver the finished product by the *Expected Arrival* date listed on the subcontractor |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:138 +msgid "The :guilabel:`Order Deadline` field lists the latest date on which the |RfQ| can be confirmed, in order for the dropshipper to deliver the components to the subcontractor by the :guilabel:`Expected Arrival` date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:142 +msgid "Click :guilabel:`Confirm Order` to turn the |RfQ| into a |PO|, and confirm the purchase of the components from the dropshipper. Doing so causes a :guilabel:`Dropship` smart button to appear at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:146 +msgid "Click the :guilabel:`Dropship` smart button to open the dropship order. This order can also be accessed from the :guilabel:`Resupply` smart button that now appears on the subcontractor |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:149 +msgid "After the dropshipper has delivered the components to the subcontractor, click the :guilabel:`Validate` button at the top of the dropship order to confirm that the subcontractor has received the components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:153 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:127 +msgid "Once the subcontractor receives the components, they begin manufacturing the component, before delivering it to the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:158 +msgid "Bike retailer *Mike's Bikes* works with a subcontractor — *Bike Friends* — to produce units of their *Bicycle* product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:161 +msgid "Mike's Bikes must purchase the required components from vendor Bike World, and have them dropshipped to Bike Friends." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:164 +msgid "On average, Bike Friends takes three days to manufacture each bicycle, plus an addition two days to deliver it to Mike's Bikes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:167 +msgid "As a result, Mike's Bikes sets a delivery lead time of five days for bicycle manufactured by Bike Friends: three days for manufacturing, plus two days for delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:170 +msgid "On the bicycle's BoM, they enter a manufacturing lead time of five days as well, to remind themselves of the date that components must be delivered to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:173 +msgid "On the product pages for each of the bicycle's components, they assign Bike World a delivery lead time of two days. This is the amount of time it takes Bike World to dropship each component directly to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:177 +msgid "On May 10th, Mike's Bikes confirms a |PO| for one bicycle, with an expected delivery date of May 17th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:180 +msgid "The |RfQ| for purchasing the components from Bike World and having them dropshipped to Bike Friends has an Expected Arrival date of May 12th, and a Deadline of May 10th. The |RfQ| must be confirmed by the deadline in order for Bike Friends to receive the components by the Expected Arrival date, giving them enough time to deliver the finished bicycle to Mike's Bikes by May 17th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:-1 +msgid "The Order Deadline and Expected Arrival dates on a dropship order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/dropship_subcontracting_lead_times.rst:190 +msgid "Mike's Bikes confirms the |RfQ| on May 10th, and Bike World delivers the components to Bike Friends on May 12th. Bike Friends manufactures the bicycle, and delivers it to Mike's Bikes on May 17th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:3 +msgid "Resupply subcontracting lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:26 +msgid "Unforeseen circumstances can impact the completion of these actions, which means that lead times should **not** be viewed as guarantees." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:32 +msgid "When using the :doc:`Resupply Subcontractor on Order ` route, a company is responsible for supplying the subcontractor with the necessary components. As a result, the subcontractor cannot begin manufacturing until the components have been received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:36 +msgid "This means that, in addition to the amount of time it takes the subcontractor to manufacture and deliver the product, the date they receive the components must also be considered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:39 +msgid "By assigning a product's subcontractor a delivery lead time, and specifying a manufacturing lead time on the product's bill of materials (BoM), *Resupply Subcontractor* orders for the product's components display the deadline by which the subcontractor must receive the components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:49 +msgid "Then, select the :guilabel:`Purchase` tab on the product's page. If the subcontractor has not already been added as a vendor, do so now by clicking :guilabel:`Add a line`, and selecting the subcontractor in the :guilabel:`Vendor` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:63 +msgid "Next, navigate to the product's |BoM| by clicking the :guilabel:`Bill of Materials` smart button at the top of the product's page. Then, select a |BoM| from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:80 +msgid "Resupply subcontracting workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:89 +msgid "In the :guilabel:`Expected Arrival` field, enter a date that provides enough time for the subcontractor to receive the components, manufacture the product, and deliver it back to the subcontracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:94 +msgid "When a product is added to an |RfQ|, the :guilabel:`Expected Arrival` field auto-populates with a date that is today's date plus the delivery lead time of the product. However, this does **not** consider the time it takes to ship the components to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:98 +msgid "When purchasing a product subcontracted using the Resupply Subcontractor on Order route, it is necessary to adjust this date to take into account the extra time needed for the components to be shipped to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:105 +msgid "Next, click :guilabel:`Confirm Order` to turn the |RfQ| into a |PO|. Doing so causes a :guilabel:`Resupply` smart button to appear at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:108 +msgid "Click the :guilabel:`Resupply` smart button to open the resupply subcontractor order, which is the order created to send components to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:111 +msgid "The :guilabel:`Deadline` field on the resupply subcontractor order shows the deadline for the subcontractor to receive the components, in order for them to have enough time to manufacture and deliver the finished product by the Expected Arrival date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:115 +msgid "The :guilabel:`Scheduled Date` field should display the latest date on which components can be shipped, while still arriving to the subcontractor by the :guilabel:`Deadline`. However, by default, the date displayed is the same as the date in the :guilabel:`Deadline` field, and must be updated to take into account the time required for shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:120 +msgid "Click on the :guilabel:`Scheduled Date` field to open a calendar popover from which a date can be selected. Select a date that allows for the components to be delivered by the :guilabel:`Deadline` on the resupply subcontractor order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:124 +msgid "After the components are shipped, click the :guilabel:`Validate` button at the top of the order to confirm they have been sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:131 +msgid "Bike retailer *Mike's Bikes* works with a subcontractor — *Bike Friends* — to produce units of their *Unicycle* product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:134 +msgid "Mike's Bikes must supply Bike Friends with the necessary components for manufacturing the unicycles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:137 +msgid "On average, Bike Friends takes three days to manufacture each unicycle, plus an additional two days to deliver it to Mike's Bikes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:140 +msgid "As a result, Mike's Bikes sets a delivery lead time of five days for unicycles manufactured by Bike Friends: three days for manufacturing, plus two days for delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:143 +msgid "On the unicycle's |BoM|, they enter a manufacturing lead time of five days, as well, to remind themselves of the date that components must be delivered to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:146 +msgid "They confirm a |PO| for one unicycle, with an expected arrival date of May 30th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:148 +msgid "The resupply subcontractor order for shipping the components to the subcontractor shows a *Deadline* of May 25th. The subcontractor must receive the components by this date, in order to have enough time to manufacture the unicycle, and deliver it by May 30th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:152 +msgid "It takes Mike's Bikes two days to deliver the components, so they update the *Scheduled Date* field on the resupply subcontractor order to May 23rd, two days before the Deadline." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:-1 +msgid "The Scheduled Date and Deadline fields on a resupply subcontractor order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/resupply_subcontracting_lead_times.rst:159 +msgid "Mike's Bikes ships the components to Bike Friends on the scheduled date of May 23rd, and they arrive on the deadline of May 25th. This gives Bike Friends enough time to manufacture the unicycle, and ship it back to Mike's Bikes by the expected arrival date of May 30th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:3 +msgid "Basic subcontracting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:12 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:10 +msgid "In manufacturing, subcontracting is the process of a company engaging a third-party manufacturer, or subcontractor, to manufacture products that are then sold by the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:13 +msgid "In basic subcontracting, the subcontractor is responsible for acquiring the necessary components. This means that the contracting company only has to worry about what happens to subcontracted products once they are produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:17 +msgid "The workflow for purchasing a product manufactured using basic subcontracting is similar to the one used when purchasing a non-subcontracted product from a vendor. The main differences are the way that subcontracted products are configured, and the fact that subcontracted products take longer to be sent from the vendor, since they must first be manufactured by them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:25 +msgid "To use subcontracting in Odoo, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Subcontracting` setting, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:29 +msgid "Once the :guilabel:`Subcontracting` setting is enabled, it is also necessary to properly configure the subcontracted product, and the product's |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:51 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:53 +msgid "Configure product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:37 +msgid "To configure a product for basic subcontracting, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:40 +msgid "On the product form, select the :guilabel:`Purchase` tab, and add the product's subcontractor as a vendor by clicking :guilabel:`Add a line`, selecting the subcontractor in the :guilabel:`Vendor` drop-down menu, and entering a price in the :guilabel:`Price` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:44 +msgid "Then, click on the :guilabel:`Inventory` tab, and use the :guilabel:`Routes` field to configure a route that determines what happens to the finished product once it has been manufactured by the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:48 +msgid "If the finished product is shipped back to the contracting company, make sure the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a sales order (SO), unless there is enough stock on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:53 +msgid "If the finished product is shipped directly to the customer by the subcontractor, make sure that **only** the :guilabel:`Dropship` route is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:57 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:83 +msgid "Configure BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:59 +msgid "To configure a |BoM| for basic subcontracting, click the :guilabel:`Bill of Materials` smart button on the product form, and select the desired |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:62 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:78 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:88 +msgid "Alternatively, navigate to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the |BoM| for the subcontracted product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:66 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:82 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:92 +msgid "For a full overview of |BoM| configuration, see the :doc:`Bill of materials <../basic_setup/bill_configuration>` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:69 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:95 +msgid "In the :guilabel:`BoM Type` field, select the :guilabel:`Subcontracting` option. Then, add one or more subcontractors in the :guilabel:`Subcontractors` field that appears below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:-1 +msgid "The \"BoM Type\" field on a BoM, configured to manufacture the product using subcontracting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:76 +msgid "Finally, click on the :guilabel:`Miscellaneous` tab. In the :guilabel:`Manuf. Lead Time` field, enter the number of days it takes the subcontractor to manufacture the product. This number is factored in when calculating the product's expected arrival date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:81 +msgid "When using basic subcontracting, there is no need to list components in the :guilabel:`Components` tab of the |BoM|, since the components required for manufacturing, and the means by which they are acquired, are handled by the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:86 +msgid "Basic subcontracting workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:88 +msgid "The basic subcontracting workflow consists of up to four steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:90 +msgid "Create a sales order (SO) for the subcontracted product; doing so creates a |PO| to purchase the product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:92 +msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a receipt order or a dropship order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:94 +msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company, **OR** process the dropship order to ship the product directly to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:97 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:135 +msgid "If the workflow was started by creating an |SO|, and the finished product is not dropshipped to the end customer, process the delivery order once the product is shipped to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:100 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:138 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:138 +msgid "The specific number of steps depends on the reason that the subcontracted product is being purchased from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:103 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:141 +msgid "If the reason is to fulfill a specific customer order, the process starts with creating an |SO|, and ends with delivering the product to the customer, or having the subcontractor dropship it to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:144 +msgid "If the reason is to increase the quantity of stock on-hand, the process starts with creating a |PO|, and ends with receiving the product into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:169 +msgid "Create SO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:112 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:150 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:171 +msgid "It is only necessary to complete this step if the product is being purchased from the subcontractor to fulfill a customer need. If the product is being purchased to increase the quantity of stock on-hand, move on to the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:116 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:154 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:175 +msgid "To create a new |SO|, navigate to :menuselection:`Sales app --> Orders --> Orders`, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:119 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:178 +msgid "Select the customer in the :guilabel:`Customer` drop-down menu. Then, click :guilabel:`Add a product` on the :guilabel:`Order Lines` tab, select a subcontracted product in the :guilabel:`Product` drop-down menu, and enter a quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:182 +msgid "Click :guilabel:`Confirm` to confirm the |SO|, at which point a :guilabel:`Purchase` smart button appears at the top of the page. This opens the |PO| created to purchase the subcontracted product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:128 +msgid "An |SO| for the product only creates a |PO| if the *Replenish on Order (MTO)* route is enabled on the product's form, **and** there is not enough stock of the product on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:131 +msgid "If there is enough stock on-hand, confirming an |SO| for the product creates a delivery order instead, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:134 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:193 +msgid "This is not the case for subcontracted products that are dropshipped to the end customer. In that case, a |PO| is **always** created, even if there is enough stock on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:138 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:197 +msgid "Process PO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:140 +msgid "If a |PO| was created in the previous step, navigate to it by clicking the :guilabel:`Purchase` smart button at the top of the |SO|, or by going to :guilabel:`Purchase app --> Orders --> Purchase Orders`, and selecting the |PO|. Then, click :guilabel:`Confirm Order` to confirm it, and move on to the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:145 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:202 +msgid "If a |PO| was not created in the previous step, do so now by navigating to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:148 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:205 +msgid "Begin filling out the |PO| by selecting a subcontractor from the :guilabel:`Vendor` drop-down menu. In the :guilabel:`Products` tab, click :guilabel:`Add a product` to create a new product line. Select a subcontracted product in the :guilabel:`Product` field, and enter the quantity in the :guilabel:`Quantity` field. Finally, click :guilabel:`Confirm Order` to confirm the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:153 +msgid "When a |PO| is confirmed for a product manufactured using basic subcontracting, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:161 +msgid "A PO for a basic subcontracting product, with a Receipt smart button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:161 +msgid "PO for a basic subcontracting product, with a Receipt smart button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:164 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:237 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:242 +msgid "Process receipt or dropship order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:166 +msgid "Once the subcontractor has finished manufacturing the product, they either ship it to the contracting company, or dropship it to the end customer, depending on how the product was :ref:`configured `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:173 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:251 +msgid "If the subcontractor ships the finished product to the contracting company, once it has been received, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:177 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:255 +msgid "Click the :guilabel:`Receive Products` button at the top of the |PO|, or the :guilabel:`Receipt` smart button at the top of the page, to open the receipt. Then, click :guilabel:`Validate` at the top of the receipt to enter the product into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:182 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:260 +msgid "Process dropship order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:184 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:262 +msgid "If the subcontractor dropships the product, once they have sent it, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:187 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:265 +msgid "Select the :guilabel:`Dropship` smart button at the top of the page to open the dropship order, and click :guilabel:`Validate` at the top of the order to confirm that the product has been sent to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:192 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:254 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:270 +msgid "Process delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:194 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:256 +msgid "If the subcontracting workflow was started by a customer |SO|, and the finished product was **not** dropshipped to the customer, but rather delivered to the contracting company, it is necessary to ship the product to the customer, and process the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:198 +msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` on the order to confirm that the product has been shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:3 +msgid "Dropship to subcontractor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:15 +msgid "In Odoo, the *Dropship Subcontractor on Order* route is used to purchase the necessary components for a subcontracted product from the vendor, and have them delivered directly to the subcontractor, each time a purchase order (PO) for that product is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:19 +msgid "The subcontractor then uses the components to manufacture the desired product, before shipping it back to the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:23 +msgid "It is necessary to understand the differences between the *Dropship* and *Dropship Subcontractor on Order* routes. While both routes involve dropshipping, they are used for different purposes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:26 +msgid "The *Dropship* route is used to purchase products from a vendor, and have them shipped directly to the end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:29 +msgid "The *Dropship Subcontractor on Order* route is used to purchase components from a vendor, and have them shipped directly to a subcontractor. By default, finished products are then sent from the subcontractor back to the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:33 +msgid "However, it is possible to combine both the *Dropship* and *Dropship Subcontractor on Order* routes so they are used for the same product. In this workflow, components are dropshipped to the subcontractor, who then ships the finished product directly to the end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:37 +msgid "This can be achieved by following steps one through five in the :ref:`workflow section ` of this doc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:43 +msgid "To use the *Dropship Subcontractor on Order* route, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and enable the checkbox next to :guilabel:`Subcontracting`, under the :guilabel:`Operations` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:47 +msgid "Once the *Subcontracting* setting is enabled, it is also necessary to properly configure the subcontracted product, the product's |BoM|, and the components listed on the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:53 +msgid "To configure a product for the *Dropship Subcontractor on Order* route, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:57 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:59 +msgid "Select the :guilabel:`Purchase` tab, and add the product's subcontractor as a vendor by clicking :guilabel:`Add a line`, selecting the subcontractor in the :guilabel:`Vendor` drop-down menu, and entering a price in the :guilabel:`Price` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:61 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:71 +msgid "Then, click on the :guilabel:`Inventory` tab to configure a route that determines what happens to the finished product, once it has been manufactured by the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:64 +msgid "If the finished product is shipped back to the contracting company, make sure that the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a |SO|, unless there is enough stock on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:69 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:79 +msgid "If the finished product is shipped directly to the customer by the subcontractor, make sure that only the :guilabel:`Dropship` route is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:73 +msgid "Configure bill of materials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:75 +msgid "To configure a |BoM| for the *Dropship Subcontractor on Order* route, click the :guilabel:`Bill of Materials` smart button on the product's page, and select the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:92 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:102 +msgid "Finally, make sure that all necessary components are specified on the :guilabel:`Components` tab. To add a new component, click :guilabel:`Add a line`, select the component in the :guilabel:`Component` drop-down menu, and specify the required quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:97 +msgid "Configure Components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:99 +msgid "To configure components for the *Dropship Subcontractor on Order* route, navigate to each component from the |BoM| by selecting the component's name in the :guilabel:`Components` tab, and clicking the :guilabel:`➡️ (right arrow)` button to the right of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:103 +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:113 +msgid "Alternatively, navigate to each component by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:106 +msgid "On the component product form, select the :guilabel:`Purchase` tab, and add a vendor by clicking :guilabel:`Add a line`, selecting the vendor in the :guilabel:`Vendor` field, and adding the price they sell the product for in the :guilabel:`Price` field. This is the vendor that sends components to the subcontractor, once they are purchased." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:111 +msgid "Then, click on the :guilabel:`Inventory` tab and select the :guilabel:`Dropship Subcontractor on Order` route in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:114 +msgid "Repeat the process for every component that must be dropshipped to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:119 +msgid "Dropship subcontractor on order workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:121 +msgid "The dropship subcontractor on order workflow consists of up to six steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:123 +msgid "Create a sales order (SO) for the subcontracted product; doing so creates a *subcontractor* |PO| to purchase the product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:125 +msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a request for quotation (RfQ) to purchase the components from the vendor, as well as a receipt order or a dropship order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:128 +msgid "Confirm the |RfQ| to turn it into a second |PO| (*vendor* |PO|); doing so creates a *Dropship Subcontractor* order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:130 +msgid "Process the *Dropship Subcontractor* order once the vendor has sent the components to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:132 +msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company **OR** process the dropship order to ship the product directly to the end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:135 +msgid "If the workflow was started by creating an |SO|, and the finished product is not dropshipped to the end customer, process the delivery order once the product has been shipped to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:141 +msgid "If the reason is to fulfill a specific customer order, the process starts with creating an SO, and ends with delivering the product to the customer, or having the subcontractor dropship it to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:144 +msgid "If the reason is to increase quantity of stock on-hand, the process starts with creating a PO, and ends with receiving the product into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:148 +msgid "Create an SO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:157 +msgid "Select the customer in the :guilabel:`Customer` drop-down menu. Then, click :guilabel:`Add a product` on the :guilabel:`Order Lines` tab, select the product in the :guilabel:`Product` drop-down menu, and enter a quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:161 +msgid "Click :guilabel:`Confirm` to confirm the |SO|, at which point a :guilabel:`Purchase` smart button appears at the top of the page. This is the *subcontractor* |PO|, or the |PO| created to purchase the subcontracted product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:166 +msgid "An |SO| for the product only creates a *subcontractor* |PO| if the *Replenish on Order (MTO)* route is enabled on the product's page, **and** there is no stock of the product on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:169 +msgid "If there is stock on-hand, confirming an |SO| for the product will instead create a delivery order, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:172 +msgid "This is not the case for subcontracted products that are dropshipped to the end customer. In that case, a *subcontractor* |PO| is **always** created, even if there is stock on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:176 +msgid "Process subcontractor PO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:178 +msgid "If a *subcontractor* |PO| was not created in the previous step, do so now by navigating to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:181 +msgid "Begin filling out the |PO| by selecting a subcontractor from the :guilabel:`Vendor` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:183 +msgid "In the :guilabel:`Products` tab, click :guilabel:`Add a product` to create a new product line. Select a product produced by the subcontractor in the :guilabel:`Product` field, and enter the quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:187 +msgid "Finally, click :guilabel:`Confirm Order` to confirm the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:189 +msgid "When a |PO| is confirmed for a product that requires dropshipping components to a subcontractor, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:-1 +msgid "A subcontractor PO for a *Dropship Subcontractor on Order* product, with a Receipt smart\n" +"button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:198 +msgid "In addition, an |RfQ| is created for the components that are purchased from the vendor and sent to the subcontractor. However, the |RfQ| **IS NOT** automatically linked to the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:201 +msgid "Once the |RfQ| is confirmed and becomes a *vendor* |PO|, a *Dropship Subcontractor* order is created. This order is linked to both the *vendor* |PO| and the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:205 +msgid "Confirm vendor RfQ" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:207 +msgid "To access the |RfQ| created by confirming the *subcontractor* |PO|, navigate to :menuselection:`Purchase app --> Orders --> Requests for Quotation`. Select the |RfQ| that lists the correct vendor in the :guilabel:`Vendor` field, and the reference number of the receipt that was created after confirming *subcontractor* |PO|, in the :guilabel:`Source Document` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:212 +msgid "On the |RfQ|, the :guilabel:`Deliver To` field reads :guilabel:`Dropship Subcontractor`, and the :guilabel:`Dropship Address` field shows the name of the subcontractor to whom components are being dropshipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:216 +msgid "Click :guilabel:`Confirm Order` to turn the |RfQ| into a *vendor* |PO|, and confirm the purchase of components from the vendor. After doing so, a :guilabel:`Dropship` smart button appears at the top of the *vendor* |PO|, and a :guilabel:`Resupply` smart button appears at the top of the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:-1 +msgid "A vendor PO for the components of a *Dropship Subcontractor on Order* product, with a\n" +"Dropship smart button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:227 +msgid "Process Dropship Subcontractor order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:229 +msgid "Once the components have been delivered to the subcontractor, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the *vendor* |PO| or the *subcontractor* |PO|. Then, click the :guilabel:`Dropship` smart button or the :guilabel:`Resupply` smart button, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:233 +msgid "Clicking either button opens the *Dropship Subcontractor* order. Click the :guilabel:`Validate` button at the top of the order to confirm that the subcontractor has received the components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:239 +msgid "Once the subcontractor has manufactured the finished product, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:242 +msgid "If the subcontracted product should be received into inventory, once the product arrives, click the :guilabel:`Receive Products` button at the top of the *subcontractor* |PO| to open the receipt. Then, click :guilabel:`Validate` at the top of the receipt to register the product into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:246 +msgid "Alternatively, select the :guilabel:`Receipt` smart button at the top of the *subcontractor* |PO|, and click :guilabel:`Validate` at the top of the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:249 +msgid "If the subcontracted product should be dropshipped, select the :guilabel:`Dropship` button at the top of the page to open the dropship order, and click :guilabel:`Validate` once the subcontractor has sent the product to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:260 +msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` to confirm that the product has been shipped to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:3 +msgid "Resupply subcontractor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:13 +msgid "In Odoo, the *Resupply Subcontractor on Order* route is used to deliver the necessary components for a subcontracted product to the subcontractor, each time a purchase order (PO) for that product is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:17 +msgid "The subcontractor then uses the components to manufacture the desired product, before shipping it back to the contracting company, or dropshipping it to the end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:21 +msgid "It is necessary to understand the differences between the *Resupply Subcontractor on Order* and the *Dropship Subcontractor on Order* routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:24 +msgid "While both routes are used to supply a subcontractor with the components required for manufacturing a product, they differ in how the components are sourced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:27 +msgid "When using *Resupply Subcontractor on Order*, components are shipped from the warehouse of the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:30 +msgid "When using *Dropship Subcontractor on Order*, components are purchased from a vendor and shipped directly to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:33 +msgid "The choice of which route to use depends upon the specific requirements of the subcontracting company and their subcontractors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:36 +msgid "See the :doc:`subcontracting_dropship` documentation for a full overview of the *Dropship Subcontractor on Order* route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:42 +msgid "To use the *Resupply Subcontractor on Order* route, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and enable the checkbox next to :guilabel:`Subcontracting`, under the :guilabel:`Operations` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:46 +msgid "Once the *Subcontracting* setting is enabled, it is also necessary to properly configure the subcontracted product, the product's bill of materials (BoM), and the components listed on the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:55 +msgid "To configure a product for the *Resupply Subcontractor on Order* route, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:64 +msgid "The value entered in the :guilabel:`Price` field on the :guilabel:`Purchase` tab of the of the subcontracted product's page is the amount paid to the subcontractor for the manufacturing of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:68 +msgid "This does not represent the total cost of the product, which includes other elements, like the cost of the product's components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:74 +msgid "If the finished product is shipped back to the contracting company, make sure that the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a sales order (SO), unless there is enough stock on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:85 +msgid "To configure a |BoM| for the *Resupply Subcontractor on Order* route, click the :guilabel:`Bill of Materials` smart button on the product's page, and select the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:107 +msgid "Configure components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:109 +msgid "To configure components for the *Resupply Subcontractor on Order* route, navigate to each component from the |BoM| by selecting the component's name in the :guilabel:`Components` tab, and clicking the :guilabel:`➡️ (right arrow)` button to the right of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:116 +msgid "On the component product form, click on the :guilabel:`Inventory` tab and select the :guilabel:`Resupply Subcontractor on Order` route in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:119 +msgid "Repeat the process for every component that must be sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:122 +msgid "Resupply subcontractor on order workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:124 +msgid "The resupply subcontractor on order workflow consists of up to five steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:126 +msgid "Create an |SO| for the subcontracted product; doing so creates a |PO| to purchase the product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:128 +msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a *Resupply Subcontractor* order, as well as a receipt order or a dropship order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:130 +msgid "Process the *Resupply Subcontractor* order once components for the subcontracted product have been sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:132 +msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company **OR** process the dropship order to ship the product directly to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:149 +msgid "While the *Resupply Subcontractor on Order* route can be used to automatically resupply a subcontractor upon confirmation of a |PO|, it is also possible to create a resupply order manually. This workflow is useful when it is necessary to resupply the subcontractor without creating a |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:154 +msgid "To resupply a subcontractor manually, navigate to the :menuselection:`Inventory` app, and click on the :guilabel:`Resupply Subcontractor` card. Create a new *Resupply Subcontractor* order by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:158 +msgid "In the :guilabel:`Delivery Address` field, select the subcontractor to whom the components should be sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:161 +msgid "Then, add each component to the :guilabel:`Operations` tab by clicking :guilabel:`Add a line`, selecting the component in the :guilabel:`Product` drop-down field, and specifying a quantity in the :guilabel:`Demand` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:165 +msgid "Finally, click :guilabel:`Mark as Todo` to register the order. Once the components have been sent to the subcontractor, click :guilabel:`Validate` to confirm that the order has been sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:187 +msgid "An |SO| for the product only creates a |PO| if the *Replenish on Order (MTO)* route is enabled on the product's page, **and** there is not enough stock of the product on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:190 +msgid "If there is enough stock on-hand, confirming an |SO| for the product instead creates a delivery order, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:199 +msgid "If a |PO| was created in the previous step, navigate to :guilabel:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|. Then, click :guilabel:`Confirm Order` to confirm it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:210 +msgid "When a |PO| is confirmed for a product that requires resupplying a subcontractor with components, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:214 +msgid "In addition, a *Resupply Subcontractor* order is created to ship the required components to the subcontractor. This order can also be accessed from the |PO|, by clicking the :guilabel:`Resupply` smart button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:223 +msgid "A PO for a *Resupply Subcontractor on Order* product, with Resupply and Receipt smart\n" +"buttons at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:223 +msgid "A PO for a *Resupply Subcontractor on Order* product, with Resupply and Receipt smart buttons at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:227 +msgid "Process Resupply Subcontractor order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:229 +msgid "Once the subcontracted product's components have been sent to the subcontractor, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:232 +msgid "Click the :guilabel:`Resupply` smart button at the top of the screen to open the *Resupply Subcontractor* order, and click :guilabel:`Validate` to confirm that the components have been sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:236 +msgid "Alternatively, navigate to the :menuselection:`Inventory` app, click the :guilabel:`# To Process` button on the :guilabel:`Resupply Subcontractor` card, and select the *Resupply Subcontractor* order. Then, click :guilabel:`Validate` to confirm that the components have been sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:244 +msgid "Once the subcontractor has finished manufacturing the product, they either ship it to the contracting company, or dropship it to the end customer, depending on how the product was :ref:`configured `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:272 +msgid "If the subcontracting workflow was started by a customer |SO|, and the finished product was **NOT** dropshipped to the customer, but rather delivered to the contracting company, it is necessary to ship the product to the customer, and process the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:276 +msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` on the order to confirm that the product has been shipped to the customer." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/workflows.rst:5 msgid "Workflows" msgstr "" @@ -15522,6 +18485,10 @@ msgstr "" msgid "Components can be scrapped from both the *Manufacturing* app and the *Shop Floor* module, before the associated manufacturing order (MO) is closed. Finished products can only be scrapped from the *Manufacturing* app, and only after closing the associated |MO|." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:25 +msgid "Scrap orders can be viewed by navigating to :menuselection:`Inventory --> Operations --> Scrap`. Each scrap order shows the date and time the order was created, along with the product and quantity that was scrapped." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:29 msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`, then remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display all virtual locations. From the list, select the :guilabel:`Virtual Locations/Scrap` location." msgstr "" @@ -15679,836 +18646,6 @@ msgstr "" msgid "Manufacturing orders *WH/MO/00009* and *WH/MO/00010* are merged to create *WH/MO/00011*. The source field for *WH/MO/00011* lists both *WH/MO/00009* and *WH/MO/00010*." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:3 -msgid "Subcontracting overview" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:7 -msgid "In manufacturing, *subcontracting* is the process of a company engaging a third-party manufacturer, or subcontractor, to manufacture products that are then sold by the contracting company." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:10 -msgid "Subcontracting provides a variety of benefits for both the contracting company and the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:13 -msgid "For the contracting company, subcontracting allows them to sell a wide variety of manufactured products, without having to worry about investing in and maintaining the equipment and labor required to handle the manufacturing themselves." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:17 -msgid "This helps contracting companies stay flexible throughout economic cycles, as they can easily increase or decrease their engagements with subcontractors, as necessitated by the current moment. It also means they are able to focus on tasks they excel at, while delegating more specialized work to subcontractors." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:22 -msgid "On the other side of the relationship, subcontracting allows subcontractors to specialize in more niche areas of production, which might not be as profitable outside the bounds of a subcontracting engagement. In certain arrangements, it also provides them with the flexibility to choose which projects they accept or decline, and how many they work on at any given time." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:27 -msgid "In Odoo, companies can configure their subcontracting workflows based on a variety of different factors, including how components are sourced, and what happens to finished products once they are manufactured." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:34 -msgid "To enable subcontracting in Odoo, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Subcontracting` setting, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:-1 -msgid "The Subcontracting setting in the manufacturing app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:42 -msgid "With subcontracting enabled, a few different features become available in Odoo:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:44 -msgid "On bills of materials (BoMs), the *BoM Type* field now includes a *Subcontracting* option. Enabling the *Subcontracting* |BoM| type designates the |BoM|'s product as a subcontracted product, which means Odoo knows that it is produced by a subcontractor, and not by the company that owns the Odoo database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:48 -msgid "Two subcontracting routes become available in the *Inventory* app, and can be assigned to specific products, on the *Inventory* tab of their product pages:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:51 -msgid "*Resupply Subcontractor on Order*" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:52 -msgid "*Dropship Subcontractor on Order*" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:55 -msgid "Subcontracting workflows" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:57 -msgid "In Odoo, there are three subcontracting workflows, the main difference between them being *how* the subcontractor obtains the necessary components:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:60 -msgid "In the *basic* subcontracting workflow, the subcontractor is fully responsible for obtaining the components. This workflow is outlined in the :doc:`subcontracting_basic` documentation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:62 -msgid "In the *Resupply Subcontractor on Order* workflow, the contracting company sends the components from their warehouse to the subcontractor. This workflow is outlined in the :doc:`subcontracting_resupply` documentation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:65 -msgid "In the *Dropship Subcontractor on Order* workflow, the contracting company purchases the components from a vendor, and has them delivered directly to the subcontractor. This workflow is outlined in the :doc:`subcontracting_dropship` documentation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:69 -msgid "In addition to how a subcontractor obtains components, it is also necessary to consider why a product is being subcontracted, as well as what happens to products once they are manufactured by the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:73 -msgid "In terms of why a product is being subcontracted, the two main reasons are to fulfill a customer order, or to replenish the quantity of stock on-hand." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:76 -msgid "In terms of what happens to products once they are manufactured, they can either be shipped to the contracting company, or dropshipped directly to an end customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:79 -msgid "Each of the three subcontracting workflows described above can be configured to facilitate any of these possibilities, and the methods for doing so are outlined in their respective documentation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:83 -msgid "Subcontracted product valuation" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:85 -msgid "The valuation of a subcontracted product depends upon a few different variables:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:87 -msgid "The cost of the required components, if provided by the contracting company; from here on referred to as `C`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:89 -msgid "The price paid to the subcontractor for the service of manufacturing the subcontracted product; from here on referred to as `M`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:91 -msgid "The cost of shipping components to the subcontractor, and having them shipped back to the contracting company; from here on referred to as `S`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:93 -msgid "The cost of dropshipping, if the components are shipped by the subcontractor to the end customer; from here on referred to as `D`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:95 -msgid "Any other associated costs, like import taxes, etc.; from here on referred to as `x`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:97 -msgid "Therefore, the total valuation of a subcontracted product (`P`) can be represented by the following equation:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:100 -msgid "P = C + M + S + D + x\n" -"\n" -"" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:103 -msgid "It is important to note that not every subcontracted product valuation will include all of these variables. For example, if the product is not dropshipped to the end customer, then there is no need to factor in the cost of dropshipping." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:3 -msgid "Basic subcontracting" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:10 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:12 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:10 -msgid "In manufacturing, subcontracting is the process of a company engaging a third-party manufacturer, or subcontractor, to manufacture products that are then sold by the contracting company." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:13 -msgid "In basic subcontracting, the subcontractor is responsible for acquiring the necessary components. This means that the contracting company only has to worry about what happens to subcontracted products once they are produced." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:17 -msgid "The workflow for purchasing a product manufactured using basic subcontracting is similar to the one used when purchasing a non-subcontracted product from a vendor. The main differences are the way that subcontracted products are configured, and the fact that subcontracted products take longer to be sent from the vendor, since they must first be manufactured by them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:25 -msgid "To use subcontracting in Odoo, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Subcontracting` setting, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:29 -msgid "Once the :guilabel:`Subcontracting` setting is enabled, it is also necessary to properly configure the subcontracted product, and the product's |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:35 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:51 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:53 -msgid "Configure product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:37 -msgid "To configure a product for basic subcontracting, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:40 -msgid "On the product form, select the :guilabel:`Purchase` tab, and add the product's subcontractor as a vendor by clicking :guilabel:`Add a line`, selecting the subcontractor in the :guilabel:`Vendor` drop-down menu, and entering a price in the :guilabel:`Price` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:44 -msgid "Then, click on the :guilabel:`Inventory` tab, and use the :guilabel:`Routes` field to configure a route that determines what happens to the finished product once it has been manufactured by the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:48 -msgid "If the finished product is shipped back to the contracting company, make sure the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a sales order (SO), unless there is enough stock on-hand to fulfill the |SO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:53 -msgid "If the finished product is shipped directly to the customer by the subcontractor, make sure that **only** the :guilabel:`Dropship` route is selected." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:57 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:83 -msgid "Configure BoM" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:59 -msgid "To configure a |BoM| for basic subcontracting, click the :guilabel:`Bill of Materials` smart button on the product form, and select the desired |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:62 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:78 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:88 -msgid "Alternatively, navigate to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the |BoM| for the subcontracted product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:66 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:82 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:92 -msgid "For a full overview of |BoM| configuration, see the :doc:`Bill of materials <../basic_setup/bill_configuration>` documentation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:69 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:85 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:95 -msgid "In the :guilabel:`BoM Type` field, select the :guilabel:`Subcontracting` option. Then, add one or more subcontractors in the :guilabel:`Subcontractors` field that appears below." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:-1 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:-1 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:-1 -msgid "The \"BoM Type\" field on a BoM, configured to manufacture the product using subcontracting." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:76 -msgid "Finally, click on the :guilabel:`Miscellaneous` tab. In the :guilabel:`Manuf. Lead Time` field, enter the number of days it takes the subcontractor to manufacture the product. This number is factored in when calculating the product's expected arrival date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:81 -msgid "When using basic subcontracting, there is no need to list components in the :guilabel:`Components` tab of the |BoM|, since the components required for manufacturing, and the means by which they are acquired, are handled by the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:86 -msgid "Basic subcontracting workflow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:88 -msgid "The basic subcontracting workflow consists of up to four steps:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:90 -msgid "Create a sales order (SO) for the subcontracted product; doing so creates a |PO| to purchase the product from the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:92 -msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a receipt order or a dropship order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:94 -msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company, **OR** process the dropship order to ship the product directly to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:97 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:135 -msgid "If the workflow was started by creating an |SO|, and the finished product is not dropshipped to the end customer, process the delivery order once the product is shipped to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:100 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:138 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:138 -msgid "The specific number of steps depends on the reason that the subcontracted product is being purchased from the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:103 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:141 -msgid "If the reason is to fulfill a specific customer order, the process starts with creating an |SO|, and ends with delivering the product to the customer, or having the subcontractor dropship it to them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:106 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:144 -msgid "If the reason is to increase the quantity of stock on-hand, the process starts with creating a |PO|, and ends with receiving the product into inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:110 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:169 -msgid "Create SO" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:112 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:150 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:171 -msgid "It is only necessary to complete this step if the product is being purchased from the subcontractor to fulfill a customer need. If the product is being purchased to increase the quantity of stock on-hand, move on to the next step." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:116 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:154 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:175 -msgid "To create a new |SO|, navigate to :menuselection:`Sales app --> Orders --> Orders`, and click :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:119 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:178 -msgid "Select the customer in the :guilabel:`Customer` drop-down menu. Then, click :guilabel:`Add a product` on the :guilabel:`Order Lines` tab, select a subcontracted product in the :guilabel:`Product` drop-down menu, and enter a quantity in the :guilabel:`Quantity` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:123 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:182 -msgid "Click :guilabel:`Confirm` to confirm the |SO|, at which point a :guilabel:`Purchase` smart button appears at the top of the page. This opens the |PO| created to purchase the subcontracted product from the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:128 -msgid "An |SO| for the product only creates a |PO| if the *Replenish on Order (MTO)* route is enabled on the product's form, **and** there is not enough stock of the product on-hand to fulfill the |SO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:131 -msgid "If there is enough stock on-hand, confirming an |SO| for the product creates a delivery order instead, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:134 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:193 -msgid "This is not the case for subcontracted products that are dropshipped to the end customer. In that case, a |PO| is **always** created, even if there is enough stock on-hand." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:138 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:197 -msgid "Process PO" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:140 -msgid "If a |PO| was created in the previous step, navigate to it by clicking the :guilabel:`Purchase` smart button at the top of the |SO|, or by going to :guilabel:`Purchase app --> Orders --> Purchase Orders`, and selecting the |PO|. Then, click :guilabel:`Confirm Order` to confirm it, and move on to the next step." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:145 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:202 -msgid "If a |PO| was not created in the previous step, do so now by navigating to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and clicking :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:148 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:205 -msgid "Begin filling out the |PO| by selecting a subcontractor from the :guilabel:`Vendor` drop-down menu. In the :guilabel:`Products` tab, click :guilabel:`Add a product` to create a new product line. Select a subcontracted product in the :guilabel:`Product` field, and enter the quantity in the :guilabel:`Quantity` field. Finally, click :guilabel:`Confirm Order` to confirm the |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:153 -msgid "When a |PO| is confirmed for a product manufactured using basic subcontracting, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:161 -msgid "A PO for a basic subcontracting product, with a Receipt smart button at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:161 -msgid "PO for a basic subcontracting product, with a Receipt smart button at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:164 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:237 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:242 -msgid "Process receipt or dropship order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:166 -msgid "Once the subcontractor has finished manufacturing the product, they either ship it to the contracting company, or dropship it to the end customer, depending on how the product was :ref:`configured `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:171 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:249 -msgid "Process receipt" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:173 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:251 -msgid "If the subcontractor ships the finished product to the contracting company, once it has been received, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:177 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:255 -msgid "Click the :guilabel:`Receive Products` button at the top of the |PO|, or the :guilabel:`Receipt` smart button at the top of the page, to open the receipt. Then, click :guilabel:`Validate` at the top of the receipt to enter the product into inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:182 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:260 -msgid "Process dropship order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:184 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:262 -msgid "If the subcontractor dropships the product, once they have sent it, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:187 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:265 -msgid "Select the :guilabel:`Dropship` smart button at the top of the page to open the dropship order, and click :guilabel:`Validate` at the top of the order to confirm that the product has been sent to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:192 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:254 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:270 -msgid "Process delivery order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:194 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:256 -msgid "If the subcontracting workflow was started by a customer |SO|, and the finished product was **not** dropshipped to the customer, but rather delivered to the contracting company, it is necessary to ship the product to the customer, and process the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:198 -msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` on the order to confirm that the product has been shipped." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:3 -msgid "Dropship to subcontractor" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:15 -msgid "In Odoo, the *Dropship Subcontractor on Order* route is used to purchase the necessary components for a subcontracted product from the vendor, and have them delivered directly to the subcontractor, each time a purchase order (PO) for that product is confirmed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:19 -msgid "The subcontractor then uses the components to manufacture the desired product, before shipping it back to the contracting company." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:23 -msgid "It is necessary to understand the differences between the *Dropship* and *Dropship Subcontractor on Order* routes. While both routes involve dropshipping, they are used for different purposes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:26 -msgid "The *Dropship* route is used to purchase products from a vendor, and have them shipped directly to the end customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:29 -msgid "The *Dropship Subcontractor on Order* route is used to purchase components from a vendor, and have them shipped directly to a subcontractor. By default, finished products are then sent from the subcontractor back to the contracting company." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:33 -msgid "However, it is possible to combine both the *Dropship* and *Dropship Subcontractor on Order* routes so they are used for the same product. In this workflow, components are dropshipped to the subcontractor, who then ships the finished product directly to the end customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:37 -msgid "This can be achieved by following steps one through five in the :ref:`workflow section ` of this doc." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:43 -msgid "To use the *Dropship Subcontractor on Order* route, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and enable the checkbox next to :guilabel:`Subcontracting`, under the :guilabel:`Operations` heading." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:47 -msgid "Once the *Subcontracting* setting is enabled, it is also necessary to properly configure the subcontracted product, the product's |BoM|, and the components listed on the |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:53 -msgid "To configure a product for the *Dropship Subcontractor on Order* route, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:57 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:59 -msgid "Select the :guilabel:`Purchase` tab, and add the product's subcontractor as a vendor by clicking :guilabel:`Add a line`, selecting the subcontractor in the :guilabel:`Vendor` drop-down menu, and entering a price in the :guilabel:`Price` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:61 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:71 -msgid "Then, click on the :guilabel:`Inventory` tab to configure a route that determines what happens to the finished product, once it has been manufactured by the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:64 -msgid "If the finished product is shipped back to the contracting company, make sure that the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a |SO|, unless there is enough stock on-hand to fulfill the |SO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:69 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:79 -msgid "If the finished product is shipped directly to the customer by the subcontractor, make sure that only the :guilabel:`Dropship` route is selected." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:73 -msgid "Configure bill of materials" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:75 -msgid "To configure a |BoM| for the *Dropship Subcontractor on Order* route, click the :guilabel:`Bill of Materials` smart button on the product's page, and select the |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:92 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:102 -msgid "Finally, make sure that all necessary components are specified on the :guilabel:`Components` tab. To add a new component, click :guilabel:`Add a line`, select the component in the :guilabel:`Component` drop-down menu, and specify the required quantity in the :guilabel:`Quantity` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:97 -msgid "Configure Components" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:99 -msgid "To configure components for the *Dropship Subcontractor on Order* route, navigate to each component from the |BoM| by selecting the component's name in the :guilabel:`Components` tab, and clicking the :guilabel:`➡️ (right arrow)` button to the right of the name." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:103 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:113 -msgid "Alternatively, navigate to each component by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the component." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:106 -msgid "On the component product form, select the :guilabel:`Purchase` tab, and add a vendor by clicking :guilabel:`Add a line`, selecting the vendor in the :guilabel:`Vendor` field, and adding the price they sell the product for in the :guilabel:`Price` field. This is the vendor that sends components to the subcontractor, once they are purchased." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:111 -msgid "Then, click on the :guilabel:`Inventory` tab and select the :guilabel:`Dropship Subcontractor on Order` route in the :guilabel:`Routes` section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:114 -msgid "Repeat the process for every component that must be dropshipped to the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:119 -msgid "Dropship subcontractor on order workflow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:121 -msgid "The dropship subcontractor on order workflow consists of up to six steps:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:123 -msgid "Create a sales order (SO) for the subcontracted product; doing so creates a *subcontractor* |PO| to purchase the product from the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:125 -msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a request for quotation (RfQ) to purchase the components from the vendor, as well as a receipt order or a dropship order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:128 -msgid "Confirm the |RfQ| to turn it into a second |PO| (*vendor* |PO|); doing so creates a *Dropship Subcontractor* order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:130 -msgid "Process the *Dropship Subcontractor* order once the vendor has sent the components to the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:132 -msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company **OR** process the dropship order to ship the product directly to the end customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:135 -msgid "If the workflow was started by creating an |SO|, and the finished product is not dropshipped to the end customer, process the delivery order once the product has been shipped to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:141 -msgid "If the reason is to fulfill a specific customer order, the process starts with creating an SO, and ends with delivering the product to the customer, or having the subcontractor dropship it to them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:144 -msgid "If the reason is to increase quantity of stock on-hand, the process starts with creating a PO, and ends with receiving the product into inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:148 -msgid "Create an SO" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:157 -msgid "Select the customer in the :guilabel:`Customer` drop-down menu. Then, click :guilabel:`Add a product` on the :guilabel:`Order Lines` tab, select the product in the :guilabel:`Product` drop-down menu, and enter a quantity in the :guilabel:`Quantity` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:161 -msgid "Click :guilabel:`Confirm` to confirm the |SO|, at which point a :guilabel:`Purchase` smart button appears at the top of the page. This is the *subcontractor* |PO|, or the |PO| created to purchase the subcontracted product from the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:166 -msgid "An |SO| for the product only creates a *subcontractor* |PO| if the *Replenish on Order (MTO)* route is enabled on the product's page, **and** there is no stock of the product on-hand." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:169 -msgid "If there is stock on-hand, confirming an |SO| for the product will instead create a delivery order, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:172 -msgid "This is not the case for subcontracted products that are dropshipped to the end customer. In that case, a *subcontractor* |PO| is **always** created, even if there is stock on-hand." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:176 -msgid "Process subcontractor PO" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:178 -msgid "If a *subcontractor* |PO| was not created in the previous step, do so now by navigating to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and clicking :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:181 -msgid "Begin filling out the |PO| by selecting a subcontractor from the :guilabel:`Vendor` drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:183 -msgid "In the :guilabel:`Products` tab, click :guilabel:`Add a product` to create a new product line. Select a product produced by the subcontractor in the :guilabel:`Product` field, and enter the quantity in the :guilabel:`Quantity` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:187 -msgid "Finally, click :guilabel:`Confirm Order` to confirm the *subcontractor* |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:189 -msgid "When a |PO| is confirmed for a product that requires dropshipping components to a subcontractor, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:-1 -msgid "A subcontractor PO for a *Dropship Subcontractor on Order* product, with a Receipt smart\n" -"button at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:198 -msgid "In addition, an |RfQ| is created for the components that are purchased from the vendor and sent to the subcontractor. However, the |RfQ| **IS NOT** automatically linked to the *subcontractor* |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:201 -msgid "Once the |RfQ| is confirmed and becomes a *vendor* |PO|, a *Dropship Subcontractor* order is created. This order is linked to both the *vendor* |PO| and the *subcontractor* |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:205 -msgid "Confirm vendor RfQ" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:207 -msgid "To access the |RfQ| created by confirming the *subcontractor* |PO|, navigate to :menuselection:`Purchase app --> Orders --> Requests for Quotation`. Select the |RfQ| that lists the correct vendor in the :guilabel:`Vendor` field, and the reference number of the receipt that was created after confirming *subcontractor* |PO|, in the :guilabel:`Source Document` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:212 -msgid "On the |RfQ|, the :guilabel:`Deliver To` field reads :guilabel:`Dropship Subcontractor`, and the :guilabel:`Dropship Address` field shows the name of the subcontractor to whom components are being dropshipped." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:216 -msgid "Click :guilabel:`Confirm Order` to turn the |RfQ| into a *vendor* |PO|, and confirm the purchase of components from the vendor. After doing so, a :guilabel:`Dropship` smart button appears at the top of the *vendor* |PO|, and a :guilabel:`Resupply` smart button appears at the top of the *subcontractor* |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:-1 -msgid "A vendor PO for the components of a *Dropship Subcontractor on Order* product, with a\n" -"Dropship smart button at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:227 -msgid "Process Dropship Subcontractor order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:229 -msgid "Once the components have been delivered to the subcontractor, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the *vendor* |PO| or the *subcontractor* |PO|. Then, click the :guilabel:`Dropship` smart button or the :guilabel:`Resupply` smart button, respectively." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:233 -msgid "Clicking either button opens the *Dropship Subcontractor* order. Click the :guilabel:`Validate` button at the top of the order to confirm that the subcontractor has received the components." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:239 -msgid "Once the subcontractor has manufactured the finished product, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the *subcontractor* |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:242 -msgid "If the subcontracted product should be received into inventory, once the product arrives, click the :guilabel:`Receive Products` button at the top of the *subcontractor* |PO| to open the receipt. Then, click :guilabel:`Validate` at the top of the receipt to register the product into inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:246 -msgid "Alternatively, select the :guilabel:`Receipt` smart button at the top of the *subcontractor* |PO|, and click :guilabel:`Validate` at the top of the receipt." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:249 -msgid "If the subcontracted product should be dropshipped, select the :guilabel:`Dropship` button at the top of the page to open the dropship order, and click :guilabel:`Validate` once the subcontractor has sent the product to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:260 -msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` to confirm that the product has been shipped to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:3 -msgid "Resupply subcontractor" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:13 -msgid "In Odoo, the *Resupply Subcontractor on Order* route is used to deliver the necessary components for a subcontracted product to the subcontractor, each time a purchase order (PO) for that product is confirmed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:17 -msgid "The subcontractor then uses the components to manufacture the desired product, before shipping it back to the contracting company, or dropshipping it to the end customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:21 -msgid "It is necessary to understand the differences between the *Resupply Subcontractor on Order* and the *Dropship Subcontractor on Order* routes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:24 -msgid "While both routes are used to supply a subcontractor with the components required for manufacturing a product, they differ in how the components are sourced." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:27 -msgid "When using *Resupply Subcontractor on Order*, components are shipped from the warehouse of the contracting company." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:30 -msgid "When using *Dropship Subcontractor on Order*, components are purchased from a vendor and shipped directly to the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:33 -msgid "The choice of which route to use depends upon the specific requirements of the subcontracting company and their subcontractors." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:36 -msgid "See the :doc:`subcontracting_dropship` documentation for a full overview of the *Dropship Subcontractor on Order* route." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:42 -msgid "To use the *Resupply Subcontractor on Order* route, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and enable the checkbox next to :guilabel:`Subcontracting`, under the :guilabel:`Operations` heading." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:46 -msgid "Once the *Subcontracting* setting is enabled, it is also necessary to properly configure the subcontracted product, the product's bill of materials (BoM), and the components listed on the |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:55 -msgid "To configure a product for the *Resupply Subcontractor on Order* route, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:64 -msgid "The value entered in the :guilabel:`Price` field on the :guilabel:`Purchase` tab of the of the subcontracted product's page is the amount paid to the subcontractor for the manufacturing of the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:68 -msgid "This does not represent the total cost of the product, which includes other elements, like the cost of the product's components." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:74 -msgid "If the finished product is shipped back to the contracting company, make sure that the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a sales order (SO), unless there is enough stock on-hand to fulfill the |SO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:85 -msgid "To configure a |BoM| for the *Resupply Subcontractor on Order* route, click the :guilabel:`Bill of Materials` smart button on the product's page, and select the |BoM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:107 -msgid "Configure components" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:109 -msgid "To configure components for the *Resupply Subcontractor on Order* route, navigate to each component from the |BoM| by selecting the component's name in the :guilabel:`Components` tab, and clicking the :guilabel:`➡️ (right arrow)` button to the right of the name." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:116 -msgid "On the component product form, click on the :guilabel:`Inventory` tab and select the :guilabel:`Resupply Subcontractor on Order` route in the :guilabel:`Routes` section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:119 -msgid "Repeat the process for every component that must be sent to the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:122 -msgid "Resupply subcontractor on order workflow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:124 -msgid "The resupply subcontractor on order workflow consists of up to five steps:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:126 -msgid "Create an |SO| for the subcontracted product; doing so creates a |PO| to purchase the product from the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:128 -msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a *Resupply Subcontractor* order, as well as a receipt order or a dropship order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:130 -msgid "Process the *Resupply Subcontractor* order once components for the subcontracted product have been sent to the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:132 -msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company **OR** process the dropship order to ship the product directly to the customer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:149 -msgid "While the *Resupply Subcontractor on Order* route can be used to automatically resupply a subcontractor upon confirmation of a |PO|, it is also possible to create a resupply order manually. This workflow is useful when it is necessary to resupply the subcontractor without creating a |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:154 -msgid "To resupply a subcontractor manually, navigate to the :menuselection:`Inventory` app, and click on the :guilabel:`Resupply Subcontractor` card. Create a new *Resupply Subcontractor* order by clicking :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:158 -msgid "In the :guilabel:`Delivery Address` field, select the subcontractor to whom the components should be sent." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:161 -msgid "Then, add each component to the :guilabel:`Operations` tab by clicking :guilabel:`Add a line`, selecting the component in the :guilabel:`Product` drop-down field, and specifying a quantity in the :guilabel:`Demand` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:165 -msgid "Finally, click :guilabel:`Mark as Todo` to register the order. Once the components have been sent to the subcontractor, click :guilabel:`Validate` to confirm that the order has been sent." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:187 -msgid "An |SO| for the product only creates a |PO| if the *Replenish on Order (MTO)* route is enabled on the product's page, **and** there is not enough stock of the product on-hand to fulfill the |SO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:190 -msgid "If there is enough stock on-hand, confirming an |SO| for the product instead creates a delivery order, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:199 -msgid "If a |PO| was created in the previous step, navigate to :guilabel:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|. Then, click :guilabel:`Confirm Order` to confirm it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:210 -msgid "When a |PO| is confirmed for a product that requires resupplying a subcontractor with components, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:214 -msgid "In addition, a *Resupply Subcontractor* order is created to ship the required components to the subcontractor. This order can also be accessed from the |PO|, by clicking the :guilabel:`Resupply` smart button at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:223 -msgid "A PO for a *Resupply Subcontractor on Order* product, with Resupply and Receipt smart\n" -"buttons at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:223 -msgid "A PO for a *Resupply Subcontractor on Order* product, with Resupply and Receipt smart buttons at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:227 -msgid "Process Resupply Subcontractor order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:229 -msgid "Once the subcontracted product's components have been sent to the subcontractor, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:232 -msgid "Click the :guilabel:`Resupply` smart button at the top of the screen to open the *Resupply Subcontractor* order, and click :guilabel:`Validate` to confirm that the components have been sent to the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:236 -msgid "Alternatively, navigate to the :menuselection:`Inventory` app, click the :guilabel:`# To Process` button on the :guilabel:`Resupply Subcontractor` card, and select the *Resupply Subcontractor* order. Then, click :guilabel:`Validate` to confirm that the components have been sent to the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:244 -msgid "Once the subcontractor has finished manufacturing the product, they either ship it to the contracting company, or dropship it to the end customer, depending on how the product was :ref:`configured `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:272 -msgid "If the subcontracting workflow was started by a customer |SO|, and the finished product was **NOT** dropshipped to the customer, but rather delivered to the contracting company, it is necessary to ship the product to the customer, and process the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:276 -msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` on the order to confirm that the product has been shipped to the customer." -msgstr "" - #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:3 msgid "Unbuild orders" msgstr "" @@ -16991,7 +19128,7 @@ msgid "Engineering change orders" msgstr "" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:12 -msgid "Utilize *engineering change orders* (*ECOs*) to track, implement, and revert change versions made to products, and :ref:`bills of materials `." +msgid "Utilize *engineering change orders* (*ECOs*) to track, implement, and revert change versions made to products, and :doc:`bills of materials <../../manufacturing/basic_setup/bill_configuration>`." msgstr "" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:15 @@ -17922,6 +20059,220 @@ msgstr "" msgid "You can insert your pivot table's data directly in the Spreadsheet app or export it as an Excel file." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:3 +msgid "Procurement expenses report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:12 +msgid "With the *Purchase* application, users can monitor procurement expenses over time. This report helps companies track and analyze spending, identify cost-saving opportunities, and ensure efficient budget management." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:17 +msgid "Create procurement expenses report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:19 +msgid "To create a |per|, first navigate to :menuselection:`Purchase app --> Reporting --> Purchase` to open the :guilabel:`Purchase Analysis` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:22 +msgid "By default, the dashboard displays a line chart overview of the :guilabel:`Untaxed Total` of :guilabel:`Purchase Orders` (POs) with a :guilabel:`Confirmation Date` for the current month, or of Requests for Quotation (RFQs) with a status of *Draft*, *Sent*, or *Cancelled*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:27 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:25 +msgid "Add filters and groups" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:29 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:27 +msgid "On the top-right, click the :icon:`oi-view-pivot` :guilabel:`(pivot)` icon to switch to pivot view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:32 +msgid "While the |per| can also be :ref:`viewed ` as a :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)`, the pivot view provides the most detailed view of the data, and is the recommended starting point." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:37 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:29 +msgid "Remove any default filters from the :guilabel:`Search...` bar. Then, click the |caret| to open the drop-down menu that contains the :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:42 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:34 +msgid "Unless otherwise specified, the report displays data from both |RFQs| and |POs|. This can be changed by selecting either :guilabel:`Requests for Quotation` or :guilabel:`Purchase Orders` under the :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:46 +msgid "Under the :guilabel:`Filters` column, select a time frame to use for comparison. The report can be filtered by either :guilabel:`Order Date` or :guilabel:`Confirmation Date`. Choose one from the list, and click the |caret| to specify the date range, either by month, quarter, or year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:50 +msgid "Next, under the :guilabel:`Group by` column, select :guilabel:`Vendor`. Then, select :guilabel:`Product Category`, which is also located in the :guilabel:`Group By` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:54 +msgid "The selections under the :guilabel:`Group By` heading can be altered, depending on the needs of the individual company. For example, selecting :guilabel:`Product`, instead of :guilabel:`Product Category`, provides a more in depth look at the performance of specific items, in place of an entire category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:59 +msgid "Next, make a selection under the :guilabel:`Comparison` heading that appears. These options are only available after the date range is selected under the :guilabel:`Filters` column, and vary based on that range. :guilabel:`Previous Period` adds a comparison to the previous period, such as the last month or quarter. :guilabel:`Previous Year` compares the same time period from the previous year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:65 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:60 +msgid "While multiple time-based filters can be added at once, only one comparison can be selected at a time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:73 +msgid "The drop-down menu of filters, group by and comparison options for the procurement expenses\n" +"report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:73 +msgid "The filter for Q2, comparison for **Previous Period**, and group-by for **Vendor** and **Product Category** were selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:77 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:68 +msgid "Add measures" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:79 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:70 +msgid "After selecting the :guilabel:`Filters`, :guilabel:`Group by`, and :guilabel:`Comparison` settings, click out of the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:82 +msgid "By default, the report displays data with the following measures: :guilabel:`Order`, :guilabel:`Total`, :guilabel:`Untaxed Total`, and :guilabel:`Count`. Click :guilabel:`Measures` at the top-left to open the drop-down list of available measures." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:86 +msgid "Click the following specific measures to include additional columns for the procurement expenses report:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:89 +msgid ":guilabel:`Total` and :guilabel:`Untaxed Total`: can include one or both measures. These are included for overall spending analysis." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:91 +msgid ":guilabel:`Average Cost`: included to evaluate cost efficiency." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:92 +msgid ":guilabel:`Days to Confirm` and :guilabel:`Days to Receive`: used to assess supplier performance." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:93 +msgid ":guilabel:`Qty Ordered` and :guilabel:`Qty Received`: used to understand order efficiency." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:94 +msgid ":guilabel:`Qty Billed` and :guilabel:`Qty to be Billed`: used to track order accuracy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:97 +msgid "Additional measures can be included in the report, if desired, to provide additional insights. For example, :guilabel:`Gross Weight` and :guilabel:`Volume` may be included for further logistics and management analysis." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:101 +msgid "After selecting all necessary measures, click out of the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:106 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:85 +msgid "View results" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:108 +msgid "After all of the filters and measures have been selected, the report generates in the selected view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:-1 +msgid "A sample version of the procurement expenses report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:114 +msgid "Click :guilabel:`Insert in Spreadsheet` to add the pivot view into an editable spreadsheet format within the *Documents* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:118 +msgid "The :guilabel:`Insert in Spreadsheet` option is **only** available if the *Documents Spreadsheet* module is installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:122 +msgid "The |per| is also available in graph view. Click the :icon:`fa-area-chart` :guilabel:`(area chart)` icon to change to graph view. Click the corresponding icon at the top of the report to switch to a :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/procurement_expenses_report.rst:128 +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:107 +msgid "To save this report as a *favorite*, see :ref:`search/favorites`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:3 +msgid "Vendor costs report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:10 +msgid "With the *Purchase* application, users can track the fluctuation of vendor costs over time. This allows users to identify the most expensive vendors, and track seasonal changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:14 +msgid "Create vendor costs reports" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:16 +msgid "To create a vendor costs report, first navigate to :menuselection:`Purchase app --> Reporting --> Purchase` to open the :guilabel:`Purchase Analysis` dashboard. By default, the dashboard displays a line chart overview of the :guilabel:`Untaxed Total` of POs (Purchase Orders) with a :guilabel:`Confirmation Date` for the current month, or of RFQs (Requests for Quotation) with a status of *Draft*, *Sent, or *Cancelled*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:38 +msgid "Under the :guilabel:`Filters` column, select a date range to use for comparison. The report can be filtered by either :guilabel:`Order Date` or :guilabel:`Confirmation Date`. Choose one from the list, and click the |caret| to specify the date range, either by month, quarter, or year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:42 +msgid "Next, under the :guilabel:`Group by` column, select :guilabel:`Vendor`. Then, select :guilabel:`Product`, which is also located in the :guilabel:`Group By` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:46 +msgid "Selecting :guilabel:`Product` is **not** required for this report. However, it is recommended, as it provides additional insight into the performance of individual vendors. Additional selections can be made under the :guilabel:`Group by` heading as well, including :guilabel:`Product Category`, :guilabel:`Status`, and :guilabel:`Purchase Representative`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:51 +msgid "To ensure the report is generated correctly, make sure that :guilabel:`Vendor` is the **first** selection made under the :guilabel:`Group By` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:54 +msgid "Next, make a selection under the :guilabel:`Comparison` heading. These options are only available after the date range is selected under the :guilabel:`Filters` column, and vary based on that range. :guilabel:`Previous Period` adds a comparison to the previous period, such as the last month or quarter. :guilabel:`Previous Year` compares the same time period from the previous year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:-1 +msgid "The drop-down menu of filters, group by and comparison options for the vendor costs report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:73 +msgid "By default, the report displays with the following measures: :guilabel:`Order`, :guilabel:`Total`, :guilabel:`Untaxed Total`, and :guilabel:`Count`. Click :guilabel:`Measures` at the top-left to open the drop-down list of available measures. Click :guilabel:`Average Cost` to add it to the report. Select any additional measures to add to the report, or click on any of the already selected measures to remove them, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:80 +msgid "It is recommended to run the report with at least :guilabel:`Average Cost`, :guilabel:`Total`, or :guilabel:`Untaxed Total` selected from the :guilabel:`Measures` list. Additional measures, such as :guilabel:`Days to Receive`, can be added to provide additional insights." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:87 +msgid "After all of the :ref:`filters and measures have been selected `, the report generates in the pivot view. Click :guilabel:`Insert in Spreadsheet` to add the pivot view into an editable spreadsheet format within the *Documents* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:93 +msgid "The :guilabel:`Insert in Spreadsheet` option is only available if the *Documents Spreadsheet* module is installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:-1 +msgid "A sample of a vendor costs report with the measures set as total and average costs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/vendor_costs_report.rst:101 +msgid "The vendor costs report is also available in *graph* view. Click the :icon:`fa-area-chart` :guilabel:`(area chart)` icon to change to graph view. Click the corresponding icon at the top of the report to switch to a :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)`." +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals.rst:5 msgid "Manage deals" msgstr "" @@ -18698,73 +21049,69 @@ msgid "*3-way matching* ensures vendor bills are only paid once some (or all) of msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:51 -msgid "To activate it, go to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, check the box next to :guilabel:`3-way matching: purchases, receptions, and bills`, and click :guilabel:`Save` to save changes." +msgid "To activate it, go to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, tick the checkbox next to :guilabel:`3-way matching`, and click :guilabel:`Save` to save changes." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:56 msgid ":guilabel:`3-way matching` is **only** intended to work with the :guilabel:`Bill Control` policy set to :guilabel:`Received quantities`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 -msgid "Activated three-way matching feature in purchase settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:64 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:60 msgid "Create and manage vendor bills on receipts" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:66 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:62 msgid "When products are received into a company's warehouse, receipts are created. Once the company processes the received quantities, they can choose to create a vendor bill directly from the warehouse receipt form. Depending on the bill control policy chosen in the settings, vendor bill creation is completed at different steps of the procurement process." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:72 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:68 msgid "With the bill control policy set to ordered quantities" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:74 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:70 msgid "To create and manage vendor bills on receipts using the *ordered quantities* bill control policy, first go to :menuselection:`Purchase app --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Ordered quantities` under :guilabel:`Bill Control`. Then, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:79 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:75 msgid "Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` to create a new request for quotation (RFQ). Doing so reveals a blank :abbr:`RFQ (request for quotation)` detail form." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:78 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:140 +msgid "On the blank detail form, add a vendor to the :abbr:`RFQ (request for quotation)` in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:82 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:144 -msgid "On the blank detail form, add a vendor to the :abbr:`RFQ (request for quotation)` in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:86 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 msgid "Then, confirm the :abbr:`RFQ (request for quotation)` by clicking the :guilabel:`Confirm Order` button above the detail form. Doing so turns the :abbr:`RFQ (request for quotation)` into a purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:90 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:86 msgid "Then, click the :guilabel:`Create Bill` button to create a vendor bill for the purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:92 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:88 msgid "Clicking the :guilabel:`Create Bill` button reveals the :guilabel:`Draft Bill` page for the purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:95 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:91 msgid "On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button to modify the bill, and add a bill date in the :guilabel:`Bill Date` field. If needed, add additional products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line` in the :guilabel:`Invoice Lines` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:99 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:95 msgid "Next, confirm the bill by clicking the :guilabel:`Confirm` button on the :guilabel:`Draft Bill` page." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:103 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:99 msgid "Since the bill control policy is set to *ordered quantities*, the draft bill can be confirmed as soon as it is created, before any products have been received." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:106 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:179 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:102 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:175 msgid "On the new :guilabel:`Vendor Bill`, add a :guilabel:`Bill Reference` number, which can be used to match the bill with additional documents (such as the :abbr:`PO (purchase order)`). Then, click :menuselection:`Confirm --> Register Payment`. Doing so causes a pop-up to appear, wherein a payment :guilabel:`Journal` can be chosen; a :guilabel:`Payment Method` selected; and a :guilabel:`Recipient Bank Account` can be selected from a drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:112 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:108 msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. Once ready, click :guilabel:`Create Payment` to finish creating the :guilabel:`Vendor Bill`. Doing so causes a green :guilabel:`In Payment` banner to display on the :abbr:`RFQ (request for quotation)` form." msgstr "" @@ -18772,87 +21119,87 @@ msgstr "" msgid "Vendor bill form for ordered quantities control policy." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:122 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:118 msgid "Each vendor bill provides the option to either :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note`. A *credit note* is typically issued when a vendor or supplier of goods get some quantity of products back from the customer to whom they were sold, while *debit notes* are reserved for goods returned from the customer/buyer to the vendor or supplier." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:128 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:124 msgid "With the bill control policy set to received quantities" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:131 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:127 msgid "If the creation of a vendor bill is attempted without receiving any quantities of a product (while using the *received quantities* bill control policy), an error message appears, and settings must be changed before proceeding." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:135 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:131 msgid "To create and manage vendor bills on receipts using the *received quantities* bill control policy, first go to :menuselection:`Purchase app --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Received quantities` under :guilabel:`Bill Control`. Then, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:140 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:136 msgid "Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` to create a new :abbr:`RFQ (request for quotation)`. Doing so reveals a blank :abbr:`RFQ (request for quotation)` detail form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:152 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 msgid "Finally, click the :guilabel:`Create Bill` button to create a bill for the purchase order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:155 -msgid "Clicking :guilabel:`Create Bill` before any products have been received will cause a :guilabel:`User Error` pop-up to appear. The :guilabel:`Purchase Order` requires the receipt of at least partial quantity of the items included on the order to create a vendor bill." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:151 +msgid "Clicking :guilabel:`Create Bill` before any products have been received will cause a :guilabel:`User Error` pop-up message to appear. The :guilabel:`Purchase Order` requires the receipt of at least partial quantity of the items included on the order to create a vendor bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 msgid "User error pop-up for received quantities control policy." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:163 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:159 msgid "Next, click the :guilabel:`Receipt` smart button to view the warehouse receipt form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:165 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:161 msgid "On the warehouse receipt form, click :menuselection:`Validate --> Apply` to mark the :guilabel:`Done` quantities. Then, navigate back to the :menuselection:`Purchase Order` (via the breadcrumbs), and click the :guilabel:`Create Bill` button on the purchase order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:169 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:165 msgid "Doing so reveals the :guilabel:`Draft Bill` for the purchase order. On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button, and add a :guilabel:`Bill Date`. If needed, add additional products to the :guilabel:`Product` lines by clicking :guilabel:`Add a line`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:173 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:169 msgid "Next, click the :guilabel:`Confirm` button to confirm the :guilabel:`Draft Bill`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:176 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:172 msgid "Since the bill control policy is set to *received quantities*, the draft bill can **only** be confirmed when at least some of the quantities are received." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:185 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:181 msgid "Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and :guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. Once ready, click :guilabel:`Create Payment` to finish creating the vendor bill. Doing so causes a green **In Payment** banner to display on the :abbr:`RFQ (request for quotation)` form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:191 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:187 msgid "Create and manage vendor bills in Accounting" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:193 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:189 msgid "Vendor bills can also be created directly from the *Accounting* app, **without** having to create a purchase order first. To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`, and click :guilabel:`Create`. Doing so reveals a blank vendor bill detail form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:197 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:193 msgid "On this blank vendor bill detail form, add a vendor in the :guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines (under the :guilabel:`Invoice Lines` tab), by clicking :guilabel:`Add a line`. Then, add a bill date in the :guilabel:`Bill Date` field, and any other necessary information. Finally, click :guilabel:`Confirm` to confirm the bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:202 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:198 msgid "From here, click the :guilabel:`Journal Items` tab to view (or change) the :guilabel:`Account` journals that were populated based on the configuration on the corresponding :guilabel:`Vendor` and :guilabel:`Product` forms." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:206 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:202 msgid "Then, click :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note` to add credit or debit notes to the bill. Or, add a :guilabel:`Bill Reference` number (while in :guilabel:`Edit` mode)." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:209 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:205 msgid "Then, when ready, click :menuselection:`Register Payment --> Create Payment` to complete the :guilabel:`Vendor Bill`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:213 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:209 msgid "To tie the draft bill to an existing purchase order, click the drop-down menu next to :guilabel:`Auto-Complete`, and select a :abbr:`PO (purchase order)` from the menu. The bill will auto-populate with the information from the :abbr:`PO (purchase order)`." msgstr "" @@ -18860,40 +21207,40 @@ msgstr "" msgid "Auto-complete drop-down list on draft vendor bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:222 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:218 msgid "Batch billing" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:224 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:220 msgid "Vendor bills can be processed and managed in batches in the *Accounting* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:226 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:222 msgid "To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`. Then, click the :guilabel:`checkbox` at the top left of the page, beside the :guilabel:`Number` column, under the :guilabel:`Create` button. This selects all existing vendor bills with a :guilabel:`Posted` or :guilabel:`Draft` :guilabel:`Status`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:231 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:227 msgid "From here, click the :guilabel:`Action` gear icon to export, delete, or send & print the bills; click the :guilabel:`Print` icon to print the invoices or bills; or click :guilabel:`Register Payment` to create and process payments for multiple vendor bills at once." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:235 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:231 msgid "When :guilabel:`Register Payment` is selected, a pop-up appears. In this pop-up window, select the appropriate journal in the :guilabel:`Journal` field, choose a payment date in the :guilabel:`Payment Date` field, and choose a :guilabel:`Payment Method`. There is also the option to :guilabel:`Group Payments` on this pop-up, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:240 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:236 msgid "When ready, click the :guilabel:`Create Payment` button, which creates a list of journal entries on a separate page. This list of journal entries are all tied to their appropriate vendor bills." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:-1 -msgid "Batch billing register payment pop-up." +msgid "Batch billing register payment pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:248 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:244 msgid "The :guilabel:`Register Payment` option for vendor bills in batches will only work for journal entries whose :guilabel:`Status` is set to :guilabel:`Posted`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:252 -msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/control_bills`" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:248 +msgid ":doc:`control_bills`" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products.rst:5 @@ -19153,11 +21500,11 @@ msgid "Go to :menuselection:`Inventory app --> Products --> Products`, select th msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:3 -msgid "Purchase in different units of measure than sales" +msgid "Purchase units of measure" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:5 -msgid "When you purchase a product, it may happen that your vendor uses a different unit of measure than you do when you sell it. This can cause confusion between sales and purchase representatives. It is also time-consuming to convert measures manually every time. With Odoo, you can configure your product once and let Odoo handle the conversion." +msgid "When you purchase a product, it may happen that your vendor uses a different unit of measure than when it is sold. This can cause confusion between sales and purchase representatives. It is also time-consuming to convert measures manually every time. With Odoo, you can configure your product once and let Odoo handle the conversion." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:10 @@ -19233,14 +21580,14 @@ msgid "Create a new units of measure category in Odoo Purchase" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:73 -msgid "The next step is to create the two units of measures. To do so, go to :menuselection:`Configuration --> Units of Measure`." +msgid "The next step is to create the two units of measures. To do so, click into the :guilabel:`Unit of Measure Category` field and enter a name for the category. Then, under the :guilabel:`Units of Measure` tab, click :guilabel:`Add a line`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:76 -msgid "First, create the unit of measure used as the reference point for converting to other units of measure inside the category by clicking on *Create*. Name the unit and select the units of measure category you just created. For the *Type*, select *Reference Unit of Measure for this category type*. Enter the *Rounding Precision* you would like to use. The quantity computed by Odoo is always a multiple of this value." +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:77 +msgid "First, create the unit of measure used as the reference point for converting to other units of measure inside the category. Name the unit, and select the units of measure category you just created. For the *Type*, select *Reference Unit of Measure for this category type*. Enter the *Rounding Precision* you would like to use. The quantity computed by Odoo is always a multiple of this value." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:82 +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:83 msgid "In the example, as you cannot purchase less than 1 roll and won't use fractions of a roll as a unit of measure, you can enter 1." msgstr "" @@ -19248,31 +21595,27 @@ msgstr "" msgid "Create a new reference unit of measure in Odoo Purchase" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:89 +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:90 msgid "If you use a *Rounding Precision* inferior to 0.01, a warning message might appear stating that it is higher than the *Decimal Accuracy* and that it might cause inconsistencies. If you wish to use a *Rounding Precision* lower than 0.01, first activate the :ref:`developer mode `, then go to :menuselection:`Settings --> Technical --> Database Structure --> Decimal Accuracy`, select *Product Unit of Measure* and edit *Digits* accordingly. For example, if you want to use a rounding precision of 0.00001, set *Digits* to 5." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:96 +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:97 msgid "Next, create a second unit of measure, name it, and select the same units of measure category as your reference unit. As *Type*, select *Smaller* or *Bigger than the reference Unit of Measure*, depending on your situation." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:100 +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:101 msgid "As the curtain roll equals to 100 square meters, you should select *Smaller*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:102 +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:103 msgid "Next, you need to enter the *Ratio* between your reference unit and the second one. If the second unit is smaller, the *Ratio* should be greater than 1. If the second unit is larger, the ratio should be smaller than 1." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:106 +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:107 msgid "For your curtain roll, the ratio should be set to 100." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:-1 -msgid "Create a second unit of measure in Odoo Purchase" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:112 +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:109 msgid "You can now configure your product just as you would using Odoo's standard units of measure." msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 5d3457116..cc93a5e48 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -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 \n" "Language-Team: LANGUAGE \n" @@ -32,11 +32,11 @@ msgstr "" msgid "`Odoo Tutorial: Email Marketing `_" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:35 +#: ../../content/applications/marketing/email_marketing.rst:38 msgid "Email marketing dashboard" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:37 +#: ../../content/applications/marketing/email_marketing.rst:40 msgid "After installing the application, click the :menuselection:`Email Marketing` app icon from the main Odoo dashboard. Doing so reveals the main :guilabel:`Mailings` dashboard in the default list view." msgstr "" @@ -44,96 +44,96 @@ msgstr "" msgid "View of the main dashboard of the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:44 +#: ../../content/applications/marketing/email_marketing.rst:47 msgid "In the search bar, the default filter of :guilabel:`My Mailings` is present to show all the mailings related to the current user. To remove that filter, click the :guilabel:`✖️ (remove)` icon next to the filter in the search bar. Doing so reveals all the mailings in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:48 +#: ../../content/applications/marketing/email_marketing.rst:51 msgid "The information on the :guilabel:`Mailings` dashboard has four different view options, located in the upper-right corner as individual icons." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:51 +#: ../../content/applications/marketing/email_marketing.rst:54 msgid "The view options, from left-to-right, are:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:53 +#: ../../content/applications/marketing/email_marketing.rst:56 msgid ":ref:`List ` (default view)" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:54 +#: ../../content/applications/marketing/email_marketing.rst:57 msgid ":ref:`Kanban `" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:55 +#: ../../content/applications/marketing/email_marketing.rst:58 msgid ":ref:`Calendar `" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:56 +#: ../../content/applications/marketing/email_marketing.rst:59 msgid ":ref:`Graph `" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:61 -#: ../../content/applications/marketing/email_marketing.rst:733 +#: ../../content/applications/marketing/email_marketing.rst:64 +#: ../../content/applications/marketing/email_marketing.rst:736 #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:420 #: ../../content/applications/marketing/surveys.rst:145 msgid "List view" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:63 +#: ../../content/applications/marketing/email_marketing.rst:66 msgid "The list view, represented by the :guilabel:`☰ (horizontal lines)` icon in the upper-right corner, is the default view of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:66 +#: ../../content/applications/marketing/email_marketing.rst:69 msgid "While in list view, there are columns dedicated to different aspects of information related to the listed emails. Those columns are as follows:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:69 +#: ../../content/applications/marketing/email_marketing.rst:72 msgid ":guilabel:`Date`: the date the email was sent." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:70 +#: ../../content/applications/marketing/email_marketing.rst:73 msgid ":guilabel:`Subject`: the subject of the email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:71 +#: ../../content/applications/marketing/email_marketing.rst:74 msgid ":guilabel:`Responsible`: the user who created the email, or the user who has been assigned to the email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:73 +#: ../../content/applications/marketing/email_marketing.rst:76 msgid ":guilabel:`Sent`: how many times the email has been sent." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:74 +#: ../../content/applications/marketing/email_marketing.rst:77 msgid ":guilabel:`Delivered (%)`: percentage of sent emails that have been successfully delivered." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:75 +#: ../../content/applications/marketing/email_marketing.rst:78 msgid ":guilabel:`Opened (%)`: percentage of sent emails that have been opened by the recipients." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:76 +#: ../../content/applications/marketing/email_marketing.rst:79 msgid ":guilabel:`Clicked (%)`: percentage of sent emails that have been clicked by the recipients." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:77 +#: ../../content/applications/marketing/email_marketing.rst:80 msgid ":guilabel:`Replied (%)`: percentage of sent emails that have been replied to by the recipients." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:78 +#: ../../content/applications/marketing/email_marketing.rst:81 msgid ":guilabel:`Status`: the status of the email (:guilabel:`Draft`, :guilabel:`In Queue`, or :guilabel:`Sent`)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:81 +#: ../../content/applications/marketing/email_marketing.rst:84 msgid "To add or remove columns, click the :guilabel:`Additional Options (two horizontal lines with dots)` icon, located to the far-right of the column titles in list view. Doing so reveals a drop-down menu of additional column options." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:88 -#: ../../content/applications/marketing/email_marketing.rst:706 +#: ../../content/applications/marketing/email_marketing.rst:91 +#: ../../content/applications/marketing/email_marketing.rst:709 #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:391 msgid "Kanban view" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:90 +#: ../../content/applications/marketing/email_marketing.rst:93 msgid "The Kanban view, represented by the :guilabel:`(inverted bar graph)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" @@ -141,39 +141,39 @@ msgstr "" msgid "Kanban view of the main dashboard of the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:97 +#: ../../content/applications/marketing/email_marketing.rst:100 msgid "While in Kanban view, the email information is displayed in the various stages." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:99 +#: ../../content/applications/marketing/email_marketing.rst:102 msgid "The stages are: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, and :guilabel:`Sent`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:101 +#: ../../content/applications/marketing/email_marketing.rst:104 msgid ":guilabel:`Draft`: the email is still being written/created." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:102 +#: ../../content/applications/marketing/email_marketing.rst:105 msgid ":guilabel:`In Queue`: the email is scheduled to be sent at a later date." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:103 +#: ../../content/applications/marketing/email_marketing.rst:106 msgid ":guilabel:`Sending`: the email is currently being sent to its recipients." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:104 +#: ../../content/applications/marketing/email_marketing.rst:107 msgid ":guilabel:`Sent`: the email has already been sent to its recipients." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:106 +#: ../../content/applications/marketing/email_marketing.rst:109 msgid "In each stage, there are drag-and-drop cards representing the emails that have been created/sent, and the stage they are in represents the current status of that mailing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:109 +#: ../../content/applications/marketing/email_marketing.rst:112 msgid "Each card on the :guilabel:`Mailings` dashboard provides key information related to that specific email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:112 +#: ../../content/applications/marketing/email_marketing.rst:115 msgid "When the cursor hovers over the upper-right corner of an email campaign card, a :guilabel:`⋮ (three vertical dots)` icon appears. When clicked, a mini drop-down menu reveals the option to color-code the email, :guilabel:`Delete` the email, or :guilabel:`Archive` the message for potential future use." msgstr "" @@ -181,16 +181,16 @@ msgstr "" msgid "View of the three-dot drop-down menu on the Odoo Email Marketing dashboard." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:124 +#: ../../content/applications/marketing/email_marketing.rst:127 #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:404 msgid "Calendar view" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:126 +#: ../../content/applications/marketing/email_marketing.rst:129 msgid "The calendar view, represented by a :guilabel:`📆 (calendar)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:129 +#: ../../content/applications/marketing/email_marketing.rst:132 msgid "While in calendar view, a monthly calendar (by default), shows when the mailings have been sent or are scheduled to be sent." msgstr "" @@ -198,43 +198,43 @@ msgstr "" msgid "Calendar view of the mailings dashboard in the Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:136 +#: ../../content/applications/marketing/email_marketing.rst:139 msgid "The current date is represented by a :guilabel:`🔴 (red circle)` icon over the date on the calendar." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:138 +#: ../../content/applications/marketing/email_marketing.rst:141 msgid "To the right of the calendar, the options to filter the results by :guilabel:`Responsible` and/or :guilabel:`Status` are available, via checkboxes." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:142 +#: ../../content/applications/marketing/email_marketing.rst:145 msgid "To hide the right sidebar, click the :guilabel:`(panel-right)` icon, located above the sidebar." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:144 +#: ../../content/applications/marketing/email_marketing.rst:147 msgid "In the top-left corner, above the calendar, the option to change the time period being displayed is available via a drop-down menu, which shows :guilabel:`Month`, by default. When clicked, the drop-down menu that appears reveals the options: :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month` (default), :guilabel:`Year`, and :guilabel:`Show weekends` (selected by default)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:149 +#: ../../content/applications/marketing/email_marketing.rst:152 msgid "Clicking any of those options changes the calendar display to reflect that desired amount of time." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:151 +#: ../../content/applications/marketing/email_marketing.rst:154 msgid "Clicking either :guilabel:`⬅️ (left arrow)` icon or :guilabel:`➡️ (right arrow)` icon changes the calendar to a previous or future time, depending on what is clicked, based on the chosen amount of time being represented." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:155 +#: ../../content/applications/marketing/email_marketing.rst:158 msgid "To jump back to the current date, click the :guilabel:`Today` button." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:160 +#: ../../content/applications/marketing/email_marketing.rst:163 msgid "Graph view" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:162 +#: ../../content/applications/marketing/email_marketing.rst:165 msgid "The graph view, represented by a :guilabel:`(line graph)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:165 +#: ../../content/applications/marketing/email_marketing.rst:168 msgid "While in graph view, the status of the emails on the :guilabel:`Mailings` page is represented in a bar graph, but other graph view options can be implemented, if needed." msgstr "" @@ -242,35 +242,35 @@ msgstr "" msgid "How the Graph view appears in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:172 +#: ../../content/applications/marketing/email_marketing.rst:175 msgid "In the upper-left corner, above the graph, there is a :guilabel:`Measures` drop-down menu. When clicked, different filter options become available to further customize the graph views." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:175 +#: ../../content/applications/marketing/email_marketing.rst:178 msgid "Those :guilabel:`Measures` options are: :guilabel:`A/B Testing percentage` and :guilabel:`Count` (default)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:178 +#: ../../content/applications/marketing/email_marketing.rst:181 msgid "To the right of the :guilabel:`Measures` drop-down menu is an :guilabel:`Insert in Spreadsheet` button, if the *Documents* application is installed. When clicked, a pop-up window appears, in which the ability to add the graph to a spreadsheet or dashboard becomes available." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:182 +#: ../../content/applications/marketing/email_marketing.rst:185 msgid "Beside the :guilabel:`Measures` drop-down menu and :guilabel:`Insert in Spreadsheet` button are different graph view options. From left-to-right, those graph view options are: :guilabel:`(bar chart)` (default), :guilabel:`(line chart)`, and :guilabel:`(pie chart)`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:187 +#: ../../content/applications/marketing/email_marketing.rst:190 msgid "Each graph view option provides its own series of additional view options, which appear to the right of the selected graph view option." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:191 +#: ../../content/applications/marketing/email_marketing.rst:194 msgid "Search options" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:193 +#: ../../content/applications/marketing/email_marketing.rst:196 msgid "Regardless of the view chosen for the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app, the :guilabel:`Filters`, :guilabel:`Group by`, and :guilabel:`Favorites` options are always available to further customize the information being displayed." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:197 +#: ../../content/applications/marketing/email_marketing.rst:200 msgid "To access those options, click the :guilabel:`(downward arrow)` icon, located to the right of the search bar. Doing so reveals a drop-down mega menu featuring those filtering and grouping options." msgstr "" @@ -278,15 +278,15 @@ msgstr "" msgid "The drop-down mega menu of search options the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:204 +#: ../../content/applications/marketing/email_marketing.rst:207 msgid "These options provide various ways to specify and organize the information seen on the :guilabel:`Mailings` dashboard." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:209 +#: ../../content/applications/marketing/email_marketing.rst:212 msgid "Filters" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:211 +#: ../../content/applications/marketing/email_marketing.rst:214 msgid "This section of the drop-down mega menu provides different ways to filter email results being shown on the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" @@ -294,11 +294,11 @@ msgstr "" msgid "View of filters drop-down menu options on the Odoo Email Marketing dashboard." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:218 +#: ../../content/applications/marketing/email_marketing.rst:221 msgid "The options are: :guilabel:`My Mailings`, :guilabel:`Sent Date`, :guilabel:`A/B Tests`, :guilabel:`A/B Tests to review`, :guilabel:`Archived`, and :guilabel:`Add Custom Filter`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:221 +#: ../../content/applications/marketing/email_marketing.rst:224 msgid "If :guilabel:`Add Custom Filter` is selected, Odoo reveals a pop-up window, with three customizable fields to fill in, in order to create custom filter rules for Odoo to use to retrieve results that fit more specific criteria." msgstr "" @@ -306,11 +306,11 @@ msgstr "" msgid "Add custom filter pop-up window that appears in Odoo Email Marketing app." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:229 +#: ../../content/applications/marketing/email_marketing.rst:232 msgid "Group By" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:231 +#: ../../content/applications/marketing/email_marketing.rst:234 msgid "This section of the drop-down mega menu provides different ways to group email results being shown on the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" @@ -318,23 +318,23 @@ msgstr "" msgid "View of the Group By drop-down menu on the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:238 +#: ../../content/applications/marketing/email_marketing.rst:241 msgid "Using this section, the data can be grouped by the messages' :guilabel:`Status`, or who it was :guilabel:`Sent By`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:241 +#: ../../content/applications/marketing/email_marketing.rst:244 msgid "There is also the option to group the data by :guilabel:`Sent Period`, which has its own sub-menu of options to choose from. The :guilabel:`Sent Period` options are :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:245 +#: ../../content/applications/marketing/email_marketing.rst:248 msgid "If none of the above :guilabel:`Group By` options deliver the desired results, click :guilabel:`Add Custom Group` at the bottom of the :guilabel:`Group By` section. Doing so reveals a drop-down menu, wherein custom criteria can be selected and applied, thus delivering any grouping of data that may be desired." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:250 +#: ../../content/applications/marketing/email_marketing.rst:253 msgid "Favorites" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:252 +#: ../../content/applications/marketing/email_marketing.rst:255 msgid "This section provides the opportunity to save custom filters and/or groupings for future use. To utilize this section, click the :guilabel:`Save current search` field, which reveals additional fields." msgstr "" @@ -342,23 +342,23 @@ msgstr "" msgid "View of the Favorites drop-down menu on the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:260 +#: ../../content/applications/marketing/email_marketing.rst:263 msgid "Give the favorited filter/grouping a title on the blank line above the checkboxes for :guilabel:`Default filter` and :guilabel:`Shared`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:263 +#: ../../content/applications/marketing/email_marketing.rst:266 msgid "Ticking the box for :guilabel:`Default filter` makes this favorited filter/grouping the default option. Ticking the box for :guilabel:`Shared` allows other users to see and use this favorited filter/grouping." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:267 +#: ../../content/applications/marketing/email_marketing.rst:270 msgid "When all desired options are configured, click :guilabel:`Save` to save the filter/grouping in the :guilabel:`Favorites` section of the mega drop-down menu." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:271 +#: ../../content/applications/marketing/email_marketing.rst:274 msgid "Settings" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:273 +#: ../../content/applications/marketing/email_marketing.rst:276 msgid "To view and modify the *Email Marketing* settings, navigate to :menuselection:`Email Marketing app --> Configuration --> Settings`." msgstr "" @@ -366,7 +366,7 @@ msgstr "" msgid "View of the Configuration menu with Settings page in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:280 +#: ../../content/applications/marketing/email_marketing.rst:283 msgid "On the :guilabel:`Settings` page, there are four features available." msgstr "" @@ -374,35 +374,35 @@ msgstr "" msgid "View of the Settings page in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:286 +#: ../../content/applications/marketing/email_marketing.rst:289 msgid "The features are:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:288 +#: ../../content/applications/marketing/email_marketing.rst:291 msgid ":guilabel:`Mailing Campaigns`: enables the option to manage mass mailing campaigns." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:289 +#: ../../content/applications/marketing/email_marketing.rst:292 msgid ":guilabel:`Blacklist Option when Unsubscribing`: allows recipients to blacklist themselves from future mailings during the unsubscribing process." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:291 +#: ../../content/applications/marketing/email_marketing.rst:294 msgid ":guilabel:`Dedicated Server`: provides the option to utilize a separate, dedicated server for mailings. When enabled, Odoo reveals a new field (and link), in which the specific server configurations must be entered, in order for it to connect properly to Odoo." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:294 +#: ../../content/applications/marketing/email_marketing.rst:297 msgid ":guilabel:`24H Stat Mailing Reports`: allows users to check how well mailings have performed a day after it has been sent." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:300 +#: ../../content/applications/marketing/email_marketing.rst:303 msgid "Create an email" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:302 +#: ../../content/applications/marketing/email_marketing.rst:305 msgid "To create an email, open the :menuselection:`Email Marketing` application, and click the :guilabel:`New` button in the upper-left corner of the :guilabel:`Mailings` dashboard page." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:305 +#: ../../content/applications/marketing/email_marketing.rst:308 msgid "Clicking :guilabel:`New` reveals a blank email form." msgstr "" @@ -410,60 +410,60 @@ msgstr "" msgid "View of a blank email detail form in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:311 +#: ../../content/applications/marketing/email_marketing.rst:314 msgid "On the email form, there are fields for the :ref:`Subject ` and :ref:`Recipients ` of the email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:314 +#: ../../content/applications/marketing/email_marketing.rst:317 msgid "Beneath that, there are three tabs: :ref:`Mail Body `, :ref:`A/B Tests `, and :ref:`Settings `." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:320 +#: ../../content/applications/marketing/email_marketing.rst:323 msgid "Subject" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:322 +#: ../../content/applications/marketing/email_marketing.rst:325 msgid "First, enter a :guilabel:`Subject` to the email. The :guilabel:`Subject` is visible in the recipients' inbox, allowing them to quickly see what the message is about." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:326 +#: ../../content/applications/marketing/email_marketing.rst:329 msgid "The :guilabel:`Subject` field is mandatory. An email can **not** be sent without a :guilabel:`Subject`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:329 +#: ../../content/applications/marketing/email_marketing.rst:332 msgid "The :guilabel:`(smiley face with a plus sign)` icon at the end of the :guilabel:`Subject` field represents emojis that can be added to the :guilabel:`Subject` field. Clicking that icon reveals a pop-up menu of emojis that can be used." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:333 +#: ../../content/applications/marketing/email_marketing.rst:336 msgid "Beside the :guilabel:`(smiley face with a plus sign)` icon at the end of the :guilabel:`Subject` field is an empty :guilabel:`(star)` icon. When clicked, the :guilabel:`(star)` icon turns gold, and the email is saved as a template in the :guilabel:`Mail Body` tab, which can be used again in the future." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:341 +#: ../../content/applications/marketing/email_marketing.rst:344 msgid "Recipients" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:343 +#: ../../content/applications/marketing/email_marketing.rst:346 msgid "Beneath the :guilabel:`Subject` field on the email form is the :guilabel:`Recipients` field. In this field, select the recipients of the email. By default, the :guilabel:`Mailing List` option is selected, but clicking the field reveals a drop-down menu of other recipient options." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:347 +#: ../../content/applications/marketing/email_marketing.rst:350 msgid "With the default :guilabel:`Mailing List` option selected, a specific mailing list **must** be chosen from the adjacent :guilabel:`Select mailing lists` field drop-down menu." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:351 +#: ../../content/applications/marketing/email_marketing.rst:354 msgid "More than one mailing list can be chosen from the :guilabel:`Select mailing lists` field." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:353 +#: ../../content/applications/marketing/email_marketing.rst:356 msgid "Odoo then sends the email to contacts on that specific mailing list(s)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:356 -#: ../../content/applications/marketing/email_marketing.rst:822 +#: ../../content/applications/marketing/email_marketing.rst:359 +#: ../../content/applications/marketing/email_marketing.rst:825 msgid ":doc:`email_marketing/mailing_lists`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:358 +#: ../../content/applications/marketing/email_marketing.rst:361 msgid "When the :guilabel:`Recipients` field is clicked, a drop-down menu of other options is revealed. Each option provides different ways Odoo can create a target audience for the email." msgstr "" @@ -471,51 +471,51 @@ msgstr "" msgid "View of recipients drop-down menu in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:365 +#: ../../content/applications/marketing/email_marketing.rst:368 msgid "Those options (excluding the default :guilabel:`Mailing List`) provide the option to create a more specified recipient filter, in an equation-like format, which appears beneath the :guilabel:`Recipients` field." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:369 +#: ../../content/applications/marketing/email_marketing.rst:372 msgid "The :guilabel:`Recipients` field options, other than the default :guilabel:`Mailing List` option, are as follows:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:372 +#: ../../content/applications/marketing/email_marketing.rst:375 msgid ":guilabel:`Contact`: ties specifically to the *Contacts* app, and includes all the contacts entered in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:374 +#: ../../content/applications/marketing/email_marketing.rst:377 msgid ":guilabel:`Event Registration`: ties specifically to the *Events* app, and provides opportunities to interact with event registrants, in order to communicate important information about the event(s), or nurture other valuable actions, such as post-event surveys, purchases, etc." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:377 +#: ../../content/applications/marketing/email_marketing.rst:380 msgid ":guilabel:`Lead/Opportunity`: ties specifically to records in the *CRM* application, which opens up a number of opportunities to influence sales or purchase decisions." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:379 +#: ../../content/applications/marketing/email_marketing.rst:382 msgid ":guilabel:`Mailing Contact`: ties specifically to the *Email Marketing* app, and focuses on specific mailing contacts that have been entered in that specific application, and are related to a specific mailing list. These contacts are also unique because they do *not* have their own contact card in the *Contacts* application. This list can be accessed by navigating to :menuselection:`Email Marketing app --> Mailing Lists --> Mailing List Contacts`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:384 +#: ../../content/applications/marketing/email_marketing.rst:387 msgid ":guilabel:`Sales Order`: ties specifically to the *Sales* app, and focuses on a specific sales orders in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:388 +#: ../../content/applications/marketing/email_marketing.rst:391 msgid "Add recipient filter" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:390 +#: ../../content/applications/marketing/email_marketing.rst:393 msgid "To add a more specific recipient filter to any :guilabel:`Recipient` option, select any recipient option (other than :guilabel:`Mailing List`), and click the :guilabel:`Modify filter (right-facing arrow)` icon beneath the :guilabel:`Recipient` field to reveal three subsequent filter rule fields, formatted like an equation." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:395 +#: ../../content/applications/marketing/email_marketing.rst:398 msgid "It is highly recommended that users implement detailed targeting criteria for the :guilabel:`Recipients` field. Typically, a single line of targeting logic is not sufficient enough for an email campaign." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:399 +#: ../../content/applications/marketing/email_marketing.rst:402 msgid "While the :guilabel:`Mailing List` option is adequate for the :guilabel:`Recipients` field, the :guilabel:`Lead/Opportunity` and :guilabel:`Event Registration` options provide far more detailed targeting criteria, which can be added on top of those seed sources." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:404 +#: ../../content/applications/marketing/email_marketing.rst:407 msgid "For example, with the :guilabel:`Lead/Opportunity` option chosen in the :guilabel:`Recipients` field, users can add various custom criteria related to :guilabel:`Created on` dates, :guilabel:`Stages`, :guilabel:`Tags`, :guilabel:`Lost Reasons`, :guilabel:`Sales Teams`, :guilabel:`Active` statuses, :guilabel:`Country`, and so much more." msgstr "" @@ -524,40 +524,40 @@ msgstr "" msgid "View of how recipient filters can be customized in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:413 +#: ../../content/applications/marketing/email_marketing.rst:416 msgid "To reveal the sub-menu options within the filter rule fields, click each field, and make the desired selections, until the preferred configuration has been achieved." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:416 +#: ../../content/applications/marketing/email_marketing.rst:419 msgid "The number of :guilabel:`records` in the database that match the configured rule(s) are indicated beneath the configured filter rule(s), in green." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:424 +#: ../../content/applications/marketing/email_marketing.rst:427 #: ../../content/applications/marketing/events/event_essentials.rst:191 msgid "Some sub-menu options in the first rule field allow for a second choice to provide even more specificity." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:427 +#: ../../content/applications/marketing/email_marketing.rst:430 msgid "To the right of each rule, there are three additional options, represented by :guilabel:`➕ (plus sign)`, :guilabel:`(sitemap)`, and :guilabel:`🗑️ (trash)` icons." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:430 +#: ../../content/applications/marketing/email_marketing.rst:433 msgid "The :guilabel:`➕ (plus sign)` icon adds a new node (line) to the overall targeting logic." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:431 +#: ../../content/applications/marketing/email_marketing.rst:434 msgid "The :guilabel:`(sitemap)` icon adds a branch to the node. A branch contains two additional, indented sub-nodes that are related to that specific rule, providing even more specificity to the parent line above it." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:434 +#: ../../content/applications/marketing/email_marketing.rst:437 msgid "The :guilabel:`🗑️ (trash)` icon deletes a specific node (line) in the array of logic." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:439 +#: ../../content/applications/marketing/email_marketing.rst:442 msgid "Mail Body tab" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:441 +#: ../../content/applications/marketing/email_marketing.rst:444 msgid "In the :guilabel:`Mail Body` tab, there are a number of pre-configured message templates to choose from." msgstr "" @@ -565,7 +565,7 @@ msgstr "" msgid "View of the templates in the Mail Body tab in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:448 +#: ../../content/applications/marketing/email_marketing.rst:451 msgid "Select the desired template, and proceed to modify every element of its design details with Odoo's drag-and-drop building blocks, which appear on the right sidebar when a template is chosen." msgstr "" @@ -573,19 +573,19 @@ msgstr "" msgid "View of the building blocks in the Mail Body tab in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:455 +#: ../../content/applications/marketing/email_marketing.rst:458 msgid "The features on the sidebar used to create and customize emails are separated into three sections: :guilabel:`Blocks`, :guilabel:`Customize`, and :guilabel:`Design`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:458 +#: ../../content/applications/marketing/email_marketing.rst:461 msgid "Each building block provides unique features and professional design elements. To use a building block, drag-and-drop the desired block element onto the body of the email being built. Once dropped, various aspects of the building block can be customized." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:463 +#: ../../content/applications/marketing/email_marketing.rst:466 msgid "To build an email from the ground up, without any building block elements, select the :guilabel:`Plain Text` template. When selected, Odoo provides a completely blank email canvas, which can be customized in a number of way using the front-end rich text editor that accepts forward slash `/` commands." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:468 +#: ../../content/applications/marketing/email_marketing.rst:471 msgid "When `/` is typed into the blank body of the email, while using a :guilabel:`Plain Text` template, a drop-down menu of various design elements appears, which can be used to create the desired email design." msgstr "" @@ -593,71 +593,71 @@ msgstr "" msgid "View of the rich text editor drop-down in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:479 +#: ../../content/applications/marketing/email_marketing.rst:482 msgid "A/B Tests tab" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:481 +#: ../../content/applications/marketing/email_marketing.rst:484 msgid "Initially, when the :guilabel:`A/B Tests` tab is opened on an email form, the only option available is :guilabel:`Allow A/B Testing`. This is **not** a required option." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:484 +#: ../../content/applications/marketing/email_marketing.rst:487 msgid "If this option is enabled, recipients are only mailed *once* for the entirety of the campaign." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:486 +#: ../../content/applications/marketing/email_marketing.rst:489 msgid "This allows the user to send different versions of the same mailing to randomly selected recipients to gauge the effectiveness of various designs, formats, layouts, content, and so on -- without any duplicate messages being sent." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:490 +#: ../../content/applications/marketing/email_marketing.rst:493 msgid "When the checkbox beside :guilabel:`Allow A/B Testing` is ticked, an :guilabel:`on (%)` field appears, in which the user determines the percentage of the pre-configured recipients that are going to be sent this current version of the mailing as part of the test." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:495 +#: ../../content/applications/marketing/email_marketing.rst:498 msgid "The default figure in the :guilabel:`on (%)` field is `10`, but that figure can be changed at any time." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:498 +#: ../../content/applications/marketing/email_marketing.rst:501 msgid "Beneath that, two additional fields appear:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:500 +#: ../../content/applications/marketing/email_marketing.rst:503 msgid "The :guilabel:`Winner Selection` field provides a drop-down menu of options, wherein the user decides what criteria should be used to determine the \"winning\" version of the email tests that are sent." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:504 +#: ../../content/applications/marketing/email_marketing.rst:507 msgid "The options in the :guilabel:`Winner Selection` field are as follows:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:506 +#: ../../content/applications/marketing/email_marketing.rst:509 msgid ":guilabel:`Manual`: allows the user to determine the \"winning\" version of the mailing. This option removes the :guilabel:`Send Final On` field." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:508 +#: ../../content/applications/marketing/email_marketing.rst:511 msgid ":guilabel:`Highest Open Rate` (default): the mailing with the highest open rate is determined to be the \"winning\" version." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:510 +#: ../../content/applications/marketing/email_marketing.rst:513 msgid ":guilabel:`Highest Click Rate`: the mailing with the highest click rate is determined to be the \"winning\" version." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:512 +#: ../../content/applications/marketing/email_marketing.rst:515 msgid ":guilabel:`Highest Reply Rate`: the mailing with the highest reply rate is determined to be the \"winning\" version." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:514 +#: ../../content/applications/marketing/email_marketing.rst:517 msgid ":guilabel:`Leads`: the mailing with the most leads generated is determined to be the \"winning\" version." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:516 +#: ../../content/applications/marketing/email_marketing.rst:519 msgid ":guilabel:`Quotations`: the mailing with the most quotations generated is determined to be the \"winning\" version." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:518 +#: ../../content/applications/marketing/email_marketing.rst:521 msgid ":guilabel:`Revenues`: the mailing with the most revenue generated is determined to be the \"winning\" version." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:521 +#: ../../content/applications/marketing/email_marketing.rst:524 msgid "The :guilabel:`Send Final On` field allows users to choose a date that is used to know *when* Odoo should determine the \"winning\" email, and subsequently, send that version of the email to the remaining recipients." msgstr "" @@ -665,23 +665,23 @@ msgstr "" msgid "View of the A/B Tests tab in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:529 +#: ../../content/applications/marketing/email_marketing.rst:532 msgid "To the right of those fields is a :guilabel:`Create an Alternative Version` button. When clicked, Odoo presents a new :guilabel:`Mail Body` tab for the user to create an alternate version of the email to test." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:536 +#: ../../content/applications/marketing/email_marketing.rst:539 msgid "Settings tab" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:538 +#: ../../content/applications/marketing/email_marketing.rst:541 msgid "The options present in the :guilabel:`Settings` tab of the mail form are divided into two sections: :guilabel:`Email Content` and :guilabel:`Tracking`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:542 +#: ../../content/applications/marketing/email_marketing.rst:545 msgid "The options available in the :guilabel:`Settings` tab vary depending on if the *Mailing Campaigns* feature is activated in :menuselection:`Email Marketing --> Configuration --> Settings`. See :ref:`email_marketing/mailing-campaigns` for more information." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:546 +#: ../../content/applications/marketing/email_marketing.rst:549 msgid "Without the *Mailing Campaigns* feature activated, the :guilabel:`Settings` tab on the email form only contains the :guilabel:`Preview Text`, :guilabel:`Send From`, :guilabel:`Reply To`, :guilabel:`Attachments`, and :guilabel:`Responsible` fields." msgstr "" @@ -689,35 +689,35 @@ msgstr "" msgid "View of settings tab in Odoo Email Marketing app, without campaign setting activated." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:555 +#: ../../content/applications/marketing/email_marketing.rst:558 msgid "Email content" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:557 +#: ../../content/applications/marketing/email_marketing.rst:560 msgid ":guilabel:`Preview Text`: allows the user to enter a preview sentence to encourage recipients to open the email. In most inboxes, this is displayed next to the subject. If left empty, the first characters of the email content appear, instead. The ability to add an emoji in this field is available, as well, via the :guilabel:`(smiley face with a plus sign)` icon." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:561 +#: ../../content/applications/marketing/email_marketing.rst:564 msgid ":guilabel:`Send From`: designate an email alias that displays as the sender of this particular email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:563 +#: ../../content/applications/marketing/email_marketing.rst:566 msgid ":guilabel:`Reply To`: designate an email alias to whom all the replies of this particular email are sent." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:565 +#: ../../content/applications/marketing/email_marketing.rst:568 msgid ":guilabel:`Attach a file`: if any specific files are required (or helpful) for this email, click the :guilabel:`Attachments` button, and upload the desired file(s) to the email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:569 +#: ../../content/applications/marketing/email_marketing.rst:572 msgid "Tracking" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:571 +#: ../../content/applications/marketing/email_marketing.rst:574 msgid ":guilabel:`Responsible`: designate a user in the database to be responsible for this particular email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:575 +#: ../../content/applications/marketing/email_marketing.rst:578 msgid "If the *Mailing Campaign* feature *is* activated, an additional :guilabel:`Campaign` field appears in the :guilabel:`Tracking` section of the :guilabel:`Settings` tab." msgstr "" @@ -725,31 +725,31 @@ msgstr "" msgid "View of settings tab in Odoo Email Marketing when campaign setting is activated." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:582 +#: ../../content/applications/marketing/email_marketing.rst:585 msgid "The additional :guilabel:`Campaign` field allows users to attach this particular email to a mailing campaign, if desired." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:585 +#: ../../content/applications/marketing/email_marketing.rst:588 msgid "If the desired campaign is not available in the initial drop-down menu, select :guilabel:`Search More` to reveal a complete list of all mailing campaigns in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:588 +#: ../../content/applications/marketing/email_marketing.rst:591 msgid "Or, type the name of the desired mailing campaign in the :guilabel:`Campaign` field, until Odoo reveals the desired campaign in the drop-down menu. Then, select the desired campaign." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:592 +#: ../../content/applications/marketing/email_marketing.rst:595 msgid "Send, schedule, test" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:594 +#: ../../content/applications/marketing/email_marketing.rst:597 msgid "Once the mailing is finalized, the following options can be utilized, via buttons located in the upper-left corner of the email form: :ref:`Send `, :ref:`Schedule `, and :ref:`Test `." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:601 +#: ../../content/applications/marketing/email_marketing.rst:604 msgid "Send" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:603 +#: ../../content/applications/marketing/email_marketing.rst:606 msgid "The :guilabel:`Send` button reveals a :guilabel:`Ready to unleash emails?` pop-up window." msgstr "" @@ -757,15 +757,15 @@ msgstr "" msgid "View of pop-up window that appears when the send button on an email form is clicked." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:609 +#: ../../content/applications/marketing/email_marketing.rst:612 msgid "When the :guilabel:`Send to all` button is clicked, Odoo sends the email to the desired recipients. Once Odoo has sent the mailing, the status changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:615 +#: ../../content/applications/marketing/email_marketing.rst:618 msgid "Schedule" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:617 +#: ../../content/applications/marketing/email_marketing.rst:620 msgid "The :guilabel:`Schedule` button reveals a :guilabel:`When do you want to send your mailing?` pop-up window." msgstr "" @@ -774,19 +774,19 @@ msgstr "" msgid "View of pop-up window that appears when the schedule button on an email form is clicked." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:624 +#: ../../content/applications/marketing/email_marketing.rst:627 msgid "In this pop-up window, click the :guilabel:`Send on` field to reveal a calendar pop-up window." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:630 +#: ../../content/applications/marketing/email_marketing.rst:633 msgid "From the calendar pop-up window, select the future date and time for Odoo to send this email. Then, click :guilabel:`✔️ Apply`. When a date and time are chosen, click the :guilabel:`Schedule` button, and the status of the mailing changes to :guilabel:`In Queue`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:637 +#: ../../content/applications/marketing/email_marketing.rst:640 msgid "Test" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:639 +#: ../../content/applications/marketing/email_marketing.rst:642 msgid "The :guilabel:`Test` button reveals a :guilabel:`Test Mailing` pop-up window." msgstr "" @@ -794,27 +794,27 @@ msgstr "" msgid "View of pop-up window that appears when the test button on an email form is clicked." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:645 +#: ../../content/applications/marketing/email_marketing.rst:648 msgid "From this pop-up window, enter the email addresses of the contacts to whom Odoo should send this test email in the :guilabel:`Recipients` field. Multiple contacts can be added in this field, if desired." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:649 +#: ../../content/applications/marketing/email_marketing.rst:652 msgid "Once all the desired email addresses have been entered in the :guilabel:`Recipients` field, click the :guilabel:`Send Test` button." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:653 +#: ../../content/applications/marketing/email_marketing.rst:656 msgid "By default, there's a daily limit applied for **all emails** sent throughout **all applications**. So, if there are remaining emails to be sent after a limit has been reached, those mailings are **not** sent automatically the next day. The sending needs to be forced, by opening the email and clicking :guilabel:`Retry`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:661 +#: ../../content/applications/marketing/email_marketing.rst:664 msgid "Mailing campaigns" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:663 +#: ../../content/applications/marketing/email_marketing.rst:666 msgid "The *Email Marketing* application provides users with the ability to build mailing campaigns." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:665 +#: ../../content/applications/marketing/email_marketing.rst:668 msgid "In order to create and customize mailing campaigns, the *Mailing Campaigns* feature **must** be activated in the *Settings* page of the *Email Marketing* application. To do that, navigate to :menuselection:`Email Marketing app --> Configuration --> Settings`, tick the box beside :guilabel:`Mailing Campaigns`, and click the :guilabel:`Save` button." msgstr "" @@ -822,11 +822,11 @@ msgstr "" msgid "View of the campaign feature setting in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:674 +#: ../../content/applications/marketing/email_marketing.rst:677 msgid "Once the :guilabel:`Mailing Campaigns` feature is activated, a new :guilabel:`Campaigns` menu option appears in the header." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:677 +#: ../../content/applications/marketing/email_marketing.rst:680 msgid "When that is clicked, Odoo reveals a separate :guilabel:`Campaigns` page, displaying all the mailing campaigns in the database, and the current stage they are in, showcased in a default Kanban view." msgstr "" @@ -834,31 +834,31 @@ msgstr "" msgid "View of the campaign page in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:685 +#: ../../content/applications/marketing/email_marketing.rst:688 msgid "This information can also be viewed in a list, by clicking the :guilabel:`☰ (horizontal lines)` icon in the upper-right corner." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:688 +#: ../../content/applications/marketing/email_marketing.rst:691 msgid "Clicking any campaign from the :guilabel:`Campaigns` page reveals that campaign's form." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:690 +#: ../../content/applications/marketing/email_marketing.rst:693 msgid "There are two different ways to create and customize campaigns in the *Email Marketing* application, either directly from the :ref:`Campaigns page ` or through the :ref:`Settings tab ` on an email form." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:697 +#: ../../content/applications/marketing/email_marketing.rst:700 msgid "Create mailing campaign (from campaigns page)" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:699 +#: ../../content/applications/marketing/email_marketing.rst:702 msgid "When the *Mailing Campaigns* feature is activated, a new *Campaigns* option appears in the header of the *Email Marketing* application. Campaigns can be created directly on the *Campaigns* page in the *Email Marketing* app." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:703 +#: ../../content/applications/marketing/email_marketing.rst:706 msgid "To do that, navigate to :menuselection:`Email Marketing app --> Campaigns --> New`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:708 +#: ../../content/applications/marketing/email_marketing.rst:711 msgid "When the :guilabel:`New` button is clicked in the default Kanban view on the :guilabel:`Campaigns` page, a Kanban card appears in the :guilabel:`New` stage." msgstr "" @@ -866,31 +866,31 @@ msgstr "" msgid "View of the campaign pop-up kanban in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:715 +#: ../../content/applications/marketing/email_marketing.rst:718 msgid "New campaign cards can also be made by clicking the :guilabel:`➕ (plus sign)` at the top of any Kanban stage on the :guilabel:`Campaigns` page." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:718 +#: ../../content/applications/marketing/email_marketing.rst:721 msgid "When the new campaign Kanban card appears, the options to enter a :guilabel:`Campaign Name`, a :guilabel:`Responsible`, and :guilabel:`Tags` become readily available." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:721 +#: ../../content/applications/marketing/email_marketing.rst:724 msgid "To add the campaign to the Kanban stage, click the :guilabel:`Add` button." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:723 +#: ../../content/applications/marketing/email_marketing.rst:726 msgid "To delete the campaign, click the :guilabel:`🗑️ (trash can)` icon." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:725 +#: ../../content/applications/marketing/email_marketing.rst:728 msgid "To further customize the campaign, click the :guilabel:`Edit` button, which reveals the campaign form for additional modifications." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:729 +#: ../../content/applications/marketing/email_marketing.rst:732 msgid "A :guilabel:`Campaign Name` **must** be entered in the Kanban card, in order for the :guilabel:`Edit` button to reveal the campaign form for further modifications." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:735 +#: ../../content/applications/marketing/email_marketing.rst:738 msgid "To enter the list view on the :guilabel:`Campaigns` page, click the :guilabel:`☰ (horizontal lines)` icon in the upper-right corner. Doing so reveals all campaign information in a list format." msgstr "" @@ -898,7 +898,7 @@ msgstr "" msgid "View of the campaign page in list view in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:742 +#: ../../content/applications/marketing/email_marketing.rst:745 msgid "To create a campaign from the :guilabel:`Campaigns` page while in list view, click the :guilabel:`New` button. Doing so reveals a blank campaign form." msgstr "" @@ -906,27 +906,27 @@ msgstr "" msgid "View of the blank campaign form in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:749 +#: ../../content/applications/marketing/email_marketing.rst:752 msgid "From this campaign form, a :guilabel:`Campaign Name`, a :guilabel:`Responsible`, and :guilabel:`Tags` can be added." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:752 +#: ../../content/applications/marketing/email_marketing.rst:755 msgid "At the top of the form, various metric-related smart buttons can be seen that showcase specific analytics related to the campaign. Those smart buttons are: :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Opportunities`, and :guilabel:`Clicks`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:757 +#: ../../content/applications/marketing/email_marketing.rst:760 msgid "Once a :guilabel:`Campaign Name` is entered and saved, additional buttons appear at the top of the campaign form." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:760 +#: ../../content/applications/marketing/email_marketing.rst:763 msgid "Those additional buttons are: :guilabel:`Send Mailing` and :guilabel:`Send SMS`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:763 +#: ../../content/applications/marketing/email_marketing.rst:766 msgid "Campaign form" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:765 +#: ../../content/applications/marketing/email_marketing.rst:768 msgid "On the campaign form (after clicking :guilabel:`Edit` from the Kanban card, or selecting an existing campaign from the :guilabel:`Campaigns` page) there are additional options and metrics available." msgstr "" @@ -934,27 +934,27 @@ msgstr "" msgid "View of the campaign form in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:772 +#: ../../content/applications/marketing/email_marketing.rst:775 msgid "At the top of the form, various smart buttons can be seen that showcase specific analytics related to the campaign. Those smart buttons are: :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Opportunities`, and :guilabel:`Clicks`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:776 +#: ../../content/applications/marketing/email_marketing.rst:779 msgid "There are also buttons to :guilabel:`Send Mailing`, :guilabel:`Send SMS`, :guilabel:`Add Post`, and :guilabel:`Add Push` (push notification)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:780 +#: ../../content/applications/marketing/email_marketing.rst:783 msgid "If the :guilabel:`Send Mailing` and :guilabel:`Send SMS` buttons are not readily available, enter a :guilabel:`Campaign Name`, then save (either manually or automatically). Doing so reveals those buttons." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:784 +#: ../../content/applications/marketing/email_marketing.rst:787 msgid "The status of the campaign can be viewed in the upper-right corner of the campaign form, as well." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:789 +#: ../../content/applications/marketing/email_marketing.rst:792 msgid "Create mailing campaign (from settings tab)" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:791 +#: ../../content/applications/marketing/email_marketing.rst:794 msgid "To create a new campaign from the :guilabel:`Settings` tab of a mailing form, click the :guilabel:`Campaign` field, and start typing the name of the new campaign. Then, select either :guilabel:`Create \"[Campaign Name]\"` or :guilabel:`Create and edit...` from the drop-down menu that appears." msgstr "" @@ -962,11 +962,11 @@ msgstr "" msgid "View of the mailing campaign creation in the Settings tab of an email form." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:800 +#: ../../content/applications/marketing/email_marketing.rst:803 msgid "Select :guilabel:`Create` to add this new mailing campaign to the database, and modify its settings in the future." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:803 +#: ../../content/applications/marketing/email_marketing.rst:806 msgid "Select :guilabel:`Create and Edit...` to add this new mailing campaign to the database, and reveal a :guilabel:`Create Campaign` pop-up window." msgstr "" @@ -974,30 +974,170 @@ msgstr "" msgid "View of the email mailing campaign pop-up window in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:810 +#: ../../content/applications/marketing/email_marketing.rst:813 msgid "Here, the new mailing campaign can be further customized. Users can adjust the :guilabel:`Campaign Name`, assign a :guilabel:`Responsible`, and add :guilabel:`Tags`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:813 +#: ../../content/applications/marketing/email_marketing.rst:816 msgid "Buttons to :guilabel:`Add Post` or :guilabel:`Send Push` (push notifications) are also available." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:815 +#: ../../content/applications/marketing/email_marketing.rst:818 msgid "There is also a status located in the upper-right corner of the :guilabel:`Create Campaign` pop-up window." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:818 +#: ../../content/applications/marketing/email_marketing.rst:821 msgid "When all modifications are ready to be finalized, click :guilabel:`Save & Close`. To delete the entire campaign, click :guilabel:`Discard`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:823 +#: ../../content/applications/marketing/email_marketing.rst:826 msgid ":doc:`email_marketing/unsubscriptions`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:824 +#: ../../content/applications/marketing/email_marketing.rst:827 msgid ":doc:`email_marketing/lost_leads_email`" msgstr "" +#: ../../content/applications/marketing/email_marketing.rst:828 +msgid ":doc:`email_marketing/analyze_metrics`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:3 +msgid "Analyze metrics" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:7 +msgid "In order to properly understand the success or failure of an email marketing campaign, it is necessary to monitor several key metrics. The insights gained from these metrics can then be used to optimize future campaigns. Odoo's *Email Marketing* application tracks several :ref:`key metrics `, that can be interpreted to improve future campaigns." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:13 +msgid "View metrics" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:15 +msgid "After a mass mail has been sent, the results for that particular mailing are displayed in multiple locations." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:18 +msgid "To access the metrics for an individual mailing, navigate to :menuselection:`Email Marketing app --> Mailings`. Locate the specific mailing in the list view, and use the column headings to view the results for that mailing. Click on one of the mailings in the list to open the record. At the top of the record, detailed metrics are displayed as smart buttons." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:-1 +msgid "The smart buttons on a mass mailing, displaying the results of the message." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:28 +msgid "Click on the smart buttons to see the recipient records for each metric." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:33 +msgid "Opened rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:35 +msgid "The *Opened* rate measures the percentage of emails opened by recipients against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:38 +msgid "A high open rate may indicate that the subject line was timely, compelling, and successfully prompted the recipients to view the message." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:41 +msgid "A low open rate may indicate the subject line failed to capture the recipients' interest. It could also indicate the email ended up in a spam or junk folder due to having a poor sender reputation or failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:46 +msgid "Replied rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:48 +msgid "The *Replied* rate measures the percentage of recipients who responded to the email directly against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:51 +msgid "A high replied rate may indicate the email resonated with recipients, prompting them to take action or provide feedback." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:54 +msgid "A low replied rate may suggest that the message lacked relevance or did not contain a clear call to action." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:58 +msgid "Clicked rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:60 +msgid "The *Clicked* through rate (CTR), measures the percentage of recipients who clicked on a link within the email against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:63 +msgid "A high |CTR| may indicate the email content was relevant and appropriately targeted. Recipients were motivated to click the links provided, and likely found the content engaging." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:66 +msgid "A low |CTR| may indicate issues with either the targeting, or the content itself. Recipients may have been unmotivated by the calls to action, if there were any, or the message itself may have been directed toward the wrong audience." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:71 +msgid "Received rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:73 +msgid "The *Received* rate measures the percentage of emails that were successfully delivered against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:76 +msgid "A high received rate can indicate that the mailing list used is up to date and the sender authentication is trusted by email providers." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:79 +msgid "A low received rate may indicate issues either with the mailing list used for the mailing or with the sender authentication. View the :ref:`email-marketing/deliverability-issues` section for more information." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:84 +msgid "Bounced rate" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:86 +msgid "The *Bounced* rate measures the percentage of emails that were unsuccessfully delivered, against the total number of sent emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:89 +msgid "A high bounce rate could indicate issues either with the mailing list used for the mailing or with the sender authentication." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:92 +msgid "A low bounce rate may indicate that the mailing list used is up to date and the sender authentication is trusted by email providers. View the :ref:`email-marketing/deliverability-issues` section for more information." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:99 +msgid "Deliverability issues" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:101 +msgid "The following define possible reasons for a high bounce rate or low received rate:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:103 +msgid "Using a mailing list that contains outdated contact information, or malformed email addresses are likely to result in a high bounce rate and/or a low received rate." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:105 +msgid "Mailings sent using a *From* email address that differs from the sender's domain are likely to bounce with certain email providers due to failing :ref:`DMARC authentication `." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:108 +msgid "Failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>` can also result in a high bounce rate." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:112 +msgid ":ref:`Mailing campaigns `" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:113 +msgid ":doc:`Manage unsubscriptions `" +msgstr "" + #: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:3 msgid "Lost leads reactivation email" msgstr "" @@ -1872,6 +2012,526 @@ msgstr "" msgid "`Odoo Tutorials: Events `_" msgstr "" +#: ../../content/applications/marketing/events/create_events.rst:3 +msgid "Create events" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:5 +msgid "With the *Events* application, event organizers can create and configure in-person or online-only events in Odoo. Each new event contains a number of customizable options that are geared around specific event logistics, as needed per event, such as ticket sales and registration desk, booths, tracks, sponsors, rooms, and more." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:10 +msgid "Events can be manually created from scratch or built off of pre-made templates. Once launched, the *Events* application then integrates with the *Website* app for the front-end promotion and registration of the event for attendees, the *Sales* app for the purchasing ability of paid tickets, as well the *CRM* application through customizable lead generation rules." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:16 +msgid "New event" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:18 +msgid "To create a new event, begin by navigating to the :menuselection:`Events app` to land on the default :guilabel:`Events` dashboard, in the :icon:`oi-view-kanban` :guilabel:`Kanban` view. From there, or alternatively from the :icon:`oi-view-list` :guilabel:`List` or :icon:`fa-tasks` :guilabel:`Gantt` views, click the :guilabel:`New` button in the upper-left corner of the dashboard to open up a new event form." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:-1 +msgid "Typical event template in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:29 +msgid "If certain fields do not readily appear on the event form, that means an additional application needs to be installed, or the database is not operating in a multi-company environment." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:32 +msgid "For example, the :guilabel:`Twitter Wall` field **only** appears if the *Social Marketing* app is installed, and the :guilabel:`Company` field **only** appears if the database is working in a multi-company environment." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:36 +msgid "These are just *additional* elements that can be used for an event. They are **not** required to create, host, and manage an event with Odoo *Events*." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:40 +msgid "Event form" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:42 +msgid "At the top of the event form are a series of smart buttons related to various event metrics, which will autopopulate with pertinent data once attendees begin to register, booths and sponsors sign on for the event, the event takes place, and so on." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:46 +msgid "Beneath the smart buttons is the event form, which contains various fields and clickable tabs that serve to configure the initial, necessary details of the event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:49 +msgid "The following are fields found on an event form:" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:51 +msgid ":guilabel:`Event Name`: the title of the event. This field is **required**." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:52 +msgid ":guilabel:`Date`: when the event is scheduled to take place. This field is auto-populated, but modifiable, and is **required**." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:54 +msgid ":guilabel:`Timezone`: the corresponding timezone related to the event. This field is auto-populated, but modifiable, and is **required**." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:56 +msgid ":guilabel:`Language`: designate a specific language for all event communications to be translated into, if necessary. This field is blank, by default, so if event-related communications are being sent to recipients who speak a different language, be sure to configure this field properly." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:59 +msgid ":guilabel:`Twitter Wall`: creates a separate page on the event website to feature specific social posts on X (formerly Twitter) that contain pre-determined desired elements." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:63 +msgid "To create and customize a :guilabel:`Twitter Wall`, type the name of the desired wall into the field, and select :guilabel:`Create and edit...` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:66 +msgid "Doing so reveals :guilabel:`Create Twitter Wall` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:0 +msgid "The Twitter Wall pop-up window in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:72 +msgid "From this window, enter a :guilabel:`Wall Name`. Then, select a certain word or hashtag for Odoo to search for on X, like `#WoodWorkingExpo24`, for example." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:75 +msgid "Next, determine the :guilabel:`Type of tweets` Odoo should showcase with that predetermined criteria. The choices in this field are: :guilabel:`Recent`, :guilabel:`Popular`, or :guilabel:`Mixed`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:79 +msgid "Users also have the option to add a brief :guilabel:`Description` to the wall, as well." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:81 +msgid "Lastly, the greyed-out, non-modifiable :guilabel:`Website URL` field will autopopulate with the full URL needed to access the document through the event website." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:84 +msgid "An image can also be added to the wall by clicking the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :guilabel:`(camera)` placeholder image in the upper-right corner of the pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:88 +msgid "Then, from the resulting file explorer window, select the desired image to be added to the wall." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:91 +msgid "This :guilabel:`Twitter Wall` field **only** appears on the event form if the *Social Marketing* app is installed, and an X account has been added as a stream on the application. To learn more, check out the :doc:`Social marketing essentials <../social_marketing/essentials/social_essentials>` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:96 +msgid ":guilabel:`Template`: choose a pre-configured event template from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:98 +msgid "Or, create a new one directly from this field, by typing in the name of the new template, and selecting either:" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:101 +msgid ":guilabel:`Create` (which creates the template, and can be edited later) or" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:102 +msgid ":guilabel:`Create and edit...` (which creates the template, and reveals a separate template page to configure the template in greater detail)." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:105 +msgid ":guilabel:`Tags`: add any corresponding tags to briefly describe the event (e.g. `Online`, `Conference`, etc.). Multiple tags can be added per event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:109 +msgid "Tags can be displayed on events that are listed on the website by enabling the *Show on Website* checkbox from :menuselection:`Events app --> Configuration --> Event Tag Categories`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:112 +msgid ":guilabel:`Organizer`: designate the organizer of the event (a company, contact, or employee)." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:113 +msgid ":guilabel:`Responsible`: designate a user in the database to be responsible for this event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:114 +msgid ":guilabel:`Company`: designate which company in the database to which this event is related. This field **only** appears if working in a multi-company environment. This field is auto-populated, but modifiable, and is **required**." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:117 +msgid ":guilabel:`Website`: choose to restrict the publishing of this event to a specific website created in Odoo. If this field is left blank, the event can be published on *all* websites in the database. To learn more, refer to the :doc:`Multiple websites <../../websites/website/configuration/multi_website>` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:121 +msgid ":guilabel:`Venue`: enter the pertinent event venue details in this field." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:122 +msgid ":guilabel:`Exhibition Map`: if desired, click the :guilabel:`Upload your file` button to upload an image of the event venue map." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:124 +msgid ":guilabel:`Limit Registrations`: if this checkbox is ticked, a limit to the amount of registrations is added to the event, and that desired limit amount **must** be entered in the blank field before :guilabel:`Attendees`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:127 +msgid ":guilabel:`Badge Dimension`: select a desired paper format dimension for event badges. The options are: :guilabel:`A4 foldable`, :guilabel:`A6`, or :guilabel:`4 per sheet`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:129 +msgid ":guilabel:`Badge Background`: if desired, click the :guilabel:`Upload your file` button to upload a custom background image for event badges." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:132 +msgid "When the above fields in the event form have been adequately filled in, move on to the four tabs at the bottom of the event form for further customization." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:135 +msgid "Those tabs are: :ref:`Tickets `, :ref:`Communication `, :ref:`Questions `, and :ref:`Notes `." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:142 +msgid "Tickets tab" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:144 +msgid "Create custom tickets (and ticket tiers) for events in the :guilabel:`Tickets` tab of an event form." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:-1 +msgid "A typical tickets tab on an event form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:150 +msgid "To create a ticket, click :guilabel:`Add a line` in the :guilabel:`Tickets` tab. Then, enter a name for the ticket (e.g. `Basic Ticket` or `VIP`) in the :guilabel:`Name` field." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:153 +msgid "In the :guilabel:`Product` field, either select the pre-configured :guilabel:`Event Registration` product, or create a new one by typing in the name of the new event registration product, and then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:159 +msgid "Upon installing Odoo *Events*, a new product type, *Event Ticket*, becomes available on product forms (:menuselection:`Sales --> Products --> Products`). In order for an event registration product to be selectable in the *Tickets* tab, the event registration :guilabel:`Product Type` **must** be set to :guilabel:`Event Ticket`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:165 +msgid "Existing event registration products can be modified directly from this field, as well, by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon, located beside the event registration product. Doing so reveals that product's form. If the *Inventory* application is installed, additional choices are available to customize for the product." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:170 +msgid "Next, set the registration cost of the ticket in the :guilabel:`Price` field." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:173 +msgid "The *Sales Price* defined on the event registration product's product form sets the default cost of a ticket. Modifying the :guilabel:`Price` of a ticket in the :guilabel:`Tickets` tab, sets a new registration cost of the ticket for that event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:177 +msgid "Next, determine a :guilabel:`Sales Start` and :guilabel:`Sales End` date in their respective fields. To do that, click into the blank field to reveal a calendar popover. From there, select the desired date and time, then click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:181 +msgid "Then, if desired, designate a :guilabel:`Maximum` amount of that specific ticket that can be sold." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:183 +msgid "The :guilabel:`Taken` column populates with the number of tickets that are sold." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:185 +msgid "Optionally, in the :guilabel:`Color` column, add a custom color to differentiate ticket badges. The selected color displays on ticket badges when printed." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:188 +msgid "To delete any tickets from the :guilabel:`Tickets` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding line for the ticket that should be deleted." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:192 +msgid "To add an optional :guilabel:`Description` column to the :guilabel:`Tickets` tab, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` drop-down menu, located to the far-right of the column titles." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:196 +msgid "Then, tick the checkbox beside :guilabel:`Description` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:198 +msgid "When added, the option to add brief descriptions for each event ticket appears, which can be used to inform attendees of any perks or amenities that may coincide with specific ticket purchases." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:204 +msgid "Communication tab" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:206 +msgid "In the :guilabel:`Communication` tab of an event form, create various marketing communications that can be scheduled to be sent at specific intervals leading up to, and following, the event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:-1 +msgid "Typical communication tab on an event form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:214 +msgid "By default, Odoo provides three separate pre-configured communications on every new event form. One is an email sent after each registration to confirm the purchase with the attendee. The other two are email event reminders that are scheduled to be sent at different time intervals leading up to the event to remind the recipient of the upcoming event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:219 +msgid "To add a communication in the :guilabel:`Communication` tab, click :guilabel:`Add a line`. Then, select the desired type of communication in the :guilabel:`Send` field. The options are: :guilabel:`Mail`, :guilabel:`SMS`, :guilabel:`Social Post`, or :guilabel:`WhatsApp`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:223 +msgid "There is no limit to the number of communications that can be added in the :guilabel:`Communication` tab of an event form." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:226 +msgid "To delete a communication from the :guilabel:`Communication` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding communication line. Doing so removes the communication from the event entirely." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:231 +msgid "The :guilabel:`Social Post` option **only** appears if the *Social Marketing* application is installed. The :guilabel:`WhatsApp` option **only** appears if the *WhatsApp Integration* module is installed." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:235 +msgid ":doc:`WhatsApp <../../productivity/whatsapp>` templates **cannot** be edited during active configuration. A separate approval from *Meta* is required." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:239 +msgid "Mail" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:241 +msgid "Select an existing email template from the :guilabel:`Template` drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:243 +msgid "Next, define the :guilabel:`Interval`, :guilabel:`Unit`, and :guilabel:`Trigger` from their respective drop-down fields, letting Odoo know when the communication should be sent." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:246 +msgid "The :guilabel:`Unit` options are: :guilabel:`Immediately`, :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, and :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:249 +msgid "Then, select an option from the :guilabel:`Trigger` drop-down menu. The options are: :guilabel:`After each registration`, :guilabel:`Before the event`, and :guilabel:`After the event`." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:252 +msgid "The :guilabel:`Sent` column populates with the number of sent communications. And, beside the number are different icons that appear, depending on the status of that particular communication." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:255 +msgid "The status of *Running* is represented by a :icon:`fa-cogs` :guilabel:`(three gears)` icon. The status of *Sent* is represented by a :icon:`fa-check` :guilabel:`(checkmark)` icon. And, the status of *Scheduled* is represented by an :icon:`fa-hourglass-half` :guilabel:`(hourglass)` icon." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:260 +msgid "To send a confirmation email an hour after an attendee registers for an event, configure the following communication:" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:263 +msgid ":guilabel:`Interval`: `1`" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:264 +msgid ":guilabel:`Unit`: :guilabel:`Hours`" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:265 +msgid ":guilabel:`Trigger`: :guilabel:`After each registration`" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:268 +msgid "Existing email templates can be modified directly from the :guilabel:`Template` drop-down menu, if necessary, by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon next to the template name. Doing so reveals a separate page where users can edit the :guilabel:`Content`, :guilabel:`Email Configuration`, and :guilabel:`Settings` of that particular email template." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:273 +msgid "To view and manage all email templates, activate :ref:`developer-mode` and navigate to :menuselection:`Settings --> Technical --> Email: Email Templates`. Modify with caution as email templates effect all communications where the template is used." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:280 +#: ../../content/applications/marketing/surveys/create.rst:50 +#: ../../content/applications/marketing/surveys/time_random.rst:20 +msgid "Questions tab" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:282 +msgid "In the :guilabel:`Questions` tab of an event form, users can create brief questionnaires for registrants to interact with, and respond to, after they register for the event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:285 +msgid "These questions can be focused on gathering basic information about the attendee, learning about their preferences, expectations, and other things of that nature. This information can also be used to create more detailed reporting metrics, in addition to being utilized to create specific lead generation rules." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:-1 +msgid "Typical questions tab on an event form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:295 +msgid "By default, Odoo provides three questions in the :guilabel:`Questions` tab for every event form. The default questions require the registrant(s) to provide their :guilabel:`Name` and :guilabel:`Email`, and make it optional to include their :guilabel:`Phone` number, as well." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:299 +msgid "The information gathered from the :guilabel:`Questions` tab can be found on the :guilabel:`Attendees` dashboard, accessible via the :icon:`fa-users` :guilabel:`Attendees` smart button. Odoo populates individual records that contain basic information about the registrant(s), as well as their preferences." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:304 +msgid "To add a question in the :guilabel:`Questions` tab, click :guilabel:`Add a line`. Doing so reveals a :guilabel:`Create Question` pop-up window. From here, users can create and configure their question." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:-1 +msgid "The Create Question pop-up window that appears in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:311 +msgid "First, enter the question in the field at the top of the form. Then, decide if the question should require a :guilabel:`Mandatory Answer` and/or if Odoo should :guilabel:`Ask once per order`, by ticking their respective boxes, if desired." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:315 +msgid "If the :guilabel:`Ask once per order` checkbox is ticked, the question will only be asked once, and its value is propogated to every attendee in the order (if multiple tickets are purchased at once). If the checkbox is *not* ticked for this setting, Odoo will present the question for every attendee that is connected to that registration." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:320 +msgid "Next, select a :guilabel:`Question Type` option:" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:322 +msgid ":guilabel:`Selection`: provide answer options to the question for registrants to choose from. Selectable answer options can be managed in the :guilabel:`Answers` column at the bottom of the pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:325 +msgid ":guilabel:`Text Input`: lets the users enter a custom response to the question in a text field." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:326 +msgid ":guilabel:`Name`: provides registrants with a field for them to enter their name." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:327 +msgid ":guilabel:`Email`: provides registrants with a field for them to enter their email address." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:328 +msgid ":guilabel:`Phone`: provides registrants with a field for them to enter their phone number." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:329 +msgid ":guilabel:`Company`: provides registrants with a field for them to enter a company they are associated with." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:332 +msgid "Once all the desired configurations have been entered, either click :guilabel:`Save & Close` to save the question, and return to the :guilabel:`Questions` tab on the event form, or click :guilabel:`Save & New` to save the question and immediately create a new question on a new :guilabel:`Create Question` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:337 +msgid "As questions are added to the :guilabel:`Questions` tab, the informative columns showcase the configurations of each question." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:340 +msgid "The informative columns are the following:" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:342 +msgid ":guilabel:`Title`" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:343 +msgid ":guilabel:`Mandatory`" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:344 +msgid ":guilabel:`Once per Order`" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:345 +msgid ":guilabel:`Type`" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:346 +msgid ":guilabel:`Answers` (if applicable)" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:348 +msgid "For :guilabel:`Selection` and :guilabel:`Text Input` types, a :icon:`fa-bar-chart` :guilabel:`Stats` button appears on the right side of the question line. When clicked, Odoo reveals a separate page, showcasing the response metrics to that specific question." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:352 +msgid "To delete any question from the :guilabel:`Questions` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding question line." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:355 +msgid "There is no limit to the number of questions that can be added in the :guilabel:`Questions` tab of an event form." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:361 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:363 +msgid "In the :guilabel:`Notes` tab of an event form, users can leave detailed internal notes and/or event-related instructions/information for attendees." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:-1 +msgid "Typical notes tab on an event form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:370 +msgid "In the :guilabel:`Note` field of the :guilabel:`Notes` tab, users can leave internal notes for other event employees, like \"to-do\" lists, contact information, instructions, and so on." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:373 +msgid "In the :guilabel:`Ticket Instructions` field of the :guilabel:`Notes` tab, users can leave specific instructions for people attending the event that appear on the attendees ticket." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:377 +#: ../../content/applications/marketing/events/event_essentials.rst:266 +msgid "Publish events" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:379 +msgid "Once all configurations and modifications are complete on the event form, it is time to publish the event on the website. Doing so makes the event visible to website visitors, and makes it possible for people to register for the event." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:383 +msgid "To publish an event after all the customizations are complete, click the :icon:`fa-globe` :guilabel:`Go to Website` smart button at the top of the event form. Doing so reveals the event's web page, which can be customized like any other web page on the site, via the :guilabel:`Edit` button." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:388 +msgid "To learn more about website design functionality and options, consult the :doc:`Building block <../../websites/website/web_design/building_blocks>` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:391 +msgid "Once the event website is ready to be shared, click the red :guilabel:`Unpublished` toggle switch in the header menu, changing it to a green :guilabel:`Published` switch. At this point, the event web page is published, and viewable/accessible by all website visitors." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:396 +msgid "Send event invites" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:398 +msgid "To send event invites to potential attendees, navigate to the desired event form, via :menuselection:`Events app --> Events`, and click into the desired event. Following this, click the :guilabel:`Invite` button in the upper-left corner of the event form." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:402 +msgid "Doing so reveals a blank email form to fill out, as desired. To learn more about how to create and customize emails like this, refer to the :ref:`Create an email ` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:406 +msgid "Proceed to create and customize an email message to send as an invite to potential attendees. Remember to include a link to the registration page on the event website, allowing interested recipients to quickly register." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:411 +msgid "Sending emails from Odoo is subject to a daily limit, which, by default, is 200. To learn more about daily limits, visit the :ref:`email_communication/daily_limit_mail` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:415 +#: ../../content/applications/marketing/events/event_templates.rst:217 +msgid ":doc:`event_essentials`" +msgstr "" + +#: ../../content/applications/marketing/events/create_events.rst:416 +msgid ":doc:`track_manage_talks`" +msgstr "" + #: ../../content/applications/marketing/events/event_essentials.rst:3 msgid "Event essentials" msgstr "" @@ -2160,10 +2820,6 @@ msgstr "" msgid "The :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test` options all function the same way for both :guilabel:`Mailing Type` options." msgstr "" -#: ../../content/applications/marketing/events/event_essentials.rst:266 -msgid "Publish events" -msgstr "" - #: ../../content/applications/marketing/events/event_essentials.rst:268 msgid "Until an event is published, it will remain hidden from public view on the website and registering for it will not be possible. To publish an event, navigate to it either from the backend of Odoo through the :guilabel:`Events` application, or access the hidden event page through the frontend as either a priveliged user or administrator." msgstr "" @@ -2180,6 +2836,266 @@ msgstr "" msgid "View of a website page and the option to publish the event in Odoo Events." msgstr "" +#: ../../content/applications/marketing/events/event_templates.rst:3 +msgid "Event templates" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:5 +msgid "The Odoo *Events* application provides the ability to customize and configure event templates, which can be used to expedite the event-creation process." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:8 +msgid "These templates can be created and personalized in the application, and then selected from an event form, in order to quickly apply a series of settings and elements to the new event, all of which can be further modified, if needed." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:13 +msgid "Event templates page" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:15 +msgid "In the Odoo *Events* application, event templates can quickly be created and modified." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:17 +msgid "To begin, navigate to :menuselection:`Events app --> Configuration --> Event Templates`. Doing so reveals the :guilabel:`Event Templates` page. Here, find all the existing event templates in the database." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:-1 +msgid "The Event Templates page in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:25 +msgid "By default, Odoo provides three pre-configured event templates: :guilabel:`Exhibition`, :guilabel:`Training`, and :guilabel:`Sport`, which all have their own unique customizations applied to them." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:29 +msgid "To change how these event templates appear on the *Template* drop-down field on an event form, drag-and-drop them into any desired order, using the :icon:`oi-draggable` :guilabel:`(draggable)` icon, located to the left of each event template line on the :guilabel:`Event Templates` page." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:34 +msgid "To learn more about event forms, refer to the :doc:`create_events` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:37 +msgid "Create event template" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:39 +msgid "There are two ways to create and configure an event template in Odoo *Events*." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:41 +msgid "**On the dashboard**, by navigating to :menuselection:`Events app --> Configuration --> Event Templates` and clicking the :guilabel:`New` button in the upper-left corner. Doing so reveals a blank event template form that can be customized in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:44 +msgid "**On an event form itself**. Start by typing the name of a new event template in the *Template* field, and click :guilabel:`Create and edit...` from the resulting drop-down menu. Doing so reveals a *Create Template* pop-up window, featuring all the same configurable fields and elements found on a standard event template form." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:50 +msgid "Clicking :guilabel:`Create \"[template name]\"` from the resulting drop-down menu, via the *Template* field on an event form creates the event template in the database, but does **not** present the user with the *Create Template* pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:54 +msgid "The event template would have to be modified, by selecting it on the *Event Templates* page (:menuselection:`Events app --> Configuration --> Event Templates`)." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:58 +msgid "Event template form" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:60 +msgid "All the fields on a standard :guilabel:`Event Template` form are *also* on the *Create Template* pop-up window, accessible via the *Template* field on an event form." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:-1 +msgid "A standard event template form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:67 +msgid "Start by providing the event template with a name in the :guilabel:`Event Template` field, located at the top of the form." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:70 +msgid "Beneath that field, there is a series of selectable checkboxes, all of which are related to how the event menu will be displayed on the event web page." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:73 +msgid ":guilabel:`Website Submenu`: enables a submenu on the event's website. When this checkbox is ticked, every other checkbox in this series is automatically ticked, as well. Then, choose to untick (deselect) any of the checkbox options, as desired." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:76 +msgid ":guilabel:`Tracks Menu Item`: adds a submenu item to navigate to a page displaying all planned tracks for the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:78 +msgid ":guilabel:`Track Proposals Menu Item`: adds a submenu item to navigate to a page, in which visitors can fill out a form to propose a track (talk, lecture, presentation, etc.) to happen during the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:81 +msgid ":guilabel:`Booth Menu Item`: adds a submenu item that takes visitors to a separate page, where an event booth can be purchased. Event booths can be customized and configured in the :guilabel:`Booths` tab of the event template form, from the *Booth Categories* page (:menuselection:`Events app --> Configuration --> Booth Categories`)." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:87 +msgid "First, users **must** create a booth product with the required *Event Booth* option set as the :guilabel:`Product Type` on the product form." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:90 +msgid ":guilabel:`Exhibitors Menu Item`: adds a submenu item that takes visitors to a separate page, showcasing all the exhibitors related to that specific event. Icons representing those exhibitors are also found on the footer of every event-specific web page, as well." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:93 +msgid ":guilabel:`Community`: adds a submenu item allowing attendees to access pre-configured virtual community rooms to meet with other attendees, and discuss various topics related to the event. When this checkbox is ticked, the :guilabel:`Allow Room Creation` feature becomes available." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:96 +msgid ":guilabel:`Allow Room Creation`: allow visitors to create community rooms of their own." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:97 +msgid ":guilabel:`Register Button`: adds a button at the end of the event submenu that takes visitors to the event-specific registration page when clicked." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:100 +msgid "Once the desired checkboxes have been ticked, select an appropriate :guilabel:`Timezone` for the event from the available drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:103 +msgid "Then, for organizational purposes, there is the option to add :guilabel:`Tags` to this event template." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:106 +msgid "There is also the option to :guilabel:`Limit Registrations` to this specific event template by ticking that checkbox. If ticked, proceed to enter the number of :guilabel:`Attendees` this template should be limited to." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:110 +msgid "Beneath those general information fields at the top of the event template form, there are five tabs:" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:112 +msgid ":ref:`Tickets `" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:113 +msgid ":ref:`Communication `" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:114 +msgid ":ref:`Booths `" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:115 +msgid ":ref:`Questions `" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:116 +msgid ":ref:`Notes `" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:121 +msgid "Booths tab" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:123 +msgid "The :guilabel:`Booths` tab on an event template form is the only tab that differentiates itself from a standard event form, where the other tabs (:guilabel:`Tickets`, :guilabel:`Communication`, :guilabel:`Questions`, and :guilabel:`Notes`) are present and configured using the same process. For more information about those tabs, refer to the :doc:`create_events` documentation." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:129 +msgid "To create a booth or booth category, an event booth product **must** be created in the database first, with the *Product Type* set to *Event Booth*. **Only** products with that specific configuration can be selected in the required *Product* field of a booth or booth category form." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:134 +msgid "Event booths can be created and customized in two ways in the Odoo *Events* application. Either in the :guilabel:`Booths` tab of an event template form, or by navigating to :menuselection:`Events app --> Configuration --> Booth Categories`, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:138 +msgid "To add a booth from the :guilabel:`Booths` tab of an event template form, click :guilabel:`Add a line`. Doing so reveals a blank :guilabel:`Create Booths` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:-1 +msgid "A Create Booths pop-up window in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:145 +msgid "Start by providing a :guilabel:`Name` for this booth in the corresponding field at the top of the pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:148 +msgid "Then, select an appropriate :guilabel:`Booth Category` from the drop-down field below. Booth categories can be created and modified from the *Booth Categories* page in the *Events* application, which is accessible by navigating to :menuselection:`Events app --> Configuration --> Booth Categories`." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:154 +msgid "A :guilabel:`Booth Category` can be created directly from this field on the :guilabel:`Create Booths` pop-up window. To accomplish that, type the name of the new booth category in the :guilabel:`Booth Category` field, and select either :guilabel:`Create` or :guilabel:`Create and edit...` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:159 +msgid "Clicking :guilabel:`Create` merely creates the category, which can (and should be) customized at a later date. Clicking :guilabel:`Create and edit...` reveals a new :guilabel:`Create Booth Category` pop-up window, from which the category can be configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:-1 +msgid "The Create Booth Category pop-up window in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:167 +msgid "From this pop-up window, proceed to name the :guilabel:`Booth Category`, modify its :guilabel:`Booth Details` settings, configure its :guilabel:`Sponsorship` options (if applicable), and leave an optional :guilabel:`Description` to explain any pertinent details related to this specific category of booths." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:172 +msgid "There is also the option to add a photo/visual representation of the booth category, via the :guilabel:`(camera)` icon in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:175 +msgid "When all desired configurations are complete, click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:177 +msgid "The same configurations and options are available by navigating to :menuselection:`Events app --> Configuration --> Booth Categories`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:180 +msgid "Once the desired :guilabel:`Booth Category` is selected, the remaining fields on the :guilabel:`Create Booths` pop-up window (:guilabel:`Currency`, :guilabel:`Product`, and :guilabel:`Price`) autopopulate, based on information configured for that selected :guilabel:`Booth Category`." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:186 +msgid "These fields **cannot** be modified from the :guilabel:`Create Booths` pop-up window. They can only be modified from the specific booth category form page." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:189 +msgid "When all desired configurations are complete, click :guilabel:`Save & Close` to save the booth, and return to the event template form. Or, click :guilabel:`Save & New` to save the booth, and start creating another booth on a fresh :guilabel:`Create Booths` pop-up window. Click :guilabel:`Discard` to remove all changes, and return to the event template form." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:194 +msgid "Once the booth has been saved, it appears in the :guilabel:`Booths` tab on the event template form." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:197 +msgid "Use event templates" +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:199 +msgid "Once an event template is complete, it is accessible on all event forms in the Odoo *Events* application." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:202 +msgid "To use an event template, navigate to the :menuselection:`Events app` and click :guilabel:`New` to open a new event form." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:205 +msgid "From the event form, click the :guilabel:`Template` field to reveal all the existing event templates in the database. They appear in the same order as they are listed in on the *Event Templates* page (:menuselection:`Events app --> Configuration --> Event Templates`)." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:209 +msgid "Select the desired event template from the :guilabel:`Template` drop-down field on the event form. Pre-configured settings automatically populate the event form, saving time during the event creation process." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:213 +msgid "Any of these pre-configured settings related to the selected event template chosen in the :guilabel:`Template` field on an event form can be modified, as desired." +msgstr "" + +#: ../../content/applications/marketing/events/event_templates.rst:218 +msgid ":doc:`create_events`" +msgstr "" + #: ../../content/applications/marketing/events/sell_tickets.rst:3 msgid "Sell tickets" msgstr "" @@ -5793,11 +6709,6 @@ msgstr "" msgid "Below those fields and options are four tabs: :guilabel:`Questions`, :guilabel:`Options`, :guilabel:`Description`, and :guilabel:`End Message`." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:50 -#: ../../content/applications/marketing/surveys/time_random.rst:20 -msgid "Questions tab" -msgstr "" - #: ../../content/applications/marketing/surveys/create.rst:52 msgid "View, access, add, and/or delete questions and sections to the survey in the :guilabel:`Questions` tab." msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index d0dbd97bb..56d75d48e 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -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 \n" "Language-Team: LANGUAGE \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 `. 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 ` 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 `, click :guilabel:`New Spreadsheet`. You can select a :guilabel:`Blank spreadsheet` or an :doc:`existing template `." 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 ` 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 "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index f5a444bbd..a42b67c7e 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -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 \n" "Language-Team: LANGUAGE \n" @@ -46,7 +46,7 @@ msgid "*Leads* act as a qualifying step before an opportunity is created. This p msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:13 #: ../../content/applications/sales/crm/optimize/gamification.rst:10 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:27 #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 @@ -181,239 +181,295 @@ msgstr "" msgid "Some filters may need to be removed from the :guilabel:`Search...` bar on the top :guilabel:`Pipeline` page to view all opportunities." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3 -msgid "Generate leads/opportunities" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:3 +msgid "Create leads (from email or manually)" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:5 -msgid "Two key ways to generate new leads or opportunities for your business are through email aliases and website contact forms. Odoo automatically creates leads in your CRM whenever someone sends a message to a Sales Team email alias or fills out a contact form on your website." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:8 +msgid "Leads can be added to the *CRM* app from custom email aliases, and by manually creating new records. This is in addition to the leads and opportunities created in the app through the :doc:`website contact form `." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:10 +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:12 +msgid "First, ensure the *Leads* feature is enabled in the database by navigating to :menuselection:`CRM app --> Configuration --> Settings`. Tick the :guilabel:`Leads` checkbox, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:17 msgid "Configure email aliases" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:12 -msgid "Each Sales Team can use its own unique email alias to generate leads/opportunities. Any email sent to a Sales Team's email alias will automatically create a lead (if leads are activated in your CRM settings) or an opportunity in the pipeline for that particular team. Configure custom email aliases on the configuration page for each Sales Team by navigating to :menuselection:`CRM --> Configuration --> Sales Teams`." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:19 +msgid "Each sales team has the option to create and utilize their own unique email alias. When messages are sent to this address, a lead (or opportunity), is created with the information from the message." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 -msgid "Configuring Sales Teams" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:23 +msgid "To create or update a sales teams' email alias, navigate to :menuselection:`CRM app --> Configuration --> Sales Teams`. Click on a team from the list to open the team's details page." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:23 -msgid "Use Contact Forms on your website" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:-1 +msgid "The sales team details page, focused on the email alias section." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:25 -msgid "By default, your website's *Contact Us* page displays Odoo's ready-to-use Contact Form. Whenever someone submits this form, a lead or an opportunity is generated in your database." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:30 +msgid "In the :guilabel:`Email Alias` field, enter a name for the email alias, or edit the existing name. In the :guilabel:`Accept Emails From` field, use the drop-down menu to choose who is allowed to send messages to this email alias:" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 -msgid "Default Contact Us page" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:34 +msgid ":guilabel:`Everyone`: messages are accepted from any email address." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:32 -msgid "The Contact Form can be activated or deactivated at any time by going to :menuselection:`Website --> Go to Website --> Customize --> Contact Form`." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:35 +msgid ":guilabel:`Authenticated Partners`: only accepts messages from email addresses associated with a a partner (contact or customer) record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 -msgid "Contact Form toggle" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:37 +msgid ":guilabel:`Followers only`: only accepts messages from those who are following a record related to the team, such as a lead or opportunity. Messages are also accepted from team members." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:39 -msgid "When the Form is deactivated, the *Contact Us* page simply displays a button to email your company directly. Any email sent this way will generate a lead/opportunity." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:39 +msgid ":guilabel:`Authenticated Employees`: only accepts messages from email addresses that are connected to a record in the *Employees* app." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 -msgid "Contact Us Page using email" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:43 +msgid "Leads created from email" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:46 -msgid "Choose which Sales Team or salesperson is automatically assigned to the leads/opportunities created from the Contact Form by going to :menuselection:`Website --> Configuration --> Settings --> Communication`." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:45 +msgid "Leads created from email alias messages can be viewed by navigating to :menuselection:`CRM app --> Leads`. Click a lead from the list to open it, and view the details." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 -msgid "Contact Form settings" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:48 +msgid "The email received by the alias is added to the *chatter* thread for the lead. The subject line of the message is added to the title field, and the :guilabel:`Email` field is updated with the contact's email address." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:55 -msgid "Customize Contact Forms" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:-1 +msgid "The chatter thread of a newly created lead in the CRM app." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:57 -msgid "Contact Forms can be customized for the specific information your team needs, using the free *Form Builder* module." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:57 +msgid "If the *leads* feature is **not** enabled on the database, messages to the email alias are added to the database as opportunities." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:60 -msgid "The *Form Builder* module is installed automatically when a Form element is added to a web page via the Website Builder. It can also be installed manually from the :guilabel:`Apps` page." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:61 +msgid ":doc:`../../../general/email_communication/email_servers`" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 -msgid "Form Builder building blocks" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:64 +msgid "Manually create leads" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:68 -msgid "Forms can be created from scratch to serve a wide variety of purposes. However, Odoo's default *Contact Us* page is designed to fit most users' needs. Start with the default form and modify from there." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:66 +msgid "Leads can be added directly to the *CRM* app by manually creating a new record. Navigate to :menuselection:`CRM app --> Leads` to view a list of existing leads." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:73 -msgid "Edit Contact Form fields" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:70 +msgid "Leads can also be added via the :doc:`Generate Leads ` button." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:75 -msgid "In Edit mode on your website, click on any field to start editing it. The following information can be edited for each field on the Contact Form:" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:72 +msgid "At the top-left of the list, click :guilabel:`New` to open a blank :guilabel:`Leads` form." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:78 -msgid ":guilabel:`Type`: Choose a custom field option or an existing field. Examples include phone, file upload, language, etc." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:74 +msgid "In the first field of the new form, enter a title for the new lead. Next, enter a :guilabel:`Contact Name`, and a :guilabel:`Company Name`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:80 -msgid ":guilabel:`Input Type`: Determine the type of entry customers should input. Available options are text,email, telephone, and URL." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:78 +msgid "If a lead is :doc:`converted to an opportunity `, the :guilabel:`Company Name` field is used to either link this opportunity to an existing customer, or to create a new customer." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:82 -msgid ":guilabel:`Input Placeholder`: Type in an example to guide users how to input information where formatting is important, such as a phone number or email address." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:82 +msgid "Manually create opportunities" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:84 -msgid ":guilabel:`Label Name`: Type in the display name to show users what information is needed from them." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:84 +msgid "To manually create an opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`. At the top-left of the page, click :guilabel:`New` to create a new opportunity Kanban card. In the :guilabel:`Organization/Contact` field, enter the name of the company the opportunity is for." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:86 -msgid ":guilabel:`Label Position`: Choose the way the label is aligned with the rest of the form. The label can be hidden, above the field, to the far left of the field, or right adjusted and closer to the field." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:88 +msgid "Choose a name, and enter it in the :guilabel:`Opportunity` field. *This is a required field.* When manually creating an opportunity, it is helpful to add a name that relates to the details of the opportunity." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:89 -msgid ":guilabel:`Required`: Toggle this option for information that you absolutely need entered." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:93 +msgid "In the example below, the opportunity is named `5 VP Chairs`. This identifies the product the customer is interested in, as well as the potential number of products." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:90 -msgid ":guilabel:`Hidden`: Toggle this option to hide the field without deleting it." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:0 +msgid "An example of an opportunity in the CRM pipeline." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:91 -msgid ":guilabel:`Shown on Mobile`: Toggle this option to show the field to users on mobile devices." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:100 +msgid "Enter the contact information for the opportunity in the :guilabel:`Email` and :guilabel:`Phone` fields." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:-1 -msgid "Editable field options" +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:103 +msgid "In the :guilabel:`Expected Revenue` field, enter an estimated value for the opportunity." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:97 -msgid "By default, when a Form is submitted, it sends you an email with the customer's inputted information. To have it automatically generate a lead/opportunity instead, edit the Form and select :guilabel:`Create an Opportunity` as the Action." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:106 +msgid "The information in the :guilabel:`Expected Revenue` and priority fields can be used to track performance for individual salespeople, and on a team basis. See :doc:`../performance/expected_revenue_report` and :doc:`../track_leads/lead_scoring` for more information." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:102 -msgid "If leads are activated in your CRM settings, selecting :guilabel:`Create an Opportunity` generates a lead instead. To learn more about activating leads in the CRM settings, head over to :doc:`convert`." +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:111 +msgid "Then, use the |st-o| :guilabel:`(star)` icons to assign a priority." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:113 +msgid "|st-o| |st-o| |st-o|: low priority" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:114 +msgid "|st| |st-o| |st-o|: medium priority" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:115 +msgid "|st| |st| |st-o|: high priority" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:116 +msgid "|st| |st| |st|: very high priority" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:119 +msgid "Assigning a priority changes the order of leads in Kanban view, with higher priority leads displayed first." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:122 +msgid "Once all the necessary information has been entered, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:-1 +msgid "The CRM pipeline with a newly created opportunity." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:3 msgid "Lead mining" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:5 -msgid "Lead mining is a feature that allows CRM users to generate new leads directly into their Odoo database. To ensure lead qualification, lead mining output is determined by a variety of filtering criteria, such as the country, the company size, and the industry." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:8 +msgid "*Lead mining* is a feature that allows *CRM* users to generate new leads directly into their Odoo database. To ensure lead qualification, lead mining output is determined by a variety of filtering criteria, such as the country, the company size, and the industry." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:12 -msgid "To get started, go to :menuselection:`CRM --> Configuration --> Settings` and activate :guilabel:`Lead Mining`." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:15 +msgid "To get started, go to :menuselection:`CRM app --> Configuration --> Settings`, and tick the :guilabel:`Lead Mining` checkbox to activate the feature. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 msgid "Activate lead mining in Odoo CRM settings." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:20 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:23 msgid "Generate leads" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:22 -msgid "After the :guilabel:`Lead Mining` setting is activated, a new button called :guilabel:`Generate Leads` is available to use in the :guilabel:`CRM` pipeline. Lead mining requests are also available through :menuselection:`CRM --> Configuration --> Lead Mining Requests`, or through :menuselection:`CRM --> Leads --> Leads` where the :guilabel:`Generate Leads` button is also available." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:25 +msgid "After the *Lead Mining* setting is activated, a new button called *Generate Leads* is available to use in the upper-left corner of the *CRM* *Pipeline* (:menuselection:`CRM app --> Sales --> My Pipeline`)." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:29 +msgid "Lead mining requests are also available through :menuselection:`CRM app --> Configuration --> Lead Mining Requests`, or through :menuselection:`CRM app --> Leads --> Leads`, where the :guilabel:`Generate Leads` button is also available." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 msgid "The Generate Leads button to use the lead mining feature." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:32 -msgid "Click on the :guilabel:`Generate Leads` button, and a window will appear offering a variety of criteria by which to generate leads." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:37 +msgid "Click the :guilabel:`Generate Leads` button, and a pop-up window appears, offering a variety of criteria by which to generate leads." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 msgid "The pop-up window with the selection criteria in order to generate leads in Odoo." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:39 -msgid "Choose to generate leads for :guilabel:`Companies` to get company information only, or choose :guilabel:`Companies and their Contacts` to get company information as well as individual employee contact information. When targeting :guilabel:`Companies and their Contacts`, there is an option to filter contacts based on :guilabel:`Role` or :guilabel:`Seniority`." -msgstr "" - #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:44 -msgid "Additional filtering options include:" -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:46 -msgid ":guilabel:`Size`: filter leads based on the number of employees at the company" -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:47 -msgid ":guilabel:`Countries`: filter leads based on the country (or countries) they are located in" +msgid "Choose to generate leads for :guilabel:`Companies` to get company information only, or choose |CC| to get company information and individual employee contact information." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:48 -msgid ":guilabel:`States`: further filter leads based on the state they are located in, if applicable" -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:49 -msgid ":guilabel:`Industries`: filter leads based on the specific industry they work in" -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:50 -msgid ":guilabel:`Sales Team`: choose which Sales Team the leads will be assigned to" +msgid "When targeting |CC|, additional options are available to filter contacts based on :guilabel:`Role` or :guilabel:`Seniority`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51 -msgid ":guilabel:`Salesperson`: choose which person(s) on the Sales Team the leads will be assigned to" +msgid "Additional filtering options include the following:" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:52 -msgid ":guilabel:`Default Tags`: choose which tags are applied directly to the leads once found" +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:53 +msgid ":guilabel:`Countries`: filter leads based on the country (or countries) they are located in." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:55 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:54 +msgid ":guilabel:`States`: further filter leads based on the state in which they are located, if applicable." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:56 +msgid ":guilabel:`Industries`: filter leads based on the specific industry they work in." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:57 +msgid ":guilabel:`Filter on Size`: tick this checkbox to specify the number of employees at the company. This generates a field labeled :guilabel:`Size`. Fill in the blanks to create a range for the desired company size." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:60 +msgid ":guilabel:`Sales Team`: choose which Sales Team the leads will be assigned to." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:61 +msgid ":guilabel:`Salesperson`: choose which member of the Sales Team the leads will be assigned to." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:62 +msgid ":guilabel:`Default Tags`: choose which tags are applied directly to the leads once found." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:65 msgid "Make sure to be aware of the latest EU regulations when receiving contact information. Get more information about the General Data Protection Regulation on `Odoo GDPR `_." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:59 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:69 +msgid "View leads" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:71 +msgid "After leads are generated, they are assigned to the designated salesperson and team. To view additional information regarding the lead, select one from the list, and click to open it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:74 +msgid "In the chatter thread for the lead, additional information is provided. This can include the number of employees, the technology used by the company, the timezone, and direct contact information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 +msgid "The chatter thread of a newly generated lead." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:82 +msgid "If :guilabel:`Leads` are **not** enabled for the database, then leads are generated as *opportunities*, and added to the pipeline for the designated salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:85 +msgid "To enable the :guilabel:`Leads` feature, navigate to :menuselection:`CRM app --> Configuration --> Settings`, and tick the :guilabel:`Leads` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:89 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:94 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:61 #: ../../content/applications/sales/rental.rst:88 msgid "Pricing" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:61 -msgid "Lead mining is an *In-App Purchase* feature and each generated lead costs one credit." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:91 +msgid "Lead mining is an *In-App Purchase* feature, and each generated lead costs one :ref:`credit `." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:63 -msgid "Choosing to generate :guilabel:`Companies and their Contacts` costs one additional credit for each contact generated." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:95 +msgid "Generating |CC| costs one additional credit for each contact generated. See here for complete pricing information: `Lead Generation by Odoo IAP `_." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:67 -msgid "See here for full pricing information: `Lead Generation by Odoo IAP `_." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:99 +msgid "To buy credits, navigate to :menuselection:`CRM app --> Configuration --> Settings`. In the :guilabel:`Lead Generation` section, under the :guilabel:`Lead Mining` feature, click :guilabel:`Buy Credits`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:70 -msgid "To buy credits, navigate to :menuselection:`CRM --> Configuration --> Settings`. In the :guilabel:`Lead Generation` section, under the :guilabel:`Lead Mining` feature, click on :guilabel:`Buy Credits`." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 -msgid "Buy credits from the lead mining settings." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:78 -msgid "Credits may also be purchased by navigating to the :menuselection:`Settings --> General Settings`. In the :guilabel:`In-App Purchases` section, under the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:103 +msgid "Credits may also be purchased by navigating to the :menuselection:`Settings app`. In the :guilabel:`Contacts` section, under the :guilabel:`Odoo IAP` feature, click :guilabel:`View My Services`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 @@ -421,16 +477,175 @@ msgstr "" msgid "Buy credits in the Odoo IAP settings." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:87 -#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:16 -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:78 -msgid "Enterprise Odoo users with a valid subscription get free credits to test :abbr:`IAP (In-App Purchase)` features before deciding to purchase more credits for the database. This includes demo/training databases, educational databases, and one-app-free databases." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:112 +msgid "Enterprise Odoo users with a valid subscription get free credits to test |IAP| features before purchasing more credits for the database. This includes demo/training databases, educational databases, and one-app-free databases." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:117 msgid ":doc:`/applications/essentials/in_app_purchase`" msgstr "" +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:3 +msgid "Create opportunities from web contact forms" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:5 +msgid "Adding a contact form to a website makes it easy to convert visitors into leads and opportunities. After a visitor submits their information, an opportunity can be created automatically, and assigned to a designated sales team and salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:12 +msgid "Customize contact forms" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:14 +msgid "By default, the *Contact Us* page on an Odoo website displays a preconfigured contact form. This form can be customized, as needed, to suit the needs of a specific sales team." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:17 +msgid "Navigate to :menuselection:`Website app --> Contact Us`, then click :guilabel:`Edit` in the top-right of the screen to open the web editor. Click on the form building block in the body of the webpage to open the form configuration settings on the right sidebar. The following options are available to customize the contact form from the :guilabel:`From` section of the right sidebar:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:-1 +msgid "The form configuration settings on an Odoo website." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:26 +msgid ":guilabel:`Action`: the default action for a contact form is :guilabel:`Send an Email`. Select :guilabel:`Create an Opportunity` from the drop-down list to capture the information in the *CRM* app." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:29 +msgid ":guilabel:`Sales Team`: choose a sales team from the drop-down menu that the opportunities from this form should be assigned to. This field **only** appears if the :guilabel:`Action` field is set to :guilabel:`Create an Opportunity`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:32 +msgid ":guilabel:`Salesperson`: if the opportunities should be assigned to a specific salesperson, select them from the drop-down menu. If no selection is made in this field, the opportunities are assigned based on the team's existing rules." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:35 +msgid ":guilabel:`Marked Fields`: use this field to alter how the form handles marked fields. The default option is to treat marked fields as :guilabel:`Required`, which is the recommended setting." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:37 +msgid ":guilabel:`Mark Text`: choose how :guilabel:`Marked Fields` should be identified. The default character is an asterisk (`*`)." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:39 +msgid ":guilabel:`Labels Width`: use this field to alter the pixel width of the labels, if desired." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:40 +msgid ":guilabel:`On Success`: select how the webpage reacts after a customer successfully submits a form. :guilabel:`Nothing` keeps the customer on the same screen, with the addition of a confirmation message that the form was submitted successfully. :guilabel:`Redirect` sends the customer to a new webpage, based on the address provided in the :guilabel:`URL` field below. :guilabel:`Show Message` replaces the form with a preconfigured message that informs the customer someone should respond to them as soon as possible." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:46 +msgid ":guilabel:`URL`: if :guilabel:`Redirect` is selected in the :guilabel:`On Success` field, enter the URL for the webpage, where customers should be directed after successfully submitting a form." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:48 +msgid ":guilabel:`Visibility`: use the drop-down menu to add any visibility conditions for this field, if desired." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:52 +msgid "If *leads* are activated in *CRM* settings, selecting :guilabel:`Create an Opportunity` generates a lead instead. To activate leads, navigate to :menuselection:`CRM app --> Configuration --> Settings`, and tick the :guilabel:`Leads` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:57 +msgid "Customize contact form fields" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:59 +msgid "In addition to the settings for the form, the settings for each field can be customized, as well. With the web editor menu still open, click into a field to open the :guilabel:`Field` configuration settings section on the sidebar. The following options are available to customize a field:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:63 +msgid ":guilabel:`Type`: choose a custom field option or an existing field type." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:64 +msgid ":guilabel:`Input Type`: determine the type of information customers should input. Available options are :guilabel:`Text`, :guilabel:`Email`, :guilabel:`Telephone`, or :guilabel:`Url`. The selection made in this field limits the format that customers can use when entering information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:67 +msgid ":guilabel:`Label`: enter the name for the field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:68 +msgid ":guilabel:`Position`: choose the way the label is aligned with the rest of the form. The label can be hidden, above the field, to the left of the field, or right adjusted and closer to the field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:70 +msgid ":guilabel:`Description`: slide the toggle to add a description for the field, which can provide additional instructions to customers. Click under the field on the form to add the description." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:72 +msgid ":guilabel:`Placeholder`: enter an example to help users know how to input information where formatting is important, such as a phone number or email address." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:74 +msgid ":guilabel:`Default Value`: enter a value to include in the form, by default, if the customer does not provide information in the field. *It is not recommended to include a default value for required fields*." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:77 +msgid ":guilabel:`Required`: slide the toggle to mark this field as required if it **must** be filled in for every submission." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:79 +msgid ":guilabel:`Visibility`: select when this field should be visible. Use the button on the left to choose whether to show or hide this field on a desktop users. Use the button on the right to choose whether to show or hide this field to mobile users." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:82 +msgid ":guilabel:`Animation`: select if this field should have any animation." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:-1 +msgid "The field configuration settings on an Odoo website." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:89 +msgid "View opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:91 +msgid "After a customer submits a contact form, and an opportunity is created, it is assigned based on the :ref:`form settings `. To view opportunities, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:96 +msgid "If leads are activated on the database, contact form submissions are generated as leads, not opportunities. To activate leads, navigate to :menuselection:`CRM app --> Configuration --> Settings`, and tick the :guilabel:`Leads` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:100 +msgid "Navigate to :menuselection:`CRM app --> Leads` to view the newly-created leads." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:102 +msgid "On the :guilabel:`My Pipeline` dashboard, click on an opportunity card in the Kanban view to open the opportunity record. The information submitted by the customer is visible on the opportunity record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:107 +msgid "As the contact form fields are customizable, the fields on the opportunity record, where the form information is stored, varies accordingly." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:110 +msgid "If the preconfigured contact form is used, the *Subject* field is added to the :guilabel:`Title` field, and the content in the :guilabel:`Notes` field, which is labeled as :guilabel:`Your Question`, is added to the :guilabel:`Internal Notes` tab." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:115 +msgid ":doc:`../pipeline/manage_sales_teams`" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:116 +msgid ":doc:`convert`" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:117 +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:109 +msgid ":doc:`../track_leads/lead_scoring`" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/opportunities_form.rst:118 +msgid ":ref:`Website forms `" +msgstr "" + #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:3 msgid "Create and send quotations" msgstr "" @@ -695,14 +910,10 @@ msgid "In Odoo's *CRM* app, *gamification tools* provide the opportunity to eval msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:12 -msgid "To install the *Gamification* module, navigate to the :menuselection:`Apps` application. Click into the :guilabel:`Search...` bar at the top of the page and remove the :guilabel:`Apps` filter. Type `Gamification` to search." +msgid "To install the *CRM Gamification* module, navigate to the :menuselection:`Apps` application. Click into the :guilabel:`Search...` bar at the top of the page and remove the :guilabel:`Apps` filter. Type `CRM Gamification` to search." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:16 -msgid "If the :guilabel:`Gamification` module is **not** already installed, click :guilabel:`Install`. After completing the installation, return to the :menuselection:`Apps` application and search for `Gamification` again." -msgstr "" - -#: ../../content/applications/sales/crm/optimize/gamification.rst:20 msgid "On the :guilabel:`CRM Gamification` module, click :guilabel:`Install`. This module features goals and challenges related to the *CRM* and *Sales* applications." msgstr "" @@ -710,31 +921,31 @@ msgstr "" msgid "View of the gamification module being installed in Odoo." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:28 -msgid "If both the *CRM* and *Sales* apps are installed, the *CRM Gamification* module is automatically installed on the database." +#: ../../content/applications/sales/crm/optimize/gamification.rst:24 +msgid "If **both** the *CRM* and *Sales* apps are installed, the *CRM Gamification* module is automatically installed on the database." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:31 +#: ../../content/applications/sales/crm/optimize/gamification.rst:27 msgid "To access the *Gamification Tools* menu, first enable :ref:`developer-mode`." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:33 +#: ../../content/applications/sales/crm/optimize/gamification.rst:29 msgid "Next, navigate to :menuselection:`Settings app --> Gamification Tools`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:-1 -msgid "View if the gamification tools menu in Odoo Settings" +msgid "View if the gamification tools menu in Odoo Settings." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:42 +#: ../../content/applications/sales/crm/optimize/gamification.rst:38 msgid "Create badges" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:44 +#: ../../content/applications/sales/crm/optimize/gamification.rst:40 msgid "*Badges* are awarded to users when they have completed a challenge. Different badges can be awarded based on the type of task completed, and can be issued to more than one user, depending on the time they accomplish the goal." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:48 +#: ../../content/applications/sales/crm/optimize/gamification.rst:44 msgid "To view the existing badges, or create a new one, navigate to :menuselection:`Settings --> Gamification Tools --> Badges`." msgstr "" @@ -742,39 +953,39 @@ msgstr "" msgid "View of the badges page in Odoo." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:56 +#: ../../content/applications/sales/crm/optimize/gamification.rst:52 msgid "Some badges can be awarded outside of challenges, as well. Select the Kanban card for the desired badge, then click :guilabel:`Grant`. This opens a :guilabel:`Grant Badge` pop-up window. Select a user from the :guilabel:`Who would you like to reward?` field." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:60 +#: ../../content/applications/sales/crm/optimize/gamification.rst:56 msgid "Add any additional information regarding why the user is receiving the reward in the field below, then click :guilabel:`Grant Badge`." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:63 +#: ../../content/applications/sales/crm/optimize/gamification.rst:59 msgid "To create a new badge, click :guilabel:`New` at the top-left of the page to open a blank form. Enter a name for the :guilabel:`Badge`, followed by a description." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:66 +#: ../../content/applications/sales/crm/optimize/gamification.rst:62 msgid "The :guilabel:`Allowance to Grant` field determines when a badge can be granted, and by whom:" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:68 +#: ../../content/applications/sales/crm/optimize/gamification.rst:64 msgid ":guilabel:`Everyone`: this badge can be manually granted by any user." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:69 +#: ../../content/applications/sales/crm/optimize/gamification.rst:65 msgid ":guilabel:`A selected list of users`: this badge can only be granted by a select group of users. If this option is selected, it generates a new field, :guilabel:`Authorized Users`. Choose the appropriate users from this drop-down list." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:72 +#: ../../content/applications/sales/crm/optimize/gamification.rst:68 msgid ":guilabel:`People having some badges`: this badge can only be granted by users who have already been awarded a specific badge. If this option is selected it generates a new field, :guilabel:`Required Badges`. Use this drop-down list to select the badge(s) a user must have before they can award this badge to others." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:76 +#: ../../content/applications/sales/crm/optimize/gamification.rst:72 msgid ":guilabel:`No one, assigned through challenges`: this badge cannot be manually granted, it can only be awarded through challenges." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:79 +#: ../../content/applications/sales/crm/optimize/gamification.rst:75 msgid "To limit the number of badges a user can send, tick the :guilabel:`Monthly Limited Spending` checkbox. This sets a limit on the number of times a user can grant this badge. In the :guilabel:`Limitation Number` field, enter the maximum number of times this badge can be sent per month, per person." msgstr "" @@ -782,83 +993,95 @@ msgstr "" msgid "The details page for a new badge." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:91 +#: ../../content/applications/sales/crm/optimize/gamification.rst:87 msgid "Create a challenge" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:93 +#: ../../content/applications/sales/crm/optimize/gamification.rst:89 msgid "To create a challenge, navigate to to :menuselection:`Settings --> Gamification Tools --> Challenges`. Click :guilabel:`New` in the top-left corner to open a blank challenge form." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:96 +#: ../../content/applications/sales/crm/optimize/gamification.rst:92 msgid "At the top of the form, enter a :guilabel:`Challenge Name`." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:99 +#: ../../content/applications/sales/crm/optimize/gamification.rst:95 msgid "Create assignment rules" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:101 +#: ../../content/applications/sales/crm/optimize/gamification.rst:97 msgid "To assign the challenge to specific users, one or more assignment rules must be utilized." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:103 +#: ../../content/applications/sales/crm/optimize/gamification.rst:99 msgid "Click into the first field under :guilabel:`Assign Challenge to`, and select a parameter from the drop-down list to define the rule. Then, click into the next field to define the rule's operator. If necessary, click into the third field to further define the parameter." msgstr "" +#: ../../content/applications/sales/crm/optimize/gamification.rst:104 +msgid "To include all users with permissions in the *Sales* app, create a rule with the following parameters:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:107 +msgid ":guilabel:`Groups`" +msgstr "" + #: ../../content/applications/sales/crm/optimize/gamification.rst:108 -msgid "To include all users with permissions in the *Sales* app, create a rule with the following parameters: - :guilabel:`Groups` - :guilabel:`is in` - `Sales/User: Own Documents Only`" +msgid ":guilabel:`is in`" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:109 +msgid "`Sales/User: Own Documents Only`" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:0 msgid "View of the assignation rules section of a Challenge form." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:118 +#: ../../content/applications/sales/crm/optimize/gamification.rst:115 msgid "In the :guilabel:`Periodicity` field, select a time frame for goals to be automatically assessed." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:121 +#: ../../content/applications/sales/crm/optimize/gamification.rst:118 msgid "Add goals" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:123 +#: ../../content/applications/sales/crm/optimize/gamification.rst:120 msgid "Challenges can be based on a single goal, or can include multiple goals with different targets. To add a goal to the challenge, click :guilabel:`Add a line` on the :guilabel:`Goals` tab." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:126 +#: ../../content/applications/sales/crm/optimize/gamification.rst:123 msgid "In the :guilabel:`Goal Definition` field, choose a goal from the drop-down list. The :guilabel:`Condition` field automatically updates to reflect the condition set on the goal definition." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:131 +#: ../../content/applications/sales/crm/optimize/gamification.rst:128 msgid "The *CRM Gamification* module contains preconfigured goals geared towards salesteams:" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:133 +#: ../../content/applications/sales/crm/optimize/gamification.rst:130 msgid ":guilabel:`New Leads`" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:134 +#: ../../content/applications/sales/crm/optimize/gamification.rst:131 msgid ":guilabel:`Time to Qualify a Lead`" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:135 +#: ../../content/applications/sales/crm/optimize/gamification.rst:132 msgid ":guilabel:`Days to Close a Dead`" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:136 +#: ../../content/applications/sales/crm/optimize/gamification.rst:133 msgid ":guilabel:`New Opportunities`" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:137 +#: ../../content/applications/sales/crm/optimize/gamification.rst:134 msgid ":guilabel:`New Sales Orders`" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:139 +#: ../../content/applications/sales/crm/optimize/gamification.rst:136 msgid "Enter a :guilabel:`Target` for the goal based on the :guilabel:`Suffix`." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:141 +#: ../../content/applications/sales/crm/optimize/gamification.rst:138 msgid "Repeat these steps for each additional goal." msgstr "" @@ -866,19 +1089,19 @@ msgstr "" msgid "The goals tab of a challenge form." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:148 +#: ../../content/applications/sales/crm/optimize/gamification.rst:145 msgid "Add rewards" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:150 +#: ../../content/applications/sales/crm/optimize/gamification.rst:147 msgid "Next, click the :guilabel:`Reward` tab. Choose the :ref:`badges ` to be awarded :guilabel:`For 1st User` and :guilabel:`For Every Succeeding User` by selecting them from the drop-down lists." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:155 +#: ../../content/applications/sales/crm/optimize/gamification.rst:152 msgid "Badges are granted when a challenge is finished. This is either at the end of a running period, at the end date of a challenge, or when the challenge is manually closed." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:158 +#: ../../content/applications/sales/crm/optimize/gamification.rst:155 msgid "After setup is complete, click the :guilabel:`Start Challenge` button at the top-left of the page to begin the challenge." msgstr "" @@ -894,6 +1117,11 @@ msgstr "" msgid "The information provided by lead enrichment can include general information about the business (including full business name and logo), social media accounts, :guilabel:`Company type`, :guilabel:`Founded` information, :guilabel:`Sectors` information, the number of :guilabel:`Employees`, :guilabel:`Estimated revenue`, :guilabel:`Phone` number, :guilabel:`Timezone`, and :guilabel:`Technologies Used`." msgstr "" +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:16 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:78 +msgid "Enterprise Odoo users with a valid subscription get free credits to test :abbr:`IAP (In-App Purchase)` features before deciding to purchase more credits for the database. This includes demo/training databases, educational databases, and one-app-free databases." +msgstr "" + #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:21 msgid "The *leads* feature **must** be activated in the *CRM* settings page in order to use lead enrichment. To access the *CRM* settings, navigate to :menuselection:`CRM app --> Configuration --> Settings`. Under the :guilabel:`CRM` section activate the :guilabel:`Leads` option and click :guilabel:`Save`." msgstr "" @@ -2888,6 +3116,126 @@ msgstr "" msgid ":doc:`../performance/win_loss`" msgstr "" +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:3 +msgid "Manage sales teams" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:5 +msgid "The *Sales Teams* feature within Odoo's *CRM* app allows for the creation and management of multiple sales teams, each with their own assignment rules, invoicing targets, and roster of salespeople." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:9 +msgid "Create a sales team" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:11 +msgid "To create a new sales team, go to :menuselection:`CRM app --> Configuration --> Sales Teams`, then click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:14 +msgid "On the blank sales team form, enter a name in the :guilabel:`Sales Team` field." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:16 +msgid "Next, select a :guilabel:`Team Leader` from the drop-down list." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:18 +msgid "Set an :guilabel:`Email Alias` to automatically generate a lead/opportunity for this sales team whenever a message is sent to that unique email address. Choose whether to accept emails from :guilabel:`Everyone`, :guilabel:`Authenticated Partners`, :guilabel:`Followers Only`, or :guilabel:`Authenticated Employees`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:23 +msgid "Select a :guilabel:`Company` from the drop-down menu to assign this team to." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:26 +msgid "The :guilabel:`Company` field is only visible in multi-company databases, and is not required." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:-1 +msgid "The settings page for a new sales team." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:33 +msgid "If the *Sales* app is installed on the database, an :guilabel:`Invoicing Target` field appears on the sales team form. This is the revenue target for the current month. The amount entered in this field is used to populate the invoicing progress bar on the :ref:`sales team dashboard `." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:39 +msgid "Add sales team members" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:41 +msgid "To add team members, click :guilabel:`Add` under the :guilabel:`Members` tab when editing the sales team's configuration page. This opens a :guilabel:`Create Sales Team Members` pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:45 +msgid "If the :guilabel:`Rule-Based Assignment` feature has **not** been enabled on the *CRM* app's *Settings* page, clicking :guilabel:`Add` under the :guilabel:`Members` tab opens an :guilabel:`Add: Salespersons` pop-up window. Tick the checkbox to the far-left of the salesperson to be added to the team, then click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:0 +msgid "The Add: Salespersons pop-up window on a new sales team." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:54 +msgid "Select a user from the :guilabel:`Salesperson` drop-down list to add them to the team. To prevent this salesperson from being automatically assigned leads, tick the :guilabel:`Skip auto assignment` checkbox. If this feature is activated, the salesperson can still be assigned leads manually." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:-1 +msgid "The Create Sales Team Members pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:62 +msgid "The :guilabel:`Leads (30 days)` field tracks how many leads the salesperson has been assigned in the past thirty days for this team, and the maximum number of leads they should be assigned. To edit the maximum number of leads this salesperson can be assigned, enter that amount in the :guilabel:`Leads (30 days)` field." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:68 +msgid ":doc:`Assignment rules <../track_leads/lead_scoring>` can be configured for individual salespeople using the :guilabel:`Domain` section." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:71 +msgid "Click :guilabel:`Save & Close` when finished, or :guilabel:`Save & New` to add additional members." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:74 +msgid "Enable multi teams" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:76 +msgid "To allow salespeople to be assigned to more than one sales team, the *Multi Teams* setting needs to be enabled. First, navigate to :menuselection:`CRM app --> Configuration --> Settings`. Under the :guilabel:`CRM` section, tick the checkbox labeled :guilabel:`Multi Teams`. Then, click :guilabel:`Save` at the top-left of the page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:-1 +msgid "The settings page of the CRM app with the Multi Teams setting enabled." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:88 +msgid "Sales team dashboard" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:90 +msgid "To view the sales team dashboard, go to :menuselection:`CRM app --> Sales --> Teams`. Any team the user is a member of appears in the dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:-1 +msgid "The sales team dashboard in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:97 +msgid "Each Kanban card gives an overview of the sales team's open opportunities, quotations, sales orders, and expected revenue, as well as a bar graph of new opportunities per week, and an invoicing progress bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:101 +msgid "Click the :guilabel:`Pipeline` button to go directly to that team's *CRM* pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:103 +msgid "Click on the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in the top-right corner of the Kanban card to open a drop-down menu. Then, to view or edit the team's settings, click :guilabel:`Configuration`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/manage_sales_teams.rst:108 +msgid ":doc:`../optimize/utilize_activities`" +msgstr "" + #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:3 msgid "Merge similar leads and opportunities" msgstr "" @@ -3004,78 +3352,6 @@ msgstr "" msgid "List of similar leads with emphasis on the contact information in the CRM app." msgstr "" -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3 -msgid "Multiple sales teams" -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:5 -msgid "Use the *Sales Teams* feature to manage several sales teams, departments, or channels, each with their own unique sales processes." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:10 -msgid "Create a new sales team" -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:12 -msgid "To create a new sales team, go to :menuselection:`CRM --> Configuration --> Sales Teams`, then click :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:15 -msgid "On the creation page, set an :guilabel:`Email Alias` to automatically generate a lead/opportunity for this sales team every time a message is sent to that unique email address. Choose whether to accept emails from :guilabel:`Everyone`, :guilabel:`Authenticated Partners`, or :guilabel:`Followers Only`." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:20 -msgid "Set an :guilabel:`Invoicing Target` if this team has specific monthly revenue goals. Set a :guilabel:`Domain` to assign leads/opportunities to this sales team based on specific filters, such as country, language, or campaign." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1 -msgid "Create a sales team in Odoo CRM." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:29 -msgid "Add members to a sales team" -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:31 -msgid "To add team members, click :guilabel:`Add` under the :guilabel:`Members` tab when editing the sales team's configuration page. Select a salesperson from the drop-down menu or create new salesperson. Set a maximum number of leads that can be assigned to this salesperson in a 30-day period to ensure that they do not overwork." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1 -msgid "Add a salesperson in Odoo CRM." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:40 -msgid "One person can be added as a team member or :guilabel:`Team Leader` to multiple sales teams, allowing them to access all of the pipelines that they need to." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:44 -msgid "Sales team dashboard" -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:46 -msgid "To view the sales team dashboard, go to :menuselection:`CRM --> Sales --> Teams`. Odoo users will see any teams that they are a part of as dashboard tiles." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:49 -msgid "Each tile gives an overview of the sales team's open opportunities, quotations, sales orders, and expected revenue, as well as a bar graph of new opportunities per week and an invoicing progress bar." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1 -msgid "Sales team overview dashboard in Odoo CRM." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:57 -msgid "Click on the three dots in the corner of a tile to open a navigational menu that lets users quickly view documents or reports, create new quotations or opportunities, pick a color for this team, or access the team's configuration page." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:-1 -msgid "Click the Three Dot Menu in Odoo CRM dashboard to view documents and create opportunities." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:65 -msgid "Click on the :guilabel:`Pipeline` button to go directly to that team's CRM pipeline." -msgstr "" - #: ../../content/applications/sales/crm/track_leads.rst:5 msgid "Assign and track leads" msgstr "" @@ -4642,7 +4918,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:25 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:49 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:50 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:63 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:81 msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings `, click :guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` section." @@ -4789,7 +5065,7 @@ msgid "Click :guilabel:`Save` at the bottom of the screen to save changes." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:73 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:40 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:41 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:72 @@ -4805,7 +5081,7 @@ msgid "Finally, fill in the mandatory fields with your :ref:`Adyen API key `." +msgid "Ingenico payment terminals require an :doc:`IoT Box `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:10 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:10 -msgid "Worldline is currently only available in Belgium, the Netherlands and Luxembourg." +msgid "Ingenico is currently only available in Belgium, the Netherlands and Luxembourg." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:11 @@ -4860,42 +5134,62 @@ msgid "Connect an IoT Box" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:20 -msgid "Connecting an Ingenico Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to the :doc:`IoT documentation `." +msgid "Connecting an Ingenico payment terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to the :doc:`IoT documentation `." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:26 -msgid "Configure the Lane/5000 for Ingenico BENELUX" +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:25 +msgid "Configure the Lane/Desk/Move 5000 terminals for Ingenico BENELUX" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:28 -msgid "Click on the F button of the terminal, then go in the :menuselection:`PoS Menu --> Settings` and enter the settings password." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27 +msgid "Press the function button (:guilabel:`F` on Lane/5000, :guilabel:`⦿` on Desk/5000 and Move/5000)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:29 +msgid "Go to :menuselection:`Kassa menu --> Settings Menu` and enter the settings password." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:30 +msgid "Select :guilabel:`Change Connection` and press :guilabel:`OK` on the next screen." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:31 -msgid "Now, click on connection change and TCP/IP. Type the IP of your *IoT Box* (you can find it on the form view of your IoT Box). Then, enter 9000 as port. The terminal will restart. Once it is done, go on your *IoT Box* form in Odoo and verify that the terminal has been found." +msgid "Select :guilabel:`TCP/IP` and :guilabel:`IP-address`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:42 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:32 +msgid "On the next screen, enter the IP address of your IoT Box." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:33 +msgid "Enter `9000` as port number and press :guilabel:`OK` on the next screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:35 +msgid "At this point, the terminal restarts and should be displayed in your IoT Box form in Odoo." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:43 msgid "Enable the payment terminal :ref:`in the application settings ` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`Ingenico` in the :guilabel:`Use a Payment Terminal` field. Then, select your terminal device in the :guilabel:`Payment Terminal Device` field." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:56 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:57 msgid "In your *PoS interface*, when processing a payment, select a *Payment Method* using a payment terminal. Check that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. When the payment is successful, the status will change to *Payment Successful*." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:65 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:66 msgid "If you want to cancel the payment request, click on cancel. You can still retry to send the payment request." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:68 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:69 msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connection between the terminal and Odoo has issues." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:74 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:75 msgid "This option will only be available if you received an error message telling you the connection failed." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:77 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:78 msgid "Once your payment is processed, on the payment record, you’ll find the type of card that has been used and the transaction ID." msgstr "" @@ -5184,6 +5478,14 @@ msgstr "" msgid "Worldline" msgstr "" +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:9 +msgid "Worldline payment terminals require an :doc:`IoT Box `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:10 +msgid "Worldline is currently only available in Belgium, the Netherlands and Luxembourg." +msgstr "" + #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:11 msgid "Odoo is compatible with Worldline terminals that use the CTEP protocol (e.g., the Yomani XR and Yoximo terminals). If you have any doubts, contact your payment provider to ensure your terminal's compatibility." msgstr "" @@ -5843,7 +6145,7 @@ msgid "Go to :menuselection:`Point of Sale --> Products --> Pricelists` and clic msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:234 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:243 msgid "Multiple prices per product" msgstr "" @@ -5876,7 +6178,7 @@ msgid "Setup form of a multiple prices pricelist" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:63 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:312 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:321 msgid "Advanced price rules" msgstr "" @@ -7336,19 +7638,99 @@ msgstr "" msgid "The Amazon Connector is designed to synchronize the data of sales orders. Other actions, such as downloading monthly fees reports, handling disputes, or issuing refunds, **must** be managed from the *Amazon Seller Central*, as usual." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:73 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:71 +msgid "As of February 19, 2024, in North American marketplaces, :abbr:`FBA (Fulfilled by Amazon)` orders created with the *Amazon Connector*, do not get the customer's name passed onto the sales/delivery order in Odoo. This is due to the fact that Amazon now calculates, and remits, sales tax on behalf of sellers. In other words, personally identifiable customer information is not transmitted to the seller any longer, after a :abbr:`FBA (Fulfilled by Amazon)` order." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:80 msgid "Supported marketplaces" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:75 -msgid "The Amazon Connector supports all the current marketplaces." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:77 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:82 msgid "If a marketplace is not listed in your Amazon marketplaces, it's possible to :ref:`add a new marketplace `." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:81 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:86 +msgid "**North America region**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:88 +msgid "Canada" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:88 +msgid "Amazon.ca" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:90 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:90 +msgid "Amazon.com.mx" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:92 +msgid "US" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:92 +msgid "Amazon.com" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:96 +msgid "**Europe region**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:98 +msgid "Germany" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:98 +msgid "Amazon.de" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:100 +msgid "Spain" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:100 +msgid "Amazon.es" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:102 +msgid "France" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:102 +msgid "Amazon.fr" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:104 +msgid "UK" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:104 +msgid "Amazon.co.uk" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:106 +msgid "Italy" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:106 +msgid "Amazon.it" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:108 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:108 +msgid "Amazon.nl" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:112 #: ../../content/applications/sales/sales/amazon_connector/manage.rst:196 #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:16 #: ../../content/applications/sales/sales/ebay_connector/manage.rst:30 @@ -7356,7 +7738,7 @@ msgstr "" msgid ":doc:`setup`" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:82 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:113 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:155 #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:17 #: ../../content/applications/sales/sales/ebay_connector/setup.rst:17 @@ -10488,7 +10870,7 @@ msgid ":guilabel:`Next Order Coupons`: Generate and share single-use coupon code msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:88 -msgid ":guilabel:`Loyalty Cards`: When making purchases, the customer accumulates points to exchange for rewards on future orders." +msgid ":guilabel:`Loyalty Cards`: When making purchases, the customer accumulates points to exchange for rewards on current and/or future orders." msgstr "" #: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:90 @@ -10947,7 +11329,7 @@ msgid "After activating and saving the :guilabel:`Pricelists` feature, the :guil msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:45 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:328 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:337 msgid "Either option reveals the :guilabel:`Pricelists` page, in which pricelists can be created and/or modified at any time." msgstr "" @@ -10956,11 +11338,18 @@ msgid "How the pricelists page looks in Odoo Sales." msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:53 -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:267 -msgid "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo *Sales* and *eCommerce*." +msgid "The order of the pricelists on the :guilabel:`Pricelists` page has an impact on how they are applied. If several pricelists share the same criteria, **only** the first listed pricelist is applied." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:55 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:57 +msgid "For example, for two pricelists with different rules, but same criteria (e.g., same website, same country), only the *first* pricelist in the list is applied." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:61 +msgid "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo *Sales* and *eCommerce*. This pricelist is applied by default, if there are no matching criteria." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:64 msgid "From the :guilabel:`Pricelists` page, either select the desired pricelist to edit, or click :guilabel:`New` to create a new pricelist, which reveals a blank pricelist form that can be configured in a number of different ways." msgstr "" @@ -10968,87 +11357,87 @@ msgstr "" msgid "How the pricelist detail form looks in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:63 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:72 msgid "When creating a new pricelist, start by adding a name for the pricelist at the top of the form, in the blank field. Next, select which :guilabel:`Currency` should be used." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:66 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:75 msgid "Then, if working in a multi-company environment, select which company this pricelist should apply to in the :guilabel:`Company` field. If this field is left blank, the pricelist is automatically applied to all companies in the database." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:71 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:80 msgid "Price rules tab" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:73 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:82 msgid "The :guilabel:`Price Rules` tab functionality on a pricelist form varies depending on the :guilabel:`Pricelists` setting chosen: either :guilabel:`Multiple prices per product` or :guilabel:`Advanced price rules (discounts, formulas)`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:77 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:86 msgid "However, the :guilabel:`Time-based rules` tab and :guilabel:`Configuration` tab are always the same, regardless of the chosen :guilabel:`Pricelists` setting." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:81 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:90 msgid "Price rules tab (multiple prices per product)" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:83 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:92 msgid "With the :guilabel:`Multiple prices per product` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to add specific products, with a specific price, to a pricelist." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:87 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:96 msgid "To add a specific product and price to a pricelist form, click the :guilabel:`Price Rules` tab, then click :guilabel:`Add a line` in the :guilabel:`Products` column. Then, select the desired product for which a specific price should be applied." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:91 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:100 msgid "Next, if necessary, select a product variant under the :guilabel:`Variants` column (e.g. a specific product size, color, etc.). If no variants are selected, then this price will apply to all variants of the product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:95 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:104 msgid "If a minimum amount of the product must be purchased in order to apply the specific price, enter the amount under the :guilabel:`Min. Quantity` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:98 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:107 msgid "To configure the price of the product for this specific pricelist, enter the desired amount under the :guilabel:`Price` column. Then, there is the option to add a :guilabel:`Start Date` and :guilabel:`End Date` to the configured product price, if desired." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:102 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111 msgid "To add another product line, click :guilabel:`Add a line` again, and repeat the process. There is no limit to how many products can be added in the :guilabel:`Price Rules` tab of a pricelist form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:105 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:114 msgid "For more information, check out the following section: :ref:`Multiple prices per product `." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:109 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:118 msgid "Price rules tab (advanced price rules)" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:120 msgid "With the :guilabel:`Advanced price rules (discounts, formulas)` setting activated, the :guilabel:`Price Rules` tab on pricelist forms provides the option to configure detailed price rules based on formulas." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:115 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:124 msgid "Check out the :ref:`Advanced price rules (discounts, formulas) ` section for detailed steps on how to add advanced price rules to a pricelist." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:128 msgid "Time-based rules tab" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:121 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:130 msgid "Time-based rules are used specifically with :doc:`subscription products `. Be sure to check out the Odoo *Subscriptions* :doc:`documentation `." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:125 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:134 msgid "Under the :guilabel:`Time-based rules` tab, the same functionality of the :guilabel:`Price Rules` tab is present, with the only difference being that a repeating time period can be applied in the :guilabel:`Period` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:129 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:138 msgid "After a :guilabel:`Product` and potential :guilabel:`Variant` are selected in the :guilabel:`Time-based rules` tab, select the blank field in the :guilabel:`Period` column to reveal a drop-down menu of pre-designated recurrence periods (e.g. `Monthly`, `Quarterly`, `Weekly`, etc.)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:133 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:142 msgid "New recurrence periods can also be directly created from this column, by typing in the new name for the :guilabel:`Period` and then selecting :guilabel:`Create` to create the time period, which can be edited later. Or, select :guilabel:`Create and edit...` to reveal a pop-up form, in which the new recurrence period can be directly configured." msgstr "" @@ -11056,23 +11445,23 @@ msgstr "" msgid "Custom time period pop-up form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:142 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:151 msgid "From this :guilabel:`Create Period` pop-up form, add a :guilabel:`Name`, :guilabel:`Duration`, then a :guilabel:`Unit` (e.g. `Days`, `Weeks`, etc.). When finished, click :guilabel:`Save and Close`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:154 msgid "Lastly, add the desired price for this time-based rule in the :guilabel:`Price` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:148 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:157 msgid ":doc:`/applications/sales/subscriptions`" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:151 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:160 msgid "Configuration tab" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:153 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:162 msgid "Under the :guilabel:`Configuration` tab, there are a few options that can further customize the pricelist." msgstr "" @@ -11080,43 +11469,43 @@ msgstr "" msgid "Configuration tab on pricelist detail form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:160 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:169 msgid "From here, under the :guilabel:`Availability` section, in the :guilabel:`Country Groups` field, certain country groups can be added to the pricelist. There is no limit to how many country groups can be added in this field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:165 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:174 msgid "If no country is set for a customer, Odoo takes the first pricelist without any country group." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:167 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:176 msgid "Under the :guilabel:`Website` section, there are a few options that can be configured. In the :guilabel:`Website` field, this pricelist can be applied to a specific website, if working in a multi-website environment. If left blank, the pricelist will be applied to all websites in the database." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:172 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:181 msgid "Click the :guilabel:`Selectable` checkbox to have this pricelist as a selectable option for customers to choose as they shop. If the :guilabel:`Selectable` box is left unchecked, customers **cannot** select this pricelist for themselves as they shop." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:176 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:185 msgid "Lastly, there is the option to add an :guilabel:`E-commerce Promotional Code`. To add a code, type in the desired promo code that, when entered during the checkout process, applies the pricelist to the customer, even if the customer does not fall into the previously-specified criteria." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:181 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:190 msgid "Show discount percentage to customers" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:183 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:192 msgid "With Odoo *Sales*, the option to show the public price *and* the computed discount percentage on the product catalog is available." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:186 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:195 msgid "To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the :guilabel:`Pricing` section, click the checkbox next to the :guilabel:`Discounts` feature, and then click :guilabel:`Save` to save all changes." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:190 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:199 msgid "After activating the :guilabel:`Discounts` feature, navigate to the pricelists page, either by clicking the :guilabel:`Pricelists` link from the :guilabel:`Settings` page, or by going to :menuselection:`Sales app --> Products --> Pricelists`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:194 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:203 msgid "On the :guilabel:`Pricelists` page, select the desired pricelist to edit. On the pricelist form, click into the :guilabel:`Configuration` tab. In the :guilabel:`Configuration` tab, at the bottom, a :guilabel:`Discounts` section is now available." msgstr "" @@ -11124,27 +11513,27 @@ msgstr "" msgid "What the discount options are on the configuration tab of a pricelist in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:202 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:211 msgid "The options available in this section are:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:204 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:213 msgid ":guilabel:`Discount included in the price`: shows the customer only the final price with the discount already included." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:206 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:215 msgid ":guilabel:`Show public price & discount to the customer`: shows the customer the public price *and* the discount they're earning." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:210 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:219 msgid "Customer pricelist application" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:212 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:221 msgid "While the default pricelist applied to any customer is the :guilabel:`Public Pricelist`, Odoo provides the opportunity to directly apply a different pricelist to customers on their contact form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:215 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:224 msgid "To do that, open the desired customer's contact form, either by navigating to :menuselection:`Sales app --> Orders --> Customers` and selecting the customer from the main :guilabel:`Customers` page, or by clicking on the customer's name on a sales order." msgstr "" @@ -11152,7 +11541,7 @@ msgstr "" msgid "Sample customer detail form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:223 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:232 msgid "On the desired customer's contact form, under the :guilabel:`Sales & Purchase` tab, in the :guilabel:`Sales` section, designate what pricelist should be applied to this specific customer from the drop-down menu in the :guilabel:`Pricelist` field." msgstr "" @@ -11160,15 +11549,15 @@ msgstr "" msgid "The pricelist field in a customer detail form in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:236 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:245 msgid "To apply several prices per individual product, select the :guilabel:`Multiple prices per product` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:240 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:249 msgid "Next, apply pricelists to specific products using the product form. Navigate to the :menuselection:`Sales app --> Products --> Products` and select the product for which multiple prices should be applied. Selecting a product from the :guilabel:`Products` page reveals that specific product's product form on a separate page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:245 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:254 msgid "On the product form, click the :guilabel:`Extra Prices` smart button, located at the top of the form." msgstr "" @@ -11176,7 +11565,7 @@ msgstr "" msgid "How the extra prices smart button appears in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:252 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:261 msgid "Doing so reveals a separate page displaying the :guilabel:`Price Rules` that are specific to that particular product. Here, price rules can be edited or created at any time." msgstr "" @@ -11184,67 +11573,71 @@ msgstr "" msgid "How the extra price rules per product page appears in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:259 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:268 msgid "To create a new price rule for a product from this specific :guilabel:`Price Rules` page, click :guilabel:`New` to add a new, customizable row that has the desired product already populated in the :guilabel:`Applied On` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:263 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:272 msgid "Next, select which :guilabel:`Pricelist` this specific product price rule should apply to, via the drop-down menu in the :guilabel:`Pricelist` column." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:270 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:276 +msgid "The :guilabel:`Public Pricelist` is the default pricelist used with Odoo *Sales* and *eCommerce*." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:279 msgid "To create a new pricelist from this page, type in the desired name of the new pricelist in the :guilabel:`Pricelist` column, then select :guilabel:`Create` from the drop-down menu. All pricelists can be modified at any time, by navigating to :menuselection:`Sales app --> Products --> Pricelists`. Pricelists can also be created on that specific :guilabel:`Pricelists` page, as well." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:276 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:285 msgid "After the desired pricelist is added to the row, designate a :guilabel:`Min. Quantity` for the price rule." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:280 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:289 msgid "If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the :guilabel:`Price` column will be applied to orders of 2 or more products. So, in theory, if a single product costs $100, customers can be encouraged to buy more, if the :guilabel:`Price` is set at $85 per product for a :guilabel:`Min. Quantity` of `2` products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:285 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:294 msgid "Next, enter the desired amount in the :guilabel:`Price` column. Then, if needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the product's price rule." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:288 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:297 msgid "And lastly, if working in a multi-company environment, select which company this price rule should be applied to in the :guilabel:`Company` field. Leaving this field blank means the price rule applies for all companies in the database." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:292 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:301 msgid "Click away from the row to activate Odoo's auto-save capability, meaning that newly-created price rule is now ready to be used." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:295 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:304 msgid "Proceed to add as many unique price rules per product as desired. There is no limit to how many price rules can be added per product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:298 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:307 msgid "With the price rule(s) in place for a specific product, customers who fall into those corresponding pricelists automatically see those new prices applied. The number of price rules applied to a particular product are also displayed in the :guilabel:`Extra Prices` smart button, located on every product form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:304 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:313 msgid "When a price rule/pricelist is added to a product via the :guilabel:`Extra Prices` smart button, it is also reflected on the pricelist itself. Similarly, when a price rule for a specific product is added to a pricelist, it is also reflected on the product form via the :guilabel:`Extra Prices` smart button." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:314 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 msgid "The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature provides the option to set price change rules based on discounts and formulas. These changes can be relative to the product list/catalog price, the product's cost, or another pricelist." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:318 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:327 msgid "To use advanced pricing rules, with discounts and formulas, select the :guilabel:`Advanced price rules (discounts, formulas)` option, after enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page (:menuselection:`Sales app --> Configuration --> Settings`), and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:332 msgid "After activating and saving that :guilabel:`Pricelists` feature, the :guilabel:`Settings` page reloads and, from here, either select the :guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app --> Products --> Pricelists`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:331 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:340 msgid "From the :guilabel:`Pricelists` page, select a desired pricelist to modify, or create a new pricelist by clicking the :guilabel:`New` button." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:334 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:343 msgid "On the pricelist form, under the :guilabel:`Price Rules` tab, click :guilabel:`Add a line` to add an advanced price rule. Doing so reveals a :guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule is configured." msgstr "" @@ -11252,35 +11645,35 @@ msgstr "" msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:343 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352 msgid "Price computation" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:345 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354 msgid "On this form, first choose one of the three :guilabel:`Computation` options:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:347 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:356 msgid ":guilabel:`Fixed Price`: the price computation is based on a fixed price." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:348 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:357 msgid ":guilabel:`Discount`: the price computation is based on a discount." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:349 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:358 msgid ":guilabel:`Formula`: the price computation is based on a formula." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:361 msgid "Each :guilabel:`Computation` option reveals its own computation-specific fields on the form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:363 msgid "If :guilabel:`Fixed Price` is selected, enter the desired price in the :guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, enter the desired discount percentage in the :guilabel:`Discount` field that appears." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:358 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:367 msgid "If :guilabel:`Formula` is selected, a number of configurable options appear." msgstr "" @@ -11288,15 +11681,15 @@ msgstr "" msgid "The various formula computation options present in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:364 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:373 msgid "To configure the :guilabel:`Formula` computation option, start by selecting an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the advanced price rule formula will be based on." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:368 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:377 msgid "Next, in the :guilabel:`Discount` field, determine how much of a discount should be applied. It should be noted that a mark-up can be applied by setting a negative discount in this field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:372 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:381 msgid "To formulate a 100% markup (or 2 times the cost of the product), with a $5 minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the :guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is often seen in retail situations." msgstr "" @@ -11304,27 +11697,27 @@ msgstr "" msgid "How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:380 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:389 msgid "Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or subtract) to the amount calculated with the discount. After that, enter a desired figure in the :guilabel:`Rounding Method` field. The rounding method sets the price so that it is a multiple of the value in the field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:385 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:394 msgid "Rounding is applied *after* the discount and *before* the surcharge." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:397 msgid "To have prices that end in 9.99, set the :guilabel:`Rounding Method` to `10` and the :guilabel:`Extra Fee` to `-0.01`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:391 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:400 msgid "Lastly, specify the minimum amount of margin over the base price in the :guilabel:`Margins` field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:393 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:402 msgid "Once all formula-related configurations are complete, Odoo provides an example of the formula in a blue block to the right of the configurations." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:397 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 msgid "To apply 20% discounts, with prices rounded up to 9.99, set the :guilabel:`Based on` field to :guilabel:`Sales Price`, the :guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to `-0.01`, and the :guilabel:`Rounding Method` field to `10`." msgstr "" @@ -11332,55 +11725,55 @@ msgstr "" msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:415 msgid "Conditions" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:408 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417 msgid "At the bottom of the :guilabel:`Create Pricelist Rules` pop-up form is the :guilabel:`Conditions` section." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:411 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 msgid "Here, start by selecting one of the options in the :guilabel:`Apply On` field:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:413 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:422 msgid ":guilabel:`All Products`: the advanced pricelist rule will be applied to all products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:423 msgid ":guilabel:`Product Category`: the advanced pricelist rule will be applied to a specific category of products." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:416 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:425 msgid ":guilabel:`Product`: the advanced pricelist rule will be applied to a specific product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:426 msgid ":guilabel:`Product Variant`: the advanced pricelist rule will be applied to a specific product variant." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:429 msgid "If any of those options, apart from :guilabel:`All Products`, are selected, a new option-specific field appears, in which the specific :guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product Variant` must be chosen." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:424 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 msgid "Then, select a minimum quantity to be applied to the advanced pricelist rule in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for the pricelist item validation in the :guilabel:`Validity` field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:428 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:437 msgid "Once all configurations are complete, either click :guilabel:`Save & Close` to save the advanced pricelist rule, or click :guilabel:`Save & New` to immediately create another advanced pricelist rule on a fresh form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:442 msgid "If a price rule is set for a particular product, and another one for its product category, Odoo takes the rule of the product itself." msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:437 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:446 msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" msgstr "" -#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:447 msgid ":doc:`/applications/websites/ecommerce/managing_products/price_management`" msgstr "" @@ -13874,7 +14267,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:85 #: ../../content/applications/sales/subscriptions/reports.rst:406 #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:182 -#: ../../content/applications/sales/subscriptions/upselling.rst:103 +#: ../../content/applications/sales/subscriptions/upselling.rst:107 msgid ":doc:`../subscriptions`" msgstr "" @@ -13883,7 +14276,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:86 #: ../../content/applications/sales/subscriptions/reports.rst:407 #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:183 -#: ../../content/applications/sales/subscriptions/upselling.rst:104 +#: ../../content/applications/sales/subscriptions/upselling.rst:108 msgid ":doc:`plans`" msgstr "" @@ -13892,7 +14285,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/renewals.rst:87 #: ../../content/applications/sales/subscriptions/reports.rst:408 #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:184 -#: ../../content/applications/sales/subscriptions/upselling.rst:105 +#: ../../content/applications/sales/subscriptions/upselling.rst:109 msgid ":doc:`products`" msgstr "" @@ -15383,7 +15776,11 @@ msgstr "" msgid "There is also a warning reminding the user that the recurring products are discounted, according to the prorated period of time, located beneath the initial subscription product in the :guilabel:`Order Lines` tab." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:71 +#: ../../content/applications/sales/subscriptions/upselling.rst:72 +msgid "The prorated amount is **only** applied to *Service* product types. It is **not** applied to *Consumable* or *Storable* product types, even if the message appears." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:75 msgid "From this new upsell quotation form, add new subscription products in the :guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and selecting the desired subscription product." msgstr "" @@ -15391,23 +15788,23 @@ msgstr "" msgid "Adding products to your subscription via the upsell option in Odoo Subscriptions" msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:78 +#: ../../content/applications/sales/subscriptions/upselling.rst:82 msgid "Once the desired upsell subscription product(s) have been added, it can be sent to the customer for approval by clicking the :guilabel:`Send by Email` button." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:82 +#: ../../content/applications/sales/subscriptions/upselling.rst:86 msgid "When the quotation is confirmed by the customer, the upsell products are added to the initial subscription. Quotation prices are then prorated to the remaining time of the current invoicing period." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:87 +#: ../../content/applications/sales/subscriptions/upselling.rst:91 msgid "Before sending the new quotation to the customer, the unit price, taxes, and even discount can be applied." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:90 +#: ../../content/applications/sales/subscriptions/upselling.rst:94 msgid "Once the customer approves, click the :guilabel:`Confirm` button on the quotation, making it a sales order. When that's clicked, a :guilabel:`Sales History` smart button appears, displaying how many sales orders are attached to this initial subscription order." msgstr "" -#: ../../content/applications/sales/subscriptions/upselling.rst:94 +#: ../../content/applications/sales/subscriptions/upselling.rst:98 msgid "When the :guilabel:`Sales History` smart button is clicked, Odoo reveals a separate page containing a list of the related sales orders, clearly showcasing their individual :guilabel:`Subscription Status`." msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index 5fcc8037a..a3c1259d4 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -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 \n" "Language-Team: LANGUAGE \n" @@ -172,11 +172,277 @@ msgstr "" msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk" msgstr "" -#: ../../content/applications/services/helpdesk.rst:8 +#: ../../content/applications/services/helpdesk.rst:7 msgid "Helpdesk" msgstr "" -#: ../../content/applications/services/helpdesk.rst:11 +#: ../../content/applications/services/helpdesk.rst:9 +msgid "Odoo *Helpdesk* is a ticketing-based customer support application. Multiple teams can be configured and managed in one dashboard, each with their own pipeline for tickets submitted by customers. Pipelines are organized in customizable stages that enable teams to track, prioritize, and solve customer issues quickly and efficiently." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:15 +msgid "Create a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:17 +msgid "To view or modify *Helpdesk* teams, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. To create a new team, click the :guilabel:`New` button in the top-left of the dashboard." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:-1 +msgid "View of the Helpdesk teams page in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:25 +msgid "On the blank Helpdesk team form, enter a :guilabel:`Name` for the new team. Then, enter a description of the team in the field below the team name, if desired. To change the company this team is assigned to, select it from the :guilabel:`Company` drop-down menu." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:30 +msgid "The team description is published on the public facing :doc:`website form `, where customers and portal users submit tickets. The description included in this field should **not** include any information that is for internal use only." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:0 +msgid "View of a Helpdesk team's website form displaying the team description." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:40 +msgid "Visibility & Assignment" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:42 +msgid "The *Visibility* settings alter which internal users and portal users have access to this team and its tickets. The *Assignment* settings alter how users are assigned to handle each ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:46 +msgid "Determine team visibility" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:48 +msgid "Under the :guilabel:`Visibility` section, select one of the following options to determine who can view this team and its tickets:" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:51 +msgid ":guilabel:`Invited internal users (private)`: internal users can access the team and the tickets they are following. This access can be modified on each ticket individually by adding or removing the user as a follower. Internal users are considered *invited* once they are added as followers to an individual ticket, or :ref:`to the team itself `." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:55 +msgid ":guilabel:`All internal users (company)`: all internal users can access the team and all of its tickets." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:57 +msgid ":guilabel:`Invited portal users and all internal users (public)`: all internal users can access the team and all of its tickets. Portal users can only access the tickets they are following." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:61 +msgid "A `Customer Support` team, meant to handle general shipping and product issues, would have the visibility set on :guilabel:`Invited portal users and all internal users`." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:64 +msgid "At the same time, a `Financial Services` team handling tickets related to accounting or tax information would only need to be visible to :guilabel:`Invited internal users`." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:68 +msgid "A team's visibility can be altered after the initial configuration. However, if the team changes from public access to either private or company-only access, portal users are removed as followers from both the team, and from individual tickets." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:75 +msgid "Follow all team's tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:77 +msgid "If a user should be notified about any updates regarding tickets for this team, select their name from the :guilabel:`Followers` drop-down menu, located in the :guilabel:`Follow All Team's Tickets` field. Multiple users can be selected to follow a single team." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:82 +msgid "External contacts can be selected in the :guilabel:`Followers` field. If the team's visibility is set to :guilabel:`Invited internal users (private)`, followers are notified about updates to the team's tickets, but are **not** able to view them in the portal." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:87 +msgid "Automatically assign new tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:89 +msgid "When tickets are received, they need to be assigned to a member of the team. This is done either manually on each ticket individually, or through :guilabel:`Automatic Assignment`. Check the :guilabel:`Automatic Assignment` checkbox to enable this feature for the team." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:-1 +msgid "View of a Helpdesk team settings page emphasizing the automatic assignment features in Odoo\n" +"Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:98 +msgid "As soon as :guilabel:`Automatic Assignment` has been enabled, additional fields appear." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:100 +msgid "Select one of the following assignment methods, based on how the workload should be allocated across the team:" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:103 +msgid ":guilabel:`Each user is assigned an equal number of tickets`: tickets are assigned to team members based on total ticket count, regardless of the number of open or closed tickets they are currently assigned." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:106 +msgid ":guilabel:`Each user has an equal number of open tickets`: tickets are assigned to team members based on how many open tickets they are currently assigned." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:110 +msgid "When :guilabel:`Each user is assigned an equal number of tickets` is selected, the overall number of tickets assigned to team members is the same, but it does **not** consider the current workload." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:114 +msgid "When :guilabel:`Each user has an equal number of open tickets` is selected, it ensures a balanced workload among team members, as it takes the current number of active tickets into account." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:117 +msgid "Finally, add the :guilabel:`Team Members` who are to be assigned tickets for this team. Leave the field empty to include all employees who have the proper assignments and access rights configured in their user account settings." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:122 +msgid "If an employee has time off scheduled in the *Time Off* application, they are **not** assigned tickets during that time. If no employees are available, the system looks ahead until there is a match." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:127 +msgid ":ref:`Manage users `" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:128 +msgid ":doc:`Access rights <../general/users/access_rights>`" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:131 +msgid "Create or modify stages" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:133 +msgid "*Stages* are used to organize the *Helpdesk* pipeline and track the progress of tickets. Stages are customizable, and can be renamed to fit the needs of each team." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:137 +msgid ":ref:`Developer mode ` **must** be activated to access the stages menu. To activate developer mode, go to :menuselection:`Settings app --> General Settings --> Developer Tools`, and click :guilabel:`Activate the developer mode`." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:141 +msgid "To view or modify *Helpdesk* stages, go to :menuselection:`Helpdesk app --> Configuration --> Stages`." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:144 +msgid "The default list view on the :guilabel:`Stages` page displays the stages currently available in *Helpdesk*. They are listed in the order they appear in the pipeline." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:147 +msgid "To change the order of the stages, click the :guilabel:`(six square)` icon, to the left of the stage name, and drag it to the desired place on the list." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:-1 +msgid "View of the stage list page emphasizing the buttons used to change the order the stages\n" +"appear in the list." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:156 +msgid "Change the stage order on the Kanban view of a *Helpdesk* team's pipeline by dragging and dropping individual columns." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:159 +msgid "To create a new stage, click the :guilabel:`New` button at the top-left of the stage list. Doing so reveals a blank stage form." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:162 +msgid "Choose a :guilabel:`Name` for the new stage, and add a description, if desired. Then, proceed to fill out the remaining fields following the steps below." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:-1 +msgid "View of a stage's settings page in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:170 +msgid "Add email and SMS templates to stages" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:172 +msgid "When an :guilabel:`Email Template` is added to a stage, an email is automatically sent to the customer when a ticket reaches that specific stage in the pipeline. Likewise, adding an :guilabel:`SMS Template` triggers an SMS text message to send to the customer." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:177 +msgid "SMS Text Messaging is an :doc:`In-App Purchase (IAP) ` service that requires prepaid credits to work. Refer to `SMS Pricing FAQ `_ for additional information." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:181 +msgid "To select an existing email template, select it from the :guilabel:`Email Template` field. Click on the :guilabel:`→ (Internal Link)` icon to the right of the field to edit the chosen template." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:184 +msgid "To create a new template, click the field, and enter a title for the new template. Then, select :guilabel:`Create and edit` from the drop-down menu that appears, and complete the form details." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:187 +msgid "Follow the same steps to select, edit, or create an :guilabel:`SMS Template`." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:-1 +msgid "View of an SMS template setup page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:194 +msgid ":doc:`/applications/general/companies/email_template`" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:197 +msgid "Assign stages to a team" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:199 +msgid "Make a selection in the :guilabel:`Helpdesk Teams` field on the :guilabel:`Stages` form. More than one team may be selected, since the same stage can be assigned to multiple teams." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:203 +msgid "Fold a stage" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:205 +msgid "By default, stages are unfolded in the Kanban view of either tickets dashboard: :guilabel:`My Tickets` (:menuselection:`Helpdesk app --> Tickets --> My Tickets`) or :guilabel:`All Tickets` (:menuselection:`Helpdesk app --> Tickets --> All Tickets`)." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:209 +msgid "Tickets in an unfolded stage are visible in the pipeline under the stage name, and are considered *open*." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:212 +msgid "Stages can be configured to be folded in the Kanban view of a tickets page (:guilabel:`My Tickets` or :guilabel:`All Tickets`)." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:215 +msgid "The name of the folded stages are still visible, though the tickets in the stage are no longer immediately visible." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:218 +msgid "To fold a stage, check the :guilabel:`Folded in Kanban` box on the :guilabel:`Stages` form." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:221 +msgid "Tickets that reach a *folded* stage are considered *closed*. Closing a ticket before the work is completed can result in reporting and communication issues. This setting should **only** be enabled for stages that are considered *closing* stages." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:225 +msgid "Stages can be temporarily folded in the Kanban view of the tickets pipeline, as well." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:227 +msgid "View a specific team's pipeline by navigating to :menuselection:`Helpdesk app`, and clicking the team's Kanban card." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:230 +msgid "Select a stage to fold temporarily, then click the :guilabel:`⚙️ (gear)` icon, and select :guilabel:`Fold`." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:-1 +msgid "Kanban view of a Helpdesk stage, with the temporary fold option emphasized." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:238 +msgid "Manually folding a stage from the Kanban view is temporary and does **not** close the tickets in the stage." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:242 msgid "`Odoo Tutorials: Helpdesk `_" msgstr "" @@ -754,7 +1020,7 @@ msgid "Enable track and bill time on a helpdesk team" msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:27 -msgid "To view and enable the *Track & Bill Time* features on a *Helpdesk* team, first navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Then, select a team from the list, or create a :doc:`new one <../overview/getting_started>`. This reveals a team's settings page." +msgid "To view and enable the *Track & Bill Time* features on a *Helpdesk* team, first navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Then, select a team from the list, or create a :doc:`new one <../../helpdesk>`. This reveals a team's settings page." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:31 @@ -1026,277 +1292,6 @@ msgstr "" msgid "Overview" msgstr "" -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:3 -msgid "Getting started with Helpdesk" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:5 -msgid "Odoo *Helpdesk* is a ticketing-based customer support application. Multiple teams can be configured and managed in one dashboard, each with their own pipeline for tickets submitted by customers. Pipelines are organized in customizable stages that enable teams to track, prioritize, and solve customer issues quickly and efficiently." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:11 -msgid "Create a Helpdesk team" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:13 -msgid "To view or modify *Helpdesk* teams, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. To create a new team, click the :guilabel:`New` button in the top-left of the dashboard." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 -msgid "View of the Helpdesk teams page in Odoo Helpdesk." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:21 -msgid "On the blank Helpdesk team form, enter a :guilabel:`Name` for the new team. Then, enter a description of the team in the field below the team name, if desired. To change the company this team is assigned to, select it from the :guilabel:`Company` drop-down menu." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:26 -msgid "The team description is published on the public facing :doc:`website form `, where customers and portal users submit tickets. The description included in this field should **not** include any information that is for internal use only." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:0 -msgid "View of a Helpdesk team's website form displaying the team description." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:35 -msgid "Visibility & Assignment" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:37 -msgid "The *Visibility* settings alter which internal users and portal users have access to this team and its tickets. The *Assignment* settings alter how users are assigned to handle each ticket." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:41 -msgid "Determine team visibility" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:43 -msgid "Under the :guilabel:`Visibility` section, select one of the following options to determine who can view this team and its tickets:" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:46 -msgid ":guilabel:`Invited internal users (private)`: internal users can access the team and the tickets they are following. This access can be modified on each ticket individually by adding or removing the user as a follower. Internal users are considered *invited* once they are added as followers to an individual ticket, or :ref:`to the team itself `." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:50 -msgid ":guilabel:`All internal users (company)`: all internal users can access the team and all of its tickets." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:52 -msgid ":guilabel:`Invited portal users and all internal users (public)`: all internal users can access the team and all of its tickets. Portal users can only access the tickets they are following." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:56 -msgid "A `Customer Support` team, meant to handle general shipping and product issues, would have the visibility set on :guilabel:`Invited portal users and all internal users`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:59 -msgid "At the same time, a `Financial Services` team handling tickets related to accounting or tax information would only need to be visible to :guilabel:`Invited internal users`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:63 -msgid "A team's visibility can be altered after the initial configuration. However, if the team changes from public access to either private or company-only access, portal users are removed as followers from both the team, and from individual tickets." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:70 -msgid "Follow all team's tickets" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:72 -msgid "If a user should be notified about any updates regarding tickets for this team, select their name from the :guilabel:`Followers` drop-down menu, located in the :guilabel:`Follow All Team's Tickets` field. Multiple users can be selected to follow a single team." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:77 -msgid "External contacts can be selected in the :guilabel:`Followers` field. If the team's visibility is set to :guilabel:`Invited internal users (private)`, followers are notified about updates to the team's tickets, but are **not** able to view them in the portal." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:82 -msgid "Automatically assign new tickets" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:84 -msgid "When tickets are received, they need to be assigned to a member of the team. This is done either manually on each ticket individually, or through :guilabel:`Automatic Assignment`. Check the :guilabel:`Automatic Assignment` checkbox to enable this feature for the team." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 -msgid "View of a Helpdesk team settings page emphasizing the automatic assignment features in Odoo\n" -"Helpdesk." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:93 -msgid "As soon as :guilabel:`Automatic Assignment` has been enabled, additional fields appear." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:95 -msgid "Select one of the following assignment methods, based on how the workload should be allocated across the team:" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:98 -msgid ":guilabel:`Each user is assigned an equal number of tickets`: tickets are assigned to team members based on total ticket count, regardless of the number of open or closed tickets they are currently assigned." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:101 -msgid ":guilabel:`Each user has an equal number of open tickets`: tickets are assigned to team members based on how many open tickets they are currently assigned." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:105 -msgid "When :guilabel:`Each user is assigned an equal number of tickets` is selected, the overall number of tickets assigned to team members is the same, but it does **not** consider the current workload." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:109 -msgid "When :guilabel:`Each user has an equal number of open tickets` is selected, it ensures a balanced workload among team members, as it takes the current number of active tickets into account." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:112 -msgid "Finally, add the :guilabel:`Team Members` who are to be assigned tickets for this team. Leave the field empty to include all employees who have the proper assignments and access rights configured in their user account settings." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:117 -msgid "If an employee has time off scheduled in the *Time Off* application, they are **not** assigned tickets during that time. If no employees are available, the system looks ahead until there is a match." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:122 -msgid ":ref:`Manage users `" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:123 -msgid ":doc:`Access rights <../../../general/users/access_rights>`" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:126 -msgid "Create or modify stages" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:128 -msgid "*Stages* are used to organize the *Helpdesk* pipeline and track the progress of tickets. Stages are customizable, and can be renamed to fit the needs of each team." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:132 -msgid ":ref:`Developer mode ` **must** be activated to access the stages menu. To activate developer mode, go to :menuselection:`Settings app --> General Settings --> Developer Tools`, and click :guilabel:`Activate the developer mode`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:136 -msgid "To view or modify *Helpdesk* stages, go to :menuselection:`Helpdesk app --> Configuration --> Stages`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:139 -msgid "The default list view on the :guilabel:`Stages` page displays the stages currently available in *Helpdesk*. They are listed in the order they appear in the pipeline." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:142 -msgid "To change the order of the stages, click the :guilabel:`(six square)` icon, to the left of the stage name, and drag it to the desired place on the list." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 -msgid "View of the stage list page emphasizing the buttons used to change the order the stages\n" -"appear in the list." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:151 -msgid "Change the stage order on the Kanban view of a *Helpdesk* team's pipeline by dragging and dropping individual columns." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:154 -msgid "To create a new stage, click the :guilabel:`New` button at the top-left of the stage list. Doing so reveals a blank stage form." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:157 -msgid "Choose a :guilabel:`Name` for the new stage, and add a description, if desired. Then, proceed to fill out the remaining fields following the steps below." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 -msgid "View of a stage's settings page in Odoo Helpdesk." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:165 -msgid "Add email and SMS templates to stages" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:167 -msgid "When an :guilabel:`Email Template` is added to a stage, an email is automatically sent to the customer when a ticket reaches that specific stage in the pipeline. Likewise, adding an :guilabel:`SMS Template` triggers an SMS text message to send to the customer." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:172 -msgid "SMS Text Messaging is an :doc:`In-App Purchase (IAP) ` service that requires prepaid credits to work. Refer to `SMS Pricing FAQ `_ for additional information." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:176 -msgid "To select an existing email template, select it from the :guilabel:`Email Template` field. Click on the :guilabel:`→ (Internal Link)` icon to the right of the field to edit the chosen template." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:179 -msgid "To create a new template, click the field, and enter a title for the new template. Then, select :guilabel:`Create and edit` from the drop-down menu that appears, and complete the form details." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:182 -msgid "Follow the same steps to select, edit, or create an :guilabel:`SMS Template`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 -msgid "View of an SMS template setup page in Odoo Helpdesk" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:189 -#: ../../content/applications/services/helpdesk/overview/ratings.rst:60 -msgid ":doc:`/applications/general/companies/email_template`" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:192 -msgid "Assign stages to a team" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:194 -msgid "Make a selection in the :guilabel:`Helpdesk Teams` field on the :guilabel:`Stages` form. More than one team may be selected, since the same stage can be assigned to multiple teams." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:198 -msgid "Fold a stage" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:200 -msgid "By default, stages are unfolded in the Kanban view of either tickets dashboard: :guilabel:`My Tickets` (:menuselection:`Helpdesk app --> Tickets --> My Tickets`) or :guilabel:`All Tickets` (:menuselection:`Helpdesk app --> Tickets --> All Tickets`)." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:204 -msgid "Tickets in an unfolded stage are visible in the pipeline under the stage name, and are considered *open*." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:207 -msgid "Stages can be configured to be folded in the Kanban view of a tickets page (:guilabel:`My Tickets` or :guilabel:`All Tickets`)." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:210 -msgid "The name of the folded stages are still visible, though the tickets in the stage are no longer immediately visible." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:213 -msgid "To fold a stage, check the :guilabel:`Folded in Kanban` box on the :guilabel:`Stages` form." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:216 -msgid "Tickets that reach a *folded* stage are considered *closed*. Closing a ticket before the work is completed can result in reporting and communication issues. This setting should **only** be enabled for stages that are considered *closing* stages." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:220 -msgid "Stages can be temporarily folded in the Kanban view of the tickets pipeline, as well." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:222 -msgid "View a specific team's pipeline by navigating to :menuselection:`Helpdesk app`, and clicking the team's Kanban card." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:225 -msgid "Select a stage to fold temporarily, then click the :guilabel:`⚙️ (gear)` icon, and select :guilabel:`Fold`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1 -msgid "Kanban view of a Helpdesk stage, with the temporary fold option emphasized." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/getting_started.rst:233 -msgid "Manually folding a stage from the Kanban view is temporary and does **not** close the tickets in the stage." -msgstr "" - #: ../../content/applications/services/helpdesk/overview/help_center.rst:3 msgid "Help Center" msgstr "" @@ -1310,7 +1305,7 @@ msgid "Overview of the settings page of a team emphasizing the Help Center featu msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:16 -msgid "To activate any *Help Center* features (*Forums*, *eLearning*, or *Knowledge*) on a *Helpdesk* team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one `. Verify the :guilabel:`Visibility` of the team is set to :guilabel:`Invited portal users and all internal users (public)` in the :guilabel:`Visibility & Assignment` section." +msgid "To activate any *Help Center* features (*Forums*, *eLearning*, or *Knowledge*) on a *Helpdesk* team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one <../../helpdesk>`. Verify the :guilabel:`Visibility` of the team is set to :guilabel:`Invited portal users and all internal users (public)` in the :guilabel:`Visibility & Assignment` section." msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:22 @@ -1326,7 +1321,7 @@ msgid "Installing a new application on a *One-App-Free* database will trigger a msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:35 -msgid ":doc:`Getting Started `" +msgid ":doc:`Helpdesk Overview <../../helpdesk>`" msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:38 @@ -1346,7 +1341,7 @@ msgid "Enable Knowledge on a Helpdesk team" msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:51 -msgid "To enable the *Knowledge* feature on a *Helpdesk* team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one `." +msgid "To enable the *Knowledge* feature on a *Helpdesk* team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one <../../helpdesk>`." msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:54 @@ -1506,7 +1501,7 @@ msgid "Enable forums on a Helpdesk team" msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:193 -msgid "To enable :guilabel:`Community Forums` on a *Helpdesk* team, start by navigating to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one `." +msgid "To enable :guilabel:`Community Forums` on a *Helpdesk* team, start by navigating to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one <../../helpdesk>`." msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:197 @@ -1570,7 +1565,7 @@ msgid "Enable eLearning courses on a Helpdesk team" msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:246 -msgid "To enable *eLearning* courses on a *Helpdesk* team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one `." +msgid "To enable *eLearning* courses on a *Helpdesk* team, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` and select a team, or create a :doc:`new one <../../helpdesk>`." msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:249 @@ -1690,15 +1685,15 @@ msgid "Customer ratings" msgstr "" #: ../../content/applications/services/helpdesk/overview/ratings.rst:5 -msgid "Asking customers to rate the support they received from a *Helpdesk* team provides an opportunity to gauge team performance and track customer satisfaction. Ratings can be published to the portal, providing customers with a general overview of the team's performance." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/ratings.rst:10 -msgid "Enable customer ratings on a Helpdesk team" +msgid "Asking customers to rate the support they received from a *Helpdesk* team provides an opportunity to gauge team performance and track customer satisfaction. Ratings can be published on the portal, providing customers with a general overview of the team's performance." msgstr "" #: ../../content/applications/services/helpdesk/overview/ratings.rst:12 -msgid "To enable *customer ratings* on a helpdesk team by going to :menuselection:`Helpdesk --> Configuration --> Teams`. Select a team from the list and navigate to the settings page. Scroll to the :guilabel:`Performance` section, and check the box for :guilabel:`Customer Ratings`." +msgid "Enable customer ratings on Helpdesk teams" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:14 +msgid "To enable *customer ratings* on a helpdesk team, navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Select a team from the list and click on it to open the settings page. Scroll to the :guilabel:`Performance` section, and tick the :guilabel:`Customer Ratings` checkbox." msgstr "" #: ../../content/applications/services/helpdesk/overview/ratings.rst:-1 @@ -1706,71 +1701,71 @@ msgid "Overview of the settings page of a helpdesk team emphasizing the rating o "in Odoo Helpdesk." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:22 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:25 msgid "Set a ratings request email template on a stage" msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:24 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:27 msgid "To automatically request ratings from customers once their tickets have closed, an email template should be added to the appropriate stage." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:27 -msgid "Once the :guilabel:`Customer Ratings` setting has been enabled on the team's settings page, (see above) click the :guilabel:`Set an Email Template on Stages` link. Select a stage from the list, or click :guilabel:`New` to create a new stage." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:30 +msgid "After the :guilabel:`Customer Ratings` :ref:`setting has been enabled ` on the team's settings page, click the :guilabel:`Set an Email Template on Stages` link. Select a stage from the list, or click :guilabel:`New` to create a new stage." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:32 -msgid "Customers should only be asked to rate tickets once an issue has been resolved and their ticket is closed. Therefore, a *ratings request* email should only be added to a stage that is **folded** in the kanban, as tickets in a *folded stage* are considered closed." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:35 +msgid "Customers should only be asked to rate tickets once an issue has been resolved and their ticket is *closed*. Therefore, a *ratings request* email should **only** be added to a stage that is folded in the Kanban, as tickets in a *folded stage* are considered closed." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:36 -msgid "On the stage's settings page, select `Helpdesk: Ticket Rating Request` in the :guilabel:`Email Template` field. This template has been pre-configured with ratings customers can use to provide feedback. To view the template, click the arrow button to the right of the field." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/ratings.rst:40 -msgid "Once the template has been added to the stage, it will automatically send a message when a ticket is moved to that stage. Customers will be asked to rate the support they received with colored icons." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:39 +msgid "On the stage's settings page, select the template, `Helpdesk: Ticket Rating Request` in the :guilabel:`Email Template` field. This template has been preconfigured with ratings customers can use to provide feedback. To view the template, click the arrow button to the right of the field." msgstr "" #: ../../content/applications/services/helpdesk/overview/ratings.rst:43 +msgid "After the template is added to the stage, it automatically sends a message when a ticket is moved to that stage. Customers are then asked to rate the support they received with colored icons." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:46 msgid "*Green smiling face* - Satisfied" msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:44 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:47 msgid "*Yellow neutral face* - Okay" msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:45 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:48 msgid "*Red frowning face* - Dissatisfied" msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1 -msgid "View of a standard helpdesk customer review email template for Odoo Helpdesk." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:50 +msgid "After selecting a rating, customers are taken to a webpage where they can provide specific written feedback to support their rating. The rating is then submitted, and the rating, as well as any additional comments, are added to the chatter on the ticket." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:51 -msgid "After selecting a rating, customers are taken to a webpage where they can provide specific written feedback to support their rating. Once a rating is submitted, it is added to the chatter on the ticket." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:55 +msgid "Customer ratings can also be viewed through the :guilabel:`Customer Ratings` report. To view this report, go to :menuselection:`Helpdesk app --> Reporting --> Customer Ratings`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:56 -msgid "Customer ratings can also be viewed through the :guilabel:`Customer Ratings` report. To view this report, go to :menuselection:`Helpdesk --> Reporting --> Customer Ratings`." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:59 +msgid ":doc:`../../../general/companies/email_template`" msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:63 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:62 msgid "Publish ratings on the customer portal" msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:65 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:64 msgid "After enabling the :guilabel:`Customer Ratings` setting, an option to publish ratings on the team's website appears. Enabling this setting provides portal users with an overview of the ratings the team has received over the last thirty days. Specific written feedback will not be included; only statistics of the team's performance will be visible." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:71 -msgid "In order to display ratings on the customer portal, a team has to have their visibility setting set to :guilabel:`Invited portal users and all internal users`. This setting is found on the team's settings page under :guilabel:`Visibility`." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:70 +msgid "To display ratings on the customer portal, a team **must** have their visibility setting set to :guilabel:`Invited portal users and all internal users (public)`. To enable this setting, navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Select a team from the list and click on it to open the settings page. Scroll to the :guilabel:`Visibility & Assignment` section, and tick the :guilabel:`Invited portal users and all internal users (public)` checkbox." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:75 -msgid "Next, to publish the ratings, go to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team. Scroll to :guilabel:`Performance` and enable :guilabel:`Publish this team's ratings on your website`." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:77 +msgid "Next, to publish the ratings, go to :menuselection:`Helpdesk app--> Configuration --> Helpdesk Teams` and select a team. Scroll to :guilabel:`Performance` and tick the checkbox for :guilabel:`Publish this team's ratings on your website`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:79 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:81 msgid "To view the ratings for a team, a customer will log into the portal and navigate to one of their tickets. After clicking on the team name in the :guilabel:`Managed By` field, they will be directed to a page with the team's ratings over the past thirty days." msgstr "" @@ -1779,37 +1774,40 @@ msgstr "" msgid "View of the ratings performance overview from the customer portal." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:88 -msgid "Manually hide individual ratings" -msgstr "" - #: ../../content/applications/services/helpdesk/overview/ratings.rst:90 -msgid "Individual ratings can be manually hidden from the portal. This allows for specific ratings to be kept out of the performance metrics that are shown to customers." +msgid ":doc:`Portal access <../../../general/users/portal>`" msgstr "" #: ../../content/applications/services/helpdesk/overview/ratings.rst:93 -msgid "To make a rating visible only to internal users, navigate to the page for a rating. This can be done in one of the following ways:" +msgid "Manually hide individual ratings" msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:96 -msgid "Go to :menuselection:`Helpdesk --> Reporting --> Customer Ratings` and click on one of the kanban cards for an individual rating." +#: ../../content/applications/services/helpdesk/overview/ratings.rst:95 +msgid "Individual ratings can be manually hidden from the portal. This allows for specific ratings to be kept out of the performance metrics shared with customers." msgstr "" #: ../../content/applications/services/helpdesk/overview/ratings.rst:98 -msgid "Navigate to :menuselection:`Helpdesk --> Tickets --> All Tickets` and remove the :guilabel:`Open` filter from the search bar. Then filter by :guilabel:`Satisfied`, :guilabel:`Okay` and/or :guilabel:`Dissatisfied`. Select a ticket from the results. Click the :guilabel:`Rating` smart button." +msgid "To make a rating visible only to internal users, navigate to the page for a rating. This can be done in one of the following ways:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:101 +msgid "Go to :menuselection:`Helpdesk app --> Reporting --> Customer Ratings` and click on one of the Kanban cards for an individual rating." msgstr "" #: ../../content/applications/services/helpdesk/overview/ratings.rst:103 +msgid "Navigate to :menuselection:`Helpdesk app--> Tickets --> All Tickets` and remove the :guilabel:`Open` filter from the search bar. Then filter by :guilabel:`Satisfied`, :guilabel:`Okay` and/or :guilabel:`Dissatisfied`. Select a ticket from the results. Click the :guilabel:`Rating` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:108 msgid "Once on the rating details page, check the :guilabel:`Visible Internally Only` box." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:110 -#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:350 -msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`" +#: ../../content/applications/services/helpdesk/overview/ratings.rst:115 +msgid ":doc:`../advanced/close_tickets`" msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:111 -msgid ":doc:`/applications/services/helpdesk/overview/reports`" +#: ../../content/applications/services/helpdesk/overview/ratings.rst:116 +msgid ":doc:`reports`" msgstr "" #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:3 @@ -1825,7 +1823,7 @@ msgid "Enable channel options to submit tickets" msgstr "" #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:13 -msgid "Go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and choose an existing team, or click :guilabel:`New` to :doc:`create a new team `." +msgid "Go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and choose an existing team, or click :guilabel:`New` to :doc:`create a new team <../../helpdesk>`." msgstr "" #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:16 @@ -2235,6 +2233,10 @@ msgstr "" msgid "As priority levels can be used as criteria for assigning :doc:`SLAs `, changing the priority level of a ticket can alter the :abbr:`SLA (Service Level Agreement)` deadline." msgstr "" +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:350 +msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`" +msgstr "" + #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:351 msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr "" @@ -2247,160 +2249,141 @@ msgstr "" msgid "Reporting" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:5 -msgid "Odoo *Helpdesk* includes several reports that provide the opportunity to track trends for customer support tickets, identify areas for improvement, manage employee workloads, and confirm when customer expectations are met." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/reports.rst:10 -msgid "Available reports" +#: ../../content/applications/services/helpdesk/overview/reports.rst:8 +msgid "Reports in Odoo *Helpdesk* provide the opportunity to manage employee workloads, identify areas for improvement, and confirm if customer expectations are being met." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:12 -msgid "Details about the reports available in Odoo *Helpdesk* can be found below. To view the different reports, go to :menuselection:`Helpdesk --> Reporting`." +msgid "Available reports" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:16 -msgid "Ticket Analysis" +#: ../../content/applications/services/helpdesk/overview/reports.rst:14 +msgid "Details about the reports available in Odoo *Helpdesk* can be found below. To view the different reports, go to :menuselection:`Helpdesk app --> Reporting`, and select one of the following: :guilabel:`Tickets Analysis`, :guilabel:`SLA Status Analysis`, or :guilabel:`Customer Ratings`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:18 -msgid "The *Ticket Analysis* report (:menuselection:`Helpdesk --> Reporting --> Ticket Analysis`) provides an overview of every customer support ticket in the database. This includes the number of tickets assigned among teams and individual users." +#: ../../content/applications/services/helpdesk/overview/reports.rst:19 +msgid "Tickets Analysis" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:22 -msgid "This report is useful in identifying where teams are spending the most time, and helps determine if there is an uneven workload distribution among the support staff. The default report counts the number of tickets per team and groups them by stage." +#: ../../content/applications/services/helpdesk/overview/reports.rst:21 +msgid "The *Tickets Analysis* report (:menuselection:`Helpdesk app --> Reporting --> Tickets Analysis`) provides an overview of every customer support ticket in the database." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:24 +msgid "This report is useful for identifying where teams are spending the most time, and helps determine if there is an uneven workload distribution among the support staff. The default report counts the number of tickets per team and groups them by stage." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:-1 msgid "View of Ticket Analysis report default view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:30 +#: ../../content/applications/services/helpdesk/overview/reports.rst:32 msgid "Alternative measures can be selected to track where the most time is spent at different points in the workflow. To change the measures used for the report that is currently displayed, or to add more, click the :guilabel:`Measures` button, and select one or more options from the drop-down menu:" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:35 -msgid ":guilabel:`Average Hours to Respond`: average number of working hours between a message sent from the customer and the response from the support team. *This is does not include messages sent when the ticket was in a folded stage*" +#: ../../content/applications/services/helpdesk/overview/reports.rst:37 +msgid ":guilabel:`Average Hours to Respond`: average number of working hours between a message sent from the customer and the response from the support team. *This does not include messages sent when the ticket was in a folded stage.*" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:38 -msgid ":guilabel:`Hours Open`: number of hours between the date the ticket was created and the closed date. If there is no closed date on the ticket, the current date is used. **This measure is not specific to working hours**" +#: ../../content/applications/services/helpdesk/overview/reports.rst:40 +msgid ":guilabel:`Hours Open`: number of hours between the date the ticket was created and the closed date. If there is no closed date on the ticket, the current date is used. **This measure is not specific to working hours.**" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:41 -msgid ":guilabel:`Hours Spent`: number of *Timesheet* hours logged on a ticket. *This measure is only available if Timesheets are enabled on a team, and the current user has the access rights to view them*" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/reports.rst:44 -msgid ":guilabel:`Hours to Assign`: number of working hours between the date on which the ticket was created and when it was assigned to a team member" +#: ../../content/applications/services/helpdesk/overview/reports.rst:43 +msgid ":guilabel:`Hours Spent`: number of *Timesheet* hours logged on a ticket. *This measure is only available if Timesheets are enabled on a team, and the current user has the access rights to view them.*" msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:46 -msgid ":guilabel:`Hours to Close`: number of working hours between the date on which the ticket was created and the date it was closed" +msgid ":guilabel:`Hours to Assign`: number of working hours between the date the ticket was created and when it was assigned to a team member." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:48 -msgid ":guilabel:`Hours to First Response`: number of working hours between the date on which the ticket was received and the date one which the first message was sent. *This does not include email sent automatically when a ticket reaches a stage*" +msgid ":guilabel:`Hours to Close`: number of working hours between the date the ticket was created and the date it was closed." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:51 -msgid ":guilabel:`Hours to SLA Deadline`: number of working hours remaining to reach the last :abbr:`SLA (Service Level Agreement)` deadline on a ticket" +#: ../../content/applications/services/helpdesk/overview/reports.rst:50 +msgid ":guilabel:`Hours to First Response`: number of working hours between the date the ticket was received and the date on which the first message was sent. *This does not include email sent automatically when a ticket reaches a stage.*" msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:53 -msgid ":guilabel:`Rating /5`: number valued assigned to the rating received from a customer (Dissatisfied = 1, Okay/Neutral = 3, Satisfied = 5)" +msgid ":guilabel:`Hours until SLA Deadline`: number of working hours remaining to reach the last |SLA| deadline on a ticket." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:55 -#: ../../content/applications/services/helpdesk/overview/reports.rst:99 -msgid ":guilabel:`Count`: number of tickets in total" +msgid ":guilabel:`Rating (/5)`: number out of five to represent customer feedback (Dissatisfied = 1, Okay/Neutral = 3, Satisfied = 5)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:57 +#: ../../content/applications/services/helpdesk/overview/reports.rst:85 +msgid ":guilabel:`Remaining Hours on SO`: hours remaining on a linked sales order." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:58 +#: ../../content/applications/services/helpdesk/overview/reports.rst:92 +msgid ":guilabel:`Count`: number of tickets in total." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:61 msgid "*Working hours* are calculated based on the default working calendar. To view or change the working calendar, go to the :menuselection:`Settings` application and select :menuselection:`Employees --> Company Working Hours`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:63 +#: ../../content/applications/services/helpdesk/overview/reports.rst:66 msgid "SLA Status Analysis" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:65 -msgid "The *SLA Status Analysis* report (:menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`) tracks how quickly an SLA (Service Level Agreement) is fulfilled, as well as the success rate of individual policies." +#: ../../content/applications/services/helpdesk/overview/reports.rst:68 +msgid "The *SLA Status Analysis* report (:menuselection:`Helpdesk app --> Reporting --> SLA Status Analysis`) :ref:`analyzes the performance ` of individual SLA (Service Level Agreement) policies." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:69 -msgid "By default, this report is filtered to show the number of :abbr:`SLAs (Service Level Agreements)` failed, as well as the failure rate over the last 30 days, grouped by team." +#: ../../content/applications/services/helpdesk/overview/reports.rst:72 +msgid "By default, this report is filtered to show the number of |SLAs| failed, in progress, and the number that have been successful. The results are grouped by teams." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:-1 msgid "View of Group by options of Ticket Analysis report." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:76 +#: ../../content/applications/services/helpdesk/overview/reports.rst:79 msgid "To change the measures used for the report that is currently displayed, or to add more, click the :guilabel:`Measures` button, and select one or more options from the drop-down menu:" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:79 -msgid ":guilabel:`% of Failed SLA`: percentage of tickets that have failed at least one :abbr:`SLA (Service Level Agreement)`" +#: ../../content/applications/services/helpdesk/overview/reports.rst:82 +msgid ":guilabel:`Number of SLA Failed`: number of tickets that have failed at least one |SLA|." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:81 -msgid ":guilabel:`% of SLA in Progress`: percentage of tickets that have at least one :abbr:`SLA (Service Level Agreement)` still in progress, and have not failed any :abbr:`SLAs (Service Level Agreements)`" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/reports.rst:84 -msgid ":guilabel:`% of Successful SLA`: percentage of tickets where all :abbr:`SLAs (Service Level Agreements)` have been successful" +#: ../../content/applications/services/helpdesk/overview/reports.rst:83 +msgid ":guilabel:`Rating (/5)`: number value representing customer feedback (Dissatisfied = 1, Okay/Neutral = 3, Satisfied = 5)." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:86 -msgid ":guilabel:`Number of SLA Failed`: number of tickets that have failed at least one :abbr:`SLA (Service Level Agreement)`" +msgid ":guilabel:`Working Hours to Assign`: number of working hours between the date the ticket was created and when it was assigned to a team member." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:88 -msgid ":guilabel:`Number of SLA Successful`: number of tickets where all :abbr:`SLAs (Service Level Agreements)` have been successful" +msgid ":guilabel:`Working Hours to Close`: number of working hours between the date the ticket was created and the date it was closed." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:90 -msgid ":guilabel:`Number of SLA in Progress`: number of tickets that have at least one :abbr:`SLA (Service Level Agreement)` still in progress, and have not failed any :abbr:`SLAs (Service Level Agreements)`" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/reports.rst:93 -msgid ":guilabel:`Working Hours to Assign`: number of working hours between the date on which the ticket was created and when it was assigned to a team member" +msgid ":guilabel:`Working Hours to Reach SLA`: number of working hours between the date the ticket was created and the date the |SLA| was satisfied." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:95 -msgid ":guilabel:`Working Hours to Close`: number of working hours between the date on which the ticket was created and the date it was closed" +msgid ":doc:`Service Level Agreements (SLA) `" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:97 -msgid ":guilabel:`Working Hours to Reach SLA`: number of working hours between the date on which the ticket was created and the date the :abbr:`SLA (Service Level Agreement)` was satisfied" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/reports.rst:102 -msgid "To see the number of tickets that were able to achieve the stated :abbr:`SLA (Service Level Agreement)` objectives, and track the amount of time it took to achieve those objectives, click :menuselection:`Measures --> Number of SLA Successful` and :menuselection:`Measures --> Working Hours to Reach SLA`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/reports.rst:107 -msgid "To sort these results by the team members assigned to the tickets, select :menuselection:`Total --> Assigned to`." -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/reports.rst:111 -msgid ":doc:`Service Level Agreements (SLA) `" -msgstr "" - -#: ../../content/applications/services/helpdesk/overview/reports.rst:114 +#: ../../content/applications/services/helpdesk/overview/reports.rst:98 msgid "Customer Ratings" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:116 -msgid "The *Customer Ratings* report (:menuselection:`Helpdesk --> Reporting -- Customer Ratings`) displays an overview of the ratings received on individual support tickets, as well as any additional comments submitted with the rating." +#: ../../content/applications/services/helpdesk/overview/reports.rst:100 +msgid "The *Customer Ratings* report (:menuselection:`Helpdesk app--> Reporting --> Customer Ratings`) displays an overview of the ratings received on individual support tickets, as well as any additional comments submitted with the rating." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:-1 -msgid "View of the kanban display in the Customer Ratings report." +msgid "View of the Kanban display in the Customer Ratings report." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:124 +#: ../../content/applications/services/helpdesk/overview/reports.rst:108 msgid "Click on an individual rating to see additional details about the rating submitted by the customer, including a link to the original ticket." msgstr "" @@ -2408,66 +2391,66 @@ msgstr "" msgid "View of the details of an individual customer rating." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:132 -msgid "On the rating's details page, select the :guilabel:`Visible Internally Only` option to hide the rating from the customer portal." +#: ../../content/applications/services/helpdesk/overview/reports.rst:116 +msgid "On the rating's details page, tick the :guilabel:`Visible Internally Only` checkbox to hide the rating from the customer portal." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:135 -msgid "The *Customer Ratings* report is displayed in a kanban view by default, but can also be displayed in graph, list, or pivot view." +#: ../../content/applications/services/helpdesk/overview/reports.rst:119 +msgid "The *Customer Ratings* report is displayed in a Kanban view by default, but can also be displayed in graph, list, or pivot view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:139 -msgid ":doc:`Ratings `" +#: ../../content/applications/services/helpdesk/overview/reports.rst:123 +msgid ":doc:`Ratings `" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:142 +#: ../../content/applications/services/helpdesk/overview/reports.rst:126 msgid "View and filter options" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:144 +#: ../../content/applications/services/helpdesk/overview/reports.rst:128 msgid "On any Odoo report, the view and filter options vary, depending on what data is being analyzed, measured, and grouped. See below for additional information on the available views for the *Helpdesk* reports." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:149 +#: ../../content/applications/services/helpdesk/overview/reports.rst:133 msgid "Only one measure may be selected at a time for graphs, but pivot tables can include multiple measures." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:153 -#: ../../content/applications/services/helpdesk/overview/sla.rst:139 +#: ../../content/applications/services/helpdesk/overview/reports.rst:137 +#: ../../content/applications/services/helpdesk/overview/sla.rst:141 msgid "Pivot view" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:155 +#: ../../content/applications/services/helpdesk/overview/reports.rst:139 msgid "The *pivot* view presents data in an interactive manner. All three *Helpdesk* reports are available in pivot view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:158 -msgid "The pivot view can be accessed on any report by selecting the :guilabel:`grid icon` at the top right of the screen." +#: ../../content/applications/services/helpdesk/overview/reports.rst:142 +msgid "The pivot view can be accessed on any report by selecting the :icon:`oi-view-pivot` :guilabel:`(pivot)` icon at the top-right of the screen." msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:-1 -#: ../../content/applications/services/helpdesk/overview/sla.rst:149 +#: ../../content/applications/services/helpdesk/overview/sla.rst:151 msgid "View of the SLA status analysis report in Odoo Helpdesk." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:165 -msgid "To add a group to a row or column to the pivot view, click the :guilabel:`➕ (plus sign)` next to :guilabel:`Total`, and then select one of the groups. To remove one, click the :guilabel:`➖ (minus sign)` and de-select the appropriate option." +#: ../../content/applications/services/helpdesk/overview/reports.rst:149 +msgid "To add a group to a row or column to the pivot view, click the :icon:`fa-plus-square` :guilabel:`(plus)` icon next to :guilabel:`Total`, and then select one of the groups. To remove one, click the :icon:`fa-minus-square-o` :guilabel:`(minus)` icon, and de-select the appropriate option." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:170 -#: ../../content/applications/services/helpdesk/overview/sla.rst:171 +#: ../../content/applications/services/helpdesk/overview/reports.rst:154 +#: ../../content/applications/services/helpdesk/overview/sla.rst:173 msgid "Graph view" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:172 +#: ../../content/applications/services/helpdesk/overview/reports.rst:156 msgid "The *graph* view presents data in either a *bar*, *line*, or *pie* chart." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:174 -msgid "Switch to the graph view by selecting the :guilabel:`line chart icon` at the top right of the screen. To switch between the different charts, select the *related icon* at the top left of the chart, while in graph view." +#: ../../content/applications/services/helpdesk/overview/reports.rst:158 +msgid "Switch to the graph view by selecting the :icon:`fa-area-chart` :guilabel:`(area chart)` icon at the top-right of the screen. To switch between the different charts, select the *related icon* at the top-left of the chart, while in graph view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:180 +#: ../../content/applications/services/helpdesk/overview/reports.rst:164 msgid "Bar chart" msgstr "" @@ -2476,7 +2459,7 @@ msgstr "" msgid "View of the SLA status analysis report in bar view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:186 +#: ../../content/applications/services/helpdesk/overview/reports.rst:170 msgid "Line chart" msgstr "" @@ -2484,7 +2467,7 @@ msgstr "" msgid "View of the Customer Ratings report in line view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:192 +#: ../../content/applications/services/helpdesk/overview/reports.rst:176 msgid "Pie chart" msgstr "" @@ -2492,43 +2475,47 @@ msgstr "" msgid "View of the Ticket analysis report in pie chart view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:199 -msgid "Both the *bar chart* and *line chart* can utilize the *stacked* view option. This presents two (or more) groups of data on top of each other, instead of next to each other, making it easier to compare data." +#: ../../content/applications/services/helpdesk/overview/reports.rst:183 +msgid "Both the *bar chart* and *line chart* can utilize the *stacked* view option. This presents two or more groups of data on top of each other, instead of next to each other, making it easier to compare data. While viewing either a bar chart or line chart, click the :icon:`fa-database` :guilabel:`(stacked)` icon to toggle the stacked view option on or off." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:204 +#: ../../content/applications/services/helpdesk/overview/reports.rst:189 msgid "Save and share a favorite search" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:206 -msgid "The *Favorites* feature found on *Helpdesk* reports allows users to save their most commonly used filters without having to reconstruct them every time they are needed." +#: ../../content/applications/services/helpdesk/overview/reports.rst:191 +msgid "The *Favorites* feature found on *Helpdesk* reports allows users to save their most commonly used filters, without having to reconstruct them every time they are needed." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:209 -msgid "To create and save new *Favorites* on a report, follow the steps below:" +#: ../../content/applications/services/helpdesk/overview/reports.rst:194 +msgid "To create and save a new *Favorites* configuration on a report, follow the steps below:" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:211 +#: ../../content/applications/services/helpdesk/overview/reports.rst:196 msgid "Set the necessary parameters using the :guilabel:`Filters`, :guilabel:`Group By` and :guilabel:`Measures` options." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:213 -msgid "Click :menuselection:`Favorites --> Save current search`." +#: ../../content/applications/services/helpdesk/overview/reports.rst:198 +msgid "Click the :icon:`fa-caret-down` :guilabel:`(down)` icon next to the :guilabel:`Search...` bar to open the drop-down menu." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:214 -msgid "Rename the search." +#: ../../content/applications/services/helpdesk/overview/reports.rst:200 +msgid "Under the :guilabel:`Favorites` heading, click :guilabel:`Save current search`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:215 -msgid "Select :guilabel:`Use by default` to have these filter settings automatically displayed when the report is opened. Otherwise, leave it blank." +#: ../../content/applications/services/helpdesk/overview/reports.rst:201 +msgid "If desired, enter a new name for the report." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:217 -msgid "Select :guilabel:`Share with all users` to make this filter available to all other database users. If this box is not checked, it will only be available to the user who creates it." +#: ../../content/applications/services/helpdesk/overview/reports.rst:202 +msgid "Tick the :guilabel:`Default Filter` checkbox to have these filter settings automatically displayed when the report is opened. Otherwise, leave it blank." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:219 +#: ../../content/applications/services/helpdesk/overview/reports.rst:204 +msgid "Tick the :guilabel:`Shared` checkbox to make this filter configuration available to all other database users. If this checkbox is not ticked, only the user who creates the filter can access it." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:207 msgid "Click :guilabel:`Save` to preserve the configuration for future use." msgstr "" @@ -2536,12 +2523,12 @@ msgstr "" msgid "View of the save favorites option in Odoo Helpdesk." msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:226 -msgid ":doc:`Start receiving tickets `" +#: ../../content/applications/services/helpdesk/overview/reports.rst:214 +msgid ":doc:`Start receiving tickets `" msgstr "" -#: ../../content/applications/services/helpdesk/overview/reports.rst:227 -msgid ":doc:`Odoo reporting `" +#: ../../content/applications/services/helpdesk/overview/reports.rst:215 +msgid ":doc:`Odoo reporting <../../../essentials/reporting>`" msgstr "" #: ../../content/applications/services/helpdesk/overview/sla.rst:3 @@ -2692,27 +2679,27 @@ msgstr "" msgid "View of a ticket's form with a failing and passing SLA in Odoo Helpdesk." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:131 +#: ../../content/applications/services/helpdesk/overview/sla.rst:133 msgid "Analyze SLA performance" msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:133 +#: ../../content/applications/services/helpdesk/overview/sla.rst:135 msgid "The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA (Service Level Agreement)` is fulfilled, as well as the performance of individual team members. Navigate to the report, and corresponding pivot table, by going to :menuselection:`Helpdesk app --> Reporting --> SLA Status Analysis`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:141 +#: ../../content/applications/services/helpdesk/overview/sla.rst:143 msgid "By default, the report displays in a :guilabel:`Pivot` view. Any :abbr:`SLA (Service Level Agreement)` policies in the database with tickets that failed to fulfill a policy, are in progress, or have satisfied a policy are listed. By default, they are grouped by team and ticket count." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:149 +#: ../../content/applications/services/helpdesk/overview/sla.rst:151 msgid "The pivot view aggregates data, which can be manipulated by adding measures and filters." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:151 +#: ../../content/applications/services/helpdesk/overview/sla.rst:153 msgid "To change the display, or add additional measurements, click the :guilabel:`Measures` button to reveal a drop-down menu of reporting criteria, and choose from the options available." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:154 +#: ../../content/applications/services/helpdesk/overview/sla.rst:156 msgid "Whenever a measurement is picked, a :guilabel:`✔️ (checkmark)` icon appears in the drop-down menu to indicate that the measurement is included, and a corresponding new column emerges in the pivot table to show the relevant calculations." msgstr "" @@ -2720,7 +2707,7 @@ msgstr "" msgid "View of the available measures in the SLA status analysis report." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:162 +#: ../../content/applications/services/helpdesk/overview/sla.rst:164 msgid "To add a group to a row or column, click the :guilabel:`➕ (plus)` icon next to the policy name and then select one of the groups. To remove one, click the :guilabel:`➖ (minus)` icon next to the policy name." msgstr "" @@ -2728,19 +2715,19 @@ msgstr "" msgid "View of the available group by options in the SLA status analysis report." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:173 +#: ../../content/applications/services/helpdesk/overview/sla.rst:175 msgid "The :guilabel:`SLA Status Analysis` report can also be viewed as a :guilabel:`Bar Chart`, :guilabel:`Line Chart`, or :guilabel:`Pie Chart`. Toggle between these views by first selecting the :guilabel:`Graph` button at the top-right of the dashboard. Then, select the appropriate chart icon at the top-left of the graph." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:180 +#: ../../content/applications/services/helpdesk/overview/sla.rst:182 msgid "Bar Chart" msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:186 +#: ../../content/applications/services/helpdesk/overview/sla.rst:188 msgid "A bar chart can deal with larger data sets and compare data across several categories." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:188 +#: ../../content/applications/services/helpdesk/overview/sla.rst:190 msgid "Line Chart" msgstr "" @@ -2748,11 +2735,11 @@ msgstr "" msgid "View of the SLA status analysis report in line view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:194 +#: ../../content/applications/services/helpdesk/overview/sla.rst:196 msgid "A line chart can visualize data trends or changes over time." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:196 +#: ../../content/applications/services/helpdesk/overview/sla.rst:198 msgid "Pie Chart" msgstr "" @@ -2760,11 +2747,11 @@ msgstr "" msgid "View of the SLA status analysis report in pie chart view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:202 +#: ../../content/applications/services/helpdesk/overview/sla.rst:204 msgid "A pie chart compares data among a small number of categories." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:205 +#: ../../content/applications/services/helpdesk/overview/sla.rst:207 msgid "Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` views can be :guilabel:`Stacked` by selecting the :guilabel:`Stacked` icon. This displays two or more groups on top of each other instead of next to each other, making it easier to compare data." msgstr "" @@ -2772,27 +2759,27 @@ msgstr "" msgid "View of the SLA status analysis report in bar view, stacked." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:214 +#: ../../content/applications/services/helpdesk/overview/sla.rst:216 msgid "Cohort view" msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:216 +#: ../../content/applications/services/helpdesk/overview/sla.rst:218 msgid "The :guilabel:`Cohort` view is used to track the changes in data over a period of time. To display the :guilabel:`SLA Status Analysis` report in a :guilabel:`Cohort` view, click the :guilabel:`Cohort` button, represented by :guilabel:`(four cascading horizontal lines)`, in the top-right corner, next to the other view options." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:225 +#: ../../content/applications/services/helpdesk/overview/sla.rst:227 msgid "View of the SLA status analysis report in cohort view." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:225 +#: ../../content/applications/services/helpdesk/overview/sla.rst:227 msgid "The cohort view examines the life cycle of data over time." msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:228 +#: ../../content/applications/services/helpdesk/overview/sla.rst:230 msgid ":ref:`Reporting views `" msgstr "" -#: ../../content/applications/services/helpdesk/overview/sla.rst:229 +#: ../../content/applications/services/helpdesk/overview/sla.rst:231 msgid ":doc:`Allow customers to close their tickets `" msgstr "" diff --git a/locale/sources/studio.pot b/locale/sources/studio.pot index 884f6872c..dfec9b099 100644 --- a/locale/sources/studio.pot +++ b/locale/sources/studio.pot @@ -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 \n" "Language-Team: LANGUAGE \n" @@ -61,19 +61,31 @@ msgid "`Odoo Tutorials: Studio `_" 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 ` 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 ` of the automation rule, switch models before clicking :guilabel:`Automations` in Studio, or :ref:`activate the 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 `. 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 ` and :ref:`Apply on ` 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 `, 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 `, 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 `, 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 `, 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 `, 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 `, 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 ` 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 ` existing on the current model that are linked to a :ref:`many2one field ` 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 diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index d77a64328..da94da0ce 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -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 \n" "Language-Team: LANGUAGE \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 `, theme, pages, menus, :doc:`languages `, :doc:`products <../../ecommerce/managing_products/products>`, assigned sales team, etc. They can also :ref:`share content and pages `." +msgid "Each website can be designed and configured independently with its own :doc:`domain name `, :doc:`theme <../web_design/themes>`, :doc:`pages <../pages>`, :doc:`menus <../pages/menus>`, :doc:`languages `, :doc:`products <../../ecommerce/managing_products/products>`, assigned sales team, etc. They can also :ref:`share content and pages `." 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 `, 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 `." 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 `. 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 `. 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 ` 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 `_." +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 `_" 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 `_" 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 `_ a Cloudflare account or use an existing one and `log in `_." 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 `_. 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 `_. 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 `, 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 `, 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 ` 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 `, 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 ` 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 ` 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 `:" 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) ` 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 `." 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 ` 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 `), 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 `, :ref:`modify its URL `, or move your site to a new :doc:`domain `. 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 `, :ref:`modify its URL `, or migrate your site from another platform to an Odoo :doc:`domain `. 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 ` 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 ` 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 ` 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 `." 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 `. 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 `. 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 ` 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 ` or :ref:`deleted `." +#: ../../content/applications/websites/website/pages.rst:187 +msgid "404, 301, and 302 redirections are meant to migrate traffic from :ref:`unpublished ` or :ref:`deleted ` 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 `_" 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 `` and `` 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:`` and :guilabel:`` 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 ` 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 ` and the :ref:`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 ""