We have in one MWS CAF portlet application on the inbox results page a extended portlet url of type action with 4 url parameters, one action parameter and 3 render parameters. When the url is clicked the value “true” is passed for the portlet preference “isResultsViewDisabled” from the inbox results portlet. In the inbox results portlet based on the value of this portlet preference the search is executed or not.
The portlet preference is defined as follows :
Is Results View Disabled
The extended portlet url is located inside a portlet simple link.
Similar we have on the task details page an extended portlet url (of type render) inside a portlet simple link, this time with two parameters, one of which sets the value of the above mentioned portlet preference to false.
The problem we had in our production environment was that the value of the portlet preference got stuck to “true”. The value did not change even if the user logged out of the application and logged back in. We tried to redeploy the CAF portlet application but the value was still “true”. After removing completely the CAF portlet application and a new deployment the value of the portlet preference got back to normal and was set each time one of the “extended portlet url” was clicked. The problem reproduced on all 4 MWS nodes from the cluster and for each user.
Does anybody encounter the same behaviour when a portlet preference value got “stuck” ? Is there a possibility to clear somehow the values of one or all portlet preferences of one task application via the admin or sysadmin user at runtime? Shouldn’t a CAF portlet application deployment reset the values of all portlet preferences?
Thank you for your suggestions/input.