Language Overrides
Language Overrides is used to adjust the text shown in the application without changing the program. This form helps the company use internal terms that are more familiar to users.
Used By
operations admins according to menu access rights
Data Type
master
Search Keys
Code
When to Use This Form
- When a standard application term needs replacing with a term the company normally uses.
- When the support team wants to standardize the wording of menus, labels, or messages shown on screen.
- When internal terms change so users are not confused when using the application.
Before You Start
- Make sure the variable name or language key to be replaced is known from the application's language list.
- Prepare replacement terms that are short, consistent, and easy for users to understand.
Workflow
- Open Settings / Language & Regional / Language Overrides.
- Enter the language and the variable name to be replaced.
- Enter the replacement term according to the company's working language.
- Re-check the wording so it does not change the meaning of the original label.
- Click Save, then check the application display in the part that uses that term.
Key Fields
| Field | Explanation for Users | Status |
|---|---|---|
Code
id |
Term override code. Use a code that is easy to trace when support needs to find a text change. | Required |
Language
lang |
Language that will use the replacement term, for example Indonesian or another active language. | Required |
Language Overrides
value |
Replacement text the application will show for that language variable. | Required |
Last Modified
updatetimestamp |
Last Modified is audit information filled in automatically by the application. | Optional |
Details and Relations
- This form has no detail table. The data is saved directly from the main fields.
What Happens After Saving
- Labels that use that variable follow the replacement term once the data is saved.
- Changing terms can affect how users read menus, buttons, or messages on screen.
- If the language or variable is wrong, the change may not be visible where expected.
Common Problems
- Term does not change on screen: check the active language, variable name, and display cache if any.
- Users are confused by the new term: choose words already used in SOPs or internal documents.
- Duplicate override: search for the same variable before creating new data.
Available Fields
The following list summarizes the fields available on the form. Rarely used fields are still listed so they are easy to look up during training or support.
| Field | Explanation for Users | Status |
|---|---|---|
Code
id |
Term override code. Use a code that is easy to trace when support needs to find a text change. | Required |
Language
lang |
Language that will use the replacement term, for example Indonesian or another active language. | Required |
Variable Name
langkey |
Variable name or language key of the label to be replaced. | Optional |
Language Overrides
value |
Replacement text the application will show for that language variable. | Required |
Created By
usercreate |
Created By is audit information filled in automatically by the application. | Optional |
Modified By
useredit |
Modified By is audit information filled in automatically by the application. | Optional |
Last Modified
updatetimestamp |
Last Modified is audit information filled in automatically by the application. | Optional |
User Checklist
Menu Location
- Settings / Language & Regional / Language Overrides
/form/langoverrides