# Localization in Infinity 25: Bundles, not scattered rules

**URL:** <https://forums.pega.com/t/localization-in-infinity-25-bundles-not-scattered-rules/10520>\
**Category:** Knowledge Share\
**Created:** [January 15, 2026, 5:40am UTC](https://forums.pega.com/t/localization-in-infinity-25-bundles-not-scattered-rules/10520 "2026-01-15T05:40:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![akuls](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/akuls/32/23686_2.png) [@akuls](https://forums.pega.com/u/akuls)\
**Post date:** [January 15, 2026, 5:40am UTC](https://forums.pega.com/t/localization-in-infinity-25-bundles-not-scattered-rules/10520/1 "2026-01-15T05:40:27Z")

</div>

Infinity 25 changes localization in a big way. Instead of maintaining individual localization rules per view, portal, or paragraph, localization is now handled through **bundles**. A **bundle** is a centralized localization rule that aggregates labels for an application. Internally, bundles are instances of **`Rule-UI-Localization`**. This makes localization easier to manage, export, translate, and serve at runtime.

## The three localization bundles in Infinity 25

Infinity 25 uses three bundle types.

### 1) Base bundle (system-generated)

The **base bundle** is the source-of-truth catalog of labels for the application.

- **Instance of** : `Rule-UI-Localization`

- **Context** : `bundle`

- **Label** : typically `<pyProductName>`

- **Applies to** : `@baseclass`

- **Creation** :

- **Used for** :

- **Important** : **do not edit manually**. Treat it as generated output.

### 2) Language bundle (runtime-served)

The **language bundle** stores translations and is what the runtime uses to render localized UI for a user.

- **Instance of** : `Rule-UI-Localization`

- **Context** : `bundle`

- **Label** : typically `<pyProductName>_<langCode>` (example: `AcmeClaims_fr-FR`)

- **Applies to** : `@baseclass`

- **Populated by** : importing translated Excel/JSON

- **Runtime behavior** :

### 3) Overrides bundle (client-owned extension)

The **overrides bundle** is a client-owned extension point. It’s where clients add their own message groups (like `MESSAGES`, `STATUSWORK`, etc.) so those labels participate in the standard export/import workflow.

- **Instance of** : `Rule-UI-Localization`

- **Context** : `overrides`

- **Label** : client-defined

- **Applies to** : `@baseclass`

- **Must be created by** : the client

- **Critical ordering** :

- **Language requirement** : overrides must be authored in the **base language** (typically English)

- **Effect** : labels from overrides are included when the base bundle is generated

Example overrides format:

```auto
{ "MESSAGES": { "my custom message": "my custom message" }, ... } 

```

## Built-on applications: the recommended approach (centralized translations)

Bundle localization also changes how translation is handled in built-on stacks. To keep things simple and predictable, the recommended pattern is to **centralize translations in the top-most application**.

### Example built-on stack

| Layer | Application | Purpose |
| --- | --- | --- |
| Top | `AcmeClaims` | Client-specific claims experience and UI customization |
| Middle | `ClaimsAccel` | Shared claims accelerators and patterns |
| Base | `Constellation` / platform | Constellation UI foundation |

In this model:

- Labels can originate in any layer (platform, accelerators, or client app).

- Translation ownership stays in one place: the top-most application.

### What you do

1. Generate a **base bundle** for each application in the stack

2. Create **language bundles only for the top-most application**

3. When generating translations from the top-most application, set:

### What this really means

- The top app becomes the single place where translation files are produced and imported.

- When labels change in lower layers, you regenerate translation inputs from the top and keep your workflow consistent.

- Teams don’t have to coordinate translations per layer.

## Migration From Infinity 24

Most existing applications will need a one-time migration step to move from legacy localization artifacts to bundles.

- **Migration activity** : Rule-UI-Localization.pxMigrateToLocalizationV2

- **What it does** : T`his will merge the existing translations to make it a bundle. Always provide the`

- **When to run** : Once environment is migrated.

- **Validation** : `Success message from the activity`

If you’re working with library-sourced labels or conditional paragraphs in Constellation, I’ve written a step-by-step guide that shows exactly how to translate the generated HTML files in the language pack and get the results at runtime:  
[https://community.pega.com/conversations/user-experience/infinity-25-localization-guide%3A-translating-dynamic-text-rules-and-decisioned-paragraphs](https://community.pega.com/conversations/user-experience/infinity-25-localization-guide%3A-translating-dynamic-text-rules-and-decisioned-paragraphs)

**Important notes :**

- During localization work, always use an **open ruleset** (or enable **branching** ) so bundle generation and updates can be saved cleanly without ruleset lock issues.

- Before you start, verify that the **top-most ruleset in the application ruleset stack actually exists in the application** (and is available). If it’s missing, rule creation can fail or land in an unexpected ruleset.

- If you’re using branching and you create a language bundle inside a branch, you have two clean ways to test it:

- Any issues with “re-translate all layers”, please install HFIX-C4425 in your system..

---

<div class="post-metadata">

**Author:** ![josenavas](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/josenavas/32/23453_2.png) [@josenavas](https://forums.pega.com/u/josenavas)\
**Post date:** [January 19, 2026, 11:04pm UTC](https://forums.pega.com/t/localization-in-infinity-25-bundles-not-scattered-rules/10520/2 "2026-01-19T23:04:07Z")

</div>

@akuls Hello Sai,

What is Pega’s recommended approach for applications that continue to evolve over time—for example, apps where new views are added or existing ones are updated in future releases?

On the current App Studio localization landing page, I noticed that once a language pack is imported, the status changes from **Ready for translation** to **Complete**. This raises a question:

If in Release 1 (R1) we localized the application in French, and then in Release 2 (R2) we introduce a new view that also requires French translation, what is the correct process? Do we need to regenerate the base bundle, re-import the updated language pack, and then validate the translations carried over from R1?

Also, I want to add that the new localization enhancements coming in Infinite 25 seem like a significant improvement to how localization is managed in Pega.

Thanks,

_-Jose_

---

<div class="post-metadata">

**Author:** ![akuls](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/akuls/32/23686_2.png) [@akuls](https://forums.pega.com/u/akuls)\
**Post date:** [January 20, 2026, 3:51am UTC](https://forums.pega.com/t/localization-in-infinity-25-bundles-not-scattered-rules/10520/3 "2026-01-20T03:51:51Z")

</div>

Hey @josenavas with every release you can delete the current language pack from the language pack screen in app studio and then create a new french bundle. Your translations from R1 will be auto-populated in the excel/json. The labels from R2 release will be blank.

note: with every language pack generation we will see couple of binary file instances make sure they are in open ruleset when your performing the above process.

---

<div class="post-metadata">

**Author:** ![josenavas](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/josenavas/32/23453_2.png) [@josenavas](https://forums.pega.com/u/josenavas)\
**Post date:** [January 29, 2026, 9:56pm UTC](https://forums.pega.com/t/localization-in-infinity-25-bundles-not-scattered-rules/10520/4 "2026-01-29T21:56:39Z")

</div>

@akuls Thanks Sai.

I have an additional question that may be more of a feature request. According to the Pega documentation, if the application does not contain a Ruleset for the user’s selected locale, the UI defaults to English. This means the **default locale** works as a fallback—for example, if a user’s locale is en\_GB, the UI displays correctly in English.

However, it would be very useful to define a default locale **other than English**. For instance, if we set es\_ES as the default locale for Spanish, then users accessing the application from Mexico (es\_MX) would still see the UI in Spanish even if that specific locale is not configured (no rulesets for that locale).

Thank you for your consideration.

Regards,

_-Jose Navas_

---

<div class="post-metadata">

**Author:** ![josenavas](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/josenavas/32/23453_2.png) [@josenavas](https://forums.pega.com/u/josenavas)\
**Post date:** [March 15, 2026, 7:37pm UTC](https://forums.pega.com/t/localization-in-infinity-25-bundles-not-scattered-rules/10520/5 "2026-03-15T19:37:52Z")

</div>

@akuls Hello Sai,  
regarding the migration from Infinity 24, in that version we used custom field labels which were replaced for dynamic text rules in Infinity 25. My question is, once we migrate from Infinity 24 to Infinity 25, are the custom field labels converted to dynamic text rules automatically? or existing views will preserve the custom field labels, and only for new views we will see the dynamic text rules.

Thanks,

_-Jose_

---

<div class="post-metadata">

**Author:** ![akuls](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/akuls/32/23686_2.png) [@akuls](https://forums.pega.com/u/akuls)\
**Post date:** [March 16, 2026, 6:58am UTC](https://forums.pega.com/t/localization-in-infinity-25-bundles-not-scattered-rules/10520/6 "2026-03-16T06:58:32Z")

</div>

custom field labels will remain as is Jose.
