URL mapping for different languages without change in URL
under review
Uppili Srinivasan
We have a requirement to configure URL mapping in the widget for multiple languages using the same application URL.
Currently, our applications support language selection:
* In some cases before login
* In others after login
However, the URL does not change when the language is switched.
Expected behavior
* When a user is in a specific module and language (e.g., English), the widget should display the mapped article in that language.
* If the user changes the language (e.g., to German), the same article should automatically load in the selected language
Current limitation
* Document360 URL mapping relies on URL changes (e.g., language codes in the URL)
* Since our application URL remains the same across languages, we are unable to map articles dynamically based on language selection
Request
We would like this to be considered as a product enhancement where URL mapping (or widget behavior) can support "language-based article mapping without depending on URL changes"
Log In
D
D360 Product Management
marked this post as
under review
K
Kavya
Hi Innovative Cod,
Thank you for sharing this detailed use case.
We understand the challenge where your application does not change the URL when switching languages, which limits the current URL-based mapping behavior in the widget.
Today, Document360’s widget mapping relies on URL patterns (including language codes) to determine which article to display. In scenarios where the URL remains the same across languages, the widget does not have a native way to identify the active language context.
Your expectation—to dynamically load the same mapped article in the selected language without relying on URL changes—is valid, especially for applications where language selection is handled internally (pre- or post-login).
We’ll take this as an enhancement request and evaluate the feasibility of supporting:
Language-based article mapping independent of URL structure
Possibly leveraging external signals (e.g., widget configuration, API, or context passed from the host application)
This will be reviewed based on priority, implementation scope, and customer traction.
We’ll share updates once we have more clarity from our evaluation.
Uppili Srinivasan
+ @@ {65ddc0940129d7ae442ea98e|alias}