Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction
  3. Configuring the Data Director Application
  4. Establishing a Root Node
  5. Defining the Business Entity Model
  6. Configuring Business Entity Properties
  7. Configuring Reference Entity Properties
  8. Transforming Business Entities and Views
  9. Configuring Hierarchy and Network Relationships
  10. Creating Match Rule Sets
  11. Configuring Search
  12. Configuring Tasks
  13. Configuring Security and Data Filters for Business Entities
  14. Configuring the Content Security Policy
  15. Integrating Data as a Service
  16. Configuring External Calls
  17. Designing the Data Director User Interface
  18. Localizing Data Director
  19. Appendix A: Provisioning Tool Frequently Asked Questions

Provisioning Tool Guide

Provisioning Tool Guide

Back Next

Localizing Task Actions, Types, and Messages

Localizing Task Actions, Types, and Messages

Task actions, task types, and task action messages are part of the metadata. Define the task metadata in the
besMetadata.properties
 file.
  1. Click
    Configuration
    General Settings
    , and then select
    Metadata Localization
    .
  2. Click
    Metadata Localization
    .
  3. In the
    Metadata Localization
     panel, under
    Metadata Bundle
    , click
    Export
    . The
    besMetadata.zip
     template file downloads.
  4. Unzip the file, and open the
    besMetadata.properties
     file in an editor of your choice.
  5. Add the task action and task action message properties. Edit the task type properties.
    Use the following syntax for the task properties:
    Property Type
    Syntax
    French Localization Example
    Task action
    taskaction.<Task action>=<Localized task action>
    taskaction.Cancel_Task=Annuler la tâche
    Replace white spaces in task action names with an underscore. In the example, the white space in
    Cancel Task
     is replaced with an underscore,
    Cancel_Task
    .
    Task type
    tasktype.<Task type>=<Localized task type>
    tasktype.AVOSBeMerge=Fusionner
    To know which task name to add, you must be aware of the predefined MDM workflows that are deployed to the ActiveVOS server as processes.
    Task action message
    taskactionmessage.<Task action configuration>.<Task action>=<Localized message>
    taskactionmessage.TypicalConfig.Escalate=Vous êtes sur le point de transmettre la tâche à votre responsable.
  6. Save the properties file with the appropriate language code and country code suffix.
    For example, to localize metadata in Canadian French, the language code is
    fr
     and the country code is
    CA
    . Save the file as
    besMetadata_fr_CA.properties
    .
  7. Compress the
    besMetadata.properties
     file and all the localized property files, such as besMetadata_fr_CA.properties, into a ZIP file named besMetadata.zip.
  8. In the
    Metadata Localization
     panel, under
    Metadata Bundle
    , click
    Import
    . The
    besMetadata.zip
     template file is imported.
0 COMMENTS
We’d like to hear from you!