| Category: | Bug report |
Priority: | Immediate |
Status: | Assigned |
| Project: | Severity: | Major |
Resolution: | Open |
|
| Component: | Reproducibility: | Always |
Assigned to: |
Adding the decorate=no parameter in URL doesn't work with JasperServer Pro and CP 4
| Attachment | Size |
|---|---|
 jasper-pro-screen1.JPG | 66.21 KB |
9 Comments:
How the heck does this kinda stuff not get picked up before a major release?!
I am also facing the same issue.
We are also facing similar issue while trying to add a custom dashboard as a home page for a role as posted at http://www.jaspersoft.com/how-set-role-based-jasperserver-home-pages
It didn't work due to this issue. Is there any workaround / simple patch for this issue?
This issue is fixed in JS CE 4.1 ..
Thank you for the info! Any simple workaround/patch for JasperServer Pro 4.1?
Based on current status and my knowledge , it is already fixed in Pro 4.1 > can u please give me screen shot/error details so that i can exactly see what issue we are talking abt ?
Product Edition: Enterprise, Product Version: 4.1.0, Build: 20110531_1311, Windows version.
Steps I did:
1) Edited jasperserver-pro\WEB-INF\jsp\modules\home\home.jsp and added <jsp:include page="homeForDemo.jsp"/> unconditionally.( without any authz tags )
2) In the jasperserver-pro\WEB-INF\jsp\modules\home\homeForDemo.jsp found the iframe location, and edited the src as follows.
src="${pageContext.request.contextPath}/flow.html?_flowId=dashboardRuntimeFlow&dashboardResource=%2Fdashboards%2FNew_Dashboard&decorate=no"
No errors in the logs. I have attached the screenshot of the home page.
I am sure that the /dashboards/New_Dashboard resource is present and the url http://localhost:8080/jasperserver-pro/flow.html?_flowId=dashboardRuntim... in a browser loads correctly.
But if i try http://localhost:8080/jasperserver-pro/flow.html?_flowId=dashboardRuntim... in a browser it doesn't work. Just shows "Dashboard Viewer" with two buttons - Refresh and Open.
1. i have tested decorate=no for the reports only and it works ok
2. For dashboards, can u please try using this parameter
&viewAsDashboardFrame=true
[ i tested in 4.1 Pro and it works for me ]
there is internal logged bug about documenting these parameters and make sure they work over the releases . sorry for inconvience ..
WOW!! viewAsDashboardFrame=true worked. Thanks a lot.
Edited the iframe src as follows to fix this.
src="${pageContext.request.contextPath}/flow.html?_flowId=dashboardRuntimeFlow&dashboardResource=%2Fdashboards%2FNew_Dashboard&decorate=no&viewAsDashboardFrame=true"