Openbravo Issue Tracking System - Openbravo Localizations | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0055023 | Openbravo Localizations | Localization Portugal | public | 2024-03-21 10:03 | 2024-05-14 22:45 |
| Reporter | jonae | ||||
| Assigned To | jonae | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Regression date | |||||
| Regression introduced by commit | |||||
| Regression level | |||||
| Support ticket | |||||
| OBNetwork customer | |||||
| Regression introduced in release | |||||
| Summary | 0055023: Enchancements in document manual window | ||||
| Description | The field “Número do Doc.Manual“ must be split into two fields named: Serie do Doc. Manual Número do Doc. Manual The field “Serie do Doc. Manual” must be also validated according to what described in the Jira (RM-12483: PT Certification 19Q3 - Document Series must be enhanced according to legal req (Q&A - 41-4696) DEVELOPMENT TO DO ) The field “Data Manual” must be renamed as “Data do Doc. Manual”. The field “Data do Doc. Manual” must include a validation, therefore the max date to include is “current” date, so no date in the future can be entered. Review why do we need to have the field “Total” in the “Documento Manual” window, while entering document and customer information. See image attached. In regards to the Doc. Manual lines, that is the window shown after pressing the process button “Add Line” (rename to “adicionar linha”??) It is a pre-requisite that the product and therefore the product search key (chave de pesquisa) can be found in the OB back-office: if it is not found = a warning is given to the end-user by saying (“The product you want to add must be created first in the Openbravo database, therefore product data required but the quantity sold, can be retrieved from there. Once created enter the product search key in the field “Chave de pesquisa” and the quantity sold in the field “Montante”) if it is found = the end-use will only be able to modify the field “Quantity” (“Montante”) The field “Total” must be a calculation between the price (including taxes) and quantity. The field “Taxa do Importo” will need to include the rate of the tax rate related to the Tax Category of the Product, as it would have been calculated by our Tax Engine. | ||||
| Steps To Reproduce | The field “Número do Doc.Manual“ must be split into two fields named: Serie do Doc. Manual Número do Doc. Manual The field “Serie do Doc. Manual” must be also validated according to what described in the Jira (RM-12483: PT Certification 19Q3 - Document Series must be enhanced according to legal req (Q&A - 41-4696) DEVELOPMENT TO DO ) The field “Data Manual” must be renamed as “Data do Doc. Manual”. The field “Data do Doc. Manual” must include a validation, therefore the max date to include is “current” date, so no date in the future can be entered. Review why do we need to have the field “Total” in the “Documento Manual” window, while entering document and customer information. See image attached. In regards to the Doc. Manual lines, that is the window shown after pressing the process button “Add Line” (rename to “adicionar linha”??) It is a pre-requisite that the product and therefore the product search key (chave de pesquisa) can be found in the OB back-office: if it is not found = a warning is given to the end-user by saying (“The product you want to add must be created first in the Openbravo database, therefore product data required but the quantity sold, can be retrieved from there. Once created enter the product search key in the field “Chave de pesquisa” and the quantity sold in the field “Montante”) if it is found = the end-use will only be able to modify the field “Quantity” (“Montante”) The field “Total” must be a calculation between the price (including taxes) and quantity. The field “Taxa do Importo” will need to include the rate of the tax rate related to the Tax Category of the Product, as it would have been calculated by our Tax Engine. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2024-03-21 10:03 | jonae | New Issue | |||
| 2024-03-21 10:03 | jonae | Assigned To | => jonae | ||
| 2024-03-21 10:37 | hgbot | Note Added: 0162456 | |||
| 2024-05-14 22:26 | hgbot | Resolution | open => fixed | ||
| 2024-05-14 22:26 | hgbot | Status | new => resolved | ||
| 2024-05-14 22:26 | hgbot | Note Added: 0164609 | |||
| 2024-05-14 22:26 | hgbot | Note Added: 0164610 | |||
| 2024-05-14 22:45 | hgbot | Note Added: 0164615 | |||
| 2024-05-14 22:45 | hgbot | Note Added: 0164616 | |||
| 2024-05-14 22:45 | hgbot | Status | resolved => closed | ||
| 2024-05-14 22:45 | hgbot | Note Added: 0164617 | |||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||