When the page is refreshed, the current state of the page is not kept intact. HTTP cookies could be used to maintain some state, but they are limited in size, and are transmitted back to the server with each request. Some client state information should also be restored when the user logs in on different machines.

As a user navigates within Windchill, they may make changes that affect the user interface display, such as selecting a tab on the information page (for example, selecting My Tab). If the browser is refreshed, the user may expect to remain on their last active tab. To retain this information, some sort of persistence mechanism is required to refresh the page to the correct state .

There are two persistence mechanisms available for use. The Client State Provider will store information in the browser and will be specific to that particular browser on that particular machine. The Server State Provider will store information in the database and will make the information available for that user on any browser and any machine.

If user interface stickiness is causing issues or acting strangely, you may need to reset the stickiness. Server state stickiness and client state stickiness are reset differently, and you don’t necessarily need to reset both, depending on what is acting strangely.

To reset the server state stickiness, navigate to http://<host>/<webapp>/app/netmarkets/jsp/user/utilitiesList.jsp and click “Reset Server Stickiness”. This action will popup a confirmation box and by clicking OK all your server state stickiness will be reset to the default state. This includes both Information Page tab order and Information Page table order.

Various actions may clear the client state provider stickiness information depending upon your browser. To ensure that all client stickiness is removed, delete all your temporary internet files (usually in the Tools menu), close all browser windows, and restart the browser.