Configure Localized Text and verify language fallback

1. Open the current behavior editor

Select a text-capable shape. In Behavior Browser, drag Text → Localized Text onto it; double-click an existing binding to edit it. This editor has no Enable language binding checkbox.

2. Fill the key and fallback

Text key is the language-catalog key, saved as TextId. Fallback text is saved as DefaultText and appears when no translation is found. These are text fields, not Tag or JavaScript expression inputs.

• Match the catalog key exactly and keep a readable fallback.
• Reuse the same key only when the intended meaning is the same.

Text key: screen.pump.start
Fallback text: Start

3. Save and reopen

Choose Save, reopen the behavior, and verify both fields. Cancel discards the current edit; canceling a newly added behavior rolls back that new binding. To remove localization, remove the behavior and set the intended fixed text.

4. Verify three runtime cases

Export and load in Mingcedar. Check a language that contains the key, a language with no matching translation, and an empty fallback. The order is translation → Fallback text → key.

Expected result The component updates after switching the host language and remains understandable when a translation is missing.

5. Troubleshoot in order

Check the binding, exact key, target-language catalog and active host language. Text lookup is distinct from a PLC value read; changing a Tag does not repair a missing translation.

• Localized Text behavior reference