Pulsar supports a multilingual experience designed to align with your users' preferred languages and regional settings. From app navigation and field labels to help text and error messages, Pulsar leverages Salesforce's built-in language features to deliver content in the language each user expects.

In addition to text translation, Pulsar also handles localization of dates, times, and currency formats, adapting dynamically based on device settings, Salesforce configurations, and currency preferences. Whether your team operates in a single country or across multiple regions, Pulsar ensures the app feels native to each user.

This guide outlines how language settings work, what is translated in Pulsar, and how localization is applied. Use it to optimize your setup and deliver a consistent, localized experience across devices and geographies.

Language Support

Pulsar reflects Salesforce translations (field labels, field values, etc.) out of the box without the user or admin having to do anything special since it displays Salesforce information as it receives on behalf of the user. It even can support custom labels if customizations within Pulsar rely on them.

Luminix translates Pulsar application-specific strings. For example (refer to the images below), the page loaded by the sync status button on the bottom left of the homepage screen or the settings page loaded by the gear icon on the bottom. These strings or button names or other messages or labels specific to the Pulsar app are translated and supported by Luminix. Here is the list of languages supported by the Pulsar application.

Languages Supported

Language Support Examples

Open

Open

Open

Open

Open

Localization

Luminix also localizes Date, Time, and Currency formats within the Pulsar app. Localization behavior is influenced by multiple settings, ensuring data reflects user expectations accurately. Pulsar automatically adapts to:

• Device language and region settings

• Salesforce server language and region settings

• Salesforce org currency settings

• Salesforce multi-currency settings, including both user currency and record currency

Localization Examples

Pulsar displays date/time formats adjusting to regional settings (e.g., MM/DD/YYYY for U.S. or DD/MM/YYYY for EMEA).

Open

Pulsar displays currency to show local symbols, decimals, and separators (e.g., €1.234,56 vs $1,234.56).

Open

Open

Recommendations

Pulsar is built to support the way your global teams work—whether that means displaying content in multiple languages or formatting data to match local conventions. By aligning with Salesforce and device-level settings, Pulsar helps ensure a seamless, localized experience for every user.

To get the most out of these capabilities, take time to test your configuration across different user profiles and regions. This ensures language and localization settings behave as expected and supports a more intuitive experience for your users worldwide.

• Test in your users’ context: Validate your implementation of Pulsar against device, Salesforce user, org, and record settings to ensure localization behaves as expected.

• Include international users in testing: Ensure a range of language-region-currency combinations are covered (e.g., German/EUR, Japanese/JPY, etc.).

• Review multi-currency scenarios: Where Salesforce multi-currency is enabled, confirm that both user-level currency and record-level currency formats are accurately reflected within the app.