Very carefully - that’s how you’d go about removing those!
But seriousy, I say this because you [b]should never hack base InfoView files[b] unless you absolutely must.
What you’re better off doing is making use of the CMC security rights/permissions to toggle on/off these toolbar functions.
For example, by not allowing a user the “Edit” or “Refresh” right on a certain folder (Prod Documents), or application (Web Intelligence) - then, upon running any such report, or using Web Intelligence - they will indeed, NOT see “refresh” or “edit”.
In rare cases would you ever want to hack base InfoView files. One reason might be to specifically remove “Export to PDF” functionalitiy for BOEXIr2 - as this level of granularity didn’t exist in that version and it was more an “all or nothing” right.
Also keep in mind that modifying base jsp’s in InfoView will, when facing new servicepack/fixpack upgrades, force you to MERGE you hacks into newer codebases - and that’s a serious maintenance nightmare.
WebElements are custom functions … you need to load custom DLLs to your repository… and enable this function in your web.xml… then you can use the funtion to hide toolbar in your reports if u’re reports are using opendoc
// change the code below to match your desired output
// please see the User Guide for more information
Im basically in the same boat. We have an open document and i want to remove edit feature through security parameters in the CMC rather then hard coding.
i basically created the user through which this cross launch would take place. but im a bit confused in setting the rights. as an experiment i put the new user in administrator group and it let the open Doc report run.
Asoon as i take it out and create a new group and assign its security it gives us the same error.
what rights should i assign and where should i do it.