Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0020210Openbravo ERP00. Application dictionarypublic2012-04-04 18:152022-02-01 08:09
aperturelabs 
Triage Platform Base 
normalmajoralways
acknowledgedopen 
30Ubuntu 10.04
3.0MP8.1 
 
Apple Safari, Google Chrome, Mozilla Firefox
Core
No
0020210: Process that execute a Jasper Report after clicking a button always fails
I'm trying to create a button associated to a process that print a Jasper Report. I created the button and the relative process. When I click this button, the result is always a new browser window with the error: "You do not have sufficient privileges to access this page". The process is defined with this parameters:
- Data Access Level: Client/Organization
- UI Pattern: Standard
- Report: No
- Jasper Report: Yes
- JR Template name: @basedesign@/my/correct/path/template.jrxml
- Create a new column in a database table, type character, lenght 1
- Create a process to print the Jasper Report template with parameters as explained in http://wiki.openbravo.com/wiki/Report_Example#Application_Dictionary [^]
- Add the button in Tables and Columns and link it to the process created
- Add the button in Windows Tab & Fields
- Recompile e restart Tomcat
- Click the button created
A possible workaround is to set the process UI pattern to manual, remove the jasper flag, set the report one, and code the java servlet that loads and renders the jrxml template.
No tags attached.
? com.wordpress.katratxo.reports-0.1.0.obx (12,105) 2012-04-10 10:06
https://issues.openbravo.com/file_download.php?file_id=5123&type=bug
Issue History
2012-04-04 18:15aperturelabsNew Issue
2012-04-04 18:15aperturelabsAssigned To => alostale
2012-04-04 18:15aperturelabsWeb browser => Apple Safari, Google Chrome, Mozilla Firefox
2012-04-04 18:15aperturelabsModules => Core
2012-04-10 10:06iperdomoFile Added: com.wordpress.katratxo.reports-0.1.0.obx
2012-04-10 10:07iperdomoNote Added: 0047410
2012-04-26 13:16alostaleWeb browserApple Safari, Google Chrome, Mozilla Firefox => Apple Safari, Google Chrome, Mozilla Firefox
2012-04-26 13:16alostaleNote Added: 0048025
2012-04-26 13:16alostaleTypedefect => design defect
2012-09-24 20:45AugustoMauchWeb browserApple Safari, Google Chrome, Mozilla Firefox => Apple Safari, Google Chrome, Mozilla Firefox
2012-09-24 20:45AugustoMauchNote Added: 0052380
2012-09-24 20:45AugustoMauchPriorityhigh => normal
2012-09-24 20:45AugustoMauchStatusnew => scheduled
2013-07-29 09:30txasuIssue Monitored: txasu
2017-03-31 14:36alostaleStatusscheduled => acknowledged
2017-04-10 14:33alostaleAssigned Toalostale => platform
2022-02-01 08:09alostaleAssigned Toplatform => Triage Platform Base

Notes
(0047410)
iperdomo   
2012-04-10 10:07   
Attached you'll find a sample module with the problem
(0048025)
alostale   
2012-04-26 13:16   
Setting as design defect, this is not implemented in current WAD processes. It needs to be decided whether it makes sense to be implemented just with the new processes to come or also for WAD.
(0052380)
AugustoMauch   
2012-09-24 20:45   
Effort: 4
Impact: low
Plan: mid