I’ve been testing out the search capabilities with XPages, similar to the Site Finder Demo. I’ve found that in setting a computed field with javascript and a search button, the computed field displays the previous querystring. I’m using a session scope variable, computed dynamically.I see the same thing happens in the Site Finder Demo that you have in the xpage tutorial.
Subject: Re: Site Finder Demo -computed field
The reason that that is happening in the Site Finder Demo is because the computed field is displaying the value of sessionScope.queryString before it’s assembled, meaning that it’s showing the previous queryString. This can be simply changed by reordering the code so that the queryString is calculated and saved to the session before displaying it on the page, perhaps in the beforePageLoad event.
Subject: Computed Field in SiteFinderDemo
SPR # OIHZ7N8M9Z has been created for this issue. Currently being investigated by development.