Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0051662 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Openbravo ERP] A. Platform | minor | have not tried | 2023-02-21 16:12 | 2023-02-26 21:09 | |||||||
| Reporter | alostale | View Status | public | |||||||||
| Assigned To | meriem_azaf | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | scheduled | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| 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 | 0051662: cannot set by role a field to be readonly on new if its column is no updateable | |||||||||||
| Description | Fields defined as editable (no read only) and whose column is as no updateable, can be edited when a new record is being created but not after saving it. It is not possible to make them read only also on creation setting a role configuration. | |||||||||||
| Steps To Reproduce | 1. Log in backoffice 2. In role window select "The White Valley Group Admin" 3. Select Business Partner window access 4. Add a new Tab Access for Business Partner tab with Editable Tab value set to Yes 5. Add a new Field Access for Organization field with Editable Field set to no 6. Log in with The White Valley Group Admin role 7. Create a new Business Partner ERROR: Organization window can be edited (while the record is new and unsaved) but we'd expect not to be | |||||||||||
| Proposed Solution | Issue 0036066 fixes the opposite case: opening up restrictions through configuration, which should not be allowed. But we should allow to define more restrictive settings per role. | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2023-02-21 16:12 | alostale | New Issue | |
| 2023-02-21 16:12 | alostale | Assigned To | => Triage Platform Base |
| 2023-02-21 16:12 | alostale | OBNetwork customer | => No |
| 2023-02-21 16:12 | alostale | Modules | => Core |
| 2023-02-21 16:12 | alostale | Triggers an Emergency Pack | => No |
| 2023-02-21 16:12 | alostale | Relationship added | related to 0036066 |
| 2023-02-21 16:13 | alostale | Relationship replaced | caused by 0036066 |
| 2023-02-26 21:09 | AugustoMauch | Status | new => scheduled |
| 2023-02-26 21:09 | AugustoMauch | Assigned To | Triage Platform Base => meriem_azaf |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |