Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0010950 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
feature request | [Openbravo ERP] 00. Application dictionary | major | have not tried | 2009-10-13 17:20 | 2009-10-16 17:55 | |||||||
Reporter | networkb | View Status | public | |||||||||
Assigned To | iciordia | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | 2.50MP6 | SCM revision | ||||||||||
Review Assigned To | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0010950: The alerts could be translated depending on the language used when loggin the application | |||||||||||
Description | The 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. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0021110) psarobe (manager) 2009-10-16 13:46 |
Is this a feature request? or a bug? |
(0021118) networkb (developer) 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 (manager) 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 |
Issue History | |||
Date Modified | Username | Field | Change |
2009-10-13 17:20 | networkb | New Issue | |
2009-10-13 17:20 | networkb | Assigned To | => rafaroda |
2009-10-14 15:14 | networkb | Target Version | => 2.40MP12 |
2009-10-16 13:46 | psarobe | Note Added: 0021110 | |
2009-10-16 13:46 | psarobe | Assigned To | rafaroda => iciordia |
2009-10-16 13:46 | psarobe | Status | new => feedback |
2009-10-16 16:05 | networkb | Note Added: 0021118 | |
2009-10-16 17:55 | iciordia | Note Added: 0021130 | |
2009-10-16 17:55 | iciordia | Status | feedback => new |
2009-10-16 17:55 | iciordia | Type | defect => feature request |
2009-10-16 17:55 | iciordia | Target Version | 2.40MP12 => |
Copyright © 2000 - 2009 MantisBT Group |