Friendly User

Hypothetical scenario:We have an Ad Hoc View (Table type), and one column can contain HTML tags. Since those tags are not rendered as HTML (tags are visible), we would like to create a calculated field that would strip tags from that column's content. Solutions:It is possible to do that on domain level in calculated fields sections. for this we would have to write a function in applicationContext-semanticLayer.xml. In the defaultSQLGenerator bean add a new entry: <entry key="escapeHTML"> <value> return "regexp_replace(" + sqlArgs[0] + ", '\\&lt;.*?&gt;', '','g')" </value> </entry> After restarting the server this function will be available to be used in domain designer calculated fields section. You just do escapeHTML(fieldName). However, while this approach might work for databases that have the regexp_replace function, but for example for MySQL, it is not good. So here you have to add a new groovy function that can be later used in the ad hoc editor. In /WEB-INF/groovy/groovy_column/BaseGroovyColumn.groovy add the following function: def StripTags(String s) { if (s == null) { return null; } else { return s.replaceAll("\\<.*?>",""); } } and in /WEB-INF/applicationContext-el.xml add : <bean parent="functionDef"> <property name="name" value="StripTags"/> <property name="javaType" value="java.lang.String"/> <property name="argumentTypes"> <list> <value>#{ objectTypeMapper.checkType('String') }</value> </list> </property> </bean> NOTE - as of 6.3.0 you need to edit applicationContext-el-operators.xml instead of applicationContext-el.xml The result is that now you have StripTags function that can be used in ad hoc calculated fields. Something to note about this approach: Since there is no SQL implementation, the property "inMemory" should be true, but this is covered because the parent bean "functionDef" already has inMemory set to true.The argumentTypes list is set correctly for a single String argument. If you have different argument types, you can look in applicationContext-el.xml for examples. In more complex cases, you may need to implement custom logic in a subclass of OperatorDefinitionImpl.Explanation of the difference between sqlArgs and args arrays:sqlArgs contains strings, which are SQL versions of the arguments passed to the function.args contains DomEL expression objects for the arguments; if you know something about these objects, you can access some useful information. For example, a string constant like 'abc' in DomEL will get turned into a Literal object, and you can get the value by accessing the "value" property, as above.

Symptoms:You consistently get the issue, when creating an ad hoc report from a view, where the user is lacking permissions for the temp folder. Resolution:To allow users to create ad hoc reports and views the user needs to have Read+Write+Delete permissions for the /temp/ folder. In some cases it might be useful to restrict access to the temp folder if the user is just executing the reports or is not a power user in the system. If you set up them later as such you need to make sure that their roles have enough permissions for the temp folder.

Symptoms:When running any report on TIBCO JasperReports Server through the UI the following error is consistently thrown: [toc]java.lang.IllegalStateException: Exception occurred rendering view org.springframework.web.servlet.view.JstlView: name 'modules/viewReport/ViewReport'; URL [/WEB-INF/jsp/modules/viewReport/ViewReport.jsp][/code]Resolution:If this exact problem occurs on a consistent basis then most likely you are running JasperReports Server on Tomcat 7.0.65 or 8.0.28. This is a known issue for those versions. Solutions would be to downgrade the Tomcat version. For example 7.0.63 would work totally fine. If you get a similar error that is thrown for other pages then you might: Be running out of memory (check the logs for the OutOfMemory exception). Increasing the JVM heap size should resolve the problem Have a customization that renders the JSP non-compilable which would require a closer look at the nature of modifications Have incorrectly compiled JSP for some reason. Stopping the server and cleaning the tomcat work folder could help in this case.