Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0055188 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [POS2] POS | minor | always | 2024-04-12 15:09 | 2024-04-25 07:56 | |||
| Reporter | charlotte_vasseur | View Status | public | |||||
| Assigned To | SABARINATH P | |||||||
| Priority | normal | Resolution | no change required | Fixed in Version | ||||
| Status | closed | 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 | 24Q1 | SCM revision | ||||||
| Review Assigned To | marvintm | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0055188: [SALES] Updated date is before creation date | |||||||
| Description | In Sales order window (and in JSon if External System if configured): updated date (local or not) is before creation date (local or not) | |||||||
| Steps To Reproduce | In POS Finalize a sale In the backoffice, go to Sales Order window Open the previous sale and deploy Audit section Check Updated and Creation dates => Updated is before Creation date (See Updated before creation date.png) Same if creation and local dates are configured Same in JSon if External System if configured to send the ticket | |||||||
| Tags | No tags attached. | |||||||
| Attached Files |  Updated before creation date.png [^] (181,906 bytes) 2024-04-12 15:09
| |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0163716) marvintm (manager) 2024-04-25 07:56 |
"created" date comes from the client device. "updated" date is set according to the date in the backend server, once the data arrives to the backend. It works in this way because as the POS supports offline, we want to have a reference about when was the document actually created and completed in the terminal, and we can only use the local date for this. If the date of the local device is incorrectly set, and "in the future", this problem can happen. The solution would then be to properly set it to the correct value, and ideally to use an automatic date mechanism that all modern operating systems provide. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2024-04-12 15:09 | charlotte_vasseur | New Issue | |
| 2024-04-12 15:09 | charlotte_vasseur | Assigned To | => Retail |
| 2024-04-12 15:09 | charlotte_vasseur | File Added: Updated before creation date.png | |
| 2024-04-12 15:09 | charlotte_vasseur | Triggers an Emergency Pack | => No |
| 2024-04-15 09:09 | guilleaer | Status | new => acknowledged |
| 2024-04-16 13:53 | SABARINATH P | Assigned To | Retail => SABARINATH P |
| 2024-04-16 13:53 | SABARINATH P | Status | acknowledged => scheduled |
| 2024-04-25 07:56 | marvintm | Review Assigned To | => marvintm |
| 2024-04-25 07:56 | marvintm | Note Added: 0163716 | |
| 2024-04-25 07:56 | marvintm | Status | scheduled => closed |
| 2024-04-25 07:56 | marvintm | Resolution | open => no change required |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |