elizam

You should still be able to use DefaultParametersForm.jsp. Just take out the default and put in your own JSP. I am not familiar with what was before, so don't know if your jsp will work directly, or if you need to modify it a little. Here are some functions that may be useful: JRS.Controls.getController().getViewModel() reads IC info from the server and populates the javascript object var drawControl = function(..) {...} defines a function which will draw each IC using the default template set (a template for each IC type) I would be very interested in exactly what you think would be helpful to know to write input controls, because I am wrapping up the documentation for them this week!

They are stored in files. The menu text is in the pro_nav_messages.properties file (commercial) or jasperserver_messages.properties file (community). If you want localization, there are also language-specific properties files. The JRS Ultimate Guide describes in detail how to add items to a menu.

Ad Hoc was redesigned in 4.7 and Ad Hoc styles have been disabled temporarily, so for now you cannot customize the Ad Hoc interface. I am not sure, but I would guess this would include adding your logo. That would be why removing the file has no effect. This capacity will be reintroduced in a future version.

Looking at your second screenshot, can you perhaps still open the Themes folder by double-clicking? Then try to right-click the default theme and select Set as Default. If you made the changes directly in the default theme (not recommended), then try to set pods-summer as default so you can continue to work. It will be some work to fix the themes, but there is a section in the install guide that tells you what has changed for the theme. (See Planning for your 4.7 upgrade chapter). It looks like the biggest problem for you is the banner height, which is smaller in the new theme.

Yes, for commercial edition, you do need to log in as superuser to make changes to login page. But remember to CHANGE your superuser password! Do not use the default password for superuser.

There also seems to be something called Organizations which you can use to limit the data users can access. Administrators only have power within their Organization. I wonder if you could do something funky like create an Organization and Domain with the data you want and then create a subOrganization for each user that accesses the exact same data. Then, because they are the only one inside that Organization, they can't administer other users. I guess they might still be able to create a new user, but they can never get outside the walls of their little world. If this works, then you could change the whole set of access to data by changing the parent Organization - mean you can use the parent Organization to be the real setup of what people can see, and the subOrganizations are this workaround to prevent people from modifying each other. Post Edited by elizam at 04/19/2012 19:55

Actually, you do need to download some code, which is also available on the same page. Click on the "Source" menu item and you will find downloadable source there. Then use the doc mentioned above to help you configure it.