Welcome to the Lionbridge Connector for Veeva Vault (“Connector”) version 1.0.0. The Connector enables you to manage the translation lifecycle effectively in Veeva Vault. The Connector facilitates built-in review work-flows in which, the files or documents pass through a review workflow before and after the translation. The translations are done quick and easy with this Connector.
This the multi-page printable view of this section. Click here to print.
Welcome to the Connector for Veeva Vault
- 1: The Translation Lifecycle
- 2: How the Connector Helps You Manage Your Translation Lifecycle
- 3: Using this Guide
- 4: How to Contact Lionbridge Connector Support
1 - The Translation Lifecycle
The translation lifecycle is the broad process of selecting content, sending it out for translation, and then receiving the translated content back from translation.
This set of steps usually fits inside a larger, more general process called the content lifecycle, which is the process of creating, reviewing, editing, approving, and publishing content.
When you consider the translation lifecycle and the content lifecycle together, you have the global content value chain, which is the strategy for managing multilingual content.
Remember that localizing content is a subset of steps in the broader content lifecycle. This will improve your focus on key localization considerations, improve processes, and keep all content stakeholders included. Together, this results in better content management.
2 - How the Connector Helps You Manage Your Translation Lifecycle
The Lionbridge Connector for Veeva Vault (Connector) is a plug-in module for Veeva Vault. The Connector features enable you to select, send, monitor, and retrieve content for translation into any language Veeva Vault supports.
These features automate the process, which reduces the effort and time required to export and re-import content that needs to be localized. This is very helpful when translating large volumes of content or ensuring that translated content is quickly re-imported to meet deadlines.
When you use the Connector, you manage your translation lifecycle entirely within the Veeva Vault:
- The Connector exports your content from Veeva Vault in XML format and delivers these content files to the Content API Platform.
- The Content API Platform delivers your content to your translation providers, based on routing rules that your company chooses and the Lionbridge Connector Team implements.
- When the translated content is ready, the Content API retrieves it from your translators and delivers it to the Connector.
- The Connector automatically re-imports the content into the correct location in Veeva Vault.
You can then review, revise, reject, or publish the translated content as needed.
Note: Neither the Connector nor the Content API performs any translation. Similarly, the Lionbridge Connector Team does not provide any translation services. Your company chooses the translation provider that performs the translation.
3 - Using this Guide
Purpose of this guide
This guide describes how to use the Lionbridge Connector (Connector) for Veeva Vault to manage your translation lifecycle. It describes how to send Veeva Vault components for translation and receive them back from translation.
Who should use this guide
This guide is intended for content editors, project, marketing, localization or translation managers, or others who are responsible for creating, editing, or approving content for translation that resides in your Veeva Vault CMS. This guide is also useful for translation providers who receive content from your Veeva Vault CMS, because it describes your company’s translation management process.
What your company setup should be
This document assumes that:
- Your company already has a functioning instance of Veeva Vault.
- The Lionbridge Connector for Veeva Vault (Connector) has been implemented, configured, and tested on your Veeva Vault CMS.
- The Lionbridge Connector Team has set up the Content API Platform to send content to your translation providers.
If Lionbridge is your company’s translation provider, it assumes that Freeway is already set up for your company.
What you should already know
This document assumes that:
- You are familiar with the Connector’s configuration for your Veeva Vault CMS, and the reasons for choosing certain configuration options. This is important because your company’s configuration determines which features are available.
- You have a strong working knowledge of the Veeva Vault Content Editor.
- You are familiar with your company’s translation process and requirements.
- You have valid user credentials to log into Veeva Vault.
- You have the required permissions to access the Connector functionality described in this guide.
Note: Not all the features described in this guide may be available. Feature availability depends on both your company’s Connector setup and the roles to which you are assigned. If you cannot access functionality that you need, contact your company’s Veeva Vault administrator.
How this guide is organized
This guide contains the following chapters:
|Welcome to the Connector for Veeva Vault||A brief description of the Lionbridge Connector for Adobe Experience Manager solution and how it fits into the translation lifecycle. It also includes information about this guide and Lionbridge Connector Support contact information.|
|Submitting Documents for Translation||How to use the Lionbridge Connector for Veeva Vault to send documents for translation.|
|Reviewing Translated Document||How to approve or reject the translated target document received.|
How to find out more about the Lionbridge Connector for Veeva Vault
For information on installing and configuring the Lionbridge Connector for Veeva Vault, read the Lionbridge Connector for Veeva Vault Installation and Configuration Guide.
This guide uses the following conventions:
|Bold||Highlights screen elements such as buttons, menu items, and fields.|
|Courier||Highlights input, file names, and paths.|
|Italics||Highlights terms for emphasis, variables, or document titles.|
|>||Indicates a menu choice. For example, “Select Admin Tools > Configuration.”|