🚀 Translate Once, Reach Everyone: Oracle APEX 26.1 Application Translation

-

🚩Introduction 

  • In modern Oracle APEX applications, it is important to make the app usable for people who speak different languages. Oracle APEX 26.1 introduces a simple way to do this called Application Translations using Text Messages. 

  • With this feature, developers can build the application in their primary language first, then convert the labels and other text into reusable Text Messages. These text messages can be exported, translated, and imported back, so the same application can run smoothly in multiple languages without extra effort.

📑 Why This Approach Is Needed

In Oracle APEX applications, users from different regions often need the app in their own language. Doing this manually by creating separate copies of the application can take time, cause mistakes, and become hard to maintain.

Using Text Message based translations becomes important when:

  • Applications need to support more than one language

  • Text needs to stay consistent and easy to update

  • Translations need to be shared with external translators using standard formats like CSV or XLIFF

  • Developers want to manage all languages from a single application

  • A simple and reliable translation process is important

This approach helps developers work faster, avoid duplicate applications, and makes the overall translation process smoother while keeping everything simple and well integrated in Oracle APEX.

👉 Use Case: Application Translations in Oracle APEX 26.1

In Oracle APEX, developers often need to make one application available in multiple languages, such as English, Spanish, or Arabic. With Application Translations, developers can enable translation from Shared Components, convert the application text into Text Messages, and define the target languages.

In this blog, we will see how Application Translations can be used in Oracle APEX 26.1 to export text messages, get them translated, and import them back into the application. It helps developers manage multiple languages from one place, making the app more accessible and easier to maintain.

Step 1: 

First we need to enable the application translation, to do so, go to Shared Component-> Globalization Attributes -> Enable Translate Application and select the Translation method as Text Message Based.

Step 2: 

Next, Go the Shared Components -> Application Translations, click on the add language and select the language which you want.

Step 3: 

Once the language is added, click on the Export Text Messages and download as XLIFF/CSV file

Step 4: 

Now, Translate the contents in the downloaded file using any AI Tools (Claude / Chatgpt) and again import it using Import Text Messages option in the Shared Components -> Application Translations

Step 5: 

Once the required languages were added, translated and imported into the application, then go the Shared Components -> Application Items, create new application item (G_LANG_PREFERENCE).

Step 6: 

Next, Go to the Shared Components -> Globalization and select the property Application Preference (use FSP_LANGUAGE_PREFERENCE) from the Translation Language Derived From.


Step 7: 

Now, Go the Shared Components -> Application Process, create the process of type (On Load: Before Header) and copy paste the code below.

BEGIN
  APEX_UTIL.SET_PREFERENCE(
        p_preference => 'FSP_LANGUAGE_PREFERENCE',
        p_value      => :G_LANG_PREFERENCE -- Application Item
    );
  apex_util.redirect_url(p_url=>'&APP_PAGE_ALIAS.' || '?session=' || '&APP_SESSION.');
END;


And in the conditions section, select the condition type as Request = Expression 1 and in the Expression1 LANG

Step 8: 

In the Global Page (0), create the Radio button / Select List with the languages you want to switch between, it should return the respective language codes (like for english : en and tamil : ta). Create the dynamic action for that page item and create the action as Execute Server-side code action and copy paste the below code. Create one hidden page item to store the url.

DECLARE
    l_url VARCHAR2(4000);
BEGIN
    l_url := apex_page.get_url(
        p_page    => :APP_PAGE_ID,
        p_request => 'LANG',
        p_items   => 'G_LANG_PREFERENCE',
        p_values  => :P0_LANG -- Page Item ('ar-om')
    );

    :P0_URL := l_url; -- hidden page item
END;

create the another action as Execute JavaScript Code action and copy paste the below code. This is used to reload the page with the request Lang and it switches between the selected languages.

window.location.href = apex.item("P0_URL").getValue();

Step 9: 

Now, save and run the page, you will see the radio button / select list page item, there you can switch between the languages, once you select different language then the page is translated into the desired language.

🔥 Conclusion

Thus, in Oracle APEX 26.1, Application Translations using Text Messages allows developers to easily manage multiple languages in a single application. This makes it simple to export, translate, and import text using standard formats, reduces manual effort, and improves usability for users across different languages.


Comments

Post a Comment

Popular posts from this blog

🔍 Extending Smart Search Filter for Multiple Regions

-
Image
🚩Introduction  In Oracle APEX, the Smart Search filter is a convenient feature that allows users to quickly search data in a Classic Report or Cards region without writing custom code. However, this functionality is limited to a single region , which can be restrictive when a page contains multiple regions that should respond to the same search input. In this tutorial, you will learn how to extend the Smart Search filter to work with multiple regions on the same page . We will implement a solution that allows one Smart Search input to drive filtering across multiple Classic Report ,Cards regions etc. By the end of this tutorial, you’ll have a clear, reusable approach for coordinating search behavior across regions, improving both usability and consistency in your Oracle APEX applications without breaking the declarative nature of APEX. 📑 Why Extending the Smart Search Filter Is Needed The built-in Smart Search filter in Oracle APEX works well when a page contains a single sear...
Read more

📌Track Active Tab switch in Region Display Selector without any plugins

-
Image
🚩Introduction  In Oracle APEX applications, Region Display Selector components helps to organize multiple regions efficiently. However, APEX does not provide a built-in declarative option to detect which tab is active when users switch between them, making it challenging to trigger conditional logic based on tab selection. This can be solved by creating the custom dyanamic action to capture the tab change. This approach enables dynamic actions like refreshing regions or executing custom logic whenever a tab becomes active, without requiring any plugins. 📑Why It is Essential to Track Tab Selection in Region Display Selector In APEX applications, pages often organize multiple regions under a Region Display Selector to separate content like Details, History, or Reports. While this improves layout, users actions on different tabs often require specific logic to run, such as refreshing a region, loading dynamic content, or updating page items. Without capturing which tab is active, de...
Read more

💡 Designing Dynamic QuickPicks in Oracle APEX

-
Image
🚩Introduction  Oracle APEX provides Quick Picks as a convenient way to allow users to populate page items with predefined values using a single click. While static Quick Picks are useful, real-world applications often require these values to be generated dynamically based on business rules, user roles, or underlying data. This blog explores how to implement Dynamic Quick Picks in Oracle APEX page items , enabling developers to build more intelligent, flexible, and user-friendly forms by driving Quick Pick values directly from database queries and runtime logic.  📑 Why Dynamic Quick Picks Are Needed   Static Quick Picks in Oracle APEX are useful for simple filtering, but Dynamic Quick Picks become essential when: Filter values must be generated at runtime based on current data, user role, or context Applications require data-driven filters instead of hardcoded values The same Quick Picks must adapt across multiple pages or regions Filter options depend ...
Read more