Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0038345
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformmajoralways2018-04-12 12:342018-05-04 14:13
ReporterucarrionView Statuspublic 
Assigned Toplatform 
PriorityhighResolutionduplicateFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0038345: Error message when trying to modify amount to keep for cash up

DescriptionThe user is not able to modify the Amount to Keep in POS Terminal Type (espèces payment method). On saving, there is a message saying that the user is not able to update data.

The role has edition permission at field level (amount to keep) but has not at window (POS Terminal Type) and tab (Payment Method) level. When trying to modify the amount to keep field, the following error message is displayed: ""La sauvegarde a échoué. org.openbravo.base.exception.OBSecurityException: Entity OBPOS_App_Payment_Type is not writable by this role/user: Chef de caisse-146"""
Steps To Reproduce+ Take a role with access to POS Terminal Type window.
+ At tab level, for"payment method" tab, unselect "editable" checkbox.
+ At field level, for"amount to keep" field, select "editable" checkbox.
+ Loggin in this role.
+ Try to modify amount to keep field.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
duplicate of design defect 0038185 newTriage Platform Base It is not possible to save register with a role with access just to one field 

-  Notes
(0104283)
jarmendariz (developer)
2018-05-04 14:13
edited on: 2018-05-04 14:20

Meanwhile this design defect is solved, a possible workaround is to use the Role Access Window to enable access to the Table used by the Window.


- Issue History
Date Modified Username Field Change
2018-04-12 12:34 ucarrion New Issue
2018-04-12 12:34 ucarrion Assigned To => platform
2018-04-12 12:34 ucarrion Modules => Core
2018-04-12 12:34 ucarrion Resolution time => 1524866400
2018-04-12 12:34 ucarrion Triggers an Emergency Pack => No
2018-04-23 17:43 jarmendariz Assigned To platform => jarmendariz
2018-04-23 17:43 jarmendariz Status new => acknowledged
2018-04-23 17:44 jarmendariz Status acknowledged => scheduled
2018-04-24 11:20 caristu Relationship added duplicate of 0038185
2018-04-24 12:19 jarmendariz Assigned To jarmendariz => platform
2018-04-24 12:19 jarmendariz Status scheduled => acknowledged
2018-05-04 14:04 jarmendariz Type defect => design defect
2018-05-04 14:04 alostale Status acknowledged => scheduled
2018-05-04 14:04 alostale Status scheduled => closed
2018-05-04 14:06 jarmendariz Status closed => new
2018-05-04 14:13 jarmendariz Note Added: 0104283
2018-05-04 14:13 jarmendariz Status new => closed
2018-05-04 14:13 jarmendariz Resolution open => duplicate
2018-05-04 14:20 jarmendariz Note Edited: 0104283 View Revisions


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker