Trying certain self-help remedies first before diving into writing a ticket might just clear up the problem, can save you a lot of time and inconvenience! These are things we often need to ask, so try them first and see what happens. If you still need to open a ticket, you’re ready to document the results of these actions and will still save valuable time by reducing our need to ask follow-up questions. Why do we ask these things? We’re happy to tell you!
Why does CiraConnect Support team ask you to clear your browser cache?
Cloud based software has another advantage we didn’t mention in the lead article: new code and bug fixes can be pushed out to all users without them having to do anything more than logging in afresh to access it. Problem becomes: your cached data is from the previous version and can create conflicts. However, if you notice odd behavior in CiraNet or any web-based platform it is a good idea to try clearing your cache. Please understand that if you report an issue to our User Support team, we often suggest that you try doing just that as a first line of support to rule out the possibility that any cached data is causing the issue you are seeing; therefore, just go ahead and make sure you try it first. You might just find it helps resolve the issue with no more time spent on your part. If you are worried about losing data, the important key here is we’re trying to encourage you to have a fresh start with the CiraNet modules, so those cookies are the ones we’re asking you to clear. A common misnomer is that when you clear your cache you lose all your passwords. This is not necessarily so. You can choose to wipe the slate clean, but you need not lose any saved passwords.
Why refreshing the page is important. Some of you have been asked to try refreshing your page by using Ctrl+F5, otherwise known as a hard return. This forces the application to bypass the cache and reload a completely fresh version of the page sent by the server. It is not to dismiss the error you may have seen, which likely will still need to be reported, but might get you up and running in the interim.
Why do we ask what browser you are using? While many of you reading this article are using Chrome, in order to support you most effectively, the Support tries not to assume anything, and if you are reporting an issue on behalf of a board or committee member, that is a definite question to ask them and disclose in the ticket when opening a support ticket on their behalf. What version of your chosen browser is great to know as well. If you are running an older version of a specific browser, that could be a contributing factor. As many of you know, we will independently try to re-produce issues that are reported to gather as much data as possible, and it’s important to try to do so in the same browsing environment you are using.
Using CiraNet Management / Board Portal
CiraNet Management / Board Portal is using the latest version of our software, currently only accessible by our internal users (board members do not now have access.) We are updating it regularly with new advancements and features. Do note that despite this being very stable software, the nature of how we are adding new functionality and value week after week means there is a slight chance for minor hiccups. We want to ask you to help contribute to improving CiraNet by reporting the issue to your supervisor.
Access to CiraNet Management / Board Portal To access the new functionality available, you need to first visit CiraNet.com, then select Management Portal Beta. (This is not currently available for Board members)
As always, my inbox is open to your feedback about any specific communication suggestions at hamed.nouri@ciraconnect.com. As a reminder, any application issues and/or application-specific requests should be submitted through either the Idea Center or Technical Support menu options in User Support.
CiraConnect, 6400 International Parkway, Suite 1000, Plano, Texas 75093, United States