Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010950Openbravo ERP00. Application dictionarypublic2009-10-13 17:202009-10-16 17:55
Reporternetworkb 
Assigned Toiciordia 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version2.50MP6 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0010950: The alerts could be translated depending on the language used when loggin the application
DescriptionThe alerts could be translated depending on the language used when loggin the application. At the moment the generated alerts can not be translated because the message is generated directly in the sql and inserted to the alert table. It should be possible to see the alerts on the language used to loggin the application.
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-10-13 17:20networkbNew Issue
2009-10-13 17:20networkbAssigned To => rafaroda
2009-10-14 15:14networkbTarget Version => 2.40MP12
2009-10-16 13:46psarobeNote Added: 0021110
2009-10-16 13:46psarobeAssigned Torafaroda => iciordia
2009-10-16 13:46psarobeStatusnew => feedback
2009-10-16 16:05networkbNote Added: 0021118
2009-10-16 17:55iciordiaNote Added: 0021130
2009-10-16 17:55iciordiaStatusfeedback => new
2009-10-16 17:55iciordiaTypedefect => feature request
2009-10-16 17:55iciordiaTarget Version2.40MP12 =>

Notes
(0021110)
psarobe   
2009-10-16 13:46   
Is this a feature request? or a bug?
(0021118)
networkb   
2009-10-16 16:05   
If the alert receipts are using different languages, they can not see in both languages properly, but only in the language that the alert has been defined.
(0021130)
iciordia   
2009-10-16 17:55   
Alerts are not designed to be multi-language although is is clear it would be better to support multi-language. So I've changed this bug to feature request.

While this feature is not ready you can work-around the problem in the following way:
1.- Join to your alert sql the table xx_trl you want to use for translations. It will create an alert instance for each system language in your instance
2.- Add a filter clause to the alert rule using @ad_language@ to filter alerts in the language of the session

This way alert will be shown using session language. Be aware this is a workaround and not a final solution (eg. if you "close" an instance alert in one language it will still be open in the other system languages)

Ismael