Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[POS2] POSmajoralways2023-06-12 17:092023-08-23 12:43
ReporternicolasurizView Statuspublic 
Assigned ToRetail 
PriorityhighResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0052724: “User language” is not taken in account for “Translated Product Name” in WebPOS REACT

DescriptionWhen a product has a translation defined in the Back-Office (for its product name)

Currently the product names never change in POS2 (always in French or always in English for each product)

We identify that the product it is in the language of the first connected user to this TILL (when the Product had been created in the TILL) :

If the user was connected in french, the “Product Name” of this product will be always displayed in French (never in English).
If the user was connected in english, the “Product Name” of this product will be always displayed in English (never in french).
Steps To ReproduceYou have to have two languages defined for the product, English and the translation to French for example.

Then, after the creation with the two languages defined, login in the POS2 and check if changing the User language in your profile, if the product changes its name.
Proposed SolutionIn WebPOS REACT : When the user change the language (in his profile) :

The displayed product Name are refreshed to be displayed in the selected language for the user.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
marvintm (manager)
2023-08-23 12:26

Currently this is a limitation of the way translatable info is managed at masterdata level:
- Data is loaded using the language of the initial login/full refresh
- Switching language is not supported, meaning that:
   - If language is switched, you will still see labels in the original language
   - If an incremental refresh is triggered and new data comes, while operating in a different language, the new data will come in the current language, leading to the records being shown in different languages depending on when they were loaded

So essentially, language switching in one terminal is not supported if translation is used for masterdata entities.

- Issue History
Date Modified Username Field Change
2023-06-12 17:09 nicolasuriz New Issue
2023-06-12 17:09 nicolasuriz Assigned To => Retail
2023-06-12 17:09 nicolasuriz Triggers an Emergency Pack => No
2023-08-23 08:49 SABARINATH P Assigned To Retail => SABARINATH P
2023-08-23 12:26 marvintm Note Added: 0153841
2023-08-23 12:26 marvintm Type defect => design defect
2023-08-23 12:43 SABARINATH P Assigned To SABARINATH P => Retail

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker