Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0016505 | Openbravo ERP | 00. Application dictionary | public | 2011-03-28 10:07 | 2011-06-16 14:25 | |||||||
Reporter | jtarbal | |||||||||||
Assigned To | alostale | |||||||||||
Priority | normal | Severity | minor | Reproducibility | always | |||||||
Status | closed | Resolution | duplicate | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | 3.0RC5 | |||||||||||
Target Version | Fixed in Version | |||||||||||
Merge Request Status | ||||||||||||
Review Assigned To | ||||||||||||
OBNetwork customer | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Support ticket | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0016505: Warning to the user in order to clean the cache after changing AD | |||||||||||
Description | Currently, with Openbravo 3RC5 changes to the AD are automatically applied and there is no need to recompile the application. This is great as it improves the implementors productivity a lot. However, from a user perspective the changes are not visible until the cache is cleaned. It would be good that the system automatically detects the need to clean the cache and warns all users to do so. As the system already has the infrastructure to do so (it happens after updating the system through the module management console), it would be good to leverage on it. | |||||||||||
Steps To Reproduce | 1.- Log in to the system with the System Administrator role. 2.- Make sure you can do changes to the core windows (you need a template in status "In development" to do so). 3.- Go to "Windows, Tabs and Fields". 4.- Find the window "Sales Order" and go to the tab "Header". 5.- Change the position of one of the fields that are visible. 6.- Log out and log in as the client admin role. 7.- Go to the "Sales Order" tab and check if the change you did in step 5 is visible. 8.- Realize that the change is not visible. 9.- Clean the internet browser cache and check it again. 10.- Realize that the change you did in step 5 is now visible. | |||||||||||
Proposed Solution | ||||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2011-03-28 10:07 | jtarbal | New Issue | ||||||||||
2011-03-28 10:07 | jtarbal | Assigned To | => alostale | |||||||||
2011-03-28 10:07 | jtarbal | Modules | => Core | |||||||||
2011-03-28 10:14 | shuehner | Note Added: 0035261 | ||||||||||
2011-03-28 10:14 | shuehner | Issue Monitored: shuehner | ||||||||||
2011-06-16 14:25 | dmitry_mezentsev | Relationship added | duplicate of 0016134 | |||||||||
2011-06-16 14:25 | dmitry_mezentsev | Note Added: 0038367 | ||||||||||
2011-06-16 14:25 | dmitry_mezentsev | Status | new => closed | |||||||||
2011-06-16 14:25 | dmitry_mezentsev | Resolution | open => duplicate |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|