Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0052031Openbravo ERP04. Warehouse managementpublic2023-03-31 20:552023-05-20 10:17
philippe_mui 
Triage Omni WMS 
highmajoralways
closedno change required 
5
 
 
Core
No
0052031: [RM-5829][AWO] Log in not possible when there is no user defined as 'Allow warehouse operations'=no
In BO, User screen : when there is no user defined as ‘Allow warehouse operations’=no, the message in attachment appears.

However, it is not an stopper to do login in AWO, it means a user with ‘Allow warehouse operations’=No but with access to AWO can still do login. We expect the same behaviour even when no users defined as ‘Allow warehouse operations’=Yes.

https://openbravo.atlassian.net/browse/RM-5829 [^]
In BO, no user is set with "Allow warehouse operations"=No

Current result : it is not possible to log in to AWO

Expected result : it is possible to connect to AWO
FASH
related to feature request 0050852 closed mtaal Display logo + users by store inside the log in page, add the org parameter in the url 
png 2023-03-31_20h55_00.png (641,158) 2023-03-31 20:55
https://issues.openbravo.com/file_download.php?file_id=18335&type=bug
Issue History
2023-03-31 20:55philippe_muiNew Issue
2023-03-31 20:55philippe_muiAssigned To => Triage Omni WMS
2023-03-31 20:55philippe_muiFile Added: 2023-03-31_20h55_00.png
2023-03-31 20:55philippe_muiModules => Core
2023-03-31 20:55philippe_muiTriggers an Emergency Pack => No
2023-03-31 20:55philippe_muiTag Attached: FASH
2023-04-03 10:42philippe_muiSummary[AWO] Log in not possible when there is no user defined as 'Allow warehouse operations'=no => [RM-5829][AWO] Log in not possible when there is no user defined as 'Allow warehouse operations'=no
2023-04-03 10:42philippe_muiDescription Updatedbug_revision_view_page.php?rev_id=25813#r25813
2023-04-11 10:27mtaalNote Added: 0148351
2023-04-12 16:41hgbotResolutionopen => fixed
2023-04-12 16:41hgbotStatusnew => resolved
2023-04-12 16:41hgbotFixed in Version => 23Q3
2023-04-12 16:41hgbotNote Added: 0148414
2023-04-17 10:35hgbotNote Added: 0148460
2023-04-17 12:11jarmendarizStatusresolved => new
2023-04-17 12:11jarmendarizResolutionfixed => open
2023-04-17 12:11jarmendarizFixed in Version23Q3 =>
2023-04-17 12:13jarmendarizNote Deleted: 0148460
2023-04-17 12:14jarmendarizNote Deleted: 0148414
2023-05-09 14:02hgbotNote Added: 0149495
2023-05-09 15:05hgbotNote Added: 0149499
2023-05-09 15:07jarmendarizNote Deleted: 0149495
2023-05-09 15:07jarmendarizNote Deleted: 0149499
2023-05-17 20:37hgbotNote Added: 0149900
2023-05-19 14:58rafarodaRelationship addedrelated to 0050852
2023-05-20 10:17AtulOpenbravoNote Added: 0150000
2023-05-20 10:17AtulOpenbravoStatusnew => closed
2023-05-20 10:17AtulOpenbravoResolutionopen => no change required
2023-05-20 10:18AtulOpenbravoNote Edited: 0150000bug_revision_view_page.php?bugnote_id=0150000#r26096

Notes
(0148351)
mtaal   
2023-04-11 10:27   
Updated expiry to be inline with project jira planning by sprint
(0149900)
hgbot   
2023-05-17 20:37   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/522 [^]
(0150000)
AtulOpenbravo   
2023-05-20 10:17   
(edited on: 2023-05-20 10:18)
It is possible to add to this URL an organization parameter whose value is a valid organization's search key; if it is set, the logo that is shown in the login page as well as the list of available users will be restricted to that organization. Ie.: https://livebuilds.openbravo.com/retail_translations_pgsql/web/org.openbravo.warehouse.advancedwarehouseoperations?organization=US [^]

If this parameter is used, then the login page will show only the filtered users, which will be a very reduced number.