[I18N] Update translation terms from Transifex

This commit is contained in:
Odoo Translation Bot
2023-12-24 00:41:04 +01:00
parent fc363ad00f
commit 2e0df8e810
154 changed files with 410571 additions and 257890 deletions
+498 -160
View File
@@ -4,10 +4,10 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Jolien De Paepe, 2023
# Martin Trigaux, 2023
# Wil Odoo, 2023
# Yenthe Van Ginneken <yenthespam@gmail.com>, 2023
# Wil Odoo, 2023
# Jolien De Paepe, 2023
# Erwin van der Ploeg <erwin@odooexperts.nl>, 2023
#
#, fuzzy
@@ -15,7 +15,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
"PO-Revision-Date: 2023-11-08 08:57+0000\n"
"Last-Translator: Erwin van der Ploeg <erwin@odooexperts.nl>, 2023\n"
"Language-Team: Dutch (https://app.transifex.com/odoo/teams/41243/nl/)\n"
@@ -749,265 +749,607 @@ msgid "Overview"
msgstr "Overzicht"
#: ../../content/applications/productivity/discuss/overview/get_started.rst:3
msgid "Get Started with Discuss"
msgid "Get started with Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:5
msgid ""
"Discuss allows you to bring all of your companys communication together "
"through messages, notes, and chat. Share information, projects, files, "
"prioritize tasks, and stay connected with colleagues and partners throughout"
" applications. Forge better relationships, increase productivity and "
"transparency by promoting a convenient way of communicating."
"Odoo *Discuss* is an internal communication app that allows users to connect"
" through messages, notes, and file sharing, either through a persistent chat"
" window that works across applications, or through the dedicated *Discuss* "
"dashboard."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:13
msgid "Choose your notifications preference"
#: ../../content/applications/productivity/discuss/overview/get_started.rst:12
msgid "Choose notifications preference"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:15
#: ../../content/applications/productivity/discuss/overview/get_started.rst:14
msgid ""
"Access your *Preferences* and choose how you would like your notifications "
"to be handled."
"Access user-specific preferences for the *Discuss* app by navigating to "
":menuselection:`Settings app --> Users --> User --> Preferences tab`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid "View of the preferences page for Odoo Discuss"
msgid "View of the Preferences tab for Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:23
#: ../../content/applications/productivity/discuss/overview/get_started.rst:21
msgid ""
"By default, the field is set as *Handle by Emails* making messages, notes, "
"and notifications where you were mentioned or that you follow, to be sent "
"through email. By choosing *Handle in Odoo*, they are shown in the *Inbox*."
"By default, the :guilabel:`Notification` field is set as :guilabel:`Handle "
"by Emails`. With this setting enabled, a notification email will be sent by "
"Odoo every time a message is sent from the chatter, a note is sent with an "
"`@` mention (from chatter), or a notification is sent for a record that the "
"user follows. Something that triggers a notification is changing of the "
"stage (if an email\\ is configured to be sent, for example if the task is "
"set to :guilabel:`Done`)."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:24
msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*."
#: ../../content/applications/productivity/discuss/overview/get_started.rst:27
msgid ""
"By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in"
" the *Discuss* app's *inbox*. Messages can have the following actions taken "
"on them: respond with an emoji by clicking :guilabel:`Add a Reaction`, or "
"reply to the message by clicking on :guilabel:`Reply`. Additional actions "
"may include starring the message by clicking :guilabel:`Marked as Todo`, or "
"pinning the message by selecting :guilabel:`Pin` or even mark the message as"
" unread by selecting :guilabel:`Marked as unread`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid "View of an inbox message and its action options in Odoo Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:30
msgid ""
"The messages tagged as *Mark as Todo* are also shown in *Starred*, while the"
" ones *Marked as Read* are moved to *History*."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid "View of messages marked as todo in Odoo Discuss"
msgid "View of an inbox message and its action options in Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:38
msgid "Start Chatting"
msgid ""
"Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the "
":guilabel:`Starred` page, while clicking :guilabel:`Mark as Read` moves the "
"message to :guilabel:`History`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:40
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid "View of messages marked as todo in Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:46
msgid "Start chatting"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:48
msgid ""
"The first time you log in to your account, OdooBot sends you a message "
"asking for permission to receive desktop notifications to chats. If "
"accepted, you receive push notifications to the messages sent to you despite"
" of where you are in Odoo."
"The first time a user logs in to their account, OdooBot sends a message "
"asking for permission to send desktop notifications for chats. If accepted, "
"the user will receive push notifications on their desktop for the messages "
"they receive, regardless of where the user is in Odoo."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid ""
"View of the messages under the messaging menu emphasizing the request for push\n"
"notifications for Odoo Discuss"
"notifications for Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:50
#: ../../content/applications/productivity/discuss/overview/get_started.rst:58
msgid ""
"To stop receiving desktop notifications, reset the notifications settings of"
" your browser."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:52
msgid ""
"To start a chat, click on *New Message* on the *Messaging Menu*, or go to "
"*Discuss* and send a *Direct Message*."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid ""
"View of discusss panel emphasizing the titles channels and direct messages "
"in Odoo Discuss"
" the browser."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:60
msgid ""
"You can also create :doc:`public and private channels <team_communication>`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:63
msgid "Mentions in the chat and on the Chatter"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:66
msgid ""
"To mention a user within a chat or the chatter type *@user-name*; to refer "
"to a channel, type *#channel-name*."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:68
msgid ""
"A notification is sent to the user mentioned either to his *Inbox* or "
"through email, depending on his settings."
"To start a chat, go to the :menuselection:`Discuss` app and click on the "
":guilabel:`+ (plus)` icon next to :guilabel:`Direct Messages` or "
":guilabel:`Channels` in the left menu of the dashboard."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid "View of a couple of chat window messages for Odoo Discuss"
msgid ""
"View of Discuss's panel emphasizing the titles channels and direct messages in Odoo\n"
"Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:69
msgid ""
"A company can also easily create :doc:`public and private channels "
"</applications/productivity/discuss/overview/team_communication>`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:73
msgid "Mentions in the chat and on the chatter"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:75
msgid ""
"To mention a user within a chat or the chatter, type `@user-name`; to refer "
"to a channel, type `#channel-name`. The user mentioned will be notified in "
"their *inbox* or through an email, depending on their communication "
"settings."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid "View of a couple of chat window messages for Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:84
msgid ""
"When a user is mentioned, the search list (list of names) suggests values "
"first based on the tasks followers, and secondly on *Employees*. If the "
"first based on the task's followers, and secondly on employees. If the "
"record being searched does not match with either a follower or employee, the"
" scope of the search becomes all partners."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:80
msgid "Chat status"
#: ../../content/applications/productivity/discuss/overview/get_started.rst:89
msgid "User status"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:82
#: ../../content/applications/productivity/discuss/overview/get_started.rst:91
msgid ""
"It is helpful to see what colleagues are up to and how quickly they can "
"respond to messages by checking their *Status*. The status is shown on the "
"left side of a contacts names on Discuss sidebar and on the *Messaging "
"menu*."
"respond to messages by checking their *status*. The status is shown on the "
"left side of a contact's name on the :guilabel:`Discuss` sidebar, on the "
"*messaging menu* and when listed in the *chatter*."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:86
#: ../../content/applications/productivity/discuss/overview/get_started.rst:95
msgid "Green = online"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:87
#: ../../content/applications/productivity/discuss/overview/get_started.rst:96
msgid "Orange = away"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:88
#: ../../content/applications/productivity/discuss/overview/get_started.rst:97
msgid "White = offline"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:89
#: ../../content/applications/productivity/discuss/overview/get_started.rst:98
msgid "Airplane = out of the office"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst-1
msgid "View of the contacts status for Odoo Discuss"
msgid "View of the contacts' status for Odoo Discuss."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:97
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:65
msgid ":doc:`team_communication`"
#: ../../content/applications/productivity/discuss/overview/get_started.rst:106
msgid ":doc:`/applications/productivity/discuss/overview/team_communication`"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:98
msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ":doc:`/applications/general/email_communication/email_servers`"
#: ../../content/applications/productivity/discuss/overview/get_started.rst:107
msgid ":doc:`/applications/productivity/discuss/overview/plan_activities`"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3
msgid "Get Organized by Planning Activities"
msgstr ""
msgid "Activities"
msgstr "Activiteiten"
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:5
msgid ""
"When you plan activities you minimize the risk of uncertainties, as you "
"provide clear directions for the course of your next action. In addition to "
"that, you do not leave space for wasteful activities and reduce the chance "
"of having overlapping actions between team members."
"*Activities* are follow-up tasks tied to a record in an Odoo database. "
"Activities can be scheduled on any page of the database that contains a "
"chatter thread, kanban view, list view, or activities view of an "
"application."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10
msgid "Where do I see my schedule activities?"
msgid "Schedule activities"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12
msgid ""
"Access and manage your activities wherever you are in Odoo by the "
"*Activities* menu."
"One way that activities are created is by clicking the :guilabel:`Schedule "
"Activity` button, located at the top of the *chatter* on any record. On the "
"pop-up window that appears, select an :guilabel:`Activity Type` from the "
"drop-down menu."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:17
msgid ""
"Individual applications have a list of *Activity Types* dedicated to that "
"application. For example, to view and edit the activities available for the "
"*CRM* application, go to :menuselection:`CRM app --> Configuration --> "
"Activity Types`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:21
msgid ""
"Enter a title for the activity in the :guilabel:`Summary` field, located in "
"the :guilabel:`Schedule Activity` pop-up window."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:24
msgid ""
"To assign the activity to a different user, select a name from the "
":guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the "
"activity is automatically assigned."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:27
msgid ""
"Lastly, feel free to add any additional information in the optional "
":guilabel:`Log a note...` field."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:30
msgid ""
"The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up "
"window auto-populates based on the configuration settings for the selected "
":guilabel:`Activity Type`. However, this date can be changed by selecting a "
"day on the calendar in the :guilabel:`Due Date` field."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:34
msgid "Lastly, click one of the following buttons:"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:36
msgid ""
":guilabel:`Schedule`: adds the activity to the chatter under "
":guilabel:`Planned activities`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:37
msgid ""
":guilabel:`Mark as Done`: adds the details of the activity to the chatter "
"under :guilabel:`Today`. The activity is not scheduled, it is automatically "
"marked as completed."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:39
msgid ""
":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` "
"marked as done, and opens a new activity window."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:41
msgid ":guilabel:`Discard`: discards any changes made on the pop-up window."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid ""
"View of crm leads page emphasizing the activities menu for Odoo Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:20
msgid "Plan activities"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:22
msgid ""
"Activities can be planned and managed from the chatter by clicking on "
"*Schedule activity*, or through Kanban views."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid ""
"View of crm leads and the option to schedule an activity for Odoo Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:31
msgid "Set your activity types"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:33
msgid ""
"A number of activities types are available by default in Odoo (call, email, "
"meeting, etc.). However, you can set new ones going to "
":menuselection:`Settings --> Activity types`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid ""
"View of the settings page emphasizing the menu activity types for Odoo "
"Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:42
msgid ""
"If you need to create an activity type with an available calendar, make sure"
" to create it with an *Action to Perform* set as *Meeting*."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:46
msgid "Recommend next activities"
msgid "View of CRM leads and the option to schedule an activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48
msgid ""
"Odoo helps you to plan a flow of activities by allowing you to set "
"*Recommended Next Activities*."
"Depending on the activity type, the :guilabel:`Schedule` button may be "
"replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` "
"button."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:51
msgid ""
"Scheduled activities are added to the chatter for the record under "
":guilabel:`Planned activities`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:57
msgid ""
"Activities can also be scheduled from the kanban, list, or activities view "
"of an application."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:61
msgid "Kanban view"
msgstr "Kanban-weergave"
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:63
msgid ""
"Select a record on which to schedule an activity. Click on the :guilabel:`🕘 "
"(clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill "
"out the pop-up form."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0
msgid ""
"Kanban view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:70
msgid "List view"
msgstr "Lijstweergave"
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:72
msgid ""
"Select a record on which to schedule an activity. Click on the :guilabel:`🕘 "
"(clock)` icon, then :guilabel:`Schedule An Activity`. If the record already "
"has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 "
"(phone)` or an :guilabel:`✉️ (envelope)` icon."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0
msgid "List view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:80
msgid "Activity view"
msgstr "Activiteit weergave"
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:82
msgid ""
"To open the activity view for an application, select the :guilabel:`🕘 "
"(clock)` icon from the menu bar anywhere in the database. Select any "
"application from the drop-down menu, and click the :guilabel:`🕘 (clock)` "
"icon for the desired app."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0
msgid ""
"Activity menu drop down with focus on where to open activity view for CRM."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:90
msgid ""
"Select a record on which to schedule an activity. Move across the row to "
"find the desired activity type, then click the :guilabel:` (plus sign)`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0
msgid ""
"Activity view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:98
msgid ""
"Activity colors, and their relation to an activity's due date, is consistent"
" throughout Odoo, regardless of the activity type, or the view."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:101
msgid ""
"Activities that appear in **green** indicate a due date sometime in the "
"future."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:102
msgid "**Yellow** indicates that the activity's due date is today."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:103
msgid ""
"**Red** indicates that the activity is overdue and the due date has passed."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:105
msgid ""
"For example, if an activity is created for a phone call, and the due date "
"passes, the activity appears with a red phone in list view, and a red clock "
"on the kanban view."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:109
msgid "View scheduled activities"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:111
msgid ""
"To view scheduled activities, open either the :menuselection:`Sales app` or "
":menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located "
"to the far-right side of the other view options."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:114
msgid ""
"Doing so opens the activities menu, showcasing all the scheduled activities "
"for the user, by default. To show all activities for every user, remove the "
":guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:118
msgid ""
"To view a consolidated list of activities separated by the application where"
" they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on"
" the header menu to see the activities for that specific application in a "
"drop-down menu."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:122
msgid ""
"The possibility to :guilabel:`Add new note` and :guilabel:`Request a "
"Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘"
" (clock)` icon on the header menu is clicked."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid "View of CRM leads page emphasizing the activities menu."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:130
msgid "Configure activity types"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:132
msgid ""
"To configure the types of activities in the database, go to "
":menuselection:`Settings app --> Discuss --> Activities --> Activity Types`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid "View of the settings page emphasizing the menu activity types."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:139
msgid ""
"Doing so reveals the :guilabel:`Activity Types` page, where the existing "
"activity types are found."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:141
msgid ""
"To edit an existing activity type, select it from the list, then click "
":guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:144
msgid ""
"At the top of a blank activity type form, start by choosing a "
":guilabel:`Name` for the new activity type."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid "New activity type form."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:152
msgid "Activity settings"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:155
#: ../../content/applications/productivity/studio/automated_actions.rst:134
msgid "Action"
msgstr "Actie"
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:157
msgid ""
"The *Action* field specifies the intent of the activity. Some actions "
"trigger specific behaviors after an activity is scheduled."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:160
msgid ""
"If :guilabel:`Upload Document` is selected, a link to upload a document is "
"added directly to the planned activity in the chatter."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:162
msgid ""
"If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users "
"have the option to open their calendar to schedule a time for this activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:164
msgid ""
"If :guilabel:`Request Signature` is selected, a link is added to the planned"
" activity in the chatter that opens a signature request pop-up window."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:168
msgid ""
"The actions available to select on an activity type vary, depending on the "
"applications currently installed in the database."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:172
msgid "Default user"
msgstr "Standaard gebruiker"
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:174
msgid ""
"To automatically assign this activity to a specific user when this activity "
"type is scheduled, choose a name from the :guilabel:`Default User` drop-down"
" menu. If this field is left blank, the activity is assigned to the user who"
" creates the activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:179
msgid "Default summary"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:181
msgid ""
"To include notes whenever this activity type is created, enter them into the"
" :guilabel:`Default Summary` field."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:185
msgid ""
"The information in the :guilabel:`Default User` and :guilabel:`Default "
"Summary` fields are included when an activity is created. However, they can "
"be altered before the activity is scheduled or saved."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:190
msgid "Next activity"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:192
msgid ""
"To automatically suggest, or trigger, a new activity after an activity has "
"been marked complete, the :guilabel:`Chaining Type` must be set."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:196
msgid "Suggest next activity"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:198
msgid ""
"In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next "
"Activity`. Upon doing so, the field underneath changes to: "
":guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to "
"select any activities to recommend as follow-up tasks to this activity type."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:202
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:230
msgid ""
"In the :guilabel:`Schedule` field, choose a default deadline for these "
"activities. To do so, configure a desired number of :guilabel:`Days`, "
":guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur "
":guilabel:`after completion date` or :guilabel:`after previous activity "
"deadline`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:207
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:235
msgid ""
"This :guilabel:`Schedule` field information can be altered before the "
"activity is scheduled."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:209
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:237
msgid "When all configurations are complete, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid "Schedule activity popup with emphasis on recommended activities."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:216
msgid ""
"If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest "
"Next Activity`, and has activities listed in the :guilabel:`Suggest` field, "
"users are presented with recommendations for activities as next steps."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:221
msgid "Trigger next activity"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:223
msgid ""
"Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` "
"immediately launches the next activity once the previous one is completed."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:226
msgid ""
"If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining "
"Type` field, the field beneath changes to: :guilabel:`Trigger`. From the "
":guilabel:`Trigger` field drop-down menu, select the activity that should be"
" launched once this activity is completed."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid ""
"View of an activity type form emphasizing the field recommended next activities for Odoo\n"
"Discuss"
"Schedule new activity popup with emphasis on Done and launch next button."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:55
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:244
msgid ""
"Once the respective activity is completed, select *Done & Schedule Next* and"
" next steps are suggested to you."
"When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger"
" Next Activity`, marking the activity as `Done` immediately launches the "
"next activity listed in the :guilabel:`Trigger` field."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1
msgid ""
"View of an activity being schedule emphasizing the recommended activities field being\n"
"shown for Odoo Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:249
#: ../../content/applications/productivity/discuss/overview/team_communication.rst:113
msgid ":doc:`get_started`"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250
msgid ":doc:`team_communication`"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/team_communication.rst:3
msgid "Use channels for team communication"
msgstr ""
@@ -5740,10 +6082,6 @@ msgid ""
" It works the same way as when you apply filters on a model."
msgstr ""
#: ../../content/applications/productivity/studio/automated_actions.rst:134
msgid "Action"
msgstr "Actie"
#: ../../content/applications/productivity/studio/automated_actions.rst:136
msgid ""
"Determine what the automated action should do (server action). There are "