Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0001022 | Openbravo ERP | 00. Application dictionary | public | 2007-03-12 17:29 | 2008-06-12 09:43 |
Reporter | psarobe | ||||
Assigned To | alostale | ||||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | No | ||||
Web browser | |||||
Modules | Core | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0001022: Role access. AD_Window_TRG | ||||
Description | Whenever you develope a new window, the Trigger "AD_Window_TRG" that is on the table "AD_Window" gives you access to all the roles that exist in the aplication. The part of the code is : INTO AD_Window_Access ( AD_Window_ID, AD_Role_ID, AD_Client_ID, AD_Org_ID, IsActive, Created, CreatedBy, Updated, UpdatedBy, IsReadWrite ) SELECT DISTINCT :new.AD_Window_ID, r.AD_Role_ID, r.AD_CLIENT_ID, r.AD_ORG_ID, 'Y', SysDate, 0, SysDate, 0, 'Y' FROM AD_Role r; This is wrong because you may develope the new window just for an especific role (Sales department) and suddenly all the roles can see it. Now you have to go throw all the roles and delete the access. | ||||
Steps To Reproduce | |||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|