Updating to the latest available jar file for Periscope and clearing your cache for in-build adjustments.
Posted by Jason Townsend on 01 May 2014 03:03 PM

For every major release of Periscope (for example 2.1, 2.2, 2.3), there are multiple fixes and enhancements made throughout the life of that build.  Some revisions require an updated JAR (for example updating your 2.2.30 jar to 2.2.31) and others require a browser cache clear to capture an adjustment to the Periscope build.  The version of Periscope that you have installed is displayed at the bottom middle of the dashboard - for example it will say "2013 -Activelogix (2.2.31).  If there is a "-M" next to the build, it denotes that it's a "military" or "offline" file version.  We notify you that your Periscope JAR is out of date with an exclamation point icon at the bottom of the dashboard.  Clicking on the icon will tell you the latest build available as well as what is included in the update.  Previous update release notes are also displayed.  Clicking "apply" will generate an email to tech support at Activelogix as a request for an updated file so we can respond with the appropriate file.  

Other minor fixes and adjustments can be captured with a cache clear of your browser history.  This varies according to the browser your using (Chrome, Firefox, IE, etc.) and you can find detailed instructions for each browser at's-Cache#Chrome_v10.2B.  It's not a bad idea to clear your cache on occasion to capture any recent adjustments that we've made to Periscope.

See the attached screenshots for more information.


 2014-04-30_1656.png (307.38 KB)
 2014-04-30_1659.png (454.97 KB)