Skip to main content

Multi-Language Documentation

aprity generates documentation in six languages, allowing you to produce Salesforce documentation that matches your organization's primary language. All AI-generated content, section headings, labels, and structural text are translated into the selected language.

Supported Languages

LanguageCode
Englishen
Frenchfr
Spanishes
Germande
Italianit
Portuguesept

How Language Selection Works

Language is selected per scan in the Generate tab before launching documentation generation.

  1. Open the Generate tab in the aprity app.
  2. Select your preferred language from the language dropdown.
  3. Configure the remaining scan options (output format, analysis toggles).
  4. Click Generate Documentation.

The entire documentation output is produced in the selected language. This includes:

  • Section headings -- "Business Rules," "Dependencies," "Technical Details," etc.
  • Labels and badges -- rule type labels, status badges, KPI card labels.
  • AI-generated content -- business rule descriptions, object summaries, and process explanations.
  • Navigation elements -- table of contents entries, index page links.
note

Language selection applies to the entire scan output. You cannot produce a single scan with mixed languages. To generate documentation in multiple languages, run separate scans -- one per language.

Plan-Based Language Access

Not all plans have access to all languages.

PlanAvailable Languages
TrialAll 6
StarterEnglish only
ProfessionalAll 6
EnterpriseAll 6
info

The Starter plan is limited to English. If you need documentation in other languages, upgrade to the Professional plan, which includes all six languages.

Translation Quality

Structural Text

Section headings, labels, and navigation text are translated using a curated translation system. These translations are pre-defined and consistent across all scans. They are not AI-generated -- they come from a maintained translation catalog that covers all user-visible text in the documentation.

AI-Generated Content

Business rule descriptions, object summaries, and process explanations are generated by the AI in the selected language. The AI produces native-quality text rather than translating from English. This means:

  • Descriptions are idiomatic in the target language.
  • Technical Salesforce terminology is preserved (e.g., "Trigger," "Flow," "Validation Rule" remain in their standard form when no established translation exists).
  • Business context and explanations are written naturally in the selected language.
tip

If your organization uses specific terminology in the target language, review the generated documentation to verify that the AI's word choices align with your internal glossary.

Salesforce API Names

Salesforce API names (object names, field names, automation names) are never translated. They appear in their original form regardless of the selected language. For example:

  • The object Custom_Object__c remains Custom_Object__c in all languages.
  • The field Account.AnnualRevenue remains Account.AnnualRevenue.
  • The trigger OpportunityTrigger remains OpportunityTrigger.

This preserves traceability between the documentation and the Salesforce metadata.

Multi-Language Workflows

Producing documentation in multiple languages

If your organization operates in multiple languages, run separate scans for each language. Each scan produces a complete documentation set in the selected language.

Comparing across languages

Since the underlying metadata and analysis are deterministic, documentation in different languages covers the same objects and rules. Only the language of the explanatory text differs.

When to Use Multi-Language

  • Your team operates in a non-English language and needs documentation that stakeholders can read without translation.
  • You are producing compliance documentation that must be in the local language of the operating entity.
  • You support multiple regions and need the same documentation in several languages.
  • You are onboarding new team members who are more comfortable reading documentation in their native language.