Difference between revisions of "Emptying the data cache of your application"

From InfoEx Help Information
Jump to navigation Jump to search
(Functionality tested by)
 
(2 intermediate revisions by the same user not shown)
Line 26: Line 26:
  
 
==Related documents==
 
==Related documents==
* [[Main Page|I need help]]
+
* [[Troubleshooting overview]]
 
* [[Updating to the latest version of the InfoEx application]]
 
* [[Updating to the latest version of the InfoEx application]]
  
 
==Functionality tested by==
 
==Functionality tested by==
* Date: Nov. 16: Pascal Haegeli / Training Server / Test Version 3.00.00
+
* Date: Nov. 16, 2013: Pascal Haegeli
  
[[Category:Help Files]]
 
 
[[Category:Super User]][[Category:Operation Administrator]][[Category:Submission Moderator]][[Category:User]]
 
[[Category:Super User]][[Category:Operation Administrator]][[Category:Submission Moderator]][[Category:User]]
[[Category:Version 3.00.00]]
+
[[Category:Version 3.4.0]]

Latest revision as of 19:11, 31 December 2013

REQUIREMENTS
Permission All user levels
Connectivity Online only

This document describes how to reset your InfoEx application if it is not performing in its regular manner any more. Examples of unusual behaviours include:

  • blank screen when you start a workflow

If you are experiencing these types of problems, please let us know so that we can track down the issue and make our application better.



Step-by-step description

1. Open your Google Chrome browser.
2. Go to https://infoex.avalancheassociation.ca/clearcache.html and wait for the message that the local cache has been wiped.
NOTE Clearing your local cache will erase any observations that have not been submitted yet and all of the customization information for your observation forms. It will not affect workflow definitions and InfoEx report templates as this information is stored on the server.
3. Go to https://infoex.avalancheassociation.ca/ to start the InfoEx application again.
NOTE After you have cleared your data cache, you need to be online to log in again since your locally stored login information has been erased in the process.

Related documents

Functionality tested by

  • Date: Nov. 16, 2013: Pascal Haegeli