Skip to main content

​
Overview

The Translations feature enables you to create multi-language versions of your apps, making them accessible to users worldwide. Elementum automatically translates field names using AI when you enable new languages, and provides tools for manual refinement and professional translation workflows.

​
Prerequisites

App Admin permissions are required to configure translations and manage language settings.
Before setting up translations, ensure you have:
1

App Admin Access

Required to configure language settings and manage translations in your app
2

Base Language Content

Your app should be fully configured in your primary language (typically English) with all field names finalized
3

Target Languages

Clear understanding of which languages your users need for optimal app experience

​
Setting Up Translations

1

Access Translation Settings

Navigate to your app’s translation configuration:How to Access:
  • Go to your App → Settings → Translations
  • Or access through the language menu (typically showing current language like “English”)
Translation settings are configured at the app level and apply to all users of that app based on their regional preferences.
2

Enable Languages

Configure which languages you want to support in your app:Language Selection Process:
  1. Click “Setup” or the language configuration option
  2. Review the setup dialog explaining automatic translation
  3. Select from Available Languages:

European Languages

  • French/Français
  • German/Deutsch
  • Spanish/Español
  • Italian/Italiano
  • Portuguese/Português

Global Languages

  • Japanese/日本語
  • And other supported languages
Setup Information:
  • Automatic Translation: Elementum will automatically translate your app using AI
  • New Content: When you add new fields and languages are enabled, they auto-translate
  • Manual Editing: You can always verify or edit AI-generated translations
  • Field Scope: Currently supports field name translations
Start with one or two languages to test the translation quality before enabling all needed languages.
3

AI Translation Process

Once you enable languages, Elementum automatically translates your app:What Gets Translated:
  • Field Names: All visible field labels in your app
  • Custom Field Labels: Any customized field names you’ve created
  • Form Elements: Field names in forms and data entry screens
  • Display Labels: Field names shown in record details and lists
AI Translation Features:
  • Context Awareness: AI understands field context for accurate translations
  • Consistency: Maintains consistent terminology across your app
  • Professional Quality: Business-appropriate translations suitable for professional use
  • Immediate Application: Translations are applied instantly after generation
Review AI translations carefully, especially for industry-specific terminology or branded terms that shouldn’t be translated.
4

Review and Edit Translations

After AI translation, review and refine the results:Translation Management Interface:
  • Language Selector: Choose which language to edit
  • Field List: View all translatable fields with original and translated names
  • Translation Status: See completion progress (e.g., “27/27” fields translated)
  • Edit Fields: Click on any translation to modify it manually
Editing Process:
  1. Select Language: Choose the target language from the dropdown
  2. Review Fields: Examine each field name translation
  3. Edit as Needed: Click on translations to modify them
  4. Save Changes: Apply your manual corrections
  5. Test Results: Verify translations appear correctly in the app
  • Industry Terms: Manually adjust technical or industry-specific terminology
  • Brand Names: Ensure brand names and product names remain consistent
  • User Context: Consider how your specific users would understand terms
  • Length Considerations: Some languages require more space than others
  • Technical Fields: Database terms, system fields, integration names
  • Business Terms: Company-specific processes, role names, status values
  • Abbreviations: Expand or localize abbreviated terms appropriately
  • Cultural Adaptation: Adjust terms for local business practices
5

Test User Experience

Verify that translations work correctly for end users:Testing Process:
  1. User Profile Settings: Ensure users can set their regional language preferences
  2. App Display: Confirm translated field names appear when users switch languages
  3. Functionality: Verify all app features work correctly with translated labels
  4. Consistency: Check that translations are consistent across all app areas
Users see translated content based on their regional settings in their User Profile, not based on browser language settings.

​
Professional Translation Workflow

For higher quality translations or specialized terminology, use professional translation services:

​
Download Translation Files

XLIFF File Export

Export your translations in industry-standard XLIFF format for professional translators.How to Download:
  1. Navigate to Translations settings
  2. Click “Download Language File” from the menu
  3. Select the target language
  4. Download the XLIFF file containing all translatable content
XLIFF File Benefits:
  • Industry Standard: Professional translators are familiar with XLIFF format
  • Context Preservation: Maintains field context and metadata for translators
  • Version Control: Tracks translation changes and maintains translation memory
  • Quality Assurance: Enables professional translation quality control processes

​
Working with Translation Companies

Preparation Steps:
1

Export Files

Download XLIFF files for each target language from your Translations settings
2

Brief Translators

Provide context about your business, industry terminology, and specific requirements:
  • Business Context: Explain your industry and target audience
  • Terminology Guidelines: Provide glossaries of important terms
  • Style Preferences: Specify formal vs. casual tone requirements
  • Brand Guidelines: Share brand names and terms that shouldn’t be translated
3

Quality Review

When you receive translated files back:
  • Terminology Check: Verify industry-specific terms are correct
  • Consistency Review: Ensure consistent terminology across all fields
  • Cultural Appropriateness: Confirm translations fit your target market
  • Length Validation: Check that translations fit within UI constraints

​
Upload Professional Translations

XLIFF File Import

Import professionally translated XLIFF files back into your app.How to Upload:
  1. Navigate to Translations settings
  2. Click “Upload Language File” from the menu
  3. Select your translated XLIFF file
  4. Review imported translations
  5. Save changes to apply professional translations
Post-Upload Process:
  • Review Changes: Check that all professional translations imported correctly
  • Test Functionality: Verify app functionality with professional translations
  • User Feedback: Gather feedback from native speakers using the app
  • Iterative Improvement: Refine translations based on user experience

​
User Experience

​
Language Display for Users

How Users See Translations:
  • User Profile Settings
  • App Interface
