Openbravo Issue Tracking System - Modules
View Issue Details
0038815ModulesAdvanced Warehouse Operationspublic2018-06-22 13:272018-06-22 13:27
maarten1962 
dmiguelez 
normalminoralways
newopen 
5
 
 
0038815: AWO Role definition / Role Access definition
It is not easy and confusing to set the Role defenition and Role Access definition for AWO users. A typical Whse has three roles:
1) Warehouse Front-End operator
2) Warehouse Supervisor
3) Warehouse Manager.

The (1) simply operates the device. Should be able to login and assign /create / confirm tasks if not restricted by the Whse Definition.
The (2) inherits (1) and adds the Task window, Errors on Processing, Whse Operations, Task Report, Batch of Task, ...
The (3) inherits (2) and adds Whse Definition, Process Request, Whse Config check, Task Type, Front-End config, Verbosity Log, ...

The confusing part is not easy to explain. Some examples:
In Process Definition, I see "Save Task" and "Print Task" and "Confirm task". What are these?
    A task is generate in receiving, in picking, in Whse Ops, ... So why should I seperatly give "Save Task" access? Seems redundant and difficult to understand/explain.
    A task is confirmed from the FE and BE, if people have access to this, isn't that implicitely giving access to Print or Confirm a task?

In View Implementation I see "Beautify Log". Why should someone not have that?

Probably what I am asking for is either 1) a proper documentation of what needs to be set for which role or 2) review of the authorizations to make it more consitent and simpler.

Then Role Access: Probably I don't understand this screen. Is this necesary for the roles I mentioned? If not, what does this window allow/disallow?

This can be viewed in the Role / Role Access windows.
No tags attached.
Issue History
2018-06-22 13:27maarten1962New Issue
2018-06-22 13:27maarten1962Assigned To => dmiguelez
2022-09-06 17:18caristuCategoryAdvance Warehouse Operations => Advanced Warehouse Operations

There are no notes attached to this issue.