Openbravo Issue Tracking System - POS2 |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0053611 | POS2 | POS | public | 2023-10-06 11:31 | 2023-11-16 14:47 |
|
Reporter | rafaroda | |
Assigned To | dcontrera | |
Priority | normal | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | 24Q1 | |
Merge Request Status | approved |
Review Assigned To | |
OBNetwork customer | No |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0053611: Create a new USER ACTION for accessing PAYMENTS AND MOVEMENTS in CASHUP process |
Description | Create a new USER ACTION for accessing PAYMENTS AND MOVEMENTS in CASHUP process
Today, the option PAYMENTS AND MOVEMENTS in CASHUP process is driven by the Preference "Hide count Information to cashier"
* If Preference "Hide count Information to cashier" = N, this option is displayed
* If Preference "Hide count Information to cashier" = Y, this option is hidden
Option PAYMENTS AND MOVEMENTS in CASHUP process should NOT be driven by Preference "Hide count Information to cashier" but rather by a USER ACTION for it
If the new User Action is configured for the role, the Option PAYMENTS AND MOVEMENTS in CASHUP process must be accessible, with the approvals if configured
If New User Action is NOT configured or configured Active = N, the option Option PAYMENTS AND MOVEMENTS in CASHUP process must not be accessible
|
Steps To Reproduce | In Live Builds https://livebuilds.openbravo.com/context/retail_pos2_modules_pgsql/web/pos/?terminal=VB-2 [^]
1) Create some tickets in POS 2 paying them in CASH
2) Start the cashup process and in the Step 1 for CASH you will see 3 dots
3) Click on the 3 dots to see the Payment and Movements: you will see the list of tickets done in Cash for this cashup session (see images attached)
Now go to backoffice and configure Preference "Hide count Information to cashier" = Y
Login and logout of POS
1) Create some tickets in POS 2 paying them in CASH
2) Start the cashup process and in the Step 1 for CASH you the 3 dots have disappeared
|
Proposed Solution | Option PAYMENTS AND MOVEMENTS in CASHUP process should NOT be driven by Preference "Hide count Information to cashier" but rather by a USER ACTION for it
If the new User Action is configured for the role, the Option PAYMENTS AND MOVEMENTS in CASHUP process must be accessible, with the approvals if configured
If New User Action is NOT configured or configured Active = N, the option Option PAYMENTS AND MOVEMENTS in CASHUP process must not be accessible
|
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0053000 | | closed | Retail | Setting the environment for a blind cash up it is possible to know the theoretical amount to count | related to | defect | 0050137 | | closed | sreehari | Preference "Hide count Information to cashier" allow to see movement when closing the till |
|
Attached Files | Screenshot from 2023-10-05 09-09-31.png (101,496) 2023-10-06 11:31 https://issues.openbravo.com/file_download.php?file_id=19019&type=bug

Screenshot from 2023-10-05 09-09-42.png (93,478) 2023-10-06 11:32 https://issues.openbravo.com/file_download.php?file_id=19020&type=bug

|
|
Issue History |
Date Modified | Username | Field | Change |
2023-10-06 11:31 | rafaroda | New Issue | |
2023-10-06 11:31 | rafaroda | Assigned To | => Retail |
2023-10-06 11:31 | rafaroda | File Added: Screenshot from 2023-10-05 09-09-31.png | |
2023-10-06 11:31 | rafaroda | OBNetwork customer | => No |
2023-10-06 11:31 | rafaroda | Triggers an Emergency Pack | => No |
2023-10-06 11:32 | rafaroda | File Added: Screenshot from 2023-10-05 09-09-42.png | |
2023-10-06 11:34 | rafaroda | Relationship added | related to 0053000 |
2023-10-06 11:35 | rafaroda | Relationship added | related to 0050137 |
2023-10-24 21:14 | dcontrera | Assigned To | Retail => dcontrera |
2023-10-24 21:38 | hgbot | Merge Request Status | => open |
2023-10-24 21:38 | hgbot | Note Added: 0156249 | |
2023-10-27 07:54 | hgbot | Merge Request Status | open => approved |
2023-10-27 07:55 | hgbot | Resolution | open => fixed |
2023-10-27 07:55 | hgbot | Status | new => closed |
2023-10-27 07:55 | hgbot | Fixed in Version | => 24Q1 |
2023-10-27 07:55 | hgbot | Note Added: 0156431 | |
2023-10-27 07:55 | hgbot | Note Added: 0156432 | |
2023-11-07 01:40 | dcontrera | Status | closed => new |
2023-11-07 01:40 | dcontrera | Resolution | fixed => open |
2023-11-07 01:40 | dcontrera | Fixed in Version | 24Q1 => |
2023-11-07 01:46 | hgbot | Note Added: 0156799 | |
2023-11-07 17:26 | hgbot | Note Added: 0156879 | |
2023-11-07 17:26 | hgbot | Resolution | open => fixed |
2023-11-07 17:26 | hgbot | Status | new => closed |
2023-11-07 17:26 | hgbot | Fixed in Version | => 24Q1 |
2023-11-07 17:26 | hgbot | Note Added: 0156880 | |
2023-11-07 17:26 | hgbot | Note Added: 0156881 | |
2023-11-09 15:00 | hgbot | Note Added: 0156977 | |
2023-11-15 19:14 | hgbot | Note Added: 0157182 | |
2023-11-16 10:51 | marvintm | Note Added: 0157201 | |
2023-11-16 10:51 | marvintm | Status | closed => new |
2023-11-16 10:51 | marvintm | Resolution | fixed => open |
2023-11-16 10:51 | marvintm | Fixed in Version | 24Q1 => |
2023-11-16 14:47 | hgbot | Resolution | open => fixed |
2023-11-16 14:47 | hgbot | Status | new => closed |
2023-11-16 14:47 | hgbot | Fixed in Version | => 24Q1 |
2023-11-16 14:47 | hgbot | Note Added: 0157228 | |
2023-11-16 14:47 | hgbot | Note Added: 0157229 | |
Notes |
|
(0156249)
|
hgbot
|
2023-10-24 21:38
|
|
|
|
(0156431)
|
hgbot
|
2023-10-27 07:55
|
|
|
|
(0156432)
|
hgbot
|
2023-10-27 07:55
|
|
|
|
(0156799)
|
hgbot
|
2023-11-07 01:46
|
|
|
|
(0156879)
|
hgbot
|
2023-11-07 17:26
|
|
|
|
(0156880)
|
hgbot
|
2023-11-07 17:26
|
|
|
|
(0156881)
|
hgbot
|
2023-11-07 17:26
|
|
|
|
(0156977)
|
hgbot
|
2023-11-09 15:00
|
|
|
|
(0157182)
|
hgbot
|
2023-11-15 19:14
|
|
|
|
|
There is still a problem with this issue, so reopening it until we fix it |
|
|
(0157228)
|
hgbot
|
2023-11-16 14:47
|
|
|
|
(0157229)
|
hgbot
|
2023-11-16 14:47
|
|
|