Openbravo Issue Tracking System - Retail Modules | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0036360 | Retail Modules | Web POS | public | 2017-06-27 13:14 | 2017-06-27 13:14 | |||||||
Reporter | egoitz | |||||||||||
Assigned To | Retail | |||||||||||
Priority | normal | Severity | major | Reproducibility | always | |||||||
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 | 0036360: Save information about last refresh on each terminal | |||||||||||
Description | For customers with a lot of terminals it would be very useful to save on the backend (i.e on application table) the datetime of the last full refresh executed on the terminal. The date of the last login after a clean cache would be also very usfull. That datetimes are very important when managing lots of terminals when you need to ensure that the terminals have the correct information. | |||||||||||
Steps To Reproduce | nY/a | |||||||||||
Proposed Solution | ||||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2017-06-27 13:14 | egoitz | New Issue | ||||||||||
2017-06-27 13:14 | egoitz | Assigned To | => Retail | |||||||||
2017-06-27 13:14 | egoitz | Triggers an Emergency Pack | => No | |||||||||
2017-06-27 13:30 | egoitz | Relationship added | related to 0036361 |
There are no notes attached to this issue. |