Localizing Case-Level Data in Constellation Views

Overview

The Localized Text component is a display-only Constellation DX component for rendering localized case-level values.

Use it when case data contains a known value, such as a case label, stage name, or status, but the UI should display the translated text for the user’s current locale.

Typical use cases include:

  • Case labels in list views
  • Stage names in case summaries
  • Status values in Details tabs or other read-only views
  • Other predefined case-level values that have corresponding localization resources

The component is intended for display scenarios only. Do not use it as a replacement for editable field components.


How it works

The component receives the value of the configured field and resolves its localized representation using the case’s localization context.

The localization context is determined from:

  • the current case, when rendered inside a case, or
  • the case class associated with the row, when rendered inside a list

For example:

Plain Text

Field value: Pending-Approval

Case class: MyOrg-Loan-Work-Application

Current locale: fr_FR

Localized Text

↓

Localization lookup using the case context

↓

Translated text

If a matching localization resource is available, the localized value is displayed.

If no localized value can be resolved, the component falls back to displaying the original field value.

The component does not generate translations. The corresponding localization resources must already exist in the application.


When to use Localized Text

Use Localized Text when:

  • The value comes from case-level data.
  • The value represents known application text.
  • A localized version of the value exists or can be configured.
  • The value only needs to be displayed.

Examples:

Scenario Example
Case label Create Account
Stage Verification
Status Pending-Approval
Shared case text Known application-defined values

Do not use it when

Use the normal component instead when:

  • The user needs to edit the value.
  • The value contains user-generated text.
  • The value does not represent a known localization value.
  • You need behavior beyond rendering localized text.

Using Localized Text in a view

Configure Localized Text as the display renderer for the case-level field that needs localization.

For example, a list might contain:

Plain Text

Case ID Case Label

C-1001 Create Account

C-1002 Review Application

The case label field can use Localized Text, while the Case ID continues to use its existing renderer.

Similarly, in a read-only Details view, Localized Text can be used for fields such as:

  • Case label
  • Stage
  • Status

Other fields in the view can continue using their existing components.


Installing and enabling the component library

1. Download the component library

Download the component ZIP from the provided GitHub repository.

Sign in to Pegasystems · GitHub


2. Import the ruleset

Import the downloaded component ruleset ZIP into the target Pega application.

After the import completes, verify that the ruleset is available in the system.


3. Add the ruleset to the application

Add the following ruleset version to the application’s ruleset stack:

Plain Text

LocalizationComponents:01-01

Save the application definition after adding the ruleset.


4. Enable the component library

In the application, navigate to Configure and search for Component libraries.

Locate the imported localization component library and enable it for the application.

Pega’s official instructions for making a library-mode DX component available to an application are here:

Adding library mode Constellation DX components to an application [docs.pega.com]

For general information about custom Constellation components, see:

Creating Constellation DX components [docs.pega.com]

Pega recommends custom DX components for advanced scenarios that cannot be addressed through out-of-the-box Infinity Studio configuration, because custom components introduce additional maintenance, upgrade, accessibility, and compliance considerations. [docs.pega.com]


5. Configure the component in the view

Open the required Constellation view, for example the Details tab.

  1. Add or select the case-level field that needs localization.
  2. Configure Localized Text as its display component.
  3. Bind it to the required case property.
  4. Save the view.

For example:

Plain Text

Details

├─ Case label → Localized Text

├─ Stage → Localized Text

├─ Status → Localized Text

└─ Case ID → Existing component

you can change the Display As component as shown below screenshot


6. Verify localization

Run the application using the required locale and verify that:

  • The case label is localized.
  • Stage and status values resolve correctly.
  • List rows use the correct case context.
  • Missing localization entries fall back to the original value.
  • Editable fields continue to use their normal input components.

Testing this in the actual list or Details view is important because localization resolution depends on both the case context and the localization resources available for that value.


Summary

Use Localized Text when a case-level value needs to be localized for display without changing the underlying case data.

The intended flow is:

Import component library → Add LocalizationComponents:01-01 → Enable component library → Configure Localized Text on the field → Verify with the target locale

This keeps localization at the presentation layer while allowing the underlying case property to retain its original value.

2 Likes

Hello @akuls

Good detailed article.

I have a question here. OOTB localization bundle in v25 and v26 provides localized text already for all of the fields, labels, etc on the case already without modifying the underlying data on the case.

So what kind of additional feature is this component bringing on to the table?

Because i need to setup this component for each and every field rendered on the UI for showing up the localized content.

Regards

JC

@akuls thanks for the knowledge share! I have added it to our constellation 101 series.

Enjoyed this article?

See suggested articles from our Constellation 101 series and view all our Knowledge Shares from our User Experience Expert Circle.

Jay, capturing a case label in the case context does not automatically make its value localizable. OOTB DX components intentionally render the value as provided without applying localization.

The screenshot demonstrates this using the same case-label property: green uses the custom DX component, while red uses the OOTB component. Where localized case-label values are required, the custom DX component can be used.