A custom portlet disappears when a user uses a link in the portlet to view a project change request and then uses the cancel button to return to the portlet twice. This only happens when the user uses a filter on the custom portlet.
Steps to Recreate:
Expected Result: The custom portlet should still appear on the Overview page.
Actual Result: The custom portlet has disappeared from the Overview page.
Error from the App-niku.log:
ERROR 2010-03-01 14:39:59,900 [http-80-Processor4] web.XMLPageProcessor (Richards:5815617__-61978356:copIssuesRisks) Unable to process portlet, standard error portlet will be substituted. Exception was: com.niku.union.web.WebException: com.niku.union.web.WebException: net.sf.saxon.trans.DynamicError: A sequence of more than one item is not allowed as the first argument of string-length()
Don't use a filter twice in a row in a user-defined portlet.
This issue has been documented as CLRT-56038 and is assigned to development for review. If you are experiencing this problem and the workaround above does not significantly help, please contact CA Clarity Support.
Keywords: CLARITYKB, CLRT-56038, clarity12open, portlet, nsql, query, custom, filter, change request.