Users control their language experience through their profile:
  • Regional Settings: Users set their preferred language in User Profile
  • Automatic Application: App immediately displays in selected language
  • Personal Preference: Each user can choose their own language independently
  • Consistent Experience: Language choice applies across all apps they access
Language Switching:
  • Immediate Effect: Language changes take effect immediately
  • No Data Loss: Changing languages doesn’t affect stored data
  • Consistent Interface: All field names update to the selected language
  • Fallback Handling: Untranslated content falls back to default language

​
Translation Scope

Elementum translates most user-facing content automatically. Here’s what is and isn’t included in the translation system.
What Is Translated:
  • ✅ Field names and labels
  • ✅ Custom field names
  • ✅ Form field labels
  • ✅ Record detail field names
  • ✅ System buttons (Save, Cancel, Delete, etc.)
  • ✅ Navigation menus
  • ✅ System messages and notifications
  • ✅ Help text and descriptions
  • ✅ Validation error messages
What Is Not Yet Translated:
  • ❌ App Names
  • ❌ Section titles
  • ❌ Widgets on Workspaces
  • ❌ Workspace names and descriptions
Current Limitations: While most of the interface is translated, App Names, Section titles, and Workspace elements remain in their original language.

​
Managing Translations

​
Translation Maintenance

Ongoing Management Tasks:
When you add new fields to your app:
  • Automatic Translation: If languages are enabled, new fields auto-translate
  • Review Process: Check AI translations for new fields
  • Manual Adjustment: Edit translations as needed for accuracy
  • Update Professional Files: Re-export XLIFF if using professional translations
When you need to update existing translations:
  • Direct Editing: Modify translations directly in the interface
  • Bulk Updates: Use XLIFF export/import for major changes
  • Version Control: Keep track of translation changes over time
  • User Communication: Notify users of significant translation updates
Regular translation quality checks:
  • Native Speaker Review: Have native speakers review translations periodically
  • User Feedback: Collect feedback from users about translation quality
  • Consistency Audits: Ensure consistent terminology across all fields
  • Professional Updates: Periodically refresh with professional translation services

​
Performance Considerations

Translation Performance:
  • Loading Speed: Translations are cached for optimal performance
  • Memory Usage: Multiple languages don’t significantly impact app performance
  • Update Speed: Translation changes apply immediately without app restart
  • Scalability: System handles multiple languages efficiently
Best Practices:
  • Gradual Rollout: Enable languages progressively rather than all at once
  • User Training: Provide guidance to users on changing language settings
  • Feedback Channels: Establish ways for users to report translation issues
  • Regular Maintenance: Schedule periodic translation quality reviews

​
Troubleshooting

​
Common Issues

Possible Causes:
  • User regional settings not configured correctly
  • Language not enabled in app translation settings
  • Browser cache showing old content
  • Translation not completed for specific fields
Solutions:
  • Verify user has correct regional language in User Profile
  • Confirm target language is enabled in app Translation settings
  • Clear browser cache and refresh the application
  • Check translation completion status for the language
Possible Causes:
  • AI translation lacks business context
  • Technical terminology not translated appropriately
  • Industry-specific terms need manual adjustment
  • Cultural context not considered in AI translation
Solutions:
  • Manually edit problematic translations in the interface
  • Use professional translation services for critical content
  • Create terminology glossaries for consistent AI translation
  • Gather feedback from native speakers and adjust accordingly
Possible Causes:
  • File format corruption during download/upload
  • Translation software compatibility issues
  • Missing or incomplete translations in file
  • File encoding problems
Solutions:
  • Re-download XLIFF files if upload fails
  • Verify translation software supports XLIFF 1.2 or 2.0
  • Check that all required fields have translations
  • Ensure files are saved with UTF-8 encoding

​
Best Practices for Success

Planning Phase:
  • Language Priority: Start with languages most needed by your user base
  • Content Readiness: Finalize all field names before enabling translations
  • Resource Planning: Budget for professional translation if needed
  • User Communication: Inform users about upcoming language support
Implementation Phase:
  • Phased Rollout: Enable one language at a time to manage quality
  • Quality Control: Review all AI translations before making them live
  • User Testing: Have native speakers test the translated interface
  • Feedback Collection: Establish channels for translation feedback
Maintenance Phase:
  • Regular Reviews: Schedule periodic translation quality assessments
  • User Feedback Integration: Continuously improve based on user input
  • Professional Updates: Refresh professional translations periodically
  • Documentation: Maintain records of translation decisions and changes

​
Integration with User Management

​
User Regional Settings

Profile Configuration:
  • Language Selection: Users set preferred language in their profile settings
  • Regional Preferences: Language choice can be part of broader regional settings
  • Default Behavior: New users may inherit organization default language
  • Individual Control: Each user controls their own language experience
Administrative Control:
  • Default Language: Admins can set organization-wide default language
  • Available Languages: Admins control which languages users can select
  • Migration Support: Tools to help users transition to new language options
  • Bulk Updates: Administrative tools for managing user language preferences

​
Multi-Language Organizations

Global Team Support:
  • Mixed Language Teams: Team members can use different languages simultaneously
  • Collaboration: Work together effectively despite different interface languages
  • Data Consistency: Underlying data remains consistent regardless of display language
  • Communication: Consider how language differences affect team communication
Reporting and Analytics:
  • Language Usage: Track which languages are most used by your organization
  • Translation Quality: Monitor user satisfaction with translations
  • Performance Impact: Assess any performance implications of multi-language support
  • Cost Analysis: Understand the cost-benefit of supporting multiple languages
By implementing the Translations feature, you can make your Elementum apps accessible to users worldwide, improving user experience and expanding your app’s reach to global teams and customers.
⌘I