Bug Fix(es) 

Issue: The Formula field did not return the expected value when language translation was applied; instead, it displayed an incorrect or unexpected value.
Expected Behavior: The behavior of the @FORMelement token in formula configuration is as follows:

1. Dropdowns: Returns the label of the selected option. If multilingual labels are configured, it will return the default language label, not the translated version shown at runtime.
2. Radio Buttons: Mirrors the behavior of dropdowns by returning the default language label of the selected option.
3. MultiSelect and Checkboxes: Returns the labels of all selected options. Please note that language translation is not supported for these field types, so only default language labels are returned.

Case Numbers: 2025-0312-8535269
Impacted Areas
Formula Field

Expected Behavior

1. When the RegexExtract and RegexExtractAll formulas are configured to use the value selected from a language-specific dropdown, the extraction is performed on the default (English) language label. The returned value reflects the English version of the dropdown option, regardless of the selected display language.
2. Values selected from the dropdown should return the right value as per the string formula applied. String value selected from dropdown should return the value chosen in given language. For example, if we configure “StringReplace“, “StringLower“, “StringUpper” formula to get value selected from language dropdown, it should return the selected value in lower case, upper case, and with replaced "," commas.

Known Issues

1. When date values are configured in different languages via the language dropdown and mapped to a date picker using both onChange form mapping and formulas, the value appears initially but then gets cleared automatically.
2. When Stage 1 is submitted with a language selected from the language dropdown, the correct language is displayed in the audit trail. However, if Stage 2 is submitted using the dashboard quick-submit option or quick-submit by email, the audit trail incorrectly displays the language value.
3. When both Prepop and Formula are configured on the same hidden form field, the formula is triggered, and the result is correctly mapped as expected. However, if Prepop is removed and only the Formula is configured on the hidden field, the formula does not get triggered, and the result is not mapped.
4. When a language is selected from the language dropdown and submitted, click “Edit” on the dashboard. The language popup appears empty, even though it is expected to be displayed.
5. In the Audit Trail, the selected radio button option is displayed in English, despite the language chosen by the user.
6. When a language is selected through the API, it shows correctly in the audit trail, but the language field looks empty on the Edit Request screen.