[Feature Request] LumApps connector support for non-English (multi-locale) content

arf

Summary

Please enhance the LumApps connector to fully support non-English content (e.g., Japanese) by:

• Correctly reading titles and body content from all available locales, not just English.
• Ensuring search results display the localized title instead of Untitled {documentType}.
• Ensuring results are always clickable, even if a localized title is missing (fallback to a URL-based title or generic label).

This is effectively a deal-blocking gap for customers whose primary content language is not English.

Current behavior

In LumApps instances where content is authored primarily in a non-English language (for example, Japanese):

• Documents whose title and body are in English index and display correctly in Glean.
• Documents whose title and/or body are in Japanese only appear in Glean search results as a generic
  Untitled {documentType}, with no clickable URL to open the original LumApps page.
• No meaningful content snippet is shown for those documents.

From investigation, this appears to be because the connector only uses the en locale field, effectively ignoring other locales such as ja, fr, de, etc.

Desired behavior

1. Multi-locale title and content support
   • The connector should read all locale key/value pairs from LumApps (e.g., ja, en, fr, de).
   • When rendering results in Glean, it should:
     • Prefer locale of choice.
     • If primary preference is not present, gracefully fall back to the first available non-empty locale
2. Always-show link behavior
   • Even if a title is missing or empty, the search result should still:
     • Display a clickable link to the LumApps document.
     • Use a sensible fallback (e.g., “View document” or a truncated URL) instead of a non-clickable Untitled {documentType}.
3. Consistent behavior across document types
   • The above should apply to:
     • Standard LumApps pages/articles.
     • Community posts and other content types supported by the connector.

Why this matters

For many customers, especially outside of English-speaking regions, the vast majority of intranet content is not in English. In these environments:

• If the connector only supports en, most of their LumApps content becomes effectively unusable in Glean:
  • Results appear as “Untitled”.
  • Links are not clickable, so users cannot open the source in LumApps.
  • Users cannot trust search coverage for their primary language.