Bug 1096771 - i18n: a selected value of a property in Properties bar does not depend on language
Summary: i18n: a selected value of a property in Properties bar does not depend on lan...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-12 12:09 UTC by Sona Mala
Modified: 2020-03-27 19:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:03:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 979053 0 high CLOSED Update i18n of designer 2021-02-22 00:41:40 UTC

Internal Links: 979053

Description Sona Mala 2014-05-12 12:09:33 UTC
Description of problem:
This issue affects a properties which has a defined set of values like Task type, Time unit, Distribution type, etc.

A drop down menu contains translated options but the selected value is always displayed in English.


Version-Release number of selected component (if applicable):
6.0.2 ER2 BPMS


Steps to Reproduce:
1. use localization for de, ja, es, ru
    - start $LC_ALL=es_ES.UTF-8 ./standalone.sh or
    - go to http://localhost:8080/business-central/org.kie.workbench.KIEWebapp/KIEWebapp.html?locale=es_ES
2. activate a property in Properties Bar (for example Task type, Distribution type, Time unit, etc.)
3. show all options for this property
4. select one
5. deactivate the property

Actual results:
Step 4: You select an option which label is translated (for example "minuto")
After step 5: the property contains a "minute" value.


Expected results:
Both labels should be equal. The label of the selected option should be equal to the label of the value of the property.


Additional info:


Note You need to log in before you can comment on or make changes to this bug.