Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[POS2] POSmajorhave not tried2022-09-20 11:132022-09-25 22:42
ReportercbernerView Statuspublic 
Assigned Tocberner 
PrioritynormalResolutionfixedFixed in Version22Q3.1
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version22Q3.1
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0050294: Terminal detects terminal data changes on forcePagerStatus and pagerConsolidation properties

DescriptionTerminal properties forcePagerStatus and pagerConsolidation generate changes because are only updated on login. They should also be updated when terminal data changes by masterdata refresh.
Steps To Reproduce1. Login POS2
2. Click on the top right icon of the pager server, and then on Force Pager
3. Click on refresh masterdata, check that it refreshes the application because it detects a change in terminal data property forcePagerStatus
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0050290 closedcberner Terminal detects terminal data changes on forcePagerStatus and pagerConsolidation properties 

-  Notes
hgbot (developer)
2022-09-21 12:24

Merge Request created: [^]
hgbot (developer)
2022-09-25 22:42

Directly closing issue as related merge request is already approved.

Repository: [^]
Changeset: 923a82919a02abb4c55665db03fe9ebdd458ed6b
Author: Cristian Berner <>
Date: 25-09-2022 13:31:59
URL: [^]

Fixes ISSUE-50294: Terminal data changes detected on forcePagerStatus and pagerConsolidation properties

This properties are no longer required to be fetched as part of
TerminalData, as we are doing that in a separate request just for Pager,
and we reuse it for this case also, as it was already being done before.

This fixes the problem of changes detected when changing any option in
frontend regarding pager, it is now transparent to the user and doesn't
produce terminal data changes.

M src/org/openbravo/pos2/term/
M web-jspack/org.openbravo.pos2/src/authentication/loginInitActions.js
M web-jspack/org.openbravo.pos2/src/core/pickupPoint/deliveryControl/pager/RegisterPagerStatusCheck.js
M web-jspack/org.openbravo.pos2/src/core/pickupPoint/deliveryControl/pager/UpdatePagerStatusInClient.js
M web-jspack/org.openbravo.pos2/src/core/pickupPoint/deliveryControl/pager/UpdatePagerStatusInServer.js
M web-jspack/org.openbravo.pos2/src/core/pickupPoint/deliveryControl/pager/__test__/UpdatePagerStatusInClient.test.js
M web-jspack/org.openbravo.pos2/src/model/setting/user-actions/__test__/ForcePagerStatus.test.js
M web-jspack/org.openbravo.pos2/src/ob-init.js
hgbot (developer)
2022-09-25 22:42

Merge request merged: [^]

- Issue History
Date Modified Username Field Change
2022-09-20 16:32 cberner Type defect => backport
2022-09-20 16:32 cberner Target Version => 22Q3.1
2022-09-21 12:24 hgbot Note Added: 0141284
2022-09-25 22:42 hgbot Resolution open => fixed
2022-09-25 22:42 hgbot Status scheduled => closed
2022-09-25 22:42 hgbot Fixed in Version => 22Q3.1
2022-09-25 22:42 hgbot Note Added: 0141352
2022-09-25 22:42 hgbot Note Added: 0141353

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker