Openbravo Issue Tracking System - POS2 | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0048567 | POS2 | Core | public | 2022-02-10 10:12 | 2022-02-10 10:12 |
| Reporter | aferraz | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0048567: Having different APIs to retrieve terminal properties in POS2 could be confusing | ||||
| Description | Right now we have three different APIs to retrieve terminal properties in POS2: - To be used in action preparations and state actions (business logic): OB.App.TerminalProperty - To be used in user actions and components (UI): org.openbravo.core2/src/core/terminal/Terminal and org.openbravo.core2/src/core/terminal/TerminalProperty. Having two APIs to retrieve same information could be confusing. It would be nice to remove Terminal or TerminalProperty API and to have only one API to retrieve terminal properties information in user actions and components. | ||||
| Steps To Reproduce | * | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2022-02-10 10:12 | aferraz | New Issue | |||
| 2022-02-10 10:12 | aferraz | Assigned To | => Triage Platform Base | ||
| 2022-02-10 10:12 | aferraz | Triggers an Emergency Pack | => No | ||
| There are no notes attached to this issue. |