Crear plantillas de proyecto

Creating project templates is the most reliable way of bundling all the resources needed for project creation in one asset which you can reuse multiple times.

Antes de empezar

Customers must be associated with at least one project template, which means that you must create at least one project template for a customer in order to create a project for that customer. Make sure that you created customers and that you added customer users to customer accounts.

Por qué y cuándo se efectúa esta tarea

Project templates enable customers (and their customer users) to create projects in Trados Customer Portal, and enable project managers to create projects on customers' behalf in Trados Enterprise.

When you create a new complex resource which is based on other component resources, you can filter the component resources by two criteria: Current folder and above (default) and Current folder. Using the filtering criteria enables you to see and use exactly the resources you own or have inherited.

When you create project templates, you use the following component resources created beforehand: file type configurations, translation engines (and its component TMs, termbases), pricing models, workflows. When you select these component resources, use the available criteria for quick and accurate resource navigation.

When you select a resource during project template creation, what gets included in the project template is a copy of that resource.

If you select a resource which has fewer languages than the project template, the missing languages are added automatically to each resource. The Save and Save as new buttons become enabled, and you can choose to save the missing languages only for the current project template or for future project templates (by creating a new resource which is automatically selected in your project template).

You can configure project templates with the same source and target language.

When this project template is included in a project which has the same source and target language, the project is automatically marked as a restricted project.

