Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0032155
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 02. Master data managementmajoralways2016-02-08 09:382016-02-12 12:03
ReporterVictorVillarView Statuspublic 
Assigned ToTriage Omni OMS 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned Tovmromanos
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0032155: Wrong behavior in the translation tab of the product window

DescriptionWrong behavior in the translation tab of the product window when the user changes the name of the product, the change is not reflected in the translation registers
Steps To ReproduceAs system admin role,
  install at least one translation pack. Example: the Spanish translation pack

Go to Product window,
  create one. Name: test
Realize that the name test appears in the translation register.
Change the name in the header to test1.
This change is not transferred to the translation register. It should transfer to these because the the Translation = 'N'
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0084151)
vmromanos (manager)
2016-02-12 12:03

The current behavior is the expected one, and it's the way it works in other windows (for example Unit of Measure).

When you create a new record, the system creates a new row in the Translation tab for each of the languages declared as system language. It uses the same name as the original record and it sets the Translation flag to N, because the record is actually not translated. Instead of using the original name, we could be using ***, XXX, NOTTRANSLATED, etc. because the record is not translated.

When you translate the record, you set the Translation flag to Y to indicate the record is translated.

If you latter on change the original name, the translation flag is automatically updated to N for all the translation rows.

There is no real benefit in updating the name of the non-translated records (Translation flag = N) because they are actually not translated, thus it really doesn't matter to have there a name with the original record name or *** or XXX because that record is set as not translated.


I may understand the purposed behavior could be interesting for the reporter for whatever reason, but in this case he can easily develop a customization to behaves this way.

- Issue History
Date Modified Username Field Change
2016-02-08 09:38 VictorVillar New Issue
2016-02-08 09:38 VictorVillar Assigned To => Triage Finance
2016-02-08 09:38 VictorVillar Modules => Core
2016-02-08 09:38 VictorVillar Resolution time => 1457391600
2016-02-08 09:38 VictorVillar Triggers an Emergency Pack => No
2016-02-08 09:39 VictorVillar Issue Monitored: networkb
2016-02-12 12:03 vmromanos Review Assigned To => vmromanos
2016-02-12 12:03 vmromanos Note Added: 0084151
2016-02-12 12:03 vmromanos Status new => closed
2016-02-12 12:03 vmromanos Resolution open => no change required


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker