Testing external resources
It is important to test external resources and custom JavaScript code that you use on dashboards before deployment. During testing, if a new gadget causes any rendering issues, the developer can try some of the following solutions:
Disable any required web browser plug‑ins.
Press ESC to stop gadget rendering on the dashboard.
Refresh the web browser.
Reset the user’s personal dashboard.
Use the computer’s network firewall to block access temporarily to the external site where the content is stored.
Remove the user’s personal dashboard file, which contains the user’s dashboard information. This deletes all the user’s dashboards currently displayed on their personal dashboard.
If the content uses a lot of memory, such as embedded video players, lots of development can increase the memory used by the web browser. Consider restarting the web browser or monitoring the memory used by the web browser.
If there are any rendering issues for a shared dashboard or gadget, the developer that created the file can try one of the following solutions:
Change the user permissions on the file.
Delete, move, or rename the shared file.
Save a new version of the file with changed or disabled content.
For example, a developer is reviewing a dashboard gadget that retrieves information from an external web site. If the external web site is not available, the developer can replace the dashboard or gadget with a text gadget that explains why the functionality is currently unavailable.
A user’s personal dashboard file contains all the user’s dashboard information. This file is located in the user’s home directory. If the user does not have a home directory, the personal dashboard file is stored in the root of the Encyclopedia volume. Deleting this file removes all shared and personal dashboards in the user’s account.