Openbravo Issue Tracking System - Openbravo ERP | |||||||||||||||||||
View Issue Details | |||||||||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||||||||
0034935 | Openbravo ERP | A. Platform | public | 2017-01-12 17:39 | 2022-02-01 08:09 | ||||||||||||||
Reporter | NaroaIriarte | ||||||||||||||||||
Assigned To | Triage Platform Base | ||||||||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||||||||
Status | acknowledged | Resolution | open | ||||||||||||||||
Platform | OS | 5 | OS Version | ||||||||||||||||
Product Version | |||||||||||||||||||
Target Version | Fixed in Version | ||||||||||||||||||
Merge Request Status | |||||||||||||||||||
Review Assigned To | |||||||||||||||||||
OBNetwork customer | |||||||||||||||||||
Web browser | |||||||||||||||||||
Modules | Core | ||||||||||||||||||
Support ticket | |||||||||||||||||||
Regression level | |||||||||||||||||||
Regression date | |||||||||||||||||||
Regression introduced in release | |||||||||||||||||||
Regression introduced by commit | |||||||||||||||||||
Triggers an Emergency Pack | No | ||||||||||||||||||
Summary | 0034935: The criterion of selection of the email Definitions is not correct | ||||||||||||||||||
Description | The criterion to select the email definition of a template is not correct currently. The query is not taking unto account if the email definition is active or not. Also it is not following a concrete order criterion sometimes. For example, if you have three email definitions, one with the arabic language, this one set as default, the others with the language of the bp (the default one when creating a new record), this two cannot be set as default because one record has already been set. In this concrete circumstance, an email definition with the language of the Bp must be chosen. But it is not clear which one. There is no a clear way of choosing it. This must be fixed. | ||||||||||||||||||
Steps To Reproduce | 1) As F&B Admin go to "Purchase Invoice" window and clear the filters. Then, select the first record in form mode. 2) Navigate to "Document Type" by clicking the 'Transaction Document' link. 3) In "Document Type" go to 'Email Definitions' subtab and create three email definition as follows: a) First one: Subject-> eng one b) Second one: Subject-> eng two c) Third one: Subject-> ara one, Check the "Default" checkbox. 4) Go again to "Purhcase Invoice" window, and selecting the first record click on the email button. One of the two eng one or eng two email definitions will be shown, but we don't know which one. 5) Go again to "Document Type" by clicking the 'Transaction Document' link and go again to the email definition subtab. 6) Open the records of eng one and eng two and uncheck the "Active" checkbox. 7) Go again to "Purhcase Invoice" window, and selecting the first record click on the email button. 8) Realize that it follows showing the eng one or eng two email defintion even if it is deactivated. This is wrong. | ||||||||||||||||||
Proposed Solution | The solution will be to change the query which is done in the "EmailDefinition_data.xsql" Adding to the where clause a check for isActive will fix the second proble, and adding an order by created asc (for example) will solve the inconsistency problem of not knowing what is the email definition which will be chosen. | ||||||||||||||||||
Additional Information | |||||||||||||||||||
Tags | No tags attached. | ||||||||||||||||||
Relationships |
| ||||||||||||||||||
Attached Files | |||||||||||||||||||
Issue History | |||||||||||||||||||
Date Modified | Username | Field | Change | ||||||||||||||||
2017-01-12 17:39 | NaroaIriarte | New Issue | |||||||||||||||||
2017-01-12 17:39 | NaroaIriarte | Assigned To | => NaroaIriarte | ||||||||||||||||
2017-01-12 17:39 | NaroaIriarte | Modules | => Core | ||||||||||||||||
2017-01-12 17:39 | NaroaIriarte | Triggers an Emergency Pack | => No | ||||||||||||||||
2017-01-12 17:40 | NaroaIriarte | Relationship added | related to 0020209 | ||||||||||||||||
2017-01-12 17:40 | NaroaIriarte | Relationship added | related to 0034900 | ||||||||||||||||
2017-01-13 12:03 | NaroaIriarte | Status | new => acknowledged | ||||||||||||||||
2017-01-13 13:18 | alostale | Type | defect => design defect | ||||||||||||||||
2017-01-13 13:19 | alostale | Note Added: 0093530 | |||||||||||||||||
2017-01-13 14:13 | NaroaIriarte | Status | acknowledged => scheduled | ||||||||||||||||
2017-01-16 09:48 | NaroaIriarte | Status | scheduled => acknowledged | ||||||||||||||||
2017-03-14 17:06 | NaroaIriarte | Assigned To | NaroaIriarte => platform | ||||||||||||||||
2022-02-01 08:09 | alostale | Assigned To | platform => Triage Platform Base |
Notes | |||||
|
|||||
|
|