Procedimiento

  1. Log in to Trados Enterprise (by accessing this link: http://languagecloud.sdl.com/lc).
  2. Go to the Resources view.
  3. Select the Project Templates tab.
  4. Select New Project Template.
  5. On the New Project Template page, select General, and then do the following:
    1. Under Name, enter a name for your project template.
    2. Under Location, select the folder where you want to set up and store the project template.
    3. Under File Type Configuration list, select a file type configuration which includes all the file types which are translatable as part of a project. You can also use the default file type configuration.
      If the project contains file types which are not included in the file type configuration, the non-matching file types will not be translatable and will function as reference files.
    4. From the Project Managers list, choose users or groups which act as project managers over the project and which can be assigned to any project task. If you select users who do not have the Administrator, Lead Project Manager or Project Manager role, then those users will dynamically receive all the permissions of the Project Manager role until the project is completed. When making task assignments, you can select the Project Managers field to assign the task to the designated project manager. To learn about the limitations of being a designated project manager on a project, consult this topic.
    5. (Optional) Select a schedule template from the Schedule Template list. This field is available only if you purchased the feature based on a commercial agreement.
    6. Under Languages, select one source language and one or more target languages. You can configure project templates with the same source and target language.
    7. (Optional) If there are custom fields which were previously configured in the same location as the one you selected at step 5b, then under Custom Fields, select one or more of the available custom fields. There can be a maximum of 50 custom fields per project template (and per project).
  6. On the Create Project Template page, select Translation Engine, and then specify a translation engine.
    ToDo this
    Add an already configured translation engine. The page is populated with details of the translation engine you have just chosen. The Translation Engine list is populated only if there are translation engines available for the selected source language.

    If you edit the details of the translation engine, you must save them by selecting Save. Saving the changes means that the old information is overwritten with the new one. You can also save your changes by selecting Save as new, which means that a new translation engine is created.

    OR
    Create a translation engine from scratch.
    1. Select New Translation Engine.
    2. In the New Translation Engine dialog:
    1. Enter a name and a description for your translation engine.
    2. From the Language Processing Rules list, select the language processing rule which will parse your linguistic resources. You can also select the default language processing rule which is created automatically when the customer is created.
    3. In the New Translation Engine dialog, under Languages:
    1. Select one language from the Source language list and one or more languages from the Target languages list. You can delete a language pair by hovering over the language field and selecting Delete.
    2. Select to add more language pairs.
    4. Under Translation Memories:

    Add a TM

    1. Select Add Translation Memory.
    2. Expand the Filters menu. RWS recommends that you keep the default filtering criterion selected: Show TMs with matching language processing rules.
    3. Select the TM and select . The first TM you select is the main TM.
    4. For each TM, select the check boxes corresponding to the way you want to use your TM: LOOKUP, CONCORDANCE, UPDATE. Specify the penalty value for the matches applied from the selected TM. To have a valid translation engine, you must specify a TM for lookup and a TM for update for each language pair. The TMs which have the UPDATE check box enabled will be updated with the changes made to TUs during translation and review.
    5. Check sign for complete selection - The check box (LOOKUP or CONCORDANCE or UPDATE) is selected for all the target languages associated with the same source language.
    6. Partial selection - The check box (LOOKUP or CONCORDANCE or UPDATE) is selected for some of the target languages associated with the same source language.
    7. Identify the TM row. Hover over the end of the TM row and select the reload button to make sure you include the latest version of the TM. For example, you have the translation engine window open, but you make changes to the TMs included in that translation engine in another window (for example, you change the name or languages of the TM). After you close the TM window, reload the TM in the translation engine to see the latest updates.
    8. Reorder the TMs in order to set the hierarchy according to which TMs will be matched against your source text. Press the hamburger menu (hamburger menu) of a TM, and then drag and drop it before or after another TM.
    9. Import TM content. Hover over the end of the TM row. Select import icon. After the import is finished, the changes will apply everywhere the TM is used. Ensure you are familiar with the prerequisites described in this topic. Then, follow steps 5 to 7 described in this topic.

    OR

    Create a TM from scratch

    1. Select New Translation Memory.
    2. Enter the following details:
      1. Enter a name for your TM.
      2. (Optional) Enter a copyright.
      3. Select a location where you want to set up and store your TM.
      4. (Optional) Enter a description detailing the context where your TM is used or any other relevant information.
    3. Under Languages:
      1. Select the source language column and choose a language from the list. Select the target language column and choose one or more languages from the list. Select new entry plus sign. Repeat this step to add more language pairs.
      2. In the Language Processing Rules box, select a language processing rule. You can also select the default language processing rule which is created automatically when the customer is created.
      3. In the Field Template box, select a field template. You can also select the default field template which is created automatically when the customer is created.
    4. Select Save.
    5. Under Machine Translation:
    1. Select Add Machine Translation Model.
    2. Select the MT engine and select . You can consult the MT provider (Machine Translation powered by RWS, Google Machine Translation or other providers) as well as the glossaries in the MT resource. To add an available glossary (a list of terms which must be kept in the source language), select Use glossaries and select the glossary. Reorder the MT providers in order to set the sequence according to which MT will be matched against your source text. Press the hamburger menu (hamburger menu) of an MT provider, and then drag and drop it before or after another MT provider. You can also drag and drop several MT providers in one go, if you use CTRL and select the providers, or if you use SHIFT and select the first and last MT provider in a range.
    6. Under Termbases:

    Add a termbase

    1. Select Add Termbases.
    2. Expand the Filters menu. RWS recommends that you keep the two default filtering criteria selected: Only show termbases with matching languages.
    3. Select the termbase, and then select .
    4. If needed, import termbase content. Hover over the end of the termbase row. Select import icon. After the import is finished, the changes will apply everywhere the termbase is used. Ensure you are familiar with the prerequisites described in this topic. Then, follow steps 4 to 6 described in this topic.
    5. Decide which termbases will be updated with new content by selecting their UPDATE check box. For each termbase, go to the ENTRY TEMPLATE column, and, from the list, select the entry template which users will need to adhere to when adding new term entries from Trados Online Editor.

    OR

    Create a termbase from scratch

    1. Select New Termbase.
    2. On the Termbase definition page, choose one of the following termbase creation methods:
      • Create a new termbase from scratch — If you choose this method, you need to enter all the fields and design your entry structure yourself.
      • Use a termbase template — If you choose this method, you already have a termbase entry structure to work with. Depending on whether you choose Basic, Advanced or another template saved on your account, you will have more or fewer fields already defined for your termbase, but you can still add, edit, or delete fields.
      • Load an existing MultiTerm termbase definition, browse for the file and select Upload — If you choose to upload an existing MultiTerm termbase definition, your termbase inherits the fields and entry structure in the termbase definition. You can still add, edit, or delete fields. This feature ensures compatibility with your MultiTerm resources.
    3. On the Termbase information page, enter the name of your termbase and, optionally, a description and a copyright year.
    4. On the Language fields page, under LANGUAGES, select the first available row, and then select a language from the list. Repeat this step to add as many languages as you need.
    5. On the Fields and structure page, create an entry structure for your termbase entries by adding fields to the default Entry level > Language level > Term level structure:
      1. Go to the Fields pane on the right side of the screen.
      2. In the FIELD NAME column, enter a name.
      3. In the TYPE column, select an option from the list: Text, Number, Boolean, Date/Time, or Picklist.
      4. In the VALUES column, you can add values only for the Picklist type. Add values and separate them with a comma.
      5. Go to left-side pane, select a level, and then select Add field.
      6. In the sub-menu pane, select the field you want to add from the list.
      7. Select all the options which apply to this field: Multiple, Mandatory, or Custom values.
      8. Confirm the field.
      9. Repeat this step to add as many custom fields as needed.
    6. On the Summary page, do the following:
      • Consult the termbase information.
      • Select the Save as a reusable termbase template check box to use this termbase definition as a template for creating a new termbase. Then, enter a name for your template.
    7. Select Finish.
    7. Select Save.
  7. On the Create Project Template page, select Pricing Model, and then select a pricing model from the list.
    ToDo this
    Add an existing pricing model Choose a pricing model from the list. The list is populated if there are pricing models for the selected source language. The page is populated with details of the pricing model you have just chosen.

    If you edit the details of the pricing model, you must save them by selecting Save. Saving the changes means that the old information is overwritten with the new one. You can also save your changes by selecting Save as new, which means that a new pricing model is created.

    OR
    Create a pricing model from scratch
    1. Select New Pricing Model.
    2. On the New Pricing Model page, do the following:
      1. In the Pricing model box, enter a name for your pricing model.
      2. In the Description box, enter the details for your pricing model: purpose, usage, time frame, project template to associate with, and so on.
      3. Specify the currency of the pricing model.
    3. Under Languages, specify a language in the Source language box, and then specify one or more languages in the Target language box.
    4. Under Language Prices, select Full screen to check the detailed costs in a separate window. Select Exit full screen to return to the normal view. Do the following:
      1. Select the language row, place the cursor in the available columns and edit the price. You can copy the price values from one language row to the other. Go to the end of the language row whose values you want to copy, expand the menu, and select Copy translation costs. Then, identify the language row where you want to copy the values, go to the end of the row, expand the menu, and select Paste, Paste to all target languages from this source language or Paste to all languages.
      2. To add other regular costs per language, go to the end of a language row, select Add Language Cost, enter the cost name and select a cost option under Select Type. If you select Volume under Select Unit, choose whether the cost refers to words or characters, and then specify a price under Set Unit Cost. If you select Hourly, under Select Unit, select the number of hours, and then specify a price under Set Unit Cost. If you select Percentage, specify a price under Set Value. If you select Per Page, under Select Unit, select the number of pages, and then specify a price under Set Unit Cost. Note that you can use both integers and decimals when expressing units. Check Example 1 and 2 in this topic for more information.
      3. To add conditional costs per language, go to the end of a language row, select Add Language Cost, enter the cost name and:
        1. Under Set Type, select Conditional.
        2. Under Set Variable Cost, select the criteria to which the conditional cost applies:
          • Word Count (the total number of words in the file/files as calculated by the system)
          • Running Total (the total cost calculated by the system for a target language or for a project)
        3. Under Set Operator, select how the condition limit is calculated.
        4. Specify a value (for the criteria you selected under Set Variable Cost) which represents the limit based on which the conditional cost is calculated.
        5. Under Set Condition Type, select how the unit cost (at step vi below) is applied:
          • Absolute = the exact value at point vi is applied overwriting the value calculated automatically by the system. We advise that you not set negative values under Set Unit Cost (at point vi) for this use case, unless you want to work for free.
          • Percentage = the percentage value at point vi is calculated (added if the value is positive, deducted if the value is negative)
          • Relative = the percentage value at point vi is added (if the value is positive) or deducted (if the value is negative)
        6. Under Set Unit Cost, specify the actual cost value.
        7. Check Example 1 of this topic to understand how conditional cost works depending on the variable cost and condition type you choose.
      4. Select Add for all languages if you want to add this cost to all your target languages or Add Cost if you want to add it only to the selected target language. Note that you can use both integers and decimals when expressing units.
      5. You can copy the additional costs from one language row to the other. Go to the end of the language row whose values you want to copy, expand the menu, and select Copy all additional language costs. Then, identify the language row where you want to copy the values, go to the end of the row, expand the menu, and select Paste, Paste to all languages or Paste to all target languages from this source language.
    5. Under Additional Cost, select Add Project Cost.
      1. In the Add Project Cost dialog, enter the cost name and select a cost option under Select Type. If you select Volume under Select Unit, select whether the cost refers to words or characters, and then specify a price under Set Unit Cost. If you select Hourly, under Select Unit, select the number of hours, and then specify a price under Set Unit Cost. If you select Percentage, specify a price under Set Value. If you select Per Page, under Select Unit, select the number of pages, and then specify a price under Set Unit Cost. Note that you can use both integers and decimals when expressing units. Check Example 1 and 2 in this topic for more information.
      2. To add conditional costs per project, select the language row, enter the cost name and:
        1. Under Set Type, select Conditional.
        2. Under Set Variable Cost, select the criteria to which the conditional cost applies:
          • Word Count (the total number of words in the file/files as calculated by the system)
          • Running Total (the total cost calculated by the system for a target language or for a project)
        3. Under Set Operator, select how the condition limit is calculated.
        4. Specify a value (for the criteria you selected under Set Variable Cost) which represents the limit based on which the conditional cost is calculated.
        5. Under Set Condition Type, select how the unit cost (at step vi below) is applied:
          • Absolute = the exact value at point vi is applied overwriting the value calculated automatically by the system. We advise that you not set negative values under Set Unit Cost (at point vi) for this use case, unless you want to work for free.
          • Percentage = the percentage value at point vi is calculated (added if the value is positive, deducted if the value is negative)
          • Relative = the percentage value at point vi is added (if the value is positive) or deducted (if the value is negative)
        6. Under Set Unit Cost, specify the actual cost value.
        7. Check Example 1 of this topic to understand how conditional cost works depending on the variable cost and condition type you choose.
      3. Select Add Cost. Note that you can use both integers and decimals when expressing units.
    6. If needed, customize the default fuzzy bands. If you configure fuzzy bands, the system overwrites the minimum match value (under project > Settings) with the lowest fuzzy match band after the project starts.
    7. Select Create.
  8. On the Create Project Template page, select Pricing Model, and then select a pricing model from the list. The list is populated if there are pricing models for the selected source language. The page is populated with details of the pricing model you have just chosen.
  9. On the Create Project Template page, select Workflow. Files can be returned to a previous workflow task if the current task supports the relevant transitions (outcomes). Consult this topic to learn about the standard transitions of various tasks.
    Workflow tasks are skipped only if they are excluded from the project workflow. Tasks are never skipped automatically if they are part of a project workflow. The Project Planning task can be excluded from the project (during project creation) if you specified the task assignees while configuring the workflow resource or the project template resource, and no other changes are required.
    ToDo this
    Add an already configured workflow (template)Choose a workflow (template) from the list. The list is populated if there are workflows for the selected source language. The page is populated with details of the workflow you have just chosen.
    If you edit the details of the workflow, you must save them by selecting Save. Saving the changes means that the old information is overwritten with the new one. You can also save your changes by selecting Save as new, which means that a new workflow is created.
    OR
    Configure the workflow
    1. Select New Workflow.
    2. On the New Workflow page, do the following:
      1. In the Name box, enter a name for your workflow.
      2. In the Description box, enter the details for your workflow: purpose, usage, time frame, project template to associate with, and so on.
    3. Under Languages, specify a language in the Source language box, and then specify one or more languages in the Target language box.
    4. Decide which workflow template you want to use as the basis for your workflow definition and who you want to assign the workflow tasks (marked Human) to. A workflow stage consists of one or more tasks. The target languages of each Human task are ordered alphabetically.
      1. From the Workflow Template list, select a workflow template. If you change your mind, and later select another project template or you are prompted to refresh the page to benefit from the latest workflow template updates, all the assignments and configurations from the previous workflow template are preserved. You can change the current workflow template with a new one. By default, the system preserves the assignees of the previous workflow template in the newly selected workflow template, for all the Human tasks which are common between the 2 workflow templates. In particular, if the newly selected workflow template is a custom workflow template, the system does not preserve the vendor order template (VOT) assigned to a custom Human task. Invalid workflow templates are disabled in the list.
      2. Under Dynamic assignment, select an option to specify which users in the assigned group receive the assignment notification:
        • Basic - the assignment notification is sent to all users
        • Service type - the assignment notification is sent to all users who have matching service types
        • Service type and language pairs - the assignment notification is sent to all users who have matching service types and languages
      3. Verify that the workflow tasks align with your process requirements. To exclude a task, hover over it, and then select the Exclude this task check box. Note that, if you exclude a task or some target languages from a task, but then you decide to include the task back in the workflow, the assignees are restored, which means that you do not need to enter the assignees from scratch.
      4. Assign users or user groups to all the human tasks. Alternatively, you can postpone all assignments to the project creation phase. Invalid assignments are marked by a warning. For each human task, select Assign task. Click Select assignees, and then choose the individual users (Users), groups (Groups) or vendors (Vendors) to assign them to that task. When you perform the assignments, use the available filters (Current folder and above, Current folder only) to ensure that you identify and assign users easily. If you want to assign a task to the project creator, under Users, select Project Creator. However, if the project was created in Trados Customer Portal, do not use the Project Creator option for the tasks that can be performed in Trados Enterprise, because Trados Customer Portal users do not typically have access to Trados Enterprise.
      5. For the Translation task and Implement Customer Review task, you need to specify the configuration. Select Configure and Assign Task, select a target language, and then select the cogwheel symbol. In the Configure_[target_name] right-hand-side pane, under Editor mode, select a configuration, and then select Save Configurations. Repeat the process for all the target languages of the Translation task and the Implement Customer Review task. To understand what each Translation configuration does, check this topic. To understand what each Implement Customer Review configuration does, check this topic.
      6. For the Linguistic Review task and the Customer Review task, you need to specify the configuration. Select Configure and Assign Task, select a target language, and then select the cogwheel symbol. In the Configure_[target_name] right-hand-side pane, under Review mode, select a configuration, and then select Save Configurations. Repeat the process for all the target languages of the Linguistic Review task and the Customer Review task. You can choose the same configuration for all target languages or a different configuration for each target language. To understand what each Linguistic Review configuration does, check this topic. To understand what each Customer Review configuration does, check this topic.
      7. If your workflow includes both a Translation and a Linguistic Review task, make sure you correlate configurations correctly. Check this topic for more details.
      8. If your workflow includes both a Customer Review and an Implement Customer Review task, make sure you correlate configurations correctly. Check this topic for more details.
      9. For the Hold for Feedback task, you need to specify the number of days after which the task is closed automatically with the status Elapsed. Select Configure and Assign Task, and then select the cogwheel symbol. In the Configure_[target_name] right-hand-side pane, under Close after (days) specify the number of days after which the task is closed automatically. The Close after (days) field has the default value of 90 days, and can have a minimum value of 1 day, and a maximum value of 365 days. The Hold for Feedback can be completed manually, but if it is not, automatic completion happens after the days specified in the Close after (days) field elapse.
      10. For the Customer Review task, you need to specify the number of days after which the task is closed automatically with the status Elapsed. Select Configure and Assign Task, and then select the cogwheel symbol. In the Configure_[target_name] right-hand-side pane, under Close after (days) specify the number of days after which the task is closed automatically. The Close after (days) field has the default value of 90 days, and can have a minimum value of 1 day, and a maximum value of 365 days. The Customer Review can be completed manually, but if it is not, automatic completion happens after the number of days specified in the Close after (days) field elapse.
      11. You can specify the number of days after which tasks are automatically completed by the system. The Close after (days) field is available for all Human tasks, except Vendor Quote Review, Vendor Quote Approval, and Error. The Close after (days) field is mandatory for and has a default value of 90 days for Hold for Feedback and Customer Review tasks. The Close after (days) field is optional for all Human tasks, except Hold for Feedback and Customer Review. For more information about how the closing date is auto-propagated from the main task to the vendor-related tasks, consult this topic.
      12. If your workflow allows for files to be returned to previous workflow tasks even after these files went through a Desktop Publishing task, all the changes made to that file during the initial Desktop Publishing task must be redone or reapplied from scratch in the subsequent Desktop Publishing task.
      13. For the Automated Translation QA Check task and the Automated Linguistic Review QA Check task, you can configure the number of times the QA check loop runs if it encounters errors. If errors are detected during these tasks, the file goes back to the previous task (either Translation, or Linguistic Review) for corrections. By default, these automated tasks run once. To increase the number of times that these automated tasks must run, identify the task, select Configure, and under Number of QA Check returns, enter a value. Select Save configurations.
        • If you enter the 0 value in the Number of QA Check returns field, then the Automated QA Check task runs once, but does not return the task back to Translation or Linguistic Review even if errors are detected.
        • If you enter a value equal to or higher than 1 in the Number of QA Check returns field, then the Automated QA Check task runs as many times as specified, and returns the task back to Translation or Linguistic Review if errors are detected. The maximum value you can enter is 2 billion.
        • If you select the Return until no QA Check errors check box, the Automated QA Check task runs as long as errors are found, irrespective of the number specified in the Number of QA Check returns field.
      14. If you want to assign a task to the designated project managers, under Users, select Project Managers. Designated project managers are specified either while creating projects or while editing the Settings > Project Information section of an existing project.
      15. To assign vendors to a task, select Vendors, and then select one of the available vendor order templates. The menu displays three tasks:
        • Vendor Quote Generation - This is an Automated task generated based on the pricing model in the vendor order template. The Vendor Quote Generation field contains the name of the vendor quote, which can be downloaded from the project Costs tab. You can edit the Vendor Quote Generation field in order to identify the vendor quote report easily.
        • Vendor Quote Review - This is a Human task which is automatically assigned to the users or Vendor Project Manager group you specified in the Managers field of the vendor order template.
        • Vendor Quote Approval - This is a Human task for which, at this stage, you must specify users or groups bearing the Administrator, Lead Project Manager or Project Manager role.
        For more information on the various vendor assignment and reassignment scenarios, consult this topic.
      16. If you want to assign groups to tasks, the system returns all groups which have a maximum of 100 users for selection. If you select several groups to assign them to the same task, and the total number of users in these groups exceeds 100 users, the system issues a warning that you must adjust your selected assignees and groups before you can save the workflow.
    5. Select Save.
  10. On the Create Project Template page, select Settings, and:
    1. Under General,
      • Decide whether you want translators or reviewers the edit source content. Enable or disable the Allow editing of source text in segments option. It is disabled by default.
      • Decide whether you want to expose a project template in Trados Customer Portal. Enable or disable the Customer Portal visibility option. It is enabled by default.
      • Decide whether you want to allow Trados Customer Portal users to add source files as a new batch in any workflow phase. Select the Allow upload of translatable files at any stage in Customer Portal check box to allow Trados Customer Portal users to add source files in any workflow phase. Clear the Allow upload of translatable files at any stage in Customer Portal check box, to allow Trados Customer Portal users to add source files only before the Customer Quote Approval step or to allow source files being added as a new batch from Trados Enterprise.
      • Decide whether you want to create a restricted project based on this template. Enable or disable the Restrict file downloads option. Restricted projects prevent all users (except administrators, lead project managers, project managers, customer requesters, and engineers) from downloading project files locally. Note that the Restrict file downloads option is enabled by default, and cannot be disabled, if you create a project template which has the same source and target language.
      • Identify the Quote Template list, and do one of the following:
        • To use the default quote template applied automatically by the system, do not select any value from the list.
        • To use a quote template customized by you, select it from the list.
        • To delete a quote template, select the X sign. The default quote template applies.
      • Specify the completion configuration and archival configuration for your project.
    2. Under Batch tasks > Pre-Processing Settings, configure how TMs are applied by configuring the following:
      • Choose a value in the Minimum match value box.
      • Choose an option from the Translation overwrite mode box:
        • Overwrite existing translation if better match found - For this option, unlocked segments (including confirmed segments) are overwritten, while unlocked Perfect Match segments and locked segments are not overwritten.
        • Keep existing translation
        • Always overwrite existing translation - For this option, Perfect Match segments (both locked and unlocked) are overwritten, while other locked segments are not overwritten.
        • Overwrite except Perfect Match translation - For this option, unlocked segments (including confirmed segments) and locked segments are overwritten, while unlocked Perfect Match segments are not overwritten.
      • Choose an option from the After applying translations box: Confirm 100% matches (default value), Confirm context matches (default value), Lock 100% matches; Lock context matches, Lock green segments (from MTQE, if available), Lock amber segments (from MTQE, if available), Lock red segments (from MTQE, if available).
      • Choose an option from the When no match found box: Leave target segment empty (default value), Copy source to target.
      • Select Advanced Settings and decide whether you want to enable the Report Cross-File Repetitions option.
      • Select Configure penalties and specify a numeric value for each standard penalty: Missing formatting penalty, Different formatting penalty, Multiple translations penalty, Auto-localization penalty, Text replacement penalty, Alignment penalty, Character-width difference penalty. The maximum value a standard penalty can have is 20. The Auto-localization penalty applies to auto-substituted dates, times, numbers and measurements. The Text Replacement penalty applies to auto-substituted variables, acronyms and alphanumeric strings. For more information about what each penalty does, consult this topic.
      • Select Configure penalties and specify a numeric value for each TU status penalty: Translated, Translation Rejected, Translation Approved, Sign-off Rejected, Signed Off, Not Translated, Draft. The maximum value a translation unit penalty can have is 20.
      • Select Configure penalties and, under Penalty filters, configure a filter which excludes certain segments from the TM during the Translation Memory Matching automated workflow step and during lookup retrieval (while you are translating).
      • Select Filters and configure a penalty filter for all non-matching TUs. Select Add New Filter, and then give your filter a name and a numerical value. Under Conditions select the criterion based on which filtering can be performed: Last modified on, Last modified by, Last used on, Last used by, Usage count, Created on, Created by, TU confirmation level, Source segment, Target segment, Source segment length, Target segment length, Number of tags in target segment, Number of tags in source segment. Depending on the criterion you choose, you must further select or enter values. To create a complex filter, use the operator check boxes and add as many conditions as you need. Select Save filter.
      • Select Cross-File Repetitions to have cross-file repetitions identified and included in analysis reports. Note that the order in which cross-file repetitions are calculated depends on the time at which files are analyzed. Since the exact processing time of a file cannot be predicted, the files which share repetitions can display different results per target language depending on the time when the file was analyzed for that particular target language. Selecting the Cross-File Repetitions check box may lead to differences in cost across target languages for the same files, as well as differences in terms of how repetitions are counted. For more information about how repetitions and cross-file repetitions are calculated, consult this topic.
      • Under Report locked segments in analysis, select one of the options:
        • Select Report locked segments in analysis > Exclude from analysis report to have locked segments completely ignored from the Analysis report. The total number of reported segments will not include any locked segments.
        • Select Report locked segments in analysis > As a separate category to have locked segments appear as a standalone category in the Analysis report. If the locked segments are repetitions, the locked segments are reported neither in the Repetitions category, nor in the Cross-File Repetitions category of the Analysis report.
        • Select Report locked segments in analysis > Using the original match category to have locked segments distributed across the available fuzzy bands. If the locked segments are repetitions, the locked segments and their repetitions are reported neither in the Repetitions category, nor in the Cross-File Repetitions category of the Analysis report.
    3. Under Batch tasks > PerfectMatch, configure how PerfectMatch is applied.
      • Segment status after execution - Select PerfectMatch and Locked if you want the PerfectMatch segments to be locked as signed off segments. Select PerfectMatch if you want the PerfectMatch segments to be marked as signed off segments. Select Keep original status if you want the PerfectMatch segments to keep the status they are currently listed with in the source.
      • Ignore formatting tags - Select or clear the setting depending in whether you want PerfectMatch to consider formatting or not.
      • Regulatory industry-compliant handling of duplicate content - Select the setting if you want PerfectMatch to take into consideration the exact order of identical segments and apply the mapping based on the order in which these segments appear in the source text. Clear the setting if you want PerfectMatch to consider the first occurrence of several identical segments as the basis for PerfectMatch across all occurrences in the source text. Let's look at an example. You have a file called File1 which is translated and which contains three identical sentences occurring in different places in the file. File2 is very similar to File1, contains the same three identical sentences, and you would like to translate File2 via PerfectMatch based on File1.
        Identical sentencesFile1File2 + RI setting ONFile2 + RI setting OFF
        Sentence1TranSentence1TranSentence1TranSentence1
        Sentence2TranSentence2TranSentence2TranSentence1
        Sentence3TranSentence3TranSentence3TranSentence1
    4. Under Batch tasks > Update Translation Memory, configure how TMs are updated throughout the project workflow depending on the status of the segments.
      • Choose an option from the If target segments differ box:
        • Merge translation units = Replace (update) only the TU (from which a match was retrieved for the edited TU) with the latest available translation AND keep the other duplicates as they are. Use this option to have multiple translations for the same source together with Multiple Translation Penalty = 0.
        • Add new translation units = Add translations as new TUs to the TM. Specify the status of the TUs (which will be added) under Segment status. This means that the existing TUs in the TM are not overwritten.
        • Overwrite existing translation units = Delete all TUs (which have the same source, all TU duplicates) and keep only the last added TU (the latest available translation). Use this option to prevent inconsistent translations.
        • Leave translation units unchanged = Keep the existing TUs and do not add any new ones.
        • Keep most recent translation units = Replace (update) only the most recent TU (from which a match was retrieved for the edited TU) with the latest available translation AND delete all other duplicates.
      • Choose an option from the Segment status box: Translated (default option), Translation Approved (default option), Signed Off (default option), Draft, Translation Rejected, Sign-off Rejected.
      • Select Update Translation Memory fields, and add fields and their values. Note that if you edit the field templates and change their type, this will impact all the project templates and projects where the field template is used. Moreover, the TMs which use these field templates are not updated and the Translation Memory Update task will fail. Therefore, if you change the field type, in the Settings > Update Translation Memory Fields section of your project template or project, edit the field values or reset the field.
      • Select Filters and configure a hard filter which automatically excludes all non-matching TUs. A hard filter completely filters out non-matching TM results. If a TM match does not match the filter conditions, it is completely excluded from lookup results. Select Hard Filter, and then, under Conditions select the criterion based on which filtering can be performed: Last modified on, Last modified by, Last used on, Last used by, Usage count, Created on, Created by, TU confirmation level, Source segment, Target segment, Source segment length, Target segment length, Number of tags in target segment, Number of tags in source segment. Depending on the criterion you choose, you must further select or enter values. To create a complex filter, use the operator check boxes and add as many conditions as you need. Select Save filter. For more information on hard filters, consult this topic.
    5. Under Verification > Tag Verifier, configure which tags should be checked and which ignored. Select Advanced Settings to specify different warnings to the elements which do not behave as expected: Note, Error, Warning. Tag Verifier is enabled by default, but you can toggle it off. To export your Tag Verifier settings in a *.json file, select the three-dot icon, and then select Export settings. To import Tag Verifier settings as a *.json file, select the three-dot icon, select Import settings, and load your file.
    6. Under Verification > QA Checker, configure how checks are performed at global level (All languages), at target-language level or both. The languages which are configured with custom settings are marked by a warning sign. QA Checker is enabled by default, but you can toggle it off. To export your QA Checker settings in a *.json file, select the three-dot icon, and then select Export settings. To import QA Checker settings as a *.json file, select the three-dot icon, select Import settings, and load your file.
      • The following settings are available at global level (All languages): Segments Verification, Segments to Exclude, Inconsistencies, Punctuation, Numbers, Word list, Regular Expressions, Trademark check, Length verification. For Numbers, note that the Check measurements covers both measurements and currency.
      • The following settings are available at target-language level: Punctuation, Numbers, Word list, Regular Expressions, Length verification. You can copy and paste the settings specified for a given target language. Select the three-dot icon, and select Copy settings to copy the settings of a language row, Paste settings to paste the settings from a language row to another language row, and Apply to all target languages to apply the settings of a language row to all available languages.
      For Punctuation, Numbers, Word list,Regular Expressions, and Length verification, which can be set at global level and/or at target-language level, the enforcement logic goes as follows:
      • If users specify these settings at global level, and keep the default values for these settings at target-language level, then the global level apply to all target languages.
      • If users specify these settings at target language level, then these values apply.
      • If users specify these settings at both global level, and target-language level, then the target-language level values take precedence over the global ones.
      Depending on your needs, select either All languages or a specific target language, and configure the settings:
      • Segments Verification: segments you forgot to translate, segments which are identical in the source and the target, various inconsistencies.
        FieldOptions
        Basic Settings
        Forgotten and empty translationSelect the Check for forgotten and empty translation check box to be notified that your translation is incomplete.
        Compare source and target segments
        • Select the Source and target are identical check box to be notified that you have not translated a segment.
        • Decide whether you want to have target segments checked based on their length and use the Longer by and Shorter by fields to configure the length value.
        Ignore segments fewer than # wordsDecide whether you would like to ignore some segments based on their number of characters or words. If you choose the latter option, configure the number of words.
        Advanced Settings
        For each of the above elements, specify different warnings to mark how severe the unexpected behavior is: Note, Error, Warning.
      • Segments to Exclude: exclude segments per translation status.
      • Inconsistencies: repetitions, non-edited fuzzy matches.
        FieldOptions
        Basic Settings
        Check for inconsistent translationsSelect the check box to have inconsistent translations highlighted.
        Check for repeated words in targetSelect the check box to be notified of repetitions.
        Check for unedited fuzzy matchesSelect the check box when you enter fuzzy matches without additional edits.
        Advanced Settings
        For each of the above elements, specify different warnings to mark how severe the unexpected behavior is: Note, Error, Warning.
        Ignore tags and Ignore caseIf you selected Check for inconsistent translation, decide whether you want to ignore tags and case from all identified inconsistent translations.
        Ignore numbers and Ignore caseIf you selected Check for repeated words in target, decide whether you want to ignore numbers and case from the repetition count.
        Only check confirmed segmentsIf you selected Check for unedited fuzzy matches, decide whether you want to narrow down your search to confirmed segments.
        Only check if match scores belowIf you selected Check for unedited fuzzy matches, decide whether you want to narrow down your search to a match score of your choice. Specify the percentage of the match score.
      • Punctuation: extra spaces, brackets, capitalization.
        FieldOptions
        Basic Settings
        End punctuationDecide which type of end punctuation should be checked for inconsistencies:
        • Check that source and target end with the same punctuation
        • Check for Spanish punctuation
        • Select the Check for unintentional spaces before check box and insert the punctuation marks which prompt a check.
        Extra dots and spacesSpecify the cases where extra dots and extra spaces should be checked for inconsistencies:
        • Check for multiple spaces
        • Check for multiple dots
        • Ignore ellipsis dots
        • Check for extra space at the end of target segments
        Capitalization checkSpecify the cases where capitalization should be checked for inconsistencies:
        • Check capitalization of initial letters
        • Check consistency of global capitalization
        Check for bracketsSelect the Check brackets check box to have brackets verified for inconsistencies.
        Advanced Settings
        For each of the above elements, specify different warnings to mark how severe the unexpected behavior is: Note, Error, Warning.
      • Numbers: numbers, dates, times, measurements
      • Word list
        FieldOptions
        Basic Settings
        Word listToggle on Word list to add the wrong and correct form of words you want checked.
        Advanced Settings
        Specify a warning to mark how severe the unexpected behavior is: Note, Error, Warning.
        Search whole words onlySelect the check box to restrict the search to whole words.
        Ignore caseSelect the check box to perform the search irrespective of the word case.
      • Regular Expressions
        FieldOptions
        Basic Settings
        Regular ExpressionsToggle on Regular Expressions to add the default conditions which automatically check the differences between source and target content.
        Advanced Settings
        Specify a warning to mark how severe the unexpected behavior is: Note, Error, Warning.
      • Trademark check - Keep the trademark list as such or add more trademark symbols to the list.
        FieldOptions
        Basic Settings
        Trademark checkToggle on Trademark check to add the trademark symbols which are automatically identified.
        Advanced Settings
        Specify a warning to mark how severe the unexpected behavior is: Note, Error, Warning.
      • Length verification: limits, character counts, context.
        FieldOptions
        Basic Settings
        Check length limitationChoose an option:
        • Check if target segments are within file specific limits
        • Check if target segments are longer than character count - Add a numeric value for the character count.
        ContextsChoose an option:
        • Check all segment contexts
        • Check the following contexts (one per line) - Add the contexts in the box.
        Advanced Settings
        Specify a warning to mark how severe the unexpected behavior is: Note, Error, Warning.
    7. Under Verification > Terminology Verifier, configure how cloud terminology is checked in Trados Studio and in Trados Online Editor. Terminology Verifier is enabled by default, but you can toggle it off. To export your Terminology Verifier settings in a *.json file, select the three-dot icon, and then select Export settings. To import Terminology Verifier settings as a *.json file, select the three-dot icon, select Import settings, and load your file. The Terminology Verifier settings apply to a specific termbase included in the project. When you export the Terminology Verifier settings attached to a specific project termbase, you can import the settings only into the same project termbase. You cannot export the Terminology Verifier settings associated with a termbase and import them in a project where the Terminology Verifier settings are associated with a different termbase.
      For Trados Studio, terminology verification is performed only on the first cloud termbase included in the translation engine. For terminology verification to work correctly in Trados Studio, you must access the advanced settings and configure the Studio Settings section.
      For Trados Online Editor, terminology verification is performed on all cloud termbases in the translation engine. Terminology is validated interactively when confirming a segment in Trados Online Editor. Moreover, the settings specified as part of terminology verification are taken into consideration as part of the Translation Automated QA Check task and the Linguistic Review Automated QA Check task.
      Under Check for the following, select or clear the available settings. The settings under the Check for the following section apply to both Trados Online Editor and Trados Studio.
      • Possible non-usage of target terms - Select this option to check source segments for known terms. Where a term is found, the corresponding target segment is examined to ensure that the correct term translation (from the termbase) has been used. By default, faulty usage is marked by a Warning message.
      • Terms which may have been set as forbidden - Select this option to check that you are not using any terms expressly forbidden by this termbase. The information about whether a term is forbidden comes from the termbase itself. By default, faulty usage is marked by an Error message. Note that you must enable this option if you want to further enable the Studio Settings > Picklist Fields option and specify the fields which indicate whether a term is forbidden or allowed.
      • Terms without the target term equivalent - Select this option to check source segments for known terms for which there is no translation in the termbase. By default, faulty usage is marked by a Note message.
      Under Exclude the following, select or clear the available settings. The settings under the Exclude the following section apply to both Trados Online Editor and Trados Studio.
      • PerfectMatch units - Select this option to exclude locked segments translated by PerfectMatch from the verification.
      • Exact matches - Select this option to exclude segments translated with a 100% translation memory match from the verification.
      • Fuzzy matches down to 99% - Specify the value down to which fuzzy matches are excluded from the verification. Use the percentage box to specify a percentage match cut-off point. For example, if you specify a limit of 90%, then segments with a 90-99% match will be included in the check and segments with a 75-89% match will be excluded.
      • Locked segments - Select this option to exclude locked segments from the verification
      Under Studio Settings, specify the available settings. As the name suggests, the settings below apply to Trados Studio only.
      • Enable recognition of two-letter terms - Select this option to search for two-letter terms if your source file contains two-letter acronyms, such as the "UN" (United Nations).
      • Termbase - The name of the first termbase listed in the translation engine is displayed here in read-only mode.
      • Picklist Fields - Select the descriptive field which indicates if a term is forbidden or allowed. To enable this option, you must first select the Terms which may have been set as forbidden check box.
    8. Under Quality Management > Translation Quality Assessment Models, choose one of the available TQA profiles (or models). Once a project template contains a TQA profile, you can choose another TQA profile, but you cannot remove TQA profiles from your project template. If you configured a Linguistic Review task or a Customer Review task with at least one target language having TQA review mode, then you must select a TQA profile, so that users performing the review can apply the relevant categories and penalties.
  11. Select Create. Go back to the Project Templates list and identify your resource. Project templates are ordered alphabetically.