# SOME DESCRIPTIVE TITLE. # Copyright (C) Odoo S.A. # This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # # Translators: # Gunther Clauwaert , 2021 # 04a2cd0fd6ee22172c36ea91f27a38c5_60041bf, 2021 # Erwin van der Ploeg , 2023 # Yenthe Van Ginneken , 2023 # Martin Trigaux, 2023 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-03-02 07:38+0000\n" "PO-Revision-Date: 2021-05-18 05:18+0000\n" "Last-Translator: Martin Trigaux, 2023\n" "Language-Team: Dutch (https://app.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: nl\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #: ../../content/applications/marketing.rst:5 msgid "Marketing" msgstr "Marketing" #: ../../content/applications/marketing/events.rst:5 msgid "Events" msgstr "Evenementen" #: ../../content/applications/marketing/events.rst:8 msgid "`Odoo Tutorials: Events `_" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:3 msgid "Event essentials" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:5 msgid "" "Odoo Events provides event coordinators with an arsenal of planning, " "communications, and reporting tools to create immersive and engaging " "experiences for customers. Namely, staff can create and publish events on " "their website, sell tickets online, scan tickets with Odoo barcode, send out" " automated emails, and generate rich reporting data once the event accepts " "registrations." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:11 msgid "Kanban concepts and organization" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:13 msgid "" "To get started, click on the :guilabel:`Events` application on the home " "dashboard, which then leads to the kanban view populated with a variety of " "pipeline stages. Key information is listed on each event card, such as the " "date/time of the event, along with the number of expected (and confirmed) " "attendees." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:18 msgid "" "To create a new stage, click :guilabel:`Add a Column` and provide a " "befitting title to reflect the purpose of that stage." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:21 msgid "" "To reorganize the stages, just drag-and-drop them until they are in the " "correct order. Stages can also be “folded” in the kanban for a cleaner " "presentation, via the :guilabel:`Settings` menu to the right of each stage's" " title, which is represented by a gear icon." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:26 msgid "" "The gear icon, by default, is hidden and will appear next to the " ":guilabel:`+` icon when moused over." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:29 msgid "When clicked, a drop-down menu of settings will appear." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rstNone msgid "Overview of events setting with the kanban view in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:36 msgid "Create a new event" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:38 msgid "" "To create an event, click :guilabel:`Create` from the Events dashboard. Odoo" " will then direct the page to a blank event template form." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:41 msgid "" "From the event form, fill out the necessary fields, either by choosing from " "existing data in the Odoo database or by creating and editing new field " "data. Key information to enter for the event includes:" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:45 msgid ":guilabel:`Event Name`: give the event a title." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:46 msgid "" ":guilabel:`Date`: includes the start and end dates/times for the event." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:47 msgid "" ":guilabel:`Timezone`: covers the timezone for when the event is taking " "place." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:48 msgid "" ":guilabel:`Template`: choose from a pre-built event template or build a " "custom one and connect it here." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:50 msgid "" ":guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. " "`tradeshow`). Tags help better organize event cards in the kanban and are " "useful when using search filters during reporting periods." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:53 msgid "" ":guilabel:`Organizer`: detail the organizer(s) for the event. This field is " "usually the company that owns the Odoo database, or a vendor." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:55 msgid "" ":guilabel:`Responsible`: name the point person who is responsible for " "organizing the event." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:56 msgid "" ":guilabel:`Website`: indicate which Odoo website(s) the event event should " "be published to." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:57 msgid "" ":guilabel:`Venue`: list the venue details here if it's a new record, or " "choose from an existing location." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:59 msgid "" ":guilabel:`Limit Registrations`: when enabled, this setting caps the " "attendee registrations to a specified amount" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:61 msgid "" ":guilabel:`Autoconfirmation`: when enabled, this setting skips the " "confirmation request that gets sent by email to event registrants, and " "automatically confirms their registration." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:64 msgid "" "Once the fields in the event form are set, move on to the " ":guilabel:`Tickets` and :guilabel:`Communication` tabs, and optionally the " ":guilabel:`Questions` tab if registrations should require additional " "information." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:69 msgid "Add and sell event tickets" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:71 msgid "" "Under the :guilabel:`Tickets` tab, add line items for each type of ticket " "the event plans to offer. Here, determine the ticket price, start/end dates " "for registrations, as well as the maximum number of tickets that can be " "sold." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:75 msgid "" "If selling tickets isn't necessary for the event, a simple " ":guilabel:`Registration` button will be displayed on the event's page by " "default." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rstNone msgid "View of the ticket tab in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:83 msgid "Send automated emails, text, and social posts to event attendees" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:85 msgid "" "Under the :guilabel:`Communication` tab, configure personalized email, SMS, " "or social post messages to keep in touch with event attendees. For each " "communication, click :guilabel:`Add a line` in the :guilabel:`Communication`" " tab form, and then choose (or create) a communications template using the " "drop-down menu under the :guilabel:`Template` column." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:90 msgid "" "Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how " "often the communication should be sent; use these time fields to specify the" " frequency of :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or " ":guilabel:`Months` communications should be sent. There is also the option " "to send communications `Immediately` after a specified :guilabel:`Trigger` " "is activated." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:96 msgid "" "In the last column, determine the :guilabel:`Trigger` which controls how and" " when the communication is sent. For this action, choose between: " ":guilabel:`Before the event`, :guilabel:`After each registration`, or " ":guilabel:`After the event`." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rstNone msgid "View of the communication tab in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:105 msgid "Attach a questionnaire to event registrations" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:107 msgid "" "Implementing a questionnaire during event sign up is an effective way to " "gauge the wants, needs, and interests of the event's attendees ahead of " "time. Questionnaires also act as informative analytics tools for reporting " "periods before (or after) events take place." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:111 msgid "" "To create a questionnaire, from the :guilabel:`Events` application, navigate" " to :menuselection:`Configuration --> Settings` and then enable the " ":guilabel:`Questions` setting." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:114 msgid "" "With the setting enabled, questions and answers can now be added (and " "recorded) under the the :guilabel:`Questions` tab back on the event form. " "For each question, specify if it should only be asked once with the " ":guilabel:`Ask once per order` checkbox, or if the question requires a " ":guilabel:`Mandatory Answer`, which will make the question required for " "registration." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:120 msgid "" "If the :guilabel:`Once per order` checkbox is enabled, then a single " "registration for 3 event attendees will show the questionnaire only once." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:123 msgid "" "There are two :guilabel:`Question Types` to choose from: " ":guilabel:`Selection` and :guilabel:`Text Input`. The :guilabel:`Selection` " "type, allows attendees to select an answer from pre-configured options, " "which are entered in the :guilabel:`Answers` tab below. The :guilabel:`Text " "Input` type allows attendees to write in their own answer to the question in" " a text box." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rstNone msgid "View of an event form, open the questions tab, and add a question." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:133 msgid "Log internal notes or add ticket instructions" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:135 msgid "" "In the :guilabel:`Notes` tab, there is the option to add a :guilabel:`Note` " "and/or :guilabel:`Ticket instructions`." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:138 msgid "" "Under :guilabel:`Note`, internal notes can be left (such as: to-do lists, " "contact information, etc.) for event staff to reference. In the " ":guilabel:`Ticket instructions` field, helpful information for staff and " "attendees can be shared (like, directions to the venue, opening/closing " "times, etc.)" 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." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rstNone msgid "View of the Notes tab in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:153 msgid "Invite attendees to the event" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:155 msgid "" "To invite people to an event, click the :guilabel:`Invite` button located in" " the top left corner of the event form." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:158 msgid "" "Inside the invite template form, are options to sent email or SMS invites. " "Each message can be fully customized, and recipients can be added." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:161 msgid "" "Adding a :guilabel:`Subject` line for the invite message is required, but " "the :guilabel:`Preview Text` field is optional. The :guilabel:`Preview Text`" " is a catchy preview sentence meant to encourage recipients to open the " "email." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:166 msgid "" "In most cases, the :guilabel:`Preview Text` is displayed next to the " "subject. Keep this field empty to ensure the first characters of the email " "content appear, instead." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:170 msgid "Select invitees and configure recipient filters" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:172 msgid "" "In the middle of the invitation form, find and click the " ":guilabel:`Recipients` field, to reveal a drop-down menu of recipient " "options. These choices represent where Odoo will find the desired " "recipients' information." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:176 msgid "" "Once an option from this menu is selected (e.g. :guilabel:`Applicant`, " ":guilabel:`Contact`, :guilabel:`Event Registration`, " ":guilabel:`Lead/Opportunity`, etc.), Odoo will send the invitation to all " "recipients who match that initial rule. Additional rules can be added to " "narrow down the target recipients, by clicking :guilabel:`Add Filter`." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rstNone msgid "" "View of the add filter button beneath the recipients field in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:185 msgid "" "Clicking :guilabel:`Add Filter` reveals three fields, formatted like an " "equation. To reveal the sub-menu options, click each field, and make the " "desired selections, until the preferred configuration has been acheived. The" " number of :guilabel:`Records` that match the rule(s) are indicated to the " "right of the :guilabel:`Recipients` field, in green." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:191 msgid "" "Some sub-menu options in the first rule field allow for a second choice to " "provide even more specificity." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:194 msgid "" "To the right of each rule, are :guilabel:`x`, :guilabel:`+`, and " ":guilabel:`...` icons. The :guilabel:`x` icon deletes a specific node (line)" " of the rule. The :guilabel:`+` icon adds a node (line) to the rule. And, " "the :guilabel:`...` icon adds a branch to the node. A branch means two " "additional, indented sub-nodes are added to the rule, providing even more " "specificity to the line above it." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:201 msgid "Build a custom event invite" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:203 msgid "" "In the :guilabel:`Mail Body` tab, there are a number of pre-configured " "message templates to choose from. Select the desired template, and modify " "every element of its design details with Odoo's drag-and-drop web builder, " "located on the right sidebar." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rstNone msgid "" "View of the drag and drop building blocks used to customize event invite " "emails." 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." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:218 msgid "" "The :guilabel:`Mail Body` tab (and template options), are only available if " "the event invite :guilabel:`Mailing Type` is designated as an " ":guilabel:`Email`. If :guilabel:`SMS` is the :guilabel:`Mailing Type`, a " ":guilabel:`SMS Content` tab (consisting of a blank text space), is " "available, instead." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:224 msgid "Modify event invite settings" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:226 msgid "" "The options under the :guilabel:`Settings` tab are different, depending on " "the specified :guilabel:`Mailing Type`." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:229 msgid "" "If the :guilabel:`Email` option is selected as the :guilabel:`Mailing Type`," " an employee can be designated as the :guilabel:`Responsible`, meaning that " "person is the one responsible for this particular invite message. " ":guilabel:`Send From` and :guilabel:`Reply To` email aliases can be " "designated here, as well." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:234 msgid "" "Also, if any specific documents are required (or helpful) for this event " "invite, they can be sent along with this email, by clicking " ":guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:238 msgid "" "If the :guilabel:`SMS` option is selected as the :guilabel:`Mailing Type`, a" " :guilabel:`Responsible` can be designated, and the option to " ":guilabel:`Include an opt-out link` is available." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:242 msgid "Send event invitations to recipients" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:244 msgid "" "If the selected :guilabel:`Mailing Type` is :guilabel:`Email`, there are " "three options to send the invite: :guilabel:`Send`, :guilabel:`Schedule`, " "and :guilabel:`Test`." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:247 msgid "" "The :guilabel:`Send` option sends the invite right away. The " ":guilabel:`Schedule` option reveals a pop-up, in which a scheduled date/time" " can be selected for the email to be sent. The :guilabel:`Test` option " "reveals a :guilabel:`Test Mailing` pop-up, where specific recipient email " "addresses can be entered for Odoo to send them the current version of the " "mailing for review before officially sending it out to prospective event " "attendees." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:253 msgid "" "If the selected :guilabel:`Mailing Type` is :guilabel:`SMS`, there are four " "options to send the invite: :guilabel:`Put in Queue`, :guilabel:`Send Now`, " ":guilabel:`Schedule`, and :guilabel:`Test`." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:256 msgid "" "The :guilabel:`Put in Queue` option schedules an SMS message to all " "recipients (that match the designated rules, if any) in the near future. " "Clicking :guilabel:`Put in Queue` reveals a pop-up, requiring confirmation. " "When confirmed, a blue banner appears on the event invite template form, " "indicating that the SMS will be sent later that day." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:262 msgid "" "The :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test` options" " all function the same way for both :guilabel:`Mailing Type` options." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:266 msgid "Publish events" msgstr "" #: ../../content/applications/marketing/events/event_essentials.rst:268 msgid "" "Until an event is published, it will remain hidden from public view on the " "website and registering for it will not be possible. To publish an event, " "navigate to it either from the 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." 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." 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." msgstr "" #: ../../content/applications/marketing/events/event_essentials.rstNone msgid "" "View of a website page and the option to publish the event in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:3 msgid "Sell tickets" msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:5 msgid "" "Create custom ticket tiers (with various price points) for potential " "attendees to choose from, directly on the event template form, under the " ":guilabel:`Tickets` tab. Odoo simplifies the ticket-purchasing process by " "providing plenty of payment method options." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:10 #: ../../content/applications/marketing/events/track_manage_talks.rst:9 msgid "Configuration" msgstr "Configuratie" #: ../../content/applications/marketing/events/sell_tickets.rst:12 msgid "" "First, in order to enable the creation (and selling of) event tickets, go to" " :menuselection:`Configuration --> Settings`, then enable the " ":guilabel:`Tickets` and :guilabel:`Online Ticketing` features." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:16 msgid "" "The :guilabel:`Tickets` feature allows tickets to be sold for an event." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:18 msgid "" "The :guilabel:`Online Tickets` feature allows for the sale of tickets to " "occur through the website." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:21 msgid "" "If these options are *not* enabled, a default :guilabel:`Register` button " "will be available for free registrations." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rstNone msgid "View of the settings page for Odoo Events." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:29 msgid "Sell tickets through sales orders" msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:31 msgid "" "In the :guilabel:`Sales` application, choose a previously-created Event " "Registration (as if it were a product), and add it as a product line. Upon " "adding the registration, a pop-up appears, which allows for the selection of" " a specific event (and ticket tier). That specific event ticket is then " "attached to the sales order." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rstNone msgid "" "View of a sales order and option to choose the specific event in Odoo " "Events." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:40 msgid "" "Events with tickets sold online or through sales orders have a " ":guilabel:`Sales Smart Button` shortcut, located at the top of the event " "template form (in the :guilabel:`Events` application)." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:43 msgid "" "Clicking the :guilabel:`Sales Smart Button` reveals a page with all the " "sales orders related to that event." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rstNone msgid "View of an event's form and the sales smart button in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rstNone msgid "" "View of an event form highlighting the column product under the tickets tab in Odoo\n" "Events." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:56 msgid "Sell tickets through the website" msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:58 msgid "" "With tickets purchased through the website, the process is similar to " "creating a :guilabel:`Sales Order` with a specific :guilabel:`Registration` " "product. Here, tickets are added to a virtual cart, and the transaction can " "be completed as usual - utilizing any of the pre-configured payment methods " "options that have been set up on the website." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:63 msgid "" "The completed purchase is automatically produced in a :guilabel:`Sales " "Order`, which can be easily accessed in the back end of the database." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rstNone msgid "View of website transaction for Odoo Events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:3 msgid "Track and manage talks" msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:5 msgid "" "With Odoo Events, it's possible to provide attendees with the power to " "propose presenters to speak at events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:11 msgid "" "First, go to :menuselection:`Events --> Configuration --> Settings` and " "enable :guilabel:`Schedule & Tracks`." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:14 msgid "" "When that feature is enabled, two more options become available: *Live " "Broadcast* and *Event Gamification*." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:17 msgid "" ":guilabel:`Live Broadcast` allows for the airing of tracks online through a " "YouTube integration." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:19 msgid "" ":guilabel:`Event Gamification` allows for the sharing of a quiz with your " "attendees, once a track (talk) is over." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:23 msgid "" ":guilabel:`Event Gamification` isn't necessary for tracks to appear on the " "event page on the website, but it can enhance the engagement and overall " "enjoyablity of the event for attendees." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:27 msgid "Talks, talk proposals, and agenda" msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:29 msgid "" "Once those two features are enabled, the following links are automatically " "added to the sub-header menu, located on the event page on the website: " ":guilabel:`Talks`, :guilabel:`Talk Proposals`, and :guilabel:`Agenda`. Any " "attendee can freely access these menu items and their corresponding content." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:33 msgid "" "The :guilabel:`Talks` link takes the attendee to a page full of all the " "talks for that event." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:35 msgid "" "The :guilabel:`Talks Proposals` link takes the attendee to a form page, " "where they can propose talks for the event." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:38 msgid "" "The :guilabel:`Agenda` link takes the attendee to a page with all the talks " "for the event, but in a calendar/time-slot format." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rstNone msgid "" "View of the published website and the talks, talk proposals, and agenda in " "Odoo Events" msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:46 msgid "Manage talk proposals" msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:48 msgid "" "When attendees fill out and submit a talk proposal form on the website, a " "new :guilabel:`Proposal` is instantly created in the back end for the event." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:52 msgid "" "All talks (Proposals, Confirmed, Announced, etc.) are accessible via the " ":guilabel:`Tracks` smart button on the event form." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rstNone msgid "" "View of the talks' proposals page emphasizing the column proposal in Odoo " "Events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:59 msgid "" "If a proposal is accepted, move the :guilabel:`Event Track` to the " "appropriate stage in the Kanban view (e.g. `Confirmed`, etc.). Then, go to " "that particular event's template form, and click the :guilabel:`Go to " "Website` smart button to reach that specific talk's page on the website." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:63 msgid "" "In the upper right corner, toggle the switch from :guilabel:`Unpublished` to" " :guilabel:`Published`, and the talk is instantly accessible on the website." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:67 msgid "Without publishing a talk, attendees will never be able to access it." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rstNone msgid "View of the website page to publish a proposed talk for Odoo Events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:74 msgid "Attendees list and attendance" msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:76 msgid "" "Once attendees have registered for a specific event, they are added to the " ":guilabel:`Attendee List` for that event, which is accessible via the " ":guilabel:`Attendees` smart button on the event template form, or " ":menuselection:`Reporting --> Attendees` and sorted by event." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:81 msgid "" "When an attendee arrives at the event, they will be marked as attending " "(:guilabel:`Confirmed Attendance`), and the status of that attendee will " "change to :guilabel:`Attended.`" msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rstNone msgid "Overview of events with the kanban view in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:88 msgid "" "When analyzing an :guilabel:`Attendees list`, Odoo provides different ways " "to view the information. Each view option presents the same information, but" " in a slightly different layout. To change the view, click on the icons in " "the upper right hand of the screen." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rstNone msgid "Various view options on the attendees list page." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:96 msgid "" "In the :guilabel:`Kanban` view, it can be confirmed whether the attendees " "have already paid or remain unpaid." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:99 msgid "" "The :guilabel:`List` view provides information in a more traditional list " "formation." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:101 msgid "" "The :guilabel:`Calendar` view provides a clear schedule visualization of " "which attendees are arriving on specific dates of the event." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:104 msgid "" "The :guilabel:`Graph` view provides graphical representations of that " "event's attendees, along with numerous filters and customizable measures for" " deeper analysis." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:107 msgid "" "The :guilabel:`Cohort` view lays out attendee data to better analyze the " "number of registration dates." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:111 msgid "" "Tickets sold through sales orders validate attendees as soon as the " "quotation is confirmed." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:114 msgid "Manage registrations" msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:116 msgid "" "Upon selecting an attendee, Odoo reveals that specific attendee's detail " "form." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:118 msgid "" "From here, event badges can be sent manually, by selecting :guilabel:`Send " "By Email`. The :guilabel:`Attendee` can also be marked as " ":guilabel:`Attended`, or the registration can be canceled altogether via the" " :guilabel:`Cancel Registration` button." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rstNone msgid "" "View of an attendee form emphasizing the send by email and cancel registration in Odoo\n" "Events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:128 msgid "Lead Generation Rules" msgstr "Leadgeneratieregels" #: ../../content/applications/marketing/events/track_manage_talks.rst:130 msgid "With Odoo, leads can be generated from events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:132 msgid "" "To create and configure a :guilabel:`Lead Generation Rule` related to " "events, navigate to :menuselection:`Events app --> Configuration --> Lead " "Generation`." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:135 msgid "" "On the :guilabel:`Lead Generation Rule` page, every configured " ":guilabel:`Lead Generation Rule` can be found, along with pertinent data " "related to those rules." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rstNone msgid "How the Lead Generation Rule page looks in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:142 msgid "" "To create a new :guilabel:`Lead Generation Rule`, click :guilabel:`Create`, " "and fill out the :guilabel:`Lead Generation Rule` form." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rstNone msgid "How the Lead Generation Rule template looks in Odoo Events." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:149 msgid "" "After naming the rule, configure *how* the lead should be created (either " ":guilabel:`Per Attendee` or :guilabel:`Per Order`), and *when* they should " "be created, (when :guilabel:`Attendees are created`, when " ":guilabel:`Attendees are confirmed`, or when :guilabel:`Attendees attended` " "the event)." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:154 msgid "" "In the :guilabel:`For any of these Events` section, there are fields to " "attach this rule to any specific event categories, company, and/or event. To" " add even more specificity to the rule, a domain filter rule can be " "configured to ensure the rule only applies to a specific target audience of " "attendees (found in the :guilabel:`If the Attendees meet these Conditions` " "section)." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:159 msgid "" "Lastly, in the :guilabel:`Lead Default Values` section, designate a " ":guilabel:`Lead Type`, then assign it to a specific :guilabel:`Sales Team` " "(and/or :guilabel:`Salesperson`), and attach tags to the rule, if necessary." msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:8 #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:3 msgid "Marketing Automation" msgstr "Marketing" #: ../../content/applications/marketing/marketing_automation.rst:11 #: ../../content/applications/marketing/sms_marketing.rst:11 msgid "" "`Odoo Tutorials: Marketing `_" msgstr "" "`Odoo Tutorials: Marketing `_" #: ../../content/applications/marketing/marketing_automation/advanced.rst:5 msgid "Advanced" msgstr "Geavanceerd" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3 msgid "Understanding metrics" msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:5 msgid "" "Metrics are detailed statistics that measure the progress (and success) of " "marketing campaigns. When creating marketing activities in a workflow, Odoo " "will visually display various metrics related to the campaign with graphs " "and data." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:9 msgid "Consider the following example:" msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone msgid "An example of a marketing automation campaign in Odoo." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:15 msgid "" "In this case, the :guilabel:`Target` of this campaign is set to " ":guilabel:`Lead/Opportunity` and was narrowed down to only focus on the " "Leads (or Opportunities) whose :guilabel:`Tag Name` contain a value of " "`product` and they *also* have an email address set up in the database." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:19 msgid "" "Beneath the filter nodes, Odoo will display how many records in the database" " fall into the previously-specified criteria filter. In this example, there " "are 18 records in the database that match the criteria." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone msgid "" "Lead generation filters used to refine records on marketing automation " "campaigns in Odoo." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:27 msgid "" "At the top of the marketing automation form, there are a series of smart " "buttons. The :guilabel:`Participations` smart button in this example " "indicates that, out of those 18 records, 25 have become participants. In " "other words, they have matched the criteria, and have already interacted " "with the campaign in one way or another." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:33 msgid "" ":guilabel:`Records` represent a real-time number. Therefore, while the " "workflow is running, changes in opportunity records (deletions, additions, " "adjustments) may occur. This means there will be real-time updates to the " "number of :guilabel:`Records`, but such updates do *not* change the number " "of :guilabel:`Participants`, as the metric *will not* exclude opportunities " "that have already been set as :guilabel:`Participants` before - Odoo will " "just add new ones. That's why the number of :guilabel:`Records` can be " "different from the number of :guilabel:`Participants` from time to time." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone msgid "" "Difference between real-time record count and total participants on a " "markeing campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:45 msgid "" "Whenever the system runs, updating numbers and triggering actions, it will " "look at the :guilabel:`Target` model, and check if new :guilabel:`Records` " "have been added (or modified), which always keeps the flow up-to-date." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:50 msgid "" "The filter here is applied to *all* activities. Leads that lose that " "specific :guilabel:`Tag` in the meantime will be excluded from later " "activities." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:54 msgid "" "Filters can also be applied to individual activities, in the " ":guilabel:`Domain` section of the activity pop-up form. Use this feature to " "specify an individual filter that will only be performed if the records " "satisfy *both* filter criteria - the activity filter and its specific domain" " filter." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:59 msgid "" "(*Example*: when configuring an SMS activity, make sure a certain phone " "number is set, in order to avoid triggering a SMS that would never be sent.)" msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 msgid "" "A relevant targeting filter that applies to a type of individual activity." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:66 msgid "" ":guilabel:`Success` represents the number of times the searching for " "participants - who match the criteria filter(s) of that activity - was " "performed successfully, in relation to the total number of participants. If " "a participant does *not* match the conditions, it will be added to " ":guilabel:`Rejected`." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone msgid "" "Overview showing participants who do or do not match filtering criteria on " "an activity." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:75 msgid "" "Hovering over the graph, Odoo displays the number of successful and rejected" " participants, per day, over the last 15 days." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:79 msgid "" "Whenever a new record is added to the :guilabel:`Target` model, it will " "automatically be added to the workflow, and it will start the workflow from " "the beginning (:guilabel:`Parent Action`)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started.rst:5 msgid "Getting Started" msgstr "Aan de slag" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:5 msgid "" "The Odoo Marketing Automation app automates a variety of marketing tasks by " "combining specific rules and filters to generate timed actions. Instead of " "manually having to build each stage of a campaign (such as a series of timed" " massmails), the Marketing Automation app allows marketers to build the " "entire campaign, and all of its stages, in one place on one dashboard." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:11 msgid "Create a campaign" msgstr "Maak een campagne" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:13 msgid "" "To create a new automated marketing campaign, open the :guilabel:`Marketing " "Automation` app and click :guilabel:`Create`. On the :guilabel:`Campaign` " "page, there are the following smart buttons and fields:" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rstNone msgid "" "A dashboard showing the creation of a new marketing automation campaign in " "Odoo." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:21 msgid "" ":guilabel:`Templates`: represents the number of pre-configured mail " "templates being used in this particular campaign. (Templates can always be " "created on-the-fly as well)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:23 msgid "" ":guilabel:`SMS`: represents the number of personalized SMS messages " "connected to this campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:24 msgid "" ":guilabel:`Clicks`: represents the number of times attached links have been " "clicked by recipients of this campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:26 msgid "" ":guilabel:`Participants`: represents the number of contacts that have " "directly participated in this campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:28 msgid "" ":guilabel:`Target`: this field is a drop-down menu to choose which model is " "targeted by this campaign (i.e., by Contacts, Sales Order, Lead/Opportunity," " etc.)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:32 msgid "Campaign filters" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:34 msgid "" "To add a filter to the target audience, click :guilabel:`Add Filter`, and a " "node field will appear. In the node field, a custom equation can be " "configured for Odoo to use when filtering who to include (and exclude) in " "this specific marketing campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rstNone msgid "A filter node in Odoo Marketing Automation." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:42 msgid "" "When the first field of the node is clicked, a nested drop-down menu of " "options appears on the screen where specific criteria is chosen based on " "needs of the campaign. The remaining fields on the node further define the " "criteria which determines which records to include (or exclude) in the " "execution of the campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:47 msgid "" "To add another node, simply click the :guilabel:`+ (plus sign)` icon to the " "right of the filtering rule. To add a branch of multiple nodes at the same " "time, click the :guilabel:`... (ellipses)` icon." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:51 msgid "" "For further information on filters, refer to :doc:`this documentation page " "`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:54 msgid "" ":guilabel:`Records` represent the number of contacts in the system that fit " "the specified criteria for a campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:58 msgid ":doc:`testing_running`" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:59 msgid ":doc:`workflow_activities`" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:3 msgid "Target an audience" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:5 msgid "" "Delivering marketing campaigns to the *right* audience is paramount when " "trying to grow a business. The :guilabel:`Odoo Marketing Automation` " "application helps marketers to do just that by providing filtering tools, " "that can be as simple or as complex as necessary, to reach the right " "customers at the right time." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:11 msgid "Work with target filters" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:13 msgid "" "When configuring the filters on a marketing campaign, there are some options" " that have an arrow icon beside them. The arrow signifies that the filter " "has more refined parameters within it." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rstNone #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rstNone msgid "The drop-down filter menu in the Marketing Automation application." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:20 msgid "" "Filters can be extended by adding *branches* and *nodes*. A *node* adds " "another filtering parameter to a group of targeting conditions (e.g. a new " "line), and a *branch* creates a narrowly refined cluster of parameters, " "allowing filters to be grouped with *Any* or *All* statements." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:24 msgid "Every time a new branch is created, there are two options:" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:26 msgid "" "Either the records can match :guilabel:`ALL` criteria for the upcoming rules" " (an AND statement where all criteria must match)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:29 msgid "" "Or, the records can match :guilabel:`ANY` criteria for the upcoming rules " "(an OR statement where only one of the criteria must match)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:32 msgid "" "To change between these two options, simply click the drop-down arrow icon " "in the green box and select :guilabel:`Any` or :guilabel:`All`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:35 msgid "" "To add a node, click on the :guilabel:`+ (plus sign icon)` and to add " "another branch click on the :guilabel:`... (ellipses icon)`. To exclude a " ":guilabel:`node` (or a :guilabel:`branch`), click on :guilabel:`x (delete)`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:44 msgid "Use cases" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:46 msgid "" "The following scenarios below outline different combinations of filters a " "marketing campaign might commonly use." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:50 msgid "" "Scenario #1: Narrow the target down to new opportunities in the pipeline" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:52 msgid "" "While in Edit mode on a campaign template form, select the " ":guilabel:`Target` field, and click :guilabel:`Search More` from the drop-" "down menu. Then, search for :guilabel:`Lead/Opportunity` and select it." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:56 msgid "" "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on" " the default :guilabel:`ID` filter option in the first portion of the filter" " equation. Doing so reveals a drop-down menu full of filter options. From " "this drop-down, scroll down (or search for) :guilabel:`Type`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:61 msgid "" "Keep the second portion of the filter equation on the default :guilabel:`= " "(equal sign)`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:63 msgid "" "Then, change the third (and final) portion of the filter equation from " ":guilabel:`Lead` to :guilabel:`Opportunity`. The number of " ":guilabel:`Records` that fit this specific filter equation will change as " "the equation is customized." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:67 #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:103 msgid "" "Add another node to this filter by clicking the :guilabel:`+ (plus sign)` to" " the right of the equation." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:70 msgid "" "With \"new\" opportunities being the target of this filter, the second node " "will focus on only locating opportunities that are in the :guilabel:`New` " "stage of the pipeline. To do that, select the default :guilabel:`ID` from " "the first portion of the second filter equation, and scroll down (or search " "for) :guilabel:`Stage` from the field drop-down menu." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:75 msgid "" "Once again, leave the second portion of the filter equation on :guilabel:`= " "(equal sign)`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:77 msgid "" "Lastly, highlight the default value in the third (and final) portion of the " "second filter equation and type in :guilabel:`New`. With that completed, " "Odoo will only target opportunities that are in the \"New\" stage of the " "pipeline." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rstNone msgid "" "A standard scenario using filters in the Odoo Marketing Automation app." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:86 msgid "" "Scenario #2: Narrow the target down to the event attendees that purchased a " "specific ticket" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:88 msgid "" "While in Edit mode on a campaign template form, select the " ":guilabel:`Target` field, and click :guilabel:`Search More` from the drop-" "down menu. Then, scroll down (or search for) :guilabel:`Event` and select " "it." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:92 msgid "" "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on" " the default :guilabel:`ID` filter option in the first portion of the filter" " equation. Doing so reveals a drop-down menu full of filter options. From " "this drop-down, scroll down (or search for) :guilabel:`Event`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:97 msgid "" "Click the the default :guilabel:`= (equal sign)` in the second portion of " "the filter equation. This reveals a drop-down menu. On this menu, select " ":guilabel:`contains`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:100 msgid "" "In the third (and final) empty portion of the filter equation, type in the " "name of the event(s) that you would like Odoo to consider for this campaign " "filter." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:106 msgid "" "The second node will focus on targeting this campaign to attendees who " "purchase a specific type of ticket to the aforementioned event(s) in the " "first filter equation. To do that, select the default :guilabel:`ID` from " "the first portion of the second filter equation, and scroll down (or search " "for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that " "same drop-down menu, select :guilabel:`Name`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:112 msgid "" "Once again, click the the default :guilabel:`= (equal sign)` in the second " "portion of the filter equation, and select :guilabel:`contains`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:115 msgid "" "Lastly, in the third (and final) portion of the second filter equation, " "which will be blank, type in the name of the ticket type that should be used" " for the filter. In this case, :guilabel:`Standard` is the name of the event" " ticket type for this sample filter." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rstNone msgid "An event ticket filter in the Odoo Marketing Automation application." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:3 msgid "Testing and running a campaign" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5 msgid "" "Odoo gives users the ability to test marketing campaigns (and mailings) " "before officially running them." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:8 msgid "" "First, open the :guilabel:`Marketing Automation` application and click on a " "campaign. Make sure the campaign already has activities configured on it (or" " build a campaign by following the directions here on :doc:`this " "documentation `). To start a test, click the " ":guilabel:`Launch a Test` button at the top of the template form." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rstNone msgid "Launch a test button in Odoo Marketing Automation." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:17 msgid "" "When clicked, a pop-up window appears. In the dropdown field choose a " "specific record to run the test on, or create a brand new record by clicking" " the :guilabel:`Search More...` link at the bottom of the dropdown menu, and" " then click the :guilabel:`Create` button." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21 msgid "" "Once the record is selected, click :guilabel:`Continue`, and Odoo will " "redirect to the campaign test page." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rstNone msgid "Test screen in Odoo Marketing Automation." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:28 msgid "" "Here, the name of the :guilabel:`Record` being tested is visible, along with" " the precise time this test workflow was started. Beneath that is the first " "activity (or activities) in the workflow." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31 msgid "" "To start a test, click the :guilabel:`Run` icon beside the first activity in" " the workflow. When clicked, the page will reload, and Odoo will show the " "various results (and analytics) connected to that specific activity." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rstNone msgid "Workflow test progress in Odoo Marketing Automation." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:39 msgid "" "Once all the workflow activities are completed, the test will end and be " "moved to the :guilabel:`Completed` stage. To stop a test before all the " "workflow activities are completed, click the :guilabel:`Stop` button." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3 msgid "Marketing activities" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5 msgid "" "When creating a campaign in the :guilabel:`Marketing Automation` app, users " "can plan marketing activities such as email or SMS campaigns. To get " "started, navigate to the :guilabel:`Workflow` area, and click :guilabel:`Add" " New Activity`. A blank activity template will appear where parameters can " "be set for that specific activity." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:10 msgid "" "When :guilabel:`Add New Activity` is selected, a blank activity template " "will appear with the following customizable fields:" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rstNone msgid "An activity template in Odoo Marketing Automation." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:17 msgid ":guilabel:`Activity Name`: the title of the activity." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:18 msgid "" ":guilabel:`Activity Type`: choose between Email, Server Action (internal " "Odoo operation), or SMS." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:19 msgid "" ":guilabel:`Mail Template`: choose from pre-configured templates (or create a" " new one on-the-fly)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20 msgid ":guilabel:`Trigger`: choose when this activity should be triggered." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21 msgid "" ":guilabel:`Expiry Duration`: configure to stop the actions after a specific " "amount of time (after the scheduled date). When selected, a " ":guilabel:`Cancel after` field appears, in which the user can choose how " "many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to " "cease after the initial date." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25 msgid "" ":guilabel:`Activity Filter`: domain related to this activity (and all " "subsequent Child Activities)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:27 msgid "" ":guilabel:`Applied Filter`: activity will *only* be performed if it " "satisfies the specified domain (filter)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:30 msgid "" "After the activity's settings are fully configured, click :guilabel:`Save & " "Close` to finish creating the activity." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:34 msgid "Workflow activity" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:36 msgid "" "Once saved, the :guilabel:`Workflow Activity` will appear in Odoo, where " "each activity will be shown as a graph by default. The configured trigger " "time for that activity can be found to the left of the :guilabel:`Workflow " "Activity` card." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40 msgid "" "In the :guilabel:`Workflow Activity` section, there is also the number of " "activities that are successful or rejected. The :guilabel:`Success` and " ":guilabel:`Rejected` numbers are color-coded in the graph for easy reference" " (in green and red, respectively)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rstNone msgid "Typical workflow activity in Odoo Marketing Automation." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:49 msgid "" "If the :guilabel:`Activity Type` of the activity is set to " ":guilabel:`Email`, there are more in-depth analytics beneath the " ":guilabel:`Workflow Activity` data detailing how many emails have been " ":guilabel:`Sent`, and what percentage of those have been " ":guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:55 msgid "Child activities" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:57 msgid "" "Odoo also has the option to :guilabel:`Add Child Activity`. *Child " "Activities* are sub-activities that are connected to (and triggered by) the " "activity above it, which is also known as its *Parent Activity*." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:61 msgid "" "Odoo provides a number of triggering options to launch a :guilabel:`Child " "Activity` - all of which depend on the trigger configurations related to the" " parent activity. Under the desired parent activity, hover over " ":guilabel:`Add child activity`, and select the trigger:" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:65 msgid ":guilabel:`Add Another Activity`: instantly add another activity." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:66 msgid "" ":guilabel:`Opened`: the next activity will be triggered if the (email) " "recipient opens the mailing." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:68 msgid "" ":guilabel:`Not Opened`: the next activity will be triggered if the recipient" " does not open the mailing." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:70 msgid "" ":guilabel:`Replied`: the next activity will be triggered if the recipient " "replies to the mailing." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:71 msgid "" ":guilabel:`Not Replied`: the next activity will be triggered if the " "recipient does not reply to the mailing." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:73 msgid "" ":guilabel:`Clicked`: the next activity will be triggered if the recipient " "clicks on a link included in the mailing." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75 msgid "" ":guilabel:`Not Clicked`: the next activity will be triggered if the " "recipient does not click on a link included in the mailing." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:77 msgid "" ":guilabel:`Bounced`: the next activity will be triggered if the mailing is " "bounced (not sent)." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:79 msgid "" "Once a trigger is selected, the user can configure the child activity (it " "has the same configuration options as a regular activity) and click " ":guilabel:`Save & Close`` to finish creating the child activity." msgstr "" #: ../../content/applications/marketing/sms_marketing.rst:8 msgid "SMS Marketing" msgstr "SMS marketing" #: ../../content/applications/marketing/sms_marketing/pricing.rst:5 msgid "Pricing and FAQ" msgstr "Prijzen en FAQ" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:5 msgid "SMS Pricing and FAQ" msgstr "SMS Prijzen en FAQ" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:8 msgid "What do I need to send SMSs?" msgstr "Wat heb ik nodig om te sms'en?" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:10 msgid "" "SMS Text Messaging is an In-App Purchase (IAP) service that *requires " "prepaid credits* to work." msgstr "" "SMS-tekstberichten zijn een in-app-aankoopservice (IAP) waarvoor *prepaid " "tegoeden* vereist zijn om te werken." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:13 msgid "How many types of SMSs are there?" msgstr "Hoeveel soorten sms'en zijn er?" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:15 msgid "There are 2 types: GSM7 and UNICODE." msgstr "Er zijn 2 types: GSM7 en UNICODE." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:17 msgid "" "**GSM7** is the standard format, with a limit of 160 characters per message," " that includes the following characters:" msgstr "" "**GSM7** is het standaardformaat, met een limiet van 160 tekens per bericht," " dat de volgende tekens bevat:" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone msgid "GSM7 characters available in Odoo SMS Marketing." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:24 msgid "" "**UNICODE** is the format applied if a special character, that *is not* in " "the GSM7 list, is used. Limit per SMS: 70 characters." msgstr "" "**UNICODE** is het formaat dat wordt toegepast als een speciaal teken, dat " "*niet* in de GSM7-lijst staat, wordt gebruikt. Limiet per sms: 70 tekens." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:28 msgid "" "For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above" " these limits, the content is divided into a multi-part message* and the " "limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. Then, " "in real-time, the system displays the number of SMS mailings the message " "represents." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34 msgid "How much does it cost to send an SMS?" msgstr "Hoeveel kost het om een ​​sms te versturen?" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36 msgid "" "The price of an SMS depends on the destination and the length (number of " "characters) of the message. To see the **price per country, please " "consult**: `Odoo SMS - FAQ `_." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:40 msgid "" "The number of SMSs a message represents will always be available in the " "database." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone msgid "" "Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:47 msgid "How to buy credits" msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49 msgid "Go to :menuselection:`Settings --> Buy Credits`." msgstr "Ga naar :menuselection:`Instellingen --> Koop Krediet`." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone msgid "Buying credits for SMS Marketing in Odoo settings." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:55 msgid "Or go to :menuselection:`Settings --> View my Services`." msgstr "Of ga naar : menuselectie: `Instellingen --> Bekijk mijn diensten`." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:62 msgid "" "If Odoo Online (Saas) is being used, along with the Enterprise version, free" " trial credits are available to test the feature." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:66 msgid "More common questions" msgstr "Meer veelgestelde vragen" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Is there an expiration time for my credits?**" msgstr "**Kunnen mijn tegoeden vervallen?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "No, credits do not expire." msgstr "Nee, tegoeden verlopen niet." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**Can I send an SMS to a phone number (which is not a mobile phone) because " "I see the icon in front of the field “phone”?**" msgstr "" "**Kan ik een sms sturen naar een telefoonnummer (dat geen mobiele telefoon " "is) omdat ik het pictogram voor het veld \"telefoon\" zie?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "Only if that phone number supports SMS (e.g. SIP phones)." msgstr "Alleen als dat telefoonnummer sms ondersteunt (bijv. SIP-telefoons)." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Do I receive an invoice to buy my credits?**" msgstr "**Ontvang ik een factuur als ik kredieten koop?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "Yes." msgstr "Ja." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Can the recipient answer me?**" msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "No, it is not possible to reply to the SMS." msgstr "Nee, het is niet mogelijk om de sms te beantwoorden." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**What happens if I send multiple SMSs at once, but I don't have enough " "credits to send them all?**" msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "Multiple SMS communications at once at are counted as a single transaction, " "so no SMSs will be sent until there are enough credits to send them all." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Do I have a history of the sent SMSs?**" msgstr "**Heb ik een overzicht van de verzonden sms'jes?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "A history of sent SMSs, along with all pertinent information related to its " "sent contacts (and the message itself), can be found in the :guilabel:`Sent`" " column of the main :guilabel:`SMS Marketing` dashboard (while in " ":guilabel:`Kanban` view)." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:91 msgid "" "For more detailed information, select a desired SMS from the main dashboard " "(in :guilabel:`Kanban` view), and click on either link in the blue banner " "above the SMS detail form to learn more." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Can I send as many SMSs I want at once?**" msgstr "**Kan ik zoveel sms'jes tegelijk verzenden als ik wil?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "Yes, if you have enough credits." msgstr "Ja, indien voldoende krediet." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**If an SMS is sent to a number that doesn't exist in the list of " "recipients, will credits be lost?**" msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "No, not if the phone number is incorrectly formatted (e.g. too many digits)." " However, if the SMS is sent to the wrong person (or to a fake number), the " "credit for that SMS will be lost." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**What happens if I send my SMS to a paying number (e.g.: a contest to win a" " ticket for a festival)?**" msgstr "" "**Wat gebeurt er als ik mijn sms naar een betalend nummer stuur " "(bijvoorbeeld: een wedstrijd om een ticket voor een festival te winnen)?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "The SMS will not be delivered to that kind of number, so no charges will be " "made." msgstr "" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**Can I identify the numbers that do not exist when I send several SMSs?**" msgstr "" "**Kan ik de niet-bestaande nummers identificeren als ik meerdere sms'jes " "stuur?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "Only the ones that have an invalid format." msgstr "Alleen degenen die een ongeldig formaat hebben." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**How does the GDPR regulation affect this service?**" msgstr "**Wat voor invloed heeft de AVG-regelgeving op deze service?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "Please find our `Privacy Policy here `__." msgstr "" "Hier vind je ons `Privacybeleid `__." #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Can I use my own SMS provider?**" msgstr "**Kan ik mijn eigen sms-provider gebruiken?**" #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "Yes, but it is not possible out-of-the-box. Odoo experts can help customize " "a database to allow for the use of a personal SMS provider. Please check our" " success packs `here `_." msgstr "" #: ../../content/applications/marketing/surveys.rst:8 msgid "Surveys" msgstr "Enquêtes" #: ../../content/applications/marketing/surveys.rst:11 msgid "`Odoo Tutorials: Surveys `_" msgstr "" #: ../../content/applications/marketing/surveys/overview.rst:5 msgid "Overview" msgstr "Overzicht" #: ../../content/applications/marketing/surveys/overview/create.rst:3 msgid "Survey essentials" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:5 msgid "" "Companies often use surveys to collect valuable information from their " "customers and employees, which in turn, allows them to make more informed " "business decisions." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:8 msgid "" "In Odoo, surveys are used to collect customer feedback, evaluate the success" " of a recent event, measure the satisfaction of customers (or employees), " "and gain more insight into shifting market sentiments." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:13 msgid "Getting started" msgstr "Starten" #: ../../content/applications/marketing/surveys/overview/create.rst:15 msgid "" "To begin, open the :guilabel:`Surveys` application and click " ":guilabel:`Create`. Odoo then redirects the page to a blank survey template " "form." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:18 msgid "" "On the survey form, add a :guilabel:`Survey Title` and then add a cover " "image to the survey by hovering over the photo icon and clicking on the " ":guilabel:`Edit (pencil)` icon. When the file explorer window opens, choose " "an image from the local files." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:22 msgid "" "Below the :guilabel:`Survey Title` are various tabs in which the survey " "questions and format can be created and customized. These tabs are labeled " "as follows:" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:25 msgid ":guilabel:`Questions`: the list of questions to be asked in the survey" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:26 msgid "" ":guilabel:`Description`: contextual information to aid in understanding the " "survey" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:27 msgid "" ":guilabel:`Options`: choices for survey respondents to answer the questions" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rstNone msgid "Various tabs that can be found on the survey template page." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:34 msgid "Questions tab" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:36 msgid "" "Add questions and sections to the survey in the :guilabel:`Questions` tab. A" " section divides the survey into parts in order to visually group similar " "questions together. To make a section, click :guilabel:`Add a section` and " "type in a section name. Then, add questions or drag and drop questions into " "the divided sections." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:41 msgid "" "Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and" " Questions` pop-up to create and customize the survey question." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rstNone msgid "The survey question pop-up window." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:49 msgid "Create questions" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:51 msgid "" "In the :guilabel:`Create Sections and Questions` pop-up, type the question " "in the :guilabel:`Question` field. Then, choose the :guilabel:`Question " "Type`. A preview of how the question type looks is shown in the preview " "window." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:55 msgid "Choose from the following :guilabel:`Question Types`:" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:57 msgid ":guilabel:`Multiple Lines Text Box`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:58 msgid ":guilabel:`Single Line Text Box`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:59 msgid ":guilabel:`Numerical Value`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:60 msgid ":guilabel:`Date`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:61 msgid ":guilabel:`Datetime`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:62 msgid ":guilabel:`Multiple choice: only one answer`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:63 msgid ":guilabel:`Multiple choice: multiple answers allowed`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:64 msgid ":guilabel:`Matrix`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:67 msgid "" "Different features appear in the :guilabel:`Answers` and :guilabel:`Options`" " tabs, depending on the :guilabel:`Question Type` chosen. However, the " ":guilabel:`Description` tab always remains the same, regardless of what " "question is chosen." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:72 msgid "Create sections and questions" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:74 msgid "" "Once a :guilabel:`Question Type` has been selected, there are three possible" " tabs where information can be customized for the question. These include " "the :guilabel:`Answers` (if applicable), :guilabel:`Description`, and " ":guilabel:`Options` tabs." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:78 msgid "" "Each tab offers a variety of different features depending on what " ":guilabel:`Question Type` was chosen." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:81 msgid "" "For example, in the :guilabel:`Options` tab, the following options may " "appear:" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:83 msgid ":guilabel:`Mandatory Answer`: the question must be answered." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:84 msgid "" ":guilabel:`Matrix Type`: for matrix-type questions, select if one choice or " "multiple choices can be selected per row." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:86 msgid ":guilabel:`Number of columns`: select how many columns are displayed." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:87 msgid ":guilabel:`Images on answers`: allow images on the answer options." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:88 msgid "" ":guilabel:`Conditional Display`: determine if the question is displayed " "based on the participant's answer to a previous question." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:90 msgid "" ":guilabel:`Show Comments Field`: allow the participant to type a comment in " "a text box." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:91 msgid "" ":guilabel:`Question Time Limit`: for live session surveys, set a time limit " "for the question." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:94 msgid "Conditional Display" msgstr "Voorwaardelijke weergave" #: ../../content/applications/marketing/surveys/overview/create.rst:96 msgid "" ":guilabel:`Conditional Display` means the question is only displayed if the " "specified conditional answer has been selected in a previous question." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:99 msgid "" "When the box next to :guilabel:`Conditional Display` is selected, the " ":guilabel:`Triggering Question` field appears. Select a question from the " "survey." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:102 msgid "" "Then, a :guilabel:`Triggering Answer` field appears. Here, select which " "answer will trigger this :guilabel:`Conditional Display` question." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:106 msgid "Options tab" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:108 msgid "" "Back on the main survey template form, under the :guilabel:`Options` tab, " "there are different sections of settings that can be modified." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:111 msgid "The sections include:" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:113 msgid "" ":guilabel:`Questions`: focuses on the overall presentation of the survey" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:114 msgid ":guilabel:`Scoring`: decides how the survey is scored" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:115 msgid ":guilabel:`Candidates`: manages access to the survey" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:116 msgid "" ":guilabel:`Live Session`: enables the survey into a real-time group " "activity." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:119 msgid "Questions" msgstr "Vragen" #: ../../content/applications/marketing/surveys/overview/create.rst:121 msgid "" "First, select the :guilabel:`Layout` of the survey. The following options " "can be chosen:" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:123 msgid ":guilabel:`One page with all the questions`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:124 msgid ":guilabel:`One page per section`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:125 msgid ":guilabel:`One page per question`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:127 msgid "" "If either the :guilabel:`One page per section` or :guilabel:`One page per " "question` options are chosen, then the :guilabel:`Back Button` option " "appears. If selected, the :guilabel:`Back Button` option allows the " "participant to go back to a question during the survey." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:131 msgid "" "Under the :guilabel:`Layout` options is the :guilabel:`Progression Mode` " "setting, which indicates how the participant's progress during the survey is" " displayed. It is shown as either a :guilabel:`Percentage` or a " ":guilabel:`Number`." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:135 msgid "" "Next, there is an option available to add a :guilabel:`Survey Time Limit`. " "To implement this option, simply check the box, and enter the amount of time" " (in minutes) participants have to complete the survey." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:139 msgid "" "After the :guilabel:`Survey Time Limit` option is a section labeled " ":guilabel:`Selection`. Here, questions can be :guilabel:`Randomized per " "section`, in other words, the number of random questions can be configured " "by section. This mode is ignored in a live session." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:144 #: ../../content/applications/marketing/surveys/overview/scoring.rst:56 msgid ":doc:`time_random`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:147 msgid "Scoring" msgstr "Scoring" #: ../../content/applications/marketing/surveys/overview/create.rst:149 msgid "" "The following options are available when deciding how a :guilabel:`Scoring` " "method:" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:151 msgid ":guilabel:`No scoring`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:152 msgid ":guilabel:`Scoring with answers at the end`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:153 msgid ":guilabel:`Scoring without answers at the end`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:155 msgid "" "If either the :guilabel:`Scoring with answers at the end` or " ":guilabel:`Scoring without answers at the end` options are selected, a " ":guilabel:`Success %` field appears. Set the percentage of correct answers " "needed to pass the survey." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:159 msgid "" "Next, there is the option to make the survey a certification. To do so, " "check the box next to the option labeled :guilabel:`Is a Certification`, and" " two additional fields appear. Select a color theme in the " ":guilabel:`Certification Template` field and then choose an :guilabel:`Email" " Template`. When a participant passes the certification with the required " "score, an email from Odoo will automatically be sent to that person using " "the selected email template." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:165 msgid "" "If the :guilabel:`Give Badge` feature is enabled and the " ":guilabel:`Certification Badge` is set, the survey participant also receives" " a badge upon passing the certification." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:169 #: ../../content/applications/marketing/surveys/overview/time_random.rst:48 msgid ":doc:`scoring`" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:172 msgid "Candidates" msgstr "Kandidaten" #: ../../content/applications/marketing/surveys/overview/create.rst:174 msgid "" "To determine access to the survey, the :guilabel:`Access Mode` has two " "options to choose between: :guilabel:`Anyone with the link` and " ":guilabel:`Invited people only`." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:177 msgid "" "Below the :guilabel:`Appraisal Managers Only` checkbox is the " ":guilabel:`Login Required` option to require a login to participate in the " "survey. If this option is activated, an :guilabel:`Attempts Limit` field " "also populates, in which the number of survey attempts is defined for the " "participant." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:182 msgid "Live Session" msgstr "Live sessie" #: ../../content/applications/marketing/surveys/overview/create.rst:184 msgid "" "The :guilabel:`Live Session` section is dedicated to users who are " "conducting surveys in real-time, wherein they directly engage with and " "collect answers from a live audience." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:187 msgid "" "Customize the :guilabel:`Session Code` here; this code is needed for " "participants to access the live session survey. Reward participants for " "quick answers by selecting the checkbox labeled :guilabel:`Reward quick " "answers`. By checking it, attendees will get more points if they answer " "quickly." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:193 msgid "Description tab" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:195 msgid "" "Back on the main survey template page is the :guilabel:`Description` tab, " "where a custom description of the survey can be added. This is displayed " "beneath the title on the survey's homepage, which is on the front end of the" " website made through the Odoo :guilabel:`Website` app." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:200 msgid "Test and share the survey" msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:202 msgid "" "Once the survey is created and saved, run a test to check for possible " "errors before finally sending it out to the participants by clicking " ":guilabel:`Test` in the upper left corner of the survey template page." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:206 msgid "" "When activated, Odoo redirects the page to a test version of the survey on " "the front end of the website. This page displays how the survey will look to" " participants. Proceed to run through the survey, like a normal participant," " to check for errors." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:210 msgid "" "To return to the survey template form in the backend, simply click the " ":guilabel:`This is a test survey. Edit Survey` link in the blue banner along" " the top of the page. Once Odoo redirects the page to the survey template in" " the backend, make any further changes, as needed, before officially sending" " the survey out to participants." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:215 msgid "" "When the survey is ready to be shared with the audience, click the " ":guilabel:`Start Survey` button in the upper-left corner of the survey " "template form. Then, click :guilabel:`Share`." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:218 msgid "" "In the pop-up window, add the survey recipients in the " ":guilabel:`Recipients` field (for existing contacts in the Odoo database) or" " the :guilabel:`Additional emails` field (for contacts that do not want to " "be listed in the Odoo database). Finally, click :guilabel:`Send`." msgstr "" #: ../../content/applications/marketing/surveys/overview/create.rst:222 msgid "" "As answers are received, check them by clicking the :guilabel:`Answers` " "smart button on the survey template form, or the :guilabel:`See Results` " "button in the upper left corner. To end the survey, click the " ":guilabel:`Close` button on the survey template form." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:3 msgid "Scoring surveys" msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:5 msgid "" "To measure a survey participant's performance, knowledge, or overall " "satisfaction, Odoo ascribes points to survey answers. At the end of the " "survey, these points are summed up, resulting in the participant's final " "score." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:9 msgid "" "To add points to questions, open the :guilabel:`Surveys` application, choose" " the desired survey form, and then click on the :guilabel:`Options` tab. " "Under the :guilabel;`Scoring` section, choose between :guilabel:`Scoring " "with answers at the end` or :guilabel:`Scoring without answers at the end`." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:14 msgid "" ":guilabel:`Scoring with answers at the end` shows the survey participant " "their answers after completing the survey, and displays which questions they" " got right or wrong. On questions where there was an incorrect answer, the " "correct answer will be highlighted." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:18 msgid "" ":guilabel:`Scoring without answers at the end` does not show the survey " "participant their answer choices after completing the survey, only their " "final score." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:21 msgid "" "To indicate correct answers, click on the :guilabel:`Questions tab` and " "choose a question. In the question form, check the :guilabel:`Is a correct " "answer` box for the choice that is the correct answer and attach a score " "value." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:25 msgid "" "Back on the :guilabel:`Options` tab of the survey, set the " ":guilabel:`Success %`. The percentage entered determines what percentage of " "correct answers is needed to pass the survey." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:28 msgid "" "Further on the :guilabel:`Options` tab of the survey, survey administrators " "can also choose to make the survey a certification. A certification " "indicates that the survey asks questions to test the participants' knowledge" " level on a subject." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:32 msgid "" "When enabling the :guilabel:`Is a certification` option, choose a " ":guilabel:`Certification email template`. The certification will " "automatically be emailed using this email template to users who pass the " "survey with a final score that is greater than or equal to the set " ":guilabel:`Success %`." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:36 msgid "" "In the :guilabel:`Candidates` section, participants can be required to log " "in to take the survey. If the :guilabel:`Login Required` setting is enabled," " two new options appear: the :guilabel:`Attempts Limit` checkbox, which " "limits the number of times a participant can attempt the survey, and the " "option to :guilabel:`Give Badge`, located beneath the " ":guilabel:`Certification` options in the :guilabel:`Scoring` section." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rstNone msgid "" "Setting the Required Score (percentage), login required, and certification " "template." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rst:46 msgid "" "Badges are displayed on the eLearning portion of a given user's portal, and " "are a way to set milestones and reward participants for passing surveys or " "gaining points. Besides the awardee, website visitors who access the " ":guilabel:`Courses` page will also be able to see the granted badges." msgstr "" #: ../../content/applications/marketing/surveys/overview/scoring.rstNone msgid "Example of how a badge looks on the eLearning portion of the website." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:3 msgid "Timed and randomized questions" msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:5 msgid "" "When creating a survey in Odoo, there are options to set a time limit on the" " survey and randomize the questions." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:9 msgid "Time limit" msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:11 msgid "" "During a timed survey, participants must finish the survey within a " "specified period of time. A common use case for implementing a time limit is" " that it greatly reduces the chance of participants looking up responses via" " external resources (e.g. web search), and reduces the survey to a \"closed " "book\" testing environment." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:16 msgid "" "Find the :guilabel:`Survey Time Limit` setting in the :guilabel:`Options` " "tab of the survey form, under the :guilabel:`Questions` section." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rstNone msgid "Time limit field in the options tab of a survey template form." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:23 msgid "" "When the :guilabel:`Survey Time Limit` option is checked, a timer will be " "displayed on every page of the survey, letting participants keep track of " "the time remaining while the survey is active." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:27 msgid "" "Participants that do not submit their survey by the preconfigured time limit" " will *not* have their answers saved." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:31 msgid "Randomized selection" msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:33 msgid "" "When a survey is randomized, Odoo shuffles the questions and reveals them in" " a random order every time a participant begins the questionnaire. Using " "randomization as a survey method discourages participants from looking at " "each other's responses, and helps control for individual testing." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rst:37 msgid "" "To randomize a survey, click the :guilabel:`Options` tab on the survey form." " In the :guilabel:`Questions` section, select :guilabel:`Randomized per " "section` for the :guilabel:`Selection` field. After enabling, navigate to " "the :guilabel:`Questions` tab and look in the :guilabel:`Random questions " "count` column. From there, determine how many questions (per section) Odoo " "should select and display during the shuffling of questions." msgstr "" #: ../../content/applications/marketing/surveys/overview/time_random.rstNone msgid "Randomized question count in the questions tab of a survey." msgstr ""