diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 6148009d1..936bf81ad 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -412,7 +412,7 @@ msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimatio msgstr "" #: ../../content/administration/install/deploy.rst:225 -#: ../../content/administration/install/deploy.rst:382 +#: ../../content/administration/install/deploy.rst:412 msgid "LiveChat" msgstr "" @@ -484,308 +484,324 @@ msgstr "" msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" msgstr "" -#: ../../content/administration/install/deploy.rst:356 -msgid "Odoo as a WSGI Application" +#: ../../content/administration/install/deploy.rst:361 +msgid "HTTPS Hardening" msgstr "" -#: ../../content/administration/install/deploy.rst:358 -msgid "It is also possible to mount Odoo as a standard WSGI_ application. Odoo provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That script should be customized (possibly after copying it from the setup directory) to correctly set the configuration directly in :mod:`odoo.tools.config` rather than through the command-line or a configuration file." -msgstr "" - -#: ../../content/administration/install/deploy.rst:364 -msgid "However the WSGI server will only expose the main HTTP endpoint for the web client, website and webservice API. Because Odoo does not control the creation of workers anymore it can not setup cron or livechat workers" +#: ../../content/administration/install/deploy.rst:363 +msgid "Add the `Strict-Transport-Security` header to all requests, in order to prevent browsers from ever sending a plain HTTP request to this domain. You will need to maintain a working HTTPS service with a valid certificate on this domain at all times, otherwise your users will see security alerts or be entirely unable to access it." msgstr "" #: ../../content/administration/install/deploy.rst:369 -msgid "Cron Workers" +msgid "Force HTTPS connections during a year for every visitor in NGINX with the line:" msgstr "" -#: ../../content/administration/install/deploy.rst:371 -msgid "Starting one of the built-in Odoo servers next to the WSGI server is required to process cron jobs. That server must be configured to only process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file setting." +#: ../../content/administration/install/deploy.rst:375 +msgid "Additional configuration can be defined for the `session_id` cookie. The `Secure` flag can be added to ensure it is never transmitted over HTTP and `SameSite=Lax` to prevent authenticated `CSRF`_." msgstr "" -#: ../../content/administration/install/deploy.rst:376 -msgid "On Linux-like systems, using the multi-processing server over the multi-threading one is recommended to benefit from better hardware usage and increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n ` cli options." +#: ../../content/administration/install/deploy.rst:386 +msgid "Odoo as a WSGI Application" msgstr "" -#: ../../content/administration/install/deploy.rst:384 -msgid "Using a gevent-compatible WSGI server is required for the correct operation of the live chat feature. That server should be able to handle many simultaneous long-lived connections but doesn't need a lot of processing power. All requests whose path starts with ``/websocket/`` should be directed to that server. A regular (thread/process-based) WSGI server should be used for all other requests." +#: ../../content/administration/install/deploy.rst:388 +msgid "It is also possible to mount Odoo as a standard WSGI_ application. Odoo provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That script should be customized (possibly after copying it from the setup directory) to correctly set the configuration directly in :mod:`odoo.tools.config` rather than through the command-line or a configuration file." msgstr "" -#: ../../content/administration/install/deploy.rst:390 -msgid "The Odoo cron server can also be used to serve the live chat requests. Just drop the :option:`--no-http ` cli option from the cron server and make sure requests whose path starts with ``/websocket/`` are directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port ` (multi-processing server)." +#: ../../content/administration/install/deploy.rst:394 +msgid "However the WSGI server will only expose the main HTTP endpoint for the web client, website and webservice API. Because Odoo does not control the creation of workers anymore it can not setup cron or livechat workers" msgstr "" #: ../../content/administration/install/deploy.rst:399 -msgid "Serving static files and attachments" +msgid "Cron Workers" msgstr "" #: ../../content/administration/install/deploy.rst:401 -msgid "For development convenience, Odoo directly serves all static files and attachments in its modules. This may not be ideal when it comes to performances, and static files should generally be served by a static HTTP server." +msgid "Starting one of the built-in Odoo servers next to the WSGI server is required to process cron jobs. That server must be configured to only process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file setting." msgstr "" #: ../../content/administration/install/deploy.rst:406 +msgid "On Linux-like systems, using the multi-processing server over the multi-threading one is recommended to benefit from better hardware usage and increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n ` cli options." +msgstr "" + +#: ../../content/administration/install/deploy.rst:414 +msgid "Using a gevent-compatible WSGI server is required for the correct operation of the live chat feature. That server should be able to handle many simultaneous long-lived connections but doesn't need a lot of processing power. All requests whose path starts with ``/websocket/`` should be directed to that server. A regular (thread/process-based) WSGI server should be used for all other requests." +msgstr "" + +#: ../../content/administration/install/deploy.rst:420 +msgid "The Odoo cron server can also be used to serve the live chat requests. Just drop the :option:`--no-http ` cli option from the cron server and make sure requests whose path starts with ``/websocket/`` are directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port ` (multi-processing server)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:429 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/install/deploy.rst:431 +msgid "For development convenience, Odoo directly serves all static files and attachments in its modules. This may not be ideal when it comes to performances, and static files should generally be served by a static HTTP server." +msgstr "" + +#: ../../content/administration/install/deploy.rst:436 msgid "Serving static files" msgstr "" -#: ../../content/administration/install/deploy.rst:408 +#: ../../content/administration/install/deploy.rst:438 msgid "Odoo static files are located in each module's :file:`static/` folder, so static files can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) in the various addons paths." msgstr "" -#: ../../content/administration/install/deploy.rst:413 +#: ../../content/administration/install/deploy.rst:443 msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise and the :option:`--addons-path ` is ``'/usr/lib/python3/dist-packages/odoo/addons'``." msgstr "" -#: ../../content/administration/install/deploy.rst:416 -#: ../../content/administration/install/deploy.rst:438 +#: ../../content/administration/install/deploy.rst:446 +#: ../../content/administration/install/deploy.rst:468 msgid "Using the above NGINX (https) configuration, the following location block should be added to serve static files via NGINX." msgstr "" -#: ../../content/administration/install/deploy.rst:433 +#: ../../content/administration/install/deploy.rst:463 msgid "Say Odoo has been installed via the **source**. The two git repositories for Community and Enterprise have been cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively and the :option:`--addons-path ` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." msgstr "" -#: ../../content/administration/install/deploy.rst:455 +#: ../../content/administration/install/deploy.rst:485 msgid "The actual NGINX configuration you need is highly dependent on your own installation. The two above snippets only highlight two possible configurations and may not be used as-is." msgstr "" -#: ../../content/administration/install/deploy.rst:459 +#: ../../content/administration/install/deploy.rst:489 msgid "Serving attachments" msgstr "" -#: ../../content/administration/install/deploy.rst:461 +#: ../../content/administration/install/deploy.rst:491 msgid "Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be directly accessed via a static web server as accessing them requires multiple lookups in the database to determine where the files are stored and whether the current user can access them or not." msgstr "" -#: ../../content/administration/install/deploy.rst:466 +#: ../../content/administration/install/deploy.rst:496 msgid "Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving files to the static web server, the `X-Sendfile `_ (apache) or `X-Accel `_ (nginx) extensions must be enabled and configured on the static web server. Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and X-Accel)." msgstr "" -#: ../../content/administration/install/deploy.rst:476 +#: ../../content/administration/install/deploy.rst:506 msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration." msgstr "" -#: ../../content/administration/install/deploy.rst:478 +#: ../../content/administration/install/deploy.rst:508 msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:" msgstr "" -#: ../../content/administration/install/deploy.rst:487 +#: ../../content/administration/install/deploy.rst:517 msgid "In case you don't know what is the path to your filestore, start Odoo with the :option:`--x-sendfile ` option and navigate to the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message contains the configuration you need." msgstr "" -#: ../../content/administration/install/deploy.rst:496 +#: ../../content/administration/install/deploy.rst:526 msgid "Security" msgstr "" -#: ../../content/administration/install/deploy.rst:498 +#: ../../content/administration/install/deploy.rst:528 msgid "For starters, keep in mind that securing an information system is a continuous process, not a one-shot operation. At any moment, you will only be as secure as the weakest link in your environment." msgstr "" -#: ../../content/administration/install/deploy.rst:502 +#: ../../content/administration/install/deploy.rst:532 msgid "So please do not take this section as the ultimate list of measures that will prevent all security problems. It's only intended as a summary of the first important things you should be sure to include in your security action plan. The rest will come from best security practices for your operating system and distribution, best practices in terms of users, passwords, and access control management, etc." msgstr "" -#: ../../content/administration/install/deploy.rst:508 +#: ../../content/administration/install/deploy.rst:538 msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:" msgstr "" -#: ../../content/administration/install/deploy.rst:511 +#: ../../content/administration/install/deploy.rst:541 msgid "Always set a strong super-admin admin password, and restrict access to the database management pages as soon as the system is set up. See :ref:`db_manager_security`." msgstr "" -#: ../../content/administration/install/deploy.rst:514 +#: ../../content/administration/install/deploy.rst:544 msgid "Choose unique logins and strong passwords for all administrator accounts on all databases. Do not use 'admin' as the login. Do not use those logins for day-to-day operations, only for controlling/managing the installation. *Never* use any default passwords like admin/admin, even for test/staging databases." msgstr "" -#: ../../content/administration/install/deploy.rst:519 +#: ../../content/administration/install/deploy.rst:549 msgid "Do **not** install demo data on internet-facing servers. Databases with demo data contain default logins and passwords that can be used to get into your systems and cause significant trouble, even on staging/dev systems." msgstr "" -#: ../../content/administration/install/deploy.rst:523 +#: ../../content/administration/install/deploy.rst:553 msgid "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. You may also use :option:`-d ` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend." msgstr "" -#: ../../content/administration/install/deploy.rst:530 +#: ../../content/administration/install/deploy.rst:560 msgid "Once your ``db_name`` and ``db_filter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list ` command-line option)" msgstr "" -#: ../../content/administration/install/deploy.rst:536 +#: ../../content/administration/install/deploy.rst:566 msgid "Make sure the PostgreSQL user (:option:`--db_user `) is *not* a super-user, and that your databases are owned by a different user. For example they could be owned by the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``. See also :ref:`setup/deploy/odoo`." msgstr "" -#: ../../content/administration/install/deploy.rst:541 +#: ../../content/administration/install/deploy.rst:571 msgid "Keep installations updated by regularly installing the latest builds, either via GitHub or by downloading the latest version from https://www.odoo.com/page/download or http://nightly.odoo.com" msgstr "" -#: ../../content/administration/install/deploy.rst:545 +#: ../../content/administration/install/deploy.rst:575 msgid "Configure your server in multi-process mode with proper limits matching your typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." msgstr "" -#: ../../content/administration/install/deploy.rst:548 +#: ../../content/administration/install/deploy.rst:578 msgid "Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate, in order to prevent eavesdropping on cleartext communications. SSL certificates are cheap, and many free options exist. Configure the web proxy to limit the size of requests, set appropriate timeouts, and then enable the :option:`proxy mode ` option. See also :ref:`https_proxy`." msgstr "" -#: ../../content/administration/install/deploy.rst:555 +#: ../../content/administration/install/deploy.rst:585 msgid "If you need to allow remote SSH access to your servers, make sure to set a strong password for **all** accounts, not just `root`. It is strongly recommended to entirely disable password-based authentication, and only allow public key authentication. Also consider restricting access via a VPN, allowing only trusted IPs in the firewall, and/or running a brute-force detection system such as `fail2ban` or equivalent." msgstr "" -#: ../../content/administration/install/deploy.rst:561 +#: ../../content/administration/install/deploy.rst:591 msgid "Consider installing appropriate rate-limiting on your proxy or firewall, to prevent brute-force attacks and denial of service attacks. See also :ref:`login_brute_force` for specific measures." msgstr "" -#: ../../content/administration/install/deploy.rst:565 +#: ../../content/administration/install/deploy.rst:595 msgid "Many network providers provide automatic mitigation for Distributed Denial of Service attacks (DDOS), but this is often an optional service, so you should consult with them." msgstr "" -#: ../../content/administration/install/deploy.rst:569 +#: ../../content/administration/install/deploy.rst:599 msgid "Whenever possible, host your public-facing demo/test/staging instances on different machines than the production ones. And apply the same security precautions as for production." msgstr "" -#: ../../content/administration/install/deploy.rst:573 +#: ../../content/administration/install/deploy.rst:603 msgid "If your public-facing Odoo server has access to sensitive internal network resources or services (e.g. via a private VLAN), implement appropriate firewall rules to protect those internal resources. This will ensure that the Odoo server cannot be used accidentally (or as a result of malicious user actions) to access or disrupt those internal resources. Typically this can be done by applying an outbound default DENY rule on the firewall, then only explicitly authorizing access to internal resources that the Odoo server needs to access. `Systemd IP traffic access control `_ may also be useful to implement per-process network access control." msgstr "" -#: ../../content/administration/install/deploy.rst:584 +#: ../../content/administration/install/deploy.rst:614 msgid "If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer, a transparent DDoS protection service (like CloudFlare) or a similar network-level device, you may wish to avoid direct access to the Odoo system. It is generally difficult to keep the endpoint IP addresses of your Odoo servers secret. For example they can appear in web server logs when querying public systems, or in the headers of emails posted from Odoo. In such a situation you may want to configure your firewall so that the endpoints are not accessible publicly except from the specific IP addresses of your WAF, load-balancer or proxy service. Service providers like CloudFlare usually maintain a public list of their IP address ranges for this purpose." msgstr "" -#: ../../content/administration/install/deploy.rst:595 +#: ../../content/administration/install/deploy.rst:625 msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques." msgstr "" -#: ../../content/administration/install/deploy.rst:598 +#: ../../content/administration/install/deploy.rst:628 msgid "Setup daily backups of your databases and filestore data, and copy them to a remote archiving server that is not accessible from the server itself." msgstr "" -#: ../../content/administration/install/deploy.rst:601 +#: ../../content/administration/install/deploy.rst:631 msgid "Deploying Odoo on Linux is strongly recommended over Windows. Should you choose nevertheless to deploy on a Windows platform, a thorough security hardening review of the server should be conducted and is outside of the scope of this guide." msgstr "" -#: ../../content/administration/install/deploy.rst:609 +#: ../../content/administration/install/deploy.rst:639 msgid "Blocking Brute Force Attacks" msgstr "" -#: ../../content/administration/install/deploy.rst:611 +#: ../../content/administration/install/deploy.rst:641 msgid "For internet-facing deployments, brute force attacks on user passwords are very common, and this threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt is performed, and reports the result: success or failure, along with the target login and source IP." msgstr "" -#: ../../content/administration/install/deploy.rst:615 +#: ../../content/administration/install/deploy.rst:645 msgid "The log entries will have the following form." msgstr "" -#: ../../content/administration/install/deploy.rst:617 +#: ../../content/administration/install/deploy.rst:647 msgid "Failed login::" msgstr "" -#: ../../content/administration/install/deploy.rst:621 +#: ../../content/administration/install/deploy.rst:651 msgid "Successful login::" msgstr "" -#: ../../content/administration/install/deploy.rst:626 +#: ../../content/administration/install/deploy.rst:656 msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`." msgstr "" -#: ../../content/administration/install/deploy.rst:628 +#: ../../content/administration/install/deploy.rst:658 msgid "For example, the following fail2ban filter definition should match a failed login::" msgstr "" -#: ../../content/administration/install/deploy.rst:635 +#: ../../content/administration/install/deploy.rst:665 msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)." msgstr "" -#: ../../content/administration/install/deploy.rst:637 +#: ../../content/administration/install/deploy.rst:667 msgid "Here is what it could look like for blocking the IP for 15 minutes when 10 failed login attempts are detected from the same IP within 1 minute::" msgstr "" -#: ../../content/administration/install/deploy.rst:651 +#: ../../content/administration/install/deploy.rst:681 msgid "Database Manager Security" msgstr "" -#: ../../content/administration/install/deploy.rst:653 +#: ../../content/administration/install/deploy.rst:683 msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." msgstr "" -#: ../../content/administration/install/deploy.rst:655 +#: ../../content/administration/install/deploy.rst:685 msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)." msgstr "" -#: ../../content/administration/install/deploy.rst:658 +#: ../../content/administration/install/deploy.rst:688 msgid "If the management screens must not be accessible at all, you should set ``list_db`` configuration option to ``False``, to block access to all the database selection and management screens." msgstr "" -#: ../../content/administration/install/deploy.rst:664 +#: ../../content/administration/install/deploy.rst:694 msgid "It is strongly recommended to disable the Database Manager for any internet-facing system! It is meant as a development/demo tool, to make it easy to quickly create and manage databases. It is not designed for use in production, and may even expose dangerous features to attackers. It is also not designed to handle large databases, and may trigger memory limits." msgstr "" -#: ../../content/administration/install/deploy.rst:670 +#: ../../content/administration/install/deploy.rst:700 msgid "On production systems, database management operations should always be performed by the system administrator, including provisioning of new databases and automated backups." msgstr "" -#: ../../content/administration/install/deploy.rst:673 +#: ../../content/administration/install/deploy.rst:703 msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``db_filter`` too) so that the system can determine the target database for each request, otherwise users will be blocked as they won't be allowed to choose the database themselves." msgstr "" -#: ../../content/administration/install/deploy.rst:678 +#: ../../content/administration/install/deploy.rst:708 msgid "If the management screens must only be accessible from a selected set of machines, use the proxy server's features to block access to all routes starting with ``/web/database`` except (maybe) ``/web/database/selector`` which displays the database-selection screen." msgstr "" -#: ../../content/administration/install/deploy.rst:682 +#: ../../content/administration/install/deploy.rst:712 msgid "If the database-management screen should be left accessible, the ``admin_passwd`` setting must be changed from its ``admin`` default: this password is checked before allowing database-alteration operations." msgstr "" -#: ../../content/administration/install/deploy.rst:686 +#: ../../content/administration/install/deploy.rst:716 msgid "It should be stored securely, and should be generated randomly e.g." msgstr "" -#: ../../content/administration/install/deploy.rst:692 +#: ../../content/administration/install/deploy.rst:722 msgid "which will generate a 32 characters pseudorandom printable string." msgstr "" -#: ../../content/administration/install/deploy.rst:695 +#: ../../content/administration/install/deploy.rst:725 msgid "Supported Browsers" msgstr "" -#: ../../content/administration/install/deploy.rst:697 +#: ../../content/administration/install/deploy.rst:727 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/install/deploy.rst:700 +#: ../../content/administration/install/deploy.rst:730 msgid "Here are the supported browsers:" msgstr "" -#: ../../content/administration/install/deploy.rst:702 +#: ../../content/administration/install/deploy.rst:732 msgid "Google Chrome" msgstr "" -#: ../../content/administration/install/deploy.rst:703 +#: ../../content/administration/install/deploy.rst:733 msgid "Mozilla Firefox" msgstr "" -#: ../../content/administration/install/deploy.rst:704 +#: ../../content/administration/install/deploy.rst:734 msgid "Microsoft Edge" msgstr "" -#: ../../content/administration/install/deploy.rst:705 +#: ../../content/administration/install/deploy.rst:735 msgid "Apple Safari" msgstr "" -#: ../../content/administration/install/deploy.rst:707 +#: ../../content/administration/install/deploy.rst:737 msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report." msgstr "" -#: ../../content/administration/install/deploy.rst:712 +#: ../../content/administration/install/deploy.rst:742 msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." msgstr "" -#: ../../content/administration/install/deploy.rst:715 +#: ../../content/administration/install/deploy.rst:745 msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software." msgstr "" -#: ../../content/administration/install/deploy.rst:718 +#: ../../content/administration/install/deploy.rst:748 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/install/deploy.rst:722 +#: ../../content/administration/install/deploy.rst:752 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 "" @@ -1432,11 +1448,11 @@ msgid "Create a new application" msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:24 -msgid "To get started, go to `Microsoft's Azure Portal `_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings will need to connect and perform the following configuration. Next, navigate to the section labeled :guilabel:`Manage Azure Active Directory`." +msgid "To get started, go to `Microsoft's Azure Portal `_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings will need to connect and perform the following configuration. Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*)." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:30 -msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select :guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`." +msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`." msgstr "" #: ../../content/administration/maintain/azure_oauth.rst:36 diff --git a/locale/sources/developer.pot b/locale/sources/developer.pot index 57fa64431..2fb885915 100644 --- a/locale/sources/developer.pot +++ b/locale/sources/developer.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1961,7 +1961,7 @@ msgid "Exporting translatable term" msgstr "" #: ../../content/developer/howtos/translations.rst:15 -msgid "A number of terms in your modules are \"implicitly translatable\" as a result, even if you haven't done any specific work towards translation you can export your module's translatable terms and may find content to work with." +msgid "A number of terms in your modules are implicitly translatable. As a result, even if you haven't done any specific work towards translation, you can export your module's translatable terms and may find content to work with." msgstr "" #: ../../content/developer/howtos/translations.rst:19 @@ -13929,7 +13929,7 @@ msgstr "" msgid "This tool allows to quickly filter data on the basis of given fields. The fields are specified as direct children of the ``searchpanel`` with tag name ``field``, and the following attributes:" msgstr "" -#: ../../content/developer/reference/backend/views.rst:2438 +#: ../../content/developer/reference/backend/views.rst:2385 msgid "``select``" msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 067e33fb4..11df223ba 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -428,7 +428,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 #: ../../content/applications/finance/fiscal_localizations/australia.rst:18 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:413 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:415 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:25 #: ../../content/applications/finance/fiscal_localizations/chile.rst:25 #: ../../content/applications/finance/fiscal_localizations/chile.rst:286 @@ -13106,50 +13106,50 @@ msgid "At the start of a POS session, users must click :guilabel:`Work in` to cl msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:395 -msgid "If you configure a POS to work with a black box, you cannot use it again without it." +msgid "If you configure a POS to work with a :abbr:`FDM (Fiscal Data Module)`, you cannot use it again without it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:400 -msgid "The Fiscal Data Module" +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 +msgid "Fiscal Data Module (FDM)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:402 -msgid "The :abbr:`FDM (Fiscal Data Module)`, or `black box `_, is a government-certified device that works together with the Point of Sale application and saves your POS orders information. Concretely, a **hash** (:dfn:`unique code`) is generated for each POS order and added to its receipt. This allows the government to verify that all revenue is declared." +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:403 +msgid "An FDM, or **black box**, is a government-certified device that works together with the Point of Sale application and saves your POS orders information. Concretely, a **hash** (:dfn:`unique code`) is generated for each POS order and added to its receipt. This allows the government to verify that all revenue is declared." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:408 -msgid "Ensure your black box is approved by the Belgian government. You can check the compliance of your black box by visiting the `Federal Public Service Finance `_ website." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:415 -msgid "Before setting up your database to work with an FDM, ensure you have the following hardware:" +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:409 +msgid "Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC01 `_ is supported by Odoo. `Contact the manufacturer (GCV BMC) `_ to order one." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:417 -msgid "a registered :ref:`black box ` (go to `www.boîtenoire.be `_ to order yours);" +msgid "Before setting up your database to work with an FDM, ensure you have the following hardware:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:419 -msgid "an RS-232 serial null modem cable per FDM;" +msgid "a **Boîtenoire.be** (certificate number BMC01) FDM;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:420 -msgid "an RS-232 serial-to-USB adapter per FDM;" +msgid "an RS-232 serial null modem cable per FDM;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:421 -msgid "an :ref:`IoT Box ` (one IoT box per black box); and" +msgid "an RS-232 serial-to-USB adapter per FDM;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:422 +msgid "an :ref:`IoT Box ` (one IoT box per FDM); and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:423 msgid "a receipt printer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:427 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:428 msgid "Black box module" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:430 msgid "As a pre-requisite, :ref:`activate ` the `Belgian Registered Cash Register` module (technical name: `pos_blackbox_be`)." msgstr "" @@ -13157,7 +13157,7 @@ msgstr "" msgid "black box modules for belgian fiscal certification" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:435 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:436 msgid "Once the module is activated, add your VAT number to your company information. To set it up, go to :menuselection:`Settings --> Companies --> Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national registration number for every staff member who operates the POS system. To do so, go to the :guilabel:`Employees` app and open an employee form. There, go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and fill in the :guilabel:`INSZ or BIS number` field." msgstr "" @@ -13165,35 +13165,35 @@ msgstr "" msgid "ISNZ or BIS number field on employee form" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:445 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:446 msgid "To input your information, click on your avatar, go to :menuselection:`My Profile --> Preference tab`, and enter your INSZ or BIS number in the designated field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:449 -msgid "You must configure the black box directly in the production database. Utilizing it in a testing environment may result in incorrect data being stored within the black box." +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:450 +msgid "You must configure the :abbr:`FDM (Fiscal Data Module)` directly in the production database. Utilizing it in a testing environment may result in incorrect data being stored within the FDM." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:455 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:456 msgid "IoT Box" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:457 -msgid "In order to use a Fiscal Data Module, you need a registered IoT Box. To register your IoT box, you must contact us through our `support contact form `_ and provide the following information:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:461 -msgid "your VAT number;" +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:458 +msgid "In order to use an :abbr:`FDM (Fiscal Data Module)`, you need a registered IoT Box. To register your IoT box, you must contact us through our `support contact form `_ and provide the following information:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:462 -msgid "your company's name, address, and legal structure; and" +msgid "your VAT number;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:463 +msgid "your company's name, address, and legal structure; and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:464 msgid "the Mac address of your IoT Box." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:465 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:466 msgid "Once your IoT box is certified, :doc:`connect <../../productivity/iot/config/connect>` it to your database. To verify that the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the :guilabel:`IOT Device` section, which should display the FDM." msgstr "" @@ -13201,19 +13201,19 @@ msgstr "" msgid "Hardware status page on a registered IoT Box" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:472 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:473 msgid "Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select your POS, scroll down to the :guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:477 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:478 msgid "To be able to use an FDM, you must at least connect one :guilabel:`Receipt Printer`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:482 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:483 msgid "VAT signing card" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:484 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:485 msgid "When you open a POS session and make your initial transaction, you are prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`. The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` upon `registration `_." msgstr "" @@ -21166,7 +21166,7 @@ msgid "Electronic Invoice Status" msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst:404 -msgid "**To be Sent**: To be sent: Indicates the document is ready to be sent to the OSE, this can be done either automatically by Odoo with a *cron* that runs every hour, or the user can send it immediately by clicking on the button “Sent now”." +msgid "**To be Sent**: Indicates the document is ready to be sent to the OSE, this can be done either automatically by Odoo with a *cron* that runs every hour, or the user can send it immediately by clicking on the button “Sent now”." msgstr "" #: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 5ea816b3c..0ce186639 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -282,7 +282,7 @@ msgid "A user with administrative access to the *Azure Settings* must connect an msgstr "" #: ../../content/applications/general/auth/azure.rst:53 -msgid "Next, navigate to the section labeled :guilabel:`Manage Azure Active Directory`. The location of this link is usually in the center of the page." +msgid "Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*). The location of this link is usually in the center of the page." msgstr "" #: ../../content/applications/general/auth/azure.rst:56 @@ -1616,7 +1616,7 @@ msgid "Creating different templates that are tailored to specific situations let msgstr "" #: ../../content/applications/general/email_communication/email_template.rst:13 -msgid "Email templates in Odoo use QWeb or XML, which allows for editing emails in their final rendering, making customizations more robust, without having to edit any code whatsoever. This means that Odoo can use a Graphical User Interface (GUI) to edit emails, which edits the backend code. When the received email is read by the end user's program, different formatting an graphics will appear in the final form of it." +msgid "Email templates in Odoo use QWeb or XML, which allows for editing emails in their final rendering, making customizations more robust, without having to edit any code whatsoever. This means that Odoo can use a Graphical User Interface (GUI) to edit emails, which edits the backend code. When the received email is read by the end user's program, different formatting and graphics will appear in the final form of it." msgstr "" #: ../../content/applications/general/email_communication/email_template.rst:19 @@ -2725,46 +2725,50 @@ msgid "IAP accounts" msgstr "" #: ../../content/applications/general/in_app_purchase.rst:27 -msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service and database. By default, IAP accounts are common to all companies, but can be restricted to specific ones. Activate the :ref:`developer mode `, then go to :menuselection:`Technical Settings --> IAP Account`." +msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service. By default, IAP accounts are common to all companies, but can be restricted to specific ones. Activate the :ref:`developer mode `, then go to :menuselection:`Technical Settings --> IAP Account`." msgstr "" #: ../../content/applications/general/in_app_purchase.rst:36 +msgid "An IAP account can be disabled by appending `+disabled` to its token. Reverting this change will re-enable the account." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:40 msgid "IAP Portal" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:38 +#: ../../content/applications/general/in_app_purchase.rst:42 msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:46 +#: ../../content/applications/general/in_app_purchase.rst:50 msgid "Get notified when credits are low" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:48 +#: ../../content/applications/general/in_app_purchase.rst:52 msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:58 +#: ../../content/applications/general/in_app_purchase.rst:62 msgid "IAP services available" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:60 +#: ../../content/applications/general/in_app_purchase.rst:64 msgid "Different services are available depending on the hosting type of your Database:" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:62 +#: ../../content/applications/general/in_app_purchase.rst:66 msgid "*Odoo Online*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:64 +#: ../../content/applications/general/in_app_purchase.rst:68 msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:68 +#: ../../content/applications/general/in_app_purchase.rst:72 msgid "Offering my own services" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:70 +#: ../../content/applications/general/in_app_purchase.rst:74 msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`/developer/howtos/provide_iap_services`." msgstr "" diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index 8c88ce519..696cade90 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-08-18 05:58+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -114,7 +114,7 @@ msgid "Add a new employee" msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:5 -msgid "When a new employee is hired, the first step is to create a new employee form. Starting in the :menuselection:`Employees` app default view, click the :guilabel:`Create` button to access a new employee form. Fill out the required information (underlined in bold) and any additional details, then click :guilabel:`Save`." +msgid "When a new employee is hired, the first step is to create a new employee form. Starting in the :menuselection:`Employees` app dashboard, click the :guilabel:`Create` button to create a new employee form. Fill out the required information (underlined in bold) and any additional details, then click :guilabel:`Save`." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 @@ -130,6 +130,7 @@ msgid "General information" msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:22 +#: ../../content/applications/hr/payroll/contracts.rst:39 msgid "Required fields" msgstr "" @@ -141,261 +142,333 @@ msgstr "" msgid ":guilabel:`Company`: Select the company from the drop-down menu that the new employee is hired by, or create a new company by typing the name in the field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:27 -msgid ":guilabel:`Working Hours`: In the :guilabel:`Work Information` tab, select the desired :guilabel:`Working Hours` from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Working Hours are located in the Work Information tab." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:35 -msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee cannot have working hours that are outside of a company's working times." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:38 -msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:41 -msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:46 -msgid "After the new working time is created, set the working hours for the employee." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:49 +#: ../../content/applications/hr/employees/new_employee.rst:33 +#: ../../content/applications/hr/payroll/contracts.rst:66 msgid "Optional fields" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:51 +#: ../../content/applications/hr/employees/new_employee.rst:35 msgid ":guilabel:`Photo`: In the top right image box of the employee card, click on the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:53 +#: ../../content/applications/hr/employees/new_employee.rst:37 msgid ":guilabel:`Job Position`: Enter the employee's job position title." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:54 +#: ../../content/applications/hr/employees/new_employee.rst:38 msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable to the employee. Any tag can be created in this field by typing it in. Once created, the new tag is available for all employee cards. There is no limit to the amount of tags that can be added." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:57 +#: ../../content/applications/hr/employees/new_employee.rst:41 msgid "Work Contact Information: Enter the employees :guilabel:`Work Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or :guilabel:`Company` name." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:59 +#: ../../content/applications/hr/employees/new_employee.rst:43 msgid ":guilabel:`Department`: Select the employee's department from the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:60 +#: ../../content/applications/hr/employees/new_employee.rst:44 msgid ":guilabel:`Manager`: Select the employee's manager from the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:61 +#: ../../content/applications/hr/employees/new_employee.rst:45 msgid ":guilabel:`Coach`: Select the employee's coach from the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:64 +#: ../../content/applications/hr/employees/new_employee.rst:48 msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:68 +#: ../../content/applications/hr/employees/new_employee.rst:52 msgid "To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, :guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`External Link` button next to the respective selection. The :guilabel:`External Link` button opens the selected form, allowing for modifications. Click :guilabel:`Save` after any edits are made." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:74 +#: ../../content/applications/hr/employees/new_employee.rst:58 msgid "Additional information tabs" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:77 +#: ../../content/applications/hr/employees/new_employee.rst:61 msgid "Resumé tab" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:80 +#: ../../content/applications/hr/employees/new_employee.rst:64 msgid "Resumé" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:82 -msgid "Next, the employee's work history is entered in the :guilabel:`Resumé` tab. Each previous experience must be entered individually. Click :guilabel:`Create a New Entry`, and the :guilabel:`Create Resumé lines` form appears. Enter the following information, then click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another line." +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "Next, enter the employee's work history in the :guilabel:`Resumé` tab. Each resumé line must be entered individually. Click :guilabel:`Create a New Entry`, and the :guilabel:`Create Resumé lines` form appears. Enter the following information for each entry." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 msgid "Add information for the previous work experience in this form." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:92 -msgid ":guilabel:`Name`: Type in the name of the previous work experience." +#: ../../content/applications/hr/employees/new_employee.rst:74 +msgid ":guilabel:`Title`: Type in the title of the previous work experience." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:93 +#: ../../content/applications/hr/employees/new_employee.rst:75 msgid ":guilabel:`Type`: From the drop-down menu, select either :guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Internal Certification`, :guilabel:`Internal Training`, or type in a new entry." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:96 +#: ../../content/applications/hr/employees/new_employee.rst:78 msgid ":guilabel:`Display Type`: Select either :guilabel:`Classic`, :guilabel:`Certification`, or :guilabel:`Course` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/employees/new_employee.rst:80 msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:101 +#: ../../content/applications/hr/employees/new_employee.rst:83 msgid ":guilabel:`Description`: Enter any relevant details in the field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:104 +#: ../../content/applications/hr/employees/new_employee.rst:85 +msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another resumé line." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:90 +msgid "After the new employee form is saved, the current position and company is automatically added to the :guilabel:`Resumé` tab as :guilabel:`Experience`, with the end date listed as :guilabel:`Current`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 msgid "Skills" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:106 -msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner a resumé line is created. Click the :guilabel:`Create a New Entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. Fill in the information, then click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and immediately create a new entry." +#: ../../content/applications/hr/employees/new_employee.rst:97 +msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner a resumé line is created. Click the :guilabel:`Create a New Entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. Fill in the information on the form." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 msgid "Create a new skill for the employee." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:116 -msgid ":guilabel:`Skill Type`: Select from the drop-down menu either :guilabel:`Languages`, :guilabel:`Dev`, :guilabel:`Music`, :guilabel:`Marketing`, or type in a new skill type. After entering the new skill type, an option to :guilabel:`Create` the skill or :guilabel:`Create and Edit` the skill appears. Click :guilabel:`Create and Edit`, and a pop-up for the specific skill type appears. This can also be accessed with the :guilabel:`External Link` button next to the new skill. This form allows for the creation of specific skills and levels. Click :guilabel:`Add a line` and enter the information for the new skill, then repeat for all other added skills. Repeat this process for the :guilabel:`Levels` section. Click :guilabel:`Add a line` to add each level and progress." +#: ../../content/applications/hr/employees/new_employee.rst:105 +msgid ":guilabel:`Skill Type`: Select a :ref:`skill type ` by clicking the radio button next to the skill type." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:0 -msgid "Add a new skill and levels." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:131 -msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. In the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. And, in the :guilabel:`Levels` field enter `beginner`, `intermediate`, and `expert`. Then, either click :guilabel:`Save & Close` or :guilabel:`Save & New`." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:136 +#: ../../content/applications/hr/employees/new_employee.rst:107 msgid ":guilabel:`Skill`: The corresponding skills associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. For example, selecting :guilabel:`Language` as the :guilabel:`Skill Type` presents a variety of languages to select from under the :guilabel:`Skills` field. Select the appropriate pre-configured skill, or type in a new one." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:140 -msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. Select a level or create a new skill level by typing it in." +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. Select a skill level, then the progress bar automatically displays the pre-defined progress for that skill level. Skill levels and progress can be modified in the :guilabel:`Skill Level` pop-up form, which is accessed via the :guilabel:`External Link` button next to :guilabel:`Skill Level` field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:142 -msgid ":guilabel:`Progress`: Progress is automatically selected based on the selected :guilabel:`Skill Level`. Skill levels and progress can be modified in the :guilabel:`Skill Type` pop-up form, which is accessed via the :guilabel:`External Link` button next to :guilabel:`Skill Type` field." +#: ../../content/applications/hr/employees/new_employee.rst:117 +msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` icon to delete the entry. Add a new line by clicking the :guilabel:`Add` button next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:128 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:130 +msgid "In order to add a skill to an employee's form, the :guilabel:`Skill Types` must be configured. Go to :menuselection:`Employees app --> Configuration --> Skill Types` to view the currently configured skill types and create new skill types. Click :guilabel:`Create` and a new :guilabel:`Skill Type` form appears. Fill out all the details and then click :guilabel:`Save`. Repeat this for all the skill types needed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:136 +msgid ":guilabel:`Skill Type`: Enter the name of the skill type. This should be somewhat generic, since the specific skills listed will be housed under this category." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:138 +msgid ":guilabel:`Skills`: Click :guilabel:`Add a line` and enter the information for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid ":guilabel:`Levels`: Click :guilabel:`Add a line` and a :guilabel:`Create Levels` form appears. Enter the name of the level, and assign a percentage (0-100) for that level. Click :guilabel:`Save & New` to save the entry and add another level, or click :guilabel:`Save & Close` to save the level and close the form." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:146 -msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` delete icon to delete the entry. Add a new line by clicking the :guilabel:`ADD` button next to the corresponding section." +msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. Next, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. Last, in the :guilabel:`Levels` field enter `Beginner`, `Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, `50`, and `100`, respectively. Then, either click :guilabel:`Save & Close` or :guilabel:`Save & New`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:151 -msgid "Work information tab" -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:153 -msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` from the drop-down menu. The :guilabel:`External Link` button opens up the selected company form in a window, and allows for editing. The :guilabel:`Work Location` is where any specific location details should be noted, such as a floor, or building." +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Add new math skills and levels with the skill types form." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:157 -msgid ":guilabel:`Approvers`: Using the drop-down menus, select the employees responsible for approving :guilabel:`Time Off`, :guilabel:`Expenses`, and :guilabel:`Timesheets` for the employee. The :guilabel:`External Link` button opens a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, and :guilabel:`Mobile` fields. These can be modified, if needed. Click :guilabel:`Save` after making any edits." +msgid "Work information tab" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:162 -msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` (required) and :guilabel:`Timezone` for the employee. The :guilabel:`External Link` button opens up a detailed view of the specific daily working hours. Working hours can be created, modified, or deleted here. Global time off (such as holidays) can be entered in the :guilabel:`Global Time Off` tab. Click :guilabel:`Add a line` to add a new global time off." +#: ../../content/applications/hr/employees/new_employee.rst:159 +msgid "The :guilabel:`Work Information` tab is where the employee's specific job related information is housed. Their working schedule, various roles, who approves their specific requests (time off, timesheets, and expenses), and specific work location details are listed here. Enter the following information for the new employee." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:167 -msgid ":guilabel:`Planning`: Click on a planning role from the drop-down menu for both the :guilabel:`Default Planning Role` and the :guilabel:`Planning Roles` fields to add a role. There is no limit to the amount of :guilabel:`Planning Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Planning Role`. The default is the *typical* role that the employee performs, where the :guilabel:`Planning Roles` are *all* the specific roles the employee is able to perform." +#: ../../content/applications/hr/employees/new_employee.rst:164 +msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` and :guilabel:`Work Location` from the corresponding drop-down menus. The work address :guilabel:`External Link` button opens up the selected company form in a window, and allows for editing. The :guilabel:`Work Location` is the specific location details, such as a floor or building. If a new work location is needed, add the location by typing it in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid ":guilabel:`Approvers`: Using the drop-down menus, select the users responsible for approving :guilabel:`Time Off`, :guilabel:`Expenses`, and :guilabel:`Timesheets` for the employee. The :guilabel:`External Link` button opens a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, and :guilabel:`Mobile` fields. These can be modified, if needed. Click :guilabel:`Save` after making any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:174 +msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` and :guilabel:`Timezone` (both required) for the employee. The :guilabel:`External Link` button opens up a detailed view of the specific daily working hours. Working hours can be modified or deleted here. Click :guilabel:`Save` to save any changes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:178 +msgid ":guilabel:`Planning`: The :guilabel:`Planning` section affects the *Planning* app, and will only appear if the *Planning* app is installed. Click on a planning role from the drop-down menu for both the :guilabel:`Default Planning Role` and the :guilabel:`Planning Roles` fields to add a role. There is no limit to the amount of :guilabel:`Planning Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Planning Role`. The default is the *typical* role that the employee performs, where the :guilabel:`Planning Roles` are *all* the specific roles the employee is able to perform." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:0 msgid "Add the work information to the Work Information tab." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:179 -msgid "Private information tab" -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:181 -msgid "No information in the :guilabel:`Private Information` tab is required, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:186 -msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Marital Status`, :guilabel:`Emergency Contact`, :guilabel:`Education`, :guilabel:`Citizenship`, :guilabel:`Dependant`, and :guilabel:`Work Permit` information is entered. Fields are entered either using a drop-down menu, clicking a check box, or typing in the information." -msgstr "" - #: ../../content/applications/hr/employees/new_employee.rst:191 -msgid ":guilabel:`Private Contact`: Enter the :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`External Link` button to open the address form. On the address form, enter the necessary details, then click :guilabel:`Save`. Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu." +msgid "The users that appear in the drop-down menu for the :guilabel:`Approvers` section must have *Administrator* rights set for the corresponding human resources role. To check who has these rights, go to :menuselection:`Settings app --> Users --> Manage Users`. Click on an employee, and check the :guilabel:`Human Resources` section of the :guilabel:`Access Rights` tab." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:197 -msgid ":guilabel:`Marital Status`: Select either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced` from the drop-down menu." +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "In order for the user to appear as an approver for :guilabel:`Expenses`, they must have either :guilabel:`Team Approver`, :guilabel:`All Approver`, or :guilabel:`Administrator` set for the :guilabel:`Expenses` role." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:200 -msgid ":guilabel:`Emergency Contact`: Type in the name and phone number of the employee's emergency contact." +#: ../../content/applications/hr/employees/new_employee.rst:199 +msgid "In order for the user to appear as an approver for :guilabel:`Time Off`, they must have either :guilabel:`Officer` or :guilabel:`Administrator` set for the :guilabel:`Time Off` role." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:202 -msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields." +#: ../../content/applications/hr/employees/new_employee.rst:201 +msgid "In order for the user to appear as an approver for :guilabel:`Timesheets`, they must have either :guilabel:`Manager`, :guilabel:`Officer`, or :guilabel:`Administrator` set for the :guilabel:`Payroll` role." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:206 -msgid ":guilabel:`Citizenship`: This section houses all the information relevant to the citizenship of the employee. Some selections use a drop-down menu, as does the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` sections. The :guilabel:`Date of Birth` uses a calendar module to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date. Type in the information for the :guilabel:`Identification No`, :guilabel:`Passport No`, and :guilabel:`Place of Birth` fields. If the employee is :guilabel:`Disabled` or a :guilabel:`Nonresident`, click the check box next to the respective fields." +msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee cannot have working hours that are outside of a company's working times." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:216 -msgid ":guilabel:`Dependant`: If the employee has any dependants, that information is entered here. Type in the number of children the employee has, and check the boxes next to :guilabel:`Disabled Children` and/or :guilabel:`Other Dependent People` if applicable." +#: ../../content/applications/hr/employees/new_employee.rst:209 +msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:219 -msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` and/or :guilabel:`Work Permit No` in the corresponding fields. Using the calendar module, select the :guilabel:`Visa Expire Date` to enter the expiration date." +#: ../../content/applications/hr/employees/new_employee.rst:212 +msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:217 +msgid "After the new working time is created, set the working hours for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:220 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:222 +msgid "No information in the :guilabel:`Private Information` tab is required, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:227 +msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Marital Status`, :guilabel:`Emergency Contact`, :guilabel:`Education`, :guilabel:`Citizenship`, :guilabel:`Dependant`, and :guilabel:`Work Permit` information is entered. Fields are entered either using a drop-down menu, clicking a check box, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:232 +msgid ":guilabel:`Private Contact`: Enter the personal :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`External Link` button to open the address form. On the address form, enter the necessary details, then click :guilabel:`Save`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:241 +msgid "Next, enter the employee's :guilabel:`Email` address and :guilabel:`Phone` number in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:244 +msgid "Select the employee's preferred :guilabel:`Language` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:246 +msgid "Enter the employee's :guilabel:`Bank Account Number` using the drop-down menu. If the bank is not already configured (the typical situation when creating a new employee) enter the bank account number, and click :guilabel:`Create and Edit`. A :guilabel:`Create: Bank Account Number` for appears. Fill in the information, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "Finally, enter the :guilabel:`Home-Work Distance` in the field. This field is only necessary if the employee is receiving any type of commuter benefits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:254 +msgid ":guilabel:`Marital Status`: Select either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid ":guilabel:`Emergency`: Type in the name and phone number of the employee's emergency contact." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:258 +msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid ":guilabel:`Citizenship`: This section houses all the information relevant to the citizenship of the employee. Some selections use a drop-down menu, as does the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` sections. The :guilabel:`Date of Birth` uses a calendar module to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date. Type in the information for the :guilabel:`Identification No`, :guilabel:`Passport No`, and :guilabel:`Place of Birth` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +msgid ":guilabel:`Dependant`: If the employee has any children, enter the :guilabel:`Number of Children` in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:272 +msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` and/or :guilabel:`Work Permit No` in the corresponding fields. Using the calendar module, select the :guilabel:`Visa Expire Date` and/or the :guilabel:`Work Permit Expiration Date` to enter the expiration date(s). If available, upload a digital copy of the work permit document. Click :guilabel:`Upload Your File`, navigate to the work permit file in the file explorer, and click :guilabel:`Open`." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 msgid "Add the private information to the Private Information tab." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:228 +#: ../../content/applications/hr/employees/new_employee.rst:284 msgid "HR settings tab" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:230 +#: ../../content/applications/hr/employees/new_employee.rst:286 msgid "This tab provides various fields for different information, depending on the country the company is located. Different fields are configured for different locations, however some sections appear regardless." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:234 -msgid ":guilabel:`Status`: If applicable, select a :guilabel:`Related User`, :guilabel:`Job Position`, and :guilabel:`Language` with the drop-down menus. Type in the :guilabel:`Registration Number of the Employee`, and the :guilabel:`NIF Country Code` if available." +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid ":guilabel:`Status`: Select an :guilabel:`Employee Type` and, if applicable, a :ref:`Related User `, with the drop-down menus." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:237 -msgid ":guilabel:`Fleet`: If the employee has access to a company car, enter the :guilabel:`Mobility Card` information here." +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid ":guilabel:`Payroll`: Select the :guilabel:`Current Contract` and :guilabel:`Job Position` from the drop-down menus. If applicable, enter the :guilabel:`Registration Number` in this section." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:239 -msgid ":guilabel:`Timesheets`: Enter the employee's cost per hour in a $XX.XX format. This is factored in when the employee is working at a work center. This value affects the employee's pay, and may also affect manufacturing costs for a product, if the value of the manufactured product is not a fixed amount." +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid ":guilabel:`Previous Employer`: This section appears only for Belgian companies, and will not be visible for other locations. These are days that will be paid to the new employee. Enter any :guilabel:`Simple Holiday Pay to Recover`, :guilabel:`Number of Days to recover`, and :guilabel:`Recovered Simple Holiday Pay` from a previous employer, for both N and N-1 categories." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:243 -msgid ":guilabel:`Attendance`: This section may only appear for Belgian companies. Enter the :guilabel:`INSZ or BIS` number if applicable. :guilabel:`Badge ID` and a :guilabel:`PIN Code` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID." +#: ../../content/applications/hr/employees/new_employee.rst:298 +msgid ":guilabel:`Previous Occupations`: This section appears ony for Belgian companies, and will not be visible for other locations. Click :guilabel:`Add a line` to enter information for each previous occupation. Enter the number of :guilabel:`Months`, the :guilabel:`Amount`, and the :guilabel:`Occupational Rate` in the corresponding fields. Click the :guilabel:`🗑️ (trash can)` icon to delete a line." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:303 +msgid ":guilabel:`Attendance/Point of Sale`: The employee's :guilabel:`Badge ID` and :guilabel:`PIN Code` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:306 +msgid ":guilabel:`Application Settings`: If applicable, enter the :guilabel:`Fleet Mobility Card` number. Enter the employee's cost per hour in a $XX.XX format. This is factored in when the employee is working at a :doc:`work center <../../inventory_and_mrp/manufacturing/management/using_work_centers>`. This value affects the manufacturing costs for a product, if the value of the manufactured product is not a fixed amount." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 msgid "Enter any information prompted in the HR Settings tab for the employee." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:253 -msgid "Personal documents tab" +#: ../../content/applications/hr/employees/new_employee.rst:319 +msgid "Employees do not also need to be users. An employee does **not** count towards billing, while *Users* **do** count towards billing. If the new employee should also be a user, the user must be created." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:255 -msgid "The :guilabel:`Personal Documents` tab is only displayed for certain countries. If this tab is not visible, it is not applicable to the company's location." +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "In the :guilabel:`Related User` field, type in the name of the user to add, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: Related User` form appears. Type in the :guilabel:`Name`, :guilabel:`Email Address`, and then select the :guilabel:`Company` from the drop-down menu. Click :guilabel:`Save` after the information is entered. Once the record is saved, the new user appears in the :guilabel:`Related User` field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:258 -msgid "Add a file for the employee's :guilabel:`ID Card Copy`, :guilabel:`Driving License`, :guilabel:`Mobile Subscription Invoice`, :guilabel:`SIM Card Copy`, and :guilabel:`Internet Subscription Invoice` by clicking the :guilabel:`Upload Your File` button next to the corresponding field. File types that can be accepted are :file:`.jpg`, :file:`.png`, and :file:`.pdf`." +#: ../../content/applications/hr/employees/new_employee.rst:330 +msgid "Documents" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:332 +msgid "All documents associated with an employee are stored in the *Documents* app. The number of documents associated with the employee appear in the :guilabel:`Documents` smart button on the employee form. Click on the smart button, and all the documents appear. For more information on the *Documents* app, refer to the :doc:`Documents documentation `." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Upload personal documents for the employee in the Personal Documents tab, either a jpg,\n" -"png, or pdf." +msgid "All uploaded documents associated with the employee appear in the documents smart-button." msgstr "" #: ../../content/applications/hr/payroll.rst:3 @@ -430,27 +503,32 @@ msgstr "" msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required." msgstr "" -#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll.rst:37 +#: ../../content/applications/hr/payroll/work_entries.rst:3 msgid "Work entries" msgstr "" -#: ../../content/applications/hr/payroll.rst:37 +#: ../../content/applications/hr/payroll.rst:39 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:42 +#: ../../content/applications/hr/payroll.rst:44 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:47 msgid "Work entry types" msgstr "" -#: ../../content/applications/hr/payroll.rst:44 +#: ../../content/applications/hr/payroll.rst:49 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:49 +#: ../../content/applications/hr/payroll.rst:54 msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entry Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:52 +#: ../../content/applications/hr/payroll.rst:57 msgid "Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees are correctly entered." msgstr "" @@ -458,27 +536,27 @@ msgstr "" msgid "List of all work entry types currently available." msgstr "" -#: ../../content/applications/hr/payroll.rst:60 +#: ../../content/applications/hr/payroll.rst:65 msgid "New work entry type" msgstr "" -#: ../../content/applications/hr/payroll.rst:62 +#: ../../content/applications/hr/payroll.rst:67 msgid "To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the form:" msgstr "" -#: ../../content/applications/hr/payroll.rst:65 +#: ../../content/applications/hr/payroll.rst:70 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:67 +#: ../../content/applications/hr/payroll.rst:72 msgid ":guilabel:`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:70 +#: ../../content/applications/hr/payroll.rst:75 msgid ":guilabel:`Sequence`: The sequence determines the order that the work entry is computed in the payslip list." msgstr "" -#: ../../content/applications/hr/payroll.rst:72 +#: ../../content/applications/hr/payroll.rst:77 msgid "Check boxes: If any of the items in the list applies to the work entry, check off the box by clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, or a new type of time off can be entered." msgstr "" @@ -486,35 +564,35 @@ msgstr "" msgid "New work entry type form." msgstr "" -#: ../../content/applications/hr/payroll.rst:81 +#: ../../content/applications/hr/payroll.rst:86 msgid ":guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the payslip." msgstr "" -#: ../../content/applications/hr/payroll.rst:84 +#: ../../content/applications/hr/payroll.rst:89 msgid ":guilabel:`No Rounding`: A timesheet entry is not modified." msgstr "" -#: ../../content/applications/hr/payroll.rst:85 +#: ../../content/applications/hr/payroll.rst:90 msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:86 +#: ../../content/applications/hr/payroll.rst:91 msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:89 +#: ../../content/applications/hr/payroll.rst:94 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:95 +#: ../../content/applications/hr/payroll.rst:100 msgid "Working times" msgstr "" -#: ../../content/applications/hr/payroll.rst:97 +#: ../../content/applications/hr/payroll.rst:102 msgid "To view the currently configured working times, go to :menuselection:`Payroll --> Configuration --> Working Times`. The working times that are available for an employee's contracts and work entries are found in this list." msgstr "" -#: ../../content/applications/hr/payroll.rst:101 +#: ../../content/applications/hr/payroll.rst:106 msgid "Working times are company-specific. Each company must identify each type of working time they use. For example, an Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working time entry for each company that uses the 40-hour standard work week." msgstr "" @@ -522,11 +600,11 @@ msgstr "" msgid "All working times currently set up in the database." msgstr "" -#: ../../content/applications/hr/payroll.rst:111 +#: ../../content/applications/hr/payroll.rst:116 msgid "New working time" msgstr "" -#: ../../content/applications/hr/payroll.rst:113 +#: ../../content/applications/hr/payroll.rst:118 msgid "To create a new working time, click the :guilabel:`Create` button. Enter the information on the form." msgstr "" @@ -534,43 +612,43 @@ msgstr "" msgid "New working type form." msgstr "" -#: ../../content/applications/hr/payroll.rst:120 +#: ../../content/applications/hr/payroll.rst:125 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:124 +#: ../../content/applications/hr/payroll.rst:129 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:130 +#: ../../content/applications/hr/payroll.rst:135 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:133 +#: ../../content/applications/hr/payroll.rst:138 msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." msgstr "" -#: ../../content/applications/hr/payroll.rst:137 +#: ../../content/applications/hr/payroll.rst:142 msgid "Salary" msgstr "" -#: ../../content/applications/hr/payroll.rst:142 +#: ../../content/applications/hr/payroll.rst:147 msgid "Structure types" msgstr "" -#: ../../content/applications/hr/payroll.rst:144 +#: ../../content/applications/hr/payroll.rst:149 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:150 +#: ../../content/applications/hr/payroll.rst:155 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:156 +#: ../../content/applications/hr/payroll.rst:161 msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Structure Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:159 +#: ../../content/applications/hr/payroll.rst:164 msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*." msgstr "" @@ -578,7 +656,7 @@ msgstr "" msgid "List of all structure types." msgstr "" -#: ../../content/applications/hr/payroll.rst:167 +#: ../../content/applications/hr/payroll.rst:172 msgid "Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." msgstr "" @@ -586,19 +664,19 @@ msgstr "" msgid "New structure type box." msgstr "" -#: ../../content/applications/hr/payroll.rst:176 +#: ../../content/applications/hr/payroll.rst:181 msgid "Structures" msgstr "" -#: ../../content/applications/hr/payroll.rst:178 +#: ../../content/applications/hr/payroll.rst:183 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:181 +#: ../../content/applications/hr/payroll.rst:186 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:185 +#: ../../content/applications/hr/payroll.rst:190 msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Structures`." msgstr "" @@ -606,11 +684,11 @@ msgstr "" msgid "All available salary structures." msgstr "" -#: ../../content/applications/hr/payroll.rst:192 +#: ../../content/applications/hr/payroll.rst:197 msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." msgstr "" -#: ../../content/applications/hr/payroll.rst:195 +#: ../../content/applications/hr/payroll.rst:200 msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee." msgstr "" @@ -618,15 +696,15 @@ msgstr "" msgid "Salary structure details for Regular Pay." msgstr "" -#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll.rst:208 msgid "Rules" msgstr "" -#: ../../content/applications/hr/payroll.rst:205 +#: ../../content/applications/hr/payroll.rst:210 msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect 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:209 +#: ../../content/applications/hr/payroll.rst:214 msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules." msgstr "" @@ -634,7 +712,7 @@ msgstr "" msgid "Rules for each salary structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:216 +#: ../../content/applications/hr/payroll.rst:221 msgid "To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the fields, then click :guilabel:`Save`." msgstr "" @@ -642,47 +720,47 @@ msgstr "" msgid "Enter the information for the new rule." msgstr "" -#: ../../content/applications/hr/payroll.rst:223 +#: ../../content/applications/hr/payroll.rst:228 msgid "The required fields for a rule are:" msgstr "" -#: ../../content/applications/hr/payroll.rst:225 +#: ../../content/applications/hr/payroll.rst:230 msgid ":guilabel:`Name`: Enter a name for the rule." msgstr "" -#: ../../content/applications/hr/payroll.rst:226 +#: ../../content/applications/hr/payroll.rst:231 msgid ":guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a new one." msgstr "" -#: ../../content/applications/hr/payroll.rst:228 +#: ../../content/applications/hr/payroll.rst:233 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 as this will affect them." msgstr "" -#: ../../content/applications/hr/payroll.rst:230 +#: ../../content/applications/hr/payroll.rst:235 msgid ":guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down menu, or enter a new one." msgstr "" -#: ../../content/applications/hr/payroll.rst:232 +#: ../../content/applications/hr/payroll.rst:237 msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, 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)." msgstr "" -#: ../../content/applications/hr/payroll.rst:236 +#: ../../content/applications/hr/payroll.rst:241 msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, 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." msgstr "" -#: ../../content/applications/hr/payroll.rst:242 +#: ../../content/applications/hr/payroll.rst:247 msgid "Rule parameters" msgstr "" -#: ../../content/applications/hr/payroll.rst:245 +#: ../../content/applications/hr/payroll.rst:250 msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration` 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:250 +#: ../../content/applications/hr/payroll.rst:255 msgid "Other input types" msgstr "" -#: ../../content/applications/hr/payroll.rst:252 +#: ../../content/applications/hr/payroll.rst:257 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 going to :menuselection:`Payroll --> Configuration --> Other Input Types`." msgstr "" @@ -690,7 +768,7 @@ msgstr "" msgid "Other input types for payroll." msgstr "" -#: ../../content/applications/hr/payroll.rst:260 +#: ../../content/applications/hr/payroll.rst:265 msgid "To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." msgstr "" @@ -698,27 +776,27 @@ msgstr "" msgid "Create a new Input Type." msgstr "" -#: ../../content/applications/hr/payroll.rst:270 +#: ../../content/applications/hr/payroll.rst:275 msgid "Salary package configurator" msgstr "" -#: ../../content/applications/hr/payroll.rst:272 +#: ../../content/applications/hr/payroll.rst:277 msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :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:277 +#: ../../content/applications/hr/payroll.rst:282 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:283 +#: ../../content/applications/hr/payroll.rst:288 msgid "Advantages" msgstr "" -#: ../../content/applications/hr/payroll.rst:285 +#: ../../content/applications/hr/payroll.rst:290 msgid "When offering potential employees a position, there can be certain *advantages* set in Odoo in addition to the salary to make the offer more appealing (such as extra time off, access to a company car, reimbursement for a phone or internet, etc.)." msgstr "" -#: ../../content/applications/hr/payroll.rst:289 +#: ../../content/applications/hr/payroll.rst:294 msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages are grouped by :guilabel:`Structure type`." msgstr "" @@ -726,7 +804,7 @@ msgstr "" msgid "Settings available for payroll." msgstr "" -#: ../../content/applications/hr/payroll.rst:296 +#: ../../content/applications/hr/payroll.rst:301 msgid "To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields, then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." msgstr "" @@ -734,39 +812,39 @@ msgstr "" msgid "List of advantages employee's can have." msgstr "" -#: ../../content/applications/hr/payroll.rst:304 +#: ../../content/applications/hr/payroll.rst:309 msgid "The required fields for an advantage are:" msgstr "" -#: ../../content/applications/hr/payroll.rst:306 +#: ../../content/applications/hr/payroll.rst:311 msgid ":guilabel:`Name`: Enter the name for the advantage." msgstr "" -#: ../../content/applications/hr/payroll.rst:307 +#: ../../content/applications/hr/payroll.rst:312 msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under." msgstr "" -#: ../../content/applications/hr/payroll.rst:309 +#: ../../content/applications/hr/payroll.rst:314 msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`." msgstr "" -#: ../../content/applications/hr/payroll.rst:312 +#: ../../content/applications/hr/payroll.rst:317 msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to." msgstr "" -#: ../../content/applications/hr/payroll.rst:316 +#: ../../content/applications/hr/payroll.rst:321 msgid "Personal info" msgstr "" -#: ../../content/applications/hr/payroll.rst:318 +#: ../../content/applications/hr/payroll.rst:323 msgid "Every employee in Odoo has an *employee card* that includes all of their personal information, resume, work information, and documents. To view an employee's card, go to the main :menuselection:`Payroll` app dashboard, and click on the employee's card, or go to :menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee cards can also be viewed by going to the :menuselection:`Employees` app." msgstr "" -#: ../../content/applications/hr/payroll.rst:325 +#: ../../content/applications/hr/payroll.rst:330 msgid "An employee card can be thought of as an employee personnel file." msgstr "" -#: ../../content/applications/hr/payroll.rst:327 +#: ../../content/applications/hr/payroll.rst:332 msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Personal Info`." msgstr "" @@ -774,7 +852,7 @@ msgstr "" msgid "Personal information that appear on employee cards to enter." msgstr "" -#: ../../content/applications/hr/payroll.rst:335 +#: ../../content/applications/hr/payroll.rst:340 msgid "To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel the edits." msgstr "" @@ -782,22 +860,787 @@ msgstr "" msgid "New personal information entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:343 +#: ../../content/applications/hr/payroll.rst:348 msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card." msgstr "" -#: ../../content/applications/hr/payroll.rst:347 +#: ../../content/applications/hr/payroll.rst:352 msgid "The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." msgstr "" -#: ../../content/applications/hr/payroll.rst:351 +#: ../../content/applications/hr/payroll.rst:356 msgid "Once the information is entered, click the :guilabel:`Save` button to save the entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:354 +#: ../../content/applications/hr/payroll.rst:359 msgid "Resume" msgstr "" -#: ../../content/applications/hr/payroll.rst:357 +#: ../../content/applications/hr/payroll.rst:362 msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration` 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/contracts.rst:3 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "Every employee in Odoo is required to have a contract in order to be paid. A contract outlines the terms of an employee's position, their compensation, their working hours, and any other details about their position." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:10 +msgid "Contract documents (PDFs) are uploaded and organized using the *Documents* application, and are signed using the *Sign* application. Ensure these applications are installed in order to send and sign contracts. Please refer to the :doc:`/applications/finance/documents` and :doc:`/applications/finance/sign` documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "To view the employee contracts, go to the :menuselection:`Payroll app --> Employees --> Contracts` from the top menu. All employee contracts, and their current contract status, are displayed in a default kanban view. The default view displays both running contracts and contracts that need action. Expired and canceled contracts are hidden in the default view." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Contracts dashboard view showing running contracts and contracts with issues." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:25 +msgid "The list of contracts in the *Payroll* application matches the list of contracts in the *Employees* application. The default contracts view in the *Payroll* application displays running contracts and contracts needing attention, while the default contracts view in the *Employees* application displays all contracts in a kanban view, organized by their stage, regardless of status. All contracts can be viewed by changing the filters." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:32 +msgid "Create a new contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:34 +msgid "In order for an employee to be paid, an active contract is required. If a new contract is needed, click the :guilabel:`Create` button on the contracts dashboard. A contract form appears where the information can be entered. Required fields are underlined in bold." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "New contract form to be filled in when creating a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid ":guilabel:`Contact Reference`: Type in the name or title for the contract, such as `John Smith Contract`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:47 +msgid ":guilabel:`Company`: Select the company the contract applies to by clicking on the drop-down menu. A new company can be created by typing the name in the field, then clicking either :guilabel:`Create` to create the new company, or :guilabel:`Create and Edit` to create the new company and edit the company details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid ":guilabel:`Salary Structure Type`: Select one of the salary structure types from the drop-down menu. The default salary structure types are :guilabel:`Employee` or :guilabel:`Worker`. A new salary structure type can be created by typing the name in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:54 +msgid ":guilabel:`Start Date`: The date the contract starts. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :guilabel:`< > (arrow)` icons, then clicking on the :guilabel:`date`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:57 +msgid ":guilabel:`Working Schedule`: Select one of the working schedules from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "The :guilabel:`Working Schedule` drop-down menu displays all the working times for the selected :guilabel:`Company`. To modify or add to this list, go to :menuselection:`Payroll --> Configuration --> Working Times` and either :guilabel:`Create` a new working time or click on an existing working time and edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:68 +msgid ":guilabel:`Employee`: Name of the employee that the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:69 +msgid ":guilabel:`Department`: The department the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +msgid ":guilabel:`Job Position`: The specific job position the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:71 +msgid ":guilabel:`Contract Type`: Choose from :guilabel:`CDI`, :guilabel:`CDD`, or :guilabel:`PFI` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid ":guilabel:`CDI` is an open-ended contract with only a start date but no end date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:75 +msgid ":guilabel:`CDD` is a contract with both a start date and an end date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:76 +msgid ":guilabel:`PFI` is a Belgian-specific contract used when hiring employees that need training, and covers the training period specifically." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:79 +msgid ":guilabel:`End Date`: If the contract has a specific end date, click the drop-down menu, navigate to the correct month and year using the arrow icons, then click on the date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:81 +msgid ":guilabel:`HR Responsible`: If there is a specific person in HR that is responsible for the contract, select the person from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid ":guilabel:`Analytic Account`: This field allows a link between the contract and a specific analytic account for accounting purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:87 +msgid "Contract details" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:89 +msgid "The contract details section allows for the addition and editing of a contract, and the ability to send the contract to the employee for approval and signatures." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Contract details in optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:96 +msgid ":guilabel:`Contract Template`: Select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:98 +msgid ":guilabel:`New Contract Document Template`: Select a contract from the drop-down menu to be modified for this new employee contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:100 +msgid ":guilabel:`Contract Update Document Template`: Select a contract from the drop-down menu if the employee has an existing contract that requires updating." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid ":guilabel:`Notes`: The notes field is a text field where any notes for the employee contract can be entered for future reference." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:106 +msgid "Modifying a contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:108 +msgid "Click the :guilabel:`External Link` button at the end of each line to open the corresponding contract template and make any changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:115 +msgid "A pop-up window appears with all the contract details. Modify the fields for the contract as needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Edit the details for the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:121 +msgid ":guilabel:`Tags`: Select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:122 +msgid ":guilabel:`Signed Document Workspace`: This is where the signatures are stored. Choose a pre-configured workspace or create a new one." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:124 +msgid ":guilabel:`Signed Document Tags`: Select or create any tags associated only with the signed contract as opposed to the original unsigned contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid ":guilabel:`Redirect Link`: Enter a redirect link for the employee to access the contract. A redirect link takes the user from one URL to another, in this case, to the newly updated contract specifically written for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:129 +msgid ":guilabel:`Who can Sign`: Select either :guilabel:`All Users` or :guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:131 +msgid ":guilabel:`All Users`: Any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:132 +msgid ":guilabel:`On Invitation`: Only users selected in this field can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:134 +msgid ":guilabel:`Invited Users`: Select the person(s) that can sign the document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid ":guilabel:`Document`: The attached document can be replaced by clicking the :guilabel:`✏️ (pencil)` icon. A pop-up window appears so another document can be selected for upload. The file must be a PDF. To remove the document, click the :guilabel:`🗑️ (trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "Once the edits are complete, click the :guilabel:`Save` button. All the information for the selected contract template populates the fields in the :guilabel:`Salary Information` tab. Any additional tabs, such as :guilabel:`Personal Documents`, appears if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "Salary information" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:150 +msgid "This section is where the specific salary details are defined. This section is country-specific, so depending on where the company is located, these fields may vary." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "Enter the amount in the various fields, or check a box to apply a benefit. Some options that can be entered here include :guilabel:`Meal Vouchers`, :guilabel:`Fuel Card`, :guilabel:`Internet`, :guilabel:`Paid Time Off`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Some fields may be automatically filled in based off of the contracts selected in the :guilabel:`Contract Details` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:161 +msgid "Attachment of salary" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:163 +msgid "Any automatic deductions or allocations for an employee, such as child support payments and wage garnishments, are referred to as a *salary attachment*. This section is where all of these deductions or allocations are set." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:167 +msgid "To add a new deduction, click :guilabel:`Add a line`. Type in a description for the allocation under :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Enter a new line for each type of garnishment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:174 +msgid "Select the :guilabel:`Garnished Type` from the drop-down menu. Choose from:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:176 +msgid ":guilabel:`Attachment of Salary`: Any payments taken out towards something that is *not* child support. Typically any garnishments such as lawsuit payments, payments toward taxes owed, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:178 +msgid ":guilabel:`Assignment of Salary`: Any deduction that is not required but voluntary, such as a pre-tax allocation to a college savings account." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:180 +msgid ":guilabel:`Child Support`: Any payments taken out specifically for child support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:182 +msgid "Enter the start and end dates the entry applies to. Click on the drop-down menu under :guilabel:`From` and :guilabel:`To`, navigate to the correct month and year by using the :guilabel:`< > (arrow)` icons, then click on the :guilabel:`date`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:186 +msgid "Last, enter the :guilabel:`Amount` that each payslip pays towards the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:188 +msgid "To delete a line, click the :guilabel:`🗑️ (trash can)` icon at the end of the line." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:191 +msgid "Save and send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "Once a contract has been created and/or modified, save the contract by clicking the :guilabel:`Save` button. Next, the contract must be sent to the employee to be signed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:196 +msgid "Click on one of the following buttons to send the contract to the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Send the contract to the employee via one of the buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid ":guilabel:`Generate Simulation Link`: This option is for Belgian companies only. Clicking this opens a pop-up window that contains the basic information from the contract as well as a link for the contract when using the salary configurator. Click :guilabel:`Send Offer` to send an email to the employee so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Sends a link to the employee for the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:212 +msgid "In order to send a contract using the :guilabel:`Generate Simulation Link`, there must be a signature field in the contract PDF being sent to the employee so they can sign it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:215 +msgid ":guilabel:`Signature Request`: Click this and a pop-up window appears where an email can be typed to the employee. Select the document, such as a contract, NDA, or Homeworking Policy, from the drop-down menu, and fill out the email section. Click :guilabel:`Send` when the email is ready to be sent." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Request a signature for the contract via email." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:224 +msgid ":guilabel:`Credit Time`: This option is for Belgian companies only. When clicked, a pop-up window appears that allows for the changing of working times, and can compute time off." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "The *Work Entries* dashboard, which can be found by going to :menuselection:`Payroll --> Work Entries --> Work Entries`, provides a visual overview of the individual time sheets of every employee, with each day split into a morning shift and an afternoon shift." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Work Entries dashboard view showing all employee's work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:13 +msgid "To change the view so that only the entries for a single day, week, or month are shown, click on one of the corresponding links for :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`, located at the top of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:17 +msgid "Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons on the left and right side of the :guilabel:`Today` button to adjust the displayed dates. The arrows will adjust the date based on the type of time selected. For example, if month is selected, the arrows will move one month with each click of the arrow. If week or day is selected, the time will move by either a week or a day for each click of the arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:24 +msgid "Adding a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:26 +msgid "If a work entry is missing and needs to be added, such as sick time or time off, click :guilabel:`Add` to create a new work entry. A pop-up will appear, with several fields to fill in." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:29 +msgid "Enter the :guilabel:`Work Entry Name`, such as `Sick Time` or any other short description. Select the :guilabel:`Employee` and the :guilabel:`Work Entry Type` from the respective drop-down lists." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Filling in the work entry Create form in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:36 +msgid "Next, enter the date and time for the work entry in the :guilabel:`From` and :guilabel:`To` drop-downs. First, select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:40 +msgid "Then, select the time by clicking on the :guilabel:`⏰ (clock)` icon, and using the :guilabel:`⬆️ (up arrow)` and :guilabel:`⬇️ (down arrow)` icons for each section to enter the hour, minute, and second for the time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:44 +msgid "The :guilabel:`Period` will display the hours based on the :guilabel:`To` and :guilabel:`From` entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Before clicking either :guilabel:`Save & Close` or :guilabel:`Save & New`, it is good to double check the :guilabel:`Period` to ensure the time stated corresponds to the :guilabel:`To` and :guilabel:`From` fields." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:0 +msgid "Hours entered in the Period field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:56 +msgid "Once the information is entered, click :guilabel:`Save & Close` to save the entry and close the pop-up, or :guilabel:`Save & New` to save the entry and create another :guilabel:`Work Entry Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:60 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "After a work entry has been either added or modified, the work entries need to be regenerated for the affected employee(s). Click on the :guilabel:`Regenerate Work Entries` button at the top of the main dashboard, and a pop-up will appear." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:66 +msgid "Select the :guilabel:`Employee` to regenerate work entries for from the :guilabel:`drop-down menu`, and adjust the :guilabel:`From` and :guilabel:`To` fields so the correct date range is displayed. Click the :guilabel:`Regenerate Work Entries` button and the work entries will be recreated. Once finished, the pop-up will close." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Regenerate a work entry for a particular employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:76 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:78 +msgid "A conflict appears for any request that has not been approved, such as sick time or vacation, or if there are any errors on the work entry, such as required fields being left blank. Conflicts are required to be resolved before payslips can be generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:82 +msgid "Any work entry that has a conflict to be resolved is indicated on the main :guilabel:`Work Entry` overview dashboard, located by going to :menuselection:`Payroll --> Work Entries --> Conflicts`, where only conflicts needing resolution are shown." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Conflicts dashboard view showing all employee's conflicts in work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:90 +msgid "Conflicts are indicated with an orange triangle in the top left corner of each individual entry. Click on an individual work entry to see the conflict details in a pop-up." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:93 +msgid "The conflict is briefly explained in an orange text box." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Details for a conflict appear in the pop-up." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "The :guilabel:`Work Entry Name`, :guilabel:`Employee`, and :guilabel:`Work Entry Type` are listed on the left side of the pop-up. The :guilabel:`From` and :guilabel:`To` date range, as well as the total time requested (in hours), appear in the :guilabel:`Period` field on the right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:103 +msgid "If there is a conflict because a time-off request for the same time already exists in the system, the time-off will be entered in the :guilabel:`Time Off` field. Clicking the :guilabel:`External Link` button next to the :guilabel:`Time Off` entry will bring up the duplicate time-off request." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "The details for the time-off request appear in the pop-up. The request can be modified if needed. Click either the :guilabel:`Validate` or :guilabel:`Refuse` button to approve or deny the request, then click the :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Edit and/or validate a duplicate time-off request." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:115 +msgid "Once the duplicate time-off request has been approved and saved, the screen goes back to the conflict. Click :guilabel:`Refuse Time Off` or :guilabel:`Approve Time Off` via the buttons in the top right to either approve or deny the request. Repeat for all conflicts until there are no conflicts to resolve." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:120 +msgid "After conflicts have been resolved, work entries must be regenerated for each employee by clicking the :guilabel:`Regenerate Work Entries` button, and entering the corresponding information for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Regenerate Work Entries button on the Work Entries Regeneration form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:129 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "To generate payslips, navigate to the time period the payslips should be generated for, either day, week, or month. When the desired pay period is displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Generate Payslips button on the Work Entry dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "If the :guilabel:`Generate Payslips` button is not active (appears light turquoise instead of dark turquoise), that indicates there are conflicts. *Solve conflicts first* will appear as a warning when :guilabel:`Generate Payslips` is moused over. Resolve all conflicts before generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "A batch entry will appear for the time period selected. The batch name appears at the top in the :guilabel:`Name` field, typically listing the month and year for the particular batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:148 +msgid "The date range the payslips apply to appears in the :guilabel:`Period` field. The company appears in the :guilabel:`Company` field, along with an option to mark the payslips as a credit note. To make changes, click the :guilabel:`Edit` button in the top left, make any changes, then click either :guilabel:`Save` to accept the changes or :guilabel:`Discard` to revert to the original data." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Batch information that appears when making a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:157 +msgid "Click the :guilabel:`Create Draft Entry` button to create the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:159 +msgid "Click on the :guilabel:`Payslips` button in the top right to view all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:162 +msgid "Payslips will have a status of *Waiting* until the :guilabel:`Create Draft Entry` button has been clicked. After, the payslip status will change to *Done*." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:165 +msgid "Payslips can be printed by clicking the box next to each payslip to print, or clicking the box next to :guilabel:`Reference` to select all the payslips at once. Click the :guilabel:`Print` button, and a PDF file will be created with all the specified payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Print button for printing the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:174 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +#: ../../content/applications/hr/recruitment/new_job.rst:60 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "In the default :menuselection:`Recruitment` dashboard view, all job positions are shown, regardless of status. Current published positions with active applicants are shown, as well as job positions that have been created but have not yet been published." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:9 +msgid "Each job position is shown in an individual kanban card. If the job position is active and candidates can apply, then a :guilabel:`Published` banner will appear in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:13 +msgid "View submitted applications by clicking the :guilabel:`# Applications` button, with `#` being the number of applications received. If a position is not published, a :guilabel:`Start Recruitment` button will appear instead." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Main dashboard view of Recruitment showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:22 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:24 +msgid "There are two ways a job position can be created: from the main :guilabel:`Recruitment` dashboard, or from the :guilabel:`Configuration` menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:27 +msgid "To create a job position from the :guilabel:`Configuration` menu, go to :menuselection:`Recruitment app --> Configuration --> Job Positions`. The job positions in this view are displayed in a list." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:30 +msgid "Create a new job position from the :guilabel:`Job Positions` dashboard by clicking the :guilabel:`Create` button in the top-left corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "Then, a :guilabel:`Create a Job Position` pop-up window will appear. From here, enter the name of the position (such as `Sales Manager`, `Mechanical Engineer`, etc.). When complete, click the :guilabel:`Create` button to save the entry, or the :guilabel:`Discard` button to delete it." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Create a new job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:41 +msgid "Once the job position has been created, it will appear as a card in the kanban view on the main :guilabel:`Recruitment`` dashboard, as well as in the list view on the :guilabel:`Configuration` dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:46 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:48 +msgid "Once the job position is created, it's time to enter the details for the position. Click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the relevant card to reveal several options, and then click :guilabel:`Edit` to edit the details." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Edit the job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:56 +msgid "Enter the job description in the :guilabel:`Job Description` tab. This information is what is visible to potential employees when searching for available jobs." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:62 +msgid "All the basic information about the job position is listed under the :guilabel:`Recruitment` tab. None of the fields are required, but it is a good idea to provide at least a few details, such as where the job is located." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:66 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:68 +msgid ":guilabel:`Company`: Select the company the job is for." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:69 +msgid ":guilabel:`Website`: Select the website where the job will be published." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid ":guilabel:`Department`: Select the relevant department for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:71 +msgid ":guilabel:`Expected New Employees`: Enter the number of employees to be hired for this position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:72 +msgid ":guilabel:`Contract Template`: Select a contract template that will be used when offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:74 +msgid ":guilabel:`Interview Form`: Select a form that applicants will fill out prior to their interview, or create a new form. Once selected, a :guilabel:`Display (Name) Form` button will appear next to the selected form. Click on this to see how the form will be displayed to the candidate on the front end." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:0 +msgid "The interview form will display a link to see the form as the candidate will." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid ":guilabel:`Recruiter`: Select the person who will be doing the recruiting for this role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Enter job information details in the recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:90 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:92 +msgid "This tab displays the :guilabel:`Employee Feedback Template` and the :guilabel:`Manager Feedback Template`, both of which will be used after the employee has been hired, the predetermined time has passed, and feedback is requested." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:97 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:99 +msgid "Once a job position has been made, the :guilabel:`Interview Form` needs to be created. In the kanban view of the :menuselection:`Recruitment` dashboard, click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the card to reveal several options, and then click :guilabel:`Create Interview Form`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Create an interview form for the new position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "Click on :guilabel:`Add a section` to add a section to the form. A line will appear, and a section heading can be entered. When complete, click off the line, or press enter to lock in the new section on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:116 +msgid "Next, click :guilabel:`Add a question` to add a question to the section. A pop-up window appears to enter the question details. Type out the question in the top line." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "There are several *Question Types* to choose from:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid ":guilabel:`Multiple Lines Text Box`: allows the applicant to enter several lines of text" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:122 +msgid ":guilabel:`Single Line Text Box`: limits the applicant to only a single line of text" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:123 +msgid ":guilabel:`Numerical Value`: only allows a number to be entered" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:124 +msgid ":guilabel:`Date`: a calendar module is presented to select a date" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:125 +msgid ":guilabel:`Datetime`: a calendar module and a clock icon is presented to select a date and time" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:126 +msgid ":guilabel:`Multiple choice: only one answer`: a multiple choice question that only allows the candidate to select one answer" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid ":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice question that allows the candidate to select multiple answers" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid ":guilabel:`Matrix`: a customizable table that allows the candidate to choose an answer for each row" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Add a new question to the interview form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "Questions and sections can be reorganized. Move them by clicking and dragging individual section headings or question lines to their desired position(s)." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:140 +msgid "Sections are indicated by a gray background, while questions have a white background." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "A sample of categories and questions for a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:146 +msgid "Next, configure the options for the interview form. Click the :guilabel:`Options` tab to view all the options to configure, by category." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:150 +msgid "Questions" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:152 +msgid ":guilabel:`Layout`: Choose how the questions should be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:154 +msgid ":guilabel:`One page with all the questions`: Display all sections and questions at the same time." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:156 +msgid ":guilabel:`One page per section`: Display each section with the corresponding questions on an individual page." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +msgid ":guilabel:`One page per question`: Display a single question on each page." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:160 +msgid ":guilabel:`Progression Mode`: Display the progress the candidate is making, either as a :guilabel:`Percentage`, or as a :guilabel:`Number`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:162 +msgid ":guilabel:`Survey Time Limit`: Check this box to limit the time allowed to complete the form. When selected, a field to enter the minutes appears next to the checked box. Enter the time (using an XX:XX minute/second format) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:165 +msgid ":guilabel:`Selection`: Display the entire form (e.g. :guilabel:`All questions`), or only a random selection of questions from each section (:guilabel:`Randomized per section`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:169 +msgid "Although it is a selectable option, the :guilabel:`Randomized per section` option is not typically selected for an interview form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:173 +msgid "Scoring" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:175 +msgid ":guilabel:`No scoring`: Select this option to not score the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:176 +msgid ":guilabel:`Scoring with answers at the end`: Select this option to score the form and display the" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:177 +msgid "correct answers for the candidate when they are finished with the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid ":guilabel:`Scoring without answers at the end`: Select this option to score the form but not display the answers to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:181 +msgid "If one of the scoring options was selected, a :guilabel:`Success %` field will appear. Enter the percentage the candidate needs to pass the exam (example, 80.00%). The entry should be written in an “XX.XX” format." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:186 +msgid "Candidates" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:188 +msgid ":guilabel:`Access Mode`: Specify who can access the exam. Either :guilabel:`Anyone with the link` or :guilabel:`Invited people only`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:190 +msgid ":guilabel:`Appraisal Managers Only`: Check this box so only the managers who are reviewing the exam can see the answers. If left unchecked, anyone can view the results." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:192 +msgid ":guilabel:`Login Required`: Check this box to require candidates to log in before taking the exam, whether they have a valid token or not." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:194 +msgid ":guilabel:`Attempts Limit`: If there is a limit to how many times the exam can be taken, check this box, then enter the maximum attempt number in the field next to it." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:198 +msgid "Live Session" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:200 +msgid ":guilabel:`Reward quick answers`: If the exam is to be taken live, check this box to award more points to participants who answer quickly." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:202 +msgid ":guilabel:`Session Code`: Enter an access code that will allow the viewers into the live exam session." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:205 +msgid "After all fields have been entered, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Various options to configure for the interview form." +msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index d51d0c7e7..3d0dc0a53 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 saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -8085,35 +8085,35 @@ msgstr "" msgid "Create a bill of materials" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:5 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:9 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:11 msgid "In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so that even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:12 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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/management/bill_configuration.rst:16 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 msgid "Set up a bill of materials (BoM)" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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*." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:21 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:26 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:29 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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)`." msgstr "" @@ -8121,19 +8121,19 @@ msgstr "" msgid "Set up a Bill of Materials." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 msgid "Specify a bill of materials (BoM) for a product variant" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:47 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:50 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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." msgstr "" @@ -8141,19 +8141,19 @@ msgstr "" msgid "Product Variants in the Bill of Materials." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:60 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62 msgid "Set up operations" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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/management/bill_configuration.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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/management/bill_configuration.rst:74 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 "" @@ -8161,22 +8161,94 @@ msgstr "" msgid "Copy Existing Operations feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:83 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85 msgid "Add by-products to a bill of materials (BoM)" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:89 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:92 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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`." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:3 +msgid "Manufacturing product configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:7 +msgid "In order to manufacture a product in Odoo *Manufacturing*, the product must be properly configured. Doing so consists of enabling the *Manufacturing* route and configuring a bill of materials (BoM) for the product. Once these steps are completed, the product is selectable when creating a new manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:13 +msgid "Activate the Manufacture route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:15 +msgid "The Manufacture route is activated for each product on its own product page. To do so, begin by navigating to :menuselection:`Manufacturing --> Products --> Products`. Then, select an existing product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:19 +msgid "On the product page, select the :guilabel:`Inventory` tab, then enable the :guilabel:`Manufacture` checkbox in the :guilabel:`Routes` section. This tells Odoo the product can be manufactured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:-1 +msgid "The Manufacturing route on the Inventory tab of a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:27 +msgid "Configure a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:29 +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/management/configure_manufacturing_product.rst:32 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:-1 +msgid "The Bill of Materials smart button on a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:40 +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/management/configure_manufacturing_product.rst:43 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:-1 +msgid "The Components tab on a bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:52 +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/management/configure_manufacturing_product.rst:59 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:-1 +msgid "The Operations tab on a bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:67 +msgid "Learn more" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:69 +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 `." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3 msgid "Use kits" msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 7131be599..6da990456 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -965,7 +965,7 @@ msgid "Under :guilabel:`Note`, internal notes can be left (such as: to-do lists, msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:144 -msgid "Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These options provide various formatting options to ensure vital internal information is organzied for event staff to review." +msgid "Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These options provide various formatting options to ensure vital internal information is organized for event staff to review." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:-1 @@ -1029,7 +1029,7 @@ msgid "View of the drag and drop building blocks used to customize event invite msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:212 -msgid "To build an email event invite from scratch, select the :guilabel:`Plain Text` template, and Odoo will provide a blank email canvas, which can be customized either by using the front-end rich text editor that accepts slash (`/`) commands, or the XML code editor when :ref:`developer mode ` is engaged and the :guilabel:`` icon is pressed." +msgid "To build an email event invite from scratch, select the :guilabel:`Plain Text` template, and Odoo will provide a blank email canvas, which can be customized either by using the frontend rich text editor that accepts slash (`/`) commands, or the XML code editor when :ref:`developer mode ` is engaged and the :guilabel:`` icon is pressed." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:218 @@ -1085,15 +1085,15 @@ 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 back end of Odoo through the :guilabel:`Events` application, or access the hidden event page through the front end as either a priveliged user or administrator." +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 "" #: ../../content/applications/marketing/events/event_essentials.rst:273 -msgid "If navigating from the back end, go to the event form, and click the :guilabel:`Go to Website` smart button to reach the event page on the website (on the front end). If starting from the front end, simply navigate to the event page that needs to be published." +msgid "If navigating from the backend, go to the event form, and click the :guilabel:`Go to Website` smart button to reach the event page on the website (on the frontend). If starting from the frontend , simply navigate to the event page that needs to be published." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:277 -msgid "No matter the route, an event page can only be published from the front end. In the upper right corner of the event page on the website, toggle the switch from the red :guilabel:`Unpublished` status to the green :guilabel:`Published` status. Doing so instantly makes the event page accessible to the public on the website." +msgid "No matter the route, an event page can only be published from the frontend. In the upper right corner of the event page on the website, toggle the switch from the red :guilabel:`Unpublished` status to the green :guilabel:`Published` status. Doing so instantly makes the event page accessible to the public on the website." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:-1 @@ -2298,7 +2298,7 @@ msgid "View of the mailing list page in the SMS marketing application." msgstr "" #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:71 -msgid "To reveal all the possible options in the :guilabel:`Recipients` field, click the field to see all the choices Odoo makes avaialble." +msgid "To reveal all the possible options in the :guilabel:`Recipients` field, click the field to see all the choices Odoo makes available." msgstr "" #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:74 diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 942b2f8f5..e3f0bcbab 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -246,46 +246,46 @@ msgid "To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure acco msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:19 -msgid "Refer to `Microsoft's documentation `_ on how to set up an Azure AD Tenant (also called an *environment*), which is a representation of an organization to manage and register apps." +msgid "Refer to `Microsoft's documentation `_ on how to set up an Microsoft Entra ID (formally called *Microsoft Azure Active Directory (Azure AD)*), which is a representation of an organization to manage and register apps." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:23 -msgid "Then, `Register an Application `_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`." +#: ../../content/applications/productivity/calendar/outlook.rst:24 +msgid "Then, `Register an Application `_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:29 +#: ../../content/applications/productivity/calendar/outlook.rst:30 msgid "When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and copy the Odoo database URI (URL) followed by `/microsoft_account/authentication`." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:33 +#: ../../content/applications/productivity/calendar/outlook.rst:34 msgid "Enter `https://www.companyname.odoo.com/microsoft_account/authentication` for the :guilabel:`Redirect URI`." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:-1 -msgid "The \"Supported account type\" and \"Redirect URI\" settings in the Microsoft Azure AD portal." +msgid "The \"Supported account type\" and \"Redirect URI\" settings in the Microsoft Entra ID portal." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:40 +#: ../../content/applications/productivity/calendar/outlook.rst:41 msgid "For more information on the restrictions and limitations of URIs, `check this page `_." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:43 +#: ../../content/applications/productivity/calendar/outlook.rst:44 msgid "Regarding the application credentials, the user *must* add a client secret, which allows Odoo to authenticate itself, requiring no interaction from the user's side. :guilabel:`Certificates` are optional." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:47 +#: ../../content/applications/productivity/calendar/outlook.rst:48 msgid "To do add a client secret, click :guilabel:`Add a certificate or secret` and then click :guilabel:`New client secret`. Next, type a :guilabel:`Description` and select when the client secret :guilabel:`Expires`." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:51 +#: ../../content/applications/productivity/calendar/outlook.rst:52 msgid "Since resetting the synchronization can be tricky, Odoo recommends setting the maximum allowed expiration date for the client secret (24 months), so there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to generate the client secret (:guilabel:`Secret ID`)." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:56 +#: ../../content/applications/productivity/calendar/outlook.rst:57 msgid "Configuration in Odoo" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:58 +#: ../../content/applications/productivity/calendar/outlook.rst:59 msgid "In the Odoo database, go to :menuselection:`Settings --> General Settings --> Integrations` and activate the :guilabel:`Outlook Calendar` setting." msgstr "" @@ -293,7 +293,7 @@ msgstr "" msgid "The \"Outlook Calendar\" setting activated in Odoo." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:65 +#: ../../content/applications/productivity/calendar/outlook.rst:66 msgid "From the Microsoft Azure portal, under the :guilabel:`Overview` section of the application, copy the :guilabel:`Application (Client) ID`, and paste it into the :guilabel:`Client ID` field in Odoo." msgstr "" @@ -301,7 +301,7 @@ msgstr "" msgid "The \"Client ID\" in the Microsoft Azure portal." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:72 +#: ../../content/applications/productivity/calendar/outlook.rst:73 msgid "In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` section, copy the :guilabel:`Client Secret Value` and paste it into the :guilabel:`Client Secret` field in Odoo." msgstr "" @@ -309,67 +309,67 @@ msgstr "" msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:79 +#: ../../content/applications/productivity/calendar/outlook.rst:80 msgid "Finally, on the Odoo :menuselection:`Settings --> General Settings` page, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:84 +#: ../../content/applications/productivity/calendar/outlook.rst:85 msgid "Sync with Outlook" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:88 +#: ../../content/applications/productivity/calendar/outlook.rst:89 msgid "Odoo highly recommends testing the Outlook calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Outlook Calendar with the user's production database." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:92 +#: ../../content/applications/productivity/calendar/outlook.rst:93 msgid "If the user has any past, present, or future events on their Odoo calendar before syncing their Outlook calendar, Outlook will treat the events pulled from Odoo's calendar during the sync as new events, causing an email notification to be sent from Outlook to all the event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:96 +#: ../../content/applications/productivity/calendar/outlook.rst:97 msgid "To avoid unwanted emails being sent to all past, present, and future event attendees, the user must add the events from the Odoo calendar to the Outlook calendar before the first ever sync, delete the events from Odoo, and then start the sync." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:100 +#: ../../content/applications/productivity/calendar/outlook.rst:101 msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Outlook will still send a notification to all event participants every time an event is edited (created, deleted, unarchived, or event date/time changed), with no exceptions. This is a limitation that cannot be fixed from Odoo's side." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:105 +#: ../../content/applications/productivity/calendar/outlook.rst:106 msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:112 +#: ../../content/applications/productivity/calendar/outlook.rst:113 msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:114 +#: ../../content/applications/productivity/calendar/outlook.rst:115 msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:115 +#: ../../content/applications/productivity/calendar/outlook.rst:116 msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:116 +#: ../../content/applications/productivity/calendar/outlook.rst:117 msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:117 +#: ../../content/applications/productivity/calendar/outlook.rst:118 msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:118 +#: ../../content/applications/productivity/calendar/outlook.rst:119 msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:119 +#: ../../content/applications/productivity/calendar/outlook.rst:120 msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:122 +#: ../../content/applications/productivity/calendar/outlook.rst:123 msgid "Sync Odoo Calendar and Outlook" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:124 +#: ../../content/applications/productivity/calendar/outlook.rst:125 msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions." msgstr "" @@ -377,19 +377,19 @@ msgstr "" msgid "The \"Outlook\" sync button in Odoo Calendar." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:132 +#: ../../content/applications/productivity/calendar/outlook.rst:133 msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:136 -msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook `. The configuration of Microsoft's Azure account is only done once, as Azure AD tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users." -msgstr "" - -#: ../../content/applications/productivity/calendar/outlook.rst:143 -msgid ":doc:`../mail_plugins/outlook`" +#: ../../content/applications/productivity/calendar/outlook.rst:137 +msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook `. The configuration of Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:144 +msgid ":doc:`../mail_plugins/outlook`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:145 msgid ":doc:`google`" msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index c4c525cd0..f79124fa4 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -68,6 +68,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:16 #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:12 #: ../../content/applications/sales/point_of_sale/restaurant.rst:20 #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10 @@ -517,7 +518,7 @@ msgid "Enrich your contacts base with Partner Autocomplete" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:5 -msgid "Parter Autocomplete helps you to enrich your contacts database with corporate data. Select one of the companies suggested in the dropdown, and quickly get all the information you need." +msgid "Partner Autocomplete helps you to enrich your contacts database with corporate data. Select one of the companies suggested in the dropdown, and quickly get all the information you need." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:11 @@ -2828,37 +2829,173 @@ msgid "Pricelists" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:5 -msgid "You probably know the concept of happy hour: during a certain period of time, the barman gives a discount on some drinks (usually 50% off or a buy one get one free). When the period is over, prices go back to normal. But how does that relate with Odoo?" +msgid "Pricelists allow you to adjust product prices depending on various criteria automatically. For example, you can set POS-specific prices, create temporary discount periods, reward specific customers, or offer discounts when set quantities are ordered." msgstr "" -#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:10 -msgid "In Odoo, you can set up happy hours. It’s one of the many possible uses of *Pricelists*. Those *Pricelists* allow the creation of multiple prices for the same product: a regular one and a special one for happy hours. Available in the *PoS* app, those are really convenient." +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:14 +msgid "Navigate to the :ref:`general POS app settings ` and ensure :guilabel:`Flexible Pricelists` are enabled under the :guilabel:`Pricing` section." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:17 -msgid "Set up Pricelists" +msgid ":ref:`Multiple prices per product ` is the default pricelist option for setting simple fixed price rules per product. Select :ref:`Advanced price rules (discounts, formulas) ` to apply price rules to multiple products at once and to compute prices dynamically using percentage discounts or more complex formulas in addition to setting fixed prices." msgstr "" -#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:19 -msgid "To set up a *Pricelist*, go to :menuselection:`Point of Sale --> Configuration --> Configuration` and enable the *Pricelist* feature. Then, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and enable *Pricelist* for the *PoS*." +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:-1 +msgid "Enabling pricelists in the general P0S settings" msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:26 -msgid "Now, you can create *Pricelists* by clicking on the *Pricelists* link. Then, set it up by choosing the product category you want to include in your happy hour and the discount." +msgid "The selected pricelist type applies to the entire database, including the :doc:`Sales <../../sales/products_prices/prices/pricing>` and :ref:`eCommerce ` apps." msgstr "" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:33 -msgid "Go back to your *PoS* settings and add the Happy Hour pricelist to the list. You can even choose a default pricelist if needed." +msgid "Create pricelists" msgstr "" -#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:39 -msgid "From now on, on the *PoS* interface, a new button is available, allowing you to choose among the different *pricelists* you added before." +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:35 +msgid "Go to :menuselection:`Point of Sale --> Products --> Pricelists` and click :guilabel:`New` or select an existing pricelist. The pricelist setup differs depending on the :ref:`selected pricelist option `." msgstr "" -#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:46 +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42 +msgid "Multiple prices per product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:44 +msgid "When pricelists are configured to use the :guilabel:`Multiple prices per product` option, it is possible to use multiple fixed prices for different products or their variants depending, if necessary, on one or several conditions. To add a new price rule to a pricelist:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:48 +msgid "Click :guilabel:`Add a line`, and select a **product** and its **variant** if needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:49 +msgid "Add the condition(s):" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:51 +msgid "a product quantity to be reached by using the :guilabel:`Min. Quantity` column;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:52 +msgid "a determined period during which the pricelist is applied by using the :guilabel:`Start Date` and :guilabel:`End Date` columns." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:55 +msgid "Add the :guilabel:`Price` to be applied when the conditions are met (if any)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:-1 +msgid "Setup form of a multiple prices pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:63 +msgid "Advanced price rules" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:65 +msgid "When pricelists are configured to use the :guilabel:`Advanced price rules (discounts, formulas)` option, it is possible to use percentage discounts/mark-ups and formulas in addition to using fixed prices. To add a new price rule to a pricelist, click :guilabel:`Add a line`. In the pop-up windows:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:69 +msgid "Select a :guilabel:`Computation` method:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:71 +msgid ":guilabel:`Fixed Price` to set a new fixed price (similarly to the :guilabel:`Multiple prices per product` option)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:73 +msgid ":guilabel:`Discount` to compute a percentage discount (e.g., `10.00` %) or mark-up (e.g., `-10.00` %)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:75 +msgid ":guilabel:`Formula` to compute the price according to a formula. It is required to define what the calculation is **based on** (:guilabel:`Sales Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`). You can then:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:79 +msgid "Apply a percentage :guilabel:`Discount` or mark-up." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:80 +msgid "Add an :guilabel:`Extra Fee` (e.g., $ `5.00`) or subtract a fixed amount (e.g., $ `-5.00`)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:81 +msgid "Define a :doc:`Rounding Method ` by forcing the price after :guilabel:`Discount` to be a multiple of the value set. The :guilabel:`Extra Fee` is applied afterward." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:86 +msgid "To have the final price end with `.99`, set the :guilabel:`Rounding Method` to `1.00` and the :guilabel:`Extra Fee` to `-0.01`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:89 +msgid "Specify the minimum (e.g., $ `20.00` ) and maximum (e.g., $ `50.00` ) profit :guilabel:`Margins` for computations based on :guilabel:`Cost`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:92 +msgid "Select on which product(s) the price rule should be **applied**:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:94 +msgid ":guilabel:`All Products`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:95 +msgid "a :guilabel:`Product Category`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:96 +msgid "a :guilabel:`Product`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:97 +msgid "a :guilabel:`Product Variant`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:99 +msgid "Add conditions, such as a specific quantity to reach for the price to change by using the :guilabel:`Min. Quantity` field or a specific period during which the pricelist should be applied by using the :guilabel:`Validity` fields." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:-1 +msgid "Setup form to configure an advanced pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:107 +msgid "Select pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:109 +msgid "Go to the :ref:`specific POS settings ` and add all the available pricelists in the :guilabel:`Available` field. Then, set its **default pricelist** in the :guilabel:`Default` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:113 +msgid "When you :ref:`open a POS session `, click the **pricelists** button, and select the desired pricelist from the list." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:-1 +msgid "Button to select a pricelist on the POS frontend" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:120 +msgid "Multiple pricelists must be selected for the **pricelist button** to be displayed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:121 +msgid "If a pricelist is selected on a POS order while its conditions are **not** met, the price will **not** be adjusted." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:125 +msgid "You can also set a pricelist to be selected automatically once a specific :ref:`customer is set `. To do so, go to the customer form and switch to the preferred pricelist in the :guilabel:`Pricelist` field of the :guilabel:`Sales & Purchase` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:130 msgid ":doc:`../../sales/products_prices/prices/pricing`" msgstr "" +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:131 +msgid ":ref:`How to use pricelists in an ecommerce environment `" +msgstr "" + #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:3 msgid "Receipts and invoices" msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index 152024a9b..773f721e3 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-09-14 05:10+0000\n" +"POT-Creation-Date: 2023-10-27 12:38+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n"