How to customize the header panel / system header for different client orgs?
5 April, 2014
Hi,
I have a YF instance running with multiple client orgs. Is there any way to customize the header panel / system header differently for different clients? I would like to put the logo for each client on the header panel.
I have only figured out how to get the same header for all clients using this -- http://wiki.yellowfin.com.au/pages/viewpage.action?pageId=3866702
By header panel I mean this -
I have a YF instance running with multiple client orgs. Is there any way to customize the header panel / system header differently for different clients? I would like to put the logo for each client on the header panel.
I have only figured out how to get the same header for all clients using this -- http://wiki.yellowfin.com.au/pages/viewpage.action?pageId=3866702
By header panel I mean this -
Hi Asif,
You should be able to use your own header/footer within any client org, as the Admin > Config >Integration item to set this is set per client org.
E.g.
[img][/img]
Please let me know if I have misunderstood what you were after, or this does not give the expected results.
Regards,
David
You should be able to use your own header/footer within any client org, as the Admin > Config >Integration item to set this is set per client org.
E.g.
[img][/img]
Please let me know if I have misunderstood what you were after, or this does not give the expected results.
Regards,
David
Hi David,
Thanks for your response. We are having some trouble working with JSP, I guess since we do not have much experience with it.
We are getting the error, 'Problem accessing the absolute URL: header.jsp', in the header area.
We copied the 'CustomHeaderExample.jsp' file from 'C:Program Filesdevelopmentexamples' folder and pasted it in the ROOT folder 'C:Program FilesYellowfin 7appserverwebappsROOT' under the name 'header,jsp'.
Then we entered 'header.jsp' in the URL of the configuration setting.
Here is the screenshot of the configuration screen.
Thanks
Thanks for your response. We are having some trouble working with JSP, I guess since we do not have much experience with it.
We are getting the error, 'Problem accessing the absolute URL: header.jsp', in the header area.
We copied the 'CustomHeaderExample.jsp' file from 'C:Program Filesdevelopmentexamples' folder and pasted it in the ROOT folder 'C:Program FilesYellowfin 7appserverwebappsROOT' under the name 'header,jsp'.
Then we entered 'header.jsp' in the URL of the configuration setting.
Here is the screenshot of the configuration screen.
Thanks
Hi Asif,
Not sure why it's not liking the path.
I know that's Java/Tomcat should be looking for the file.
It can also be case sensitive, so that's another thing to look at.
Do you have another folder under the WebApps directory?
Regards,
David
Not sure why it's not liking the path.
I know that's Java/Tomcat should be looking for the file.
It can also be case sensitive, so that's another thing to look at.
Do you have another folder under the WebApps directory?
Regards,
David
Hey David - We recently implemented client orgs as well on our instance and applied the custom header. Works fine for both the default org and the client org, but we get that "Problem accessing the absolute URL: custom_header.jsp" on the org selection screen. Just some text at the top.
Do you think it could be a permissions issue on the jsp file itself? We're running on Ubuntu.
Do you think it could be a permissions issue on the jsp file itself? We're running on Ubuntu.
Hi Nicholas,
Yeah that should really be the only reason why you cannot access the page.
I have seen similar things in the past and it was just the pathing convention.
Can you access the .jsp via the browser.
Regards,
David
Yeah that should really be the only reason why you cannot access the page.
I have seen similar things in the past and it was just the pathing convention.
Can you access the .jsp via the browser.
Regards,
David
We figured it out. There was some code in our JSP page that was dependent on an authenticated user to determine which client org (we have different headers for different orgs). Since the selection screen doesn't have a client yet, it was bombing. Got that sorted and it works fine.
Ahhh, that makes sense, I didn't even think about that!
Please let us know if you run into any other issues.
Thanks,
David
Please let us know if you run into any other issues.
Thanks,
David