Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0055150Openbravo ERP01. General setuppublic2024-04-09 09:362024-05-06 12:15
ReporterLeyre 
Assigned ToTriage Platform Base 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionPR24Q2Fixed in VersionPR24Q2 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression levelProduction - Confirmed Stable
Regression date2023-09-17
Regression introduced in releasePR23Q4
Regression introduced by commithttps://gitlab.com/openbravo/product/openbravo/-/commit/fcd246dff378226fbc702ed953da646619b6c35f [^]
Triggers an Emergency PackNo
Summary0055150: It is possible to active more terminals that are allowed in the instance.
DescriptionIt is possible to active more terminals that are allowed in the instance.
Steps To ReproduceAs system administator:
1. Open the "Instance Activation" window and confirm the maximum number of allowed active POS terminals in the instance. In my case, for example, 3.
2. Confirm that there are less active terminals than the maximum allowed. In my case 1.

Change the role:
3. Open the "Channel - Touchpoint" window.
2. Select more terminals than the allowed in the instance and click on the button "Activate or deactivate the current(selected) record(s)". See attached image.

Result: It is possible to active more terminals than allowed. Additionally, if you change to "System Administrator" role and navigate to the "Instance Activation" window, even if you click the refresh button, the data is not refershed.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
caused by feature request 0053407 closed meriem_azaf Multi-record activation/deactivation 
blocks defect 0055134 closed meriem_azaf It is possible to active more terminals that are allowed in the instance. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2024-04-10 08:23AugustoMauchTypedefect => backport
2024-04-10 08:23AugustoMauchTarget Version => PR24Q2
2024-04-16 09:38hgbotNote Added: 0163251
2024-05-06 12:12alostaleRelationship addedcaused by 0053407
2024-05-06 12:15hgbotResolutionopen => fixed
2024-05-06 12:15hgbotStatusscheduled => closed
2024-05-06 12:15hgbotFixed in Version => PR24Q2
2024-05-06 12:15hgbotNote Added: 0164106
2024-05-06 12:15hgbotNote Added: 0164107

Notes
(0163251)
hgbot   
2024-04-16 09:38   
Merge Request created: https://gitlab.com/openbravo/product/openbravo/-/merge_requests/1201 [^]
(0164106)
hgbot   
2024-05-06 12:15   
Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/openbravo [^]
Changeset: df1111f5d8c92ffcf05db7f97149246da79a2901
Author: Augusto Mauch <augusto.mauch@openbravo.com>
Date: 06-05-2024 10:14:48
URL: https://gitlab.com/openbravo/product/openbravo/-/commit/df1111f5d8c92ffcf05db7f97149246da79a2901 [^]

Fixes ISSUE-55150: Event handlers get accurate info on the number of active records

The problem was that when enabling/disabling recordsa using the EnableOrDisableMultipleRecords process, the
event handlers were not receiving accurate info on the number of currently active records if data was flushed
updated updating them all.

In order to prevent this problem, now data is flushed after updating each records. This results in a slower execution
of the process but it is still reasonable fast (changing the active flag of 100 records took <100ms)

---
M modules/org.openbravo.client.application/src/org/openbravo/client/application/EnableOrDisableMultipleRecords.java
---
(0164107)
hgbot   
2024-05-06 12:15   
Merge request merged: https://gitlab.com/openbravo/product/openbravo/-/merge_requests/1201 [^]