XTM is an enterprise translation management system and cloud-based TMS platform popular among enterprises and language service providers. BeLazy supports integration with XTM through two distinct user scenarios: project manager and linguist roles, each with specific capabilities and access levels. 

Use cases:

BeLazy supports integration with XTM through a comprehensive connector that enables seamless translation project management. There are two main use cases where the XTM integration comes in handy:

  • You have an instance of XTM where you create projects manually or automatically via content connectors or the API, and would like these jobs to automatically appear in the business management system,
  • Your customer sends you work via XTM assignments, and you want to automatically pick them up in your business management system.

BeLazy connects XTM with any business management system or tracker, and allows:

  • Project and job listing with all details, including analysis and metrics,
  • Extracting XLIFF files for each XTM job for offline translation workflows,
  • Project creation in a business management system or tracker,
  • Linguist assignment monitoring in XTM, and reassigning linguists in the business management system or tracker,
  • Linguist assignment monitoring in the business management system or tracker, and reassigning linguists in XTM,
  • Delivery monitoring in XTM, and closing the corresponding jobs in the business management system or tracker,
  • Delivery monitoring in the business management system or tracker, and uploading the translated XLIFFs to XTM.


Integration type:

The XTM integration impersonates users through the internal APIs used in the client-server communication. This implementation was chosen because it allows integration to work with both project manager and linguist roles, whereas linguists normally do not have access to APIs. The integration supports 2-factor authentication. Having the XTM APIs is not a requirement.


Requirements:

You need your XTM username, password, and company name, and optionally your license name. The integration requires appropriate user permissions based on your role - project managers have full access while linguists have restricted capabilities matching their XTM permissions. 


Expected URL format:

The URL format depends on your XTM Cloud instance. Use your custom XTM Cloud URL. For most cloud instances, you can use https://www.xtm-cloud.com/. If you have difficulties logging in, let us know.


XTM-specific configuration:

  • Company name: Enter your XTM company identifier. You can find this information in the login page of your XTM system. This is required to establish the connection to your specific XTM instance.

  • License (optional): During the login to XTM if you have given a choice to select a license, enter the name of the license. This field can be left blank if your XTM instance doesn't require license selection.

  • Enable XLIFF workflow: Check this option to enable XLIFF-based workflow processing. This allows BeLazy to download and upload XLIFF files and manage the associated workflow states within the XTM system.

  • User type selection: Select your account preferences. This is only necessary if the account possesses both project manager and linguist capabilities simultaneously. Choose "Project manager" for PM access or "Linguist" for translator access, depending on your primary role and the permissions you want BeLazy to use. The integration automatically detects user roles and provides appropriate functionality if only one user type is available.

  • Project download options: Configure which XTM projects BeLazy should pick up. Choose List all projects to monitor all accessible projects, or select List my projects only to only list the projects assigned to the specific project manager. Note: this setting is often the source why certain projects do not appear in BeLazy.

  • XLIFF upload approve segment status type: Select the segment status type for XLIFF upload approval. Upon uploading XLIFF, XTM "cleans up" these files into the translation memory. This setting determines which segments will be processed when uploading completed translations back to XTM.

Functionalities and connector-specific information:


XTM for Project Managers:

  • Unit of acceptance: Project per target language in the project manager integration
  • Multiple target languages: Supported - each target language creates a separate job with bundling available
  • Specialization, End Client, Workflow, Analysis: Extracted from project metadata and metrics
  • Project exclusion: Not supported
  • Download files: XLIFF files are downloaded and uploaded
  • Delivery: Monitoring of XTM workflow completion, delivering XLIFF files and closing XTM jobs, automatic status synchronization
  • Linguist assignment: Bidirectional monitoring and assignment
  • Vendor creation: Not supported - vendors must be manually created in XTM
  • Project bundling: Supported
  • 2-factor authentication: Supported
  • Pricing: Analysis extracted from project metrics, but pricing calculated by business management system
  • Analysis creation: Can trigger XTM analysis processes and extract comprehensive metrics
  • Connector-specific data extracted: See here

XTM for Linguists:

  • Unit of acceptance: Job (individual assignments can be bundled)
  • Multiple target languages: Only with bundling. Individual jobs represent single language pairs
  • Project metadata: Limited to information available through linguist interface
  • Project exclusion: Not supported
  • Download files: XLIFF package download for assigned jobs
  • Upload files: XLIFF upload for job completion and delivery
  • Delivery: Job completion monitoring and status updates
  • Linguist assignment: Not applicable - linguist receives pre-assigned work
  • Vendor creation: Not supported
  • Project bundling: Supported for managing multiple job assignments
  • 2-factor authentication: Supported
  • Pricing: Not supported - handled by business management system
  • Analysis creation: Cannot create analyses - uses existing project analyses
  • Connector-specific data extracted: See here