Note: This guide will primarily cover accessing the console on a PC using Google Chrome, but some Mac specific instructions are included as well. The process for accessing the console using Microsoft Edge is very similar to Chrome and any major differences will be noted.
Summit is a web browser based application, the application is accessed by opening a web browser (Chrome and Edge being the primarily supported options) and navigating to a specific address. Occasionally, issues that are observed within Summit can be caused by communication problems between the backend portions of the software and the User Interface within the browser. The developer console is a tool baked into the browser that can be accessed to view error messages and other pieces of information that are generated when preforming specific actions within Summit. These error messages are rarely something simple for an end user to decipher and solve the problem, but can be extremely valuable for our developers in diagnosing and fixing issues that may arise.
When interacting with our support team, you may be asked to provide a screenshot of the information found in the console in addition to what you were doing within the application when the problem arose. This information will most likely be asked for in scenarios where Summit "crashes" or a window within the application either fails to load or is stuck in the loading state. The process of accessing the console is fairly simple and very similar between Chrome and Edge, but as there are some small differences between the two, instructions for each will be provided below. Additionally, the chrome instructions will have some Mac specific instructions that will be highlighted in BLUE.
CHROME:
In Chrome, the easiest way to access the console is by using the keyboard shortcut Ctrl + Shift + J (Cmd + Option + J on a Mac). Alternatively, you can use your mouse to right click within the webpage and select the Inspect option, as shown below, and then click on the console tab in the window that opens up.
Clicking on inspect or using the keyboard will bring up the developer console. The console will open on the right side of the screen by default and have a series of entries, usually with red and yellow entries listing possible errors. The entries in the console are chronological with the most recent ones at the bottom of the list. Take a screenshot of the information in the console after the error occurs and include that information when submitting a support ticket. One note, closing the browser will clear out the information in the console, so you may have to perform the action that caused the problem again to accurately capture the information in the console.
Below is an example from a test environment where a treatment plan assigned to a prescription had been improperly deleted and not replaced, so an error message appeared when attempting to give the patient an injection.
EDGE:
The process for accessing the console in Edge is very similar to the process in chrome with only some cosmetic differences. The console can be reached by either using the Ctrl + Shift + i keyboard shortcut or by right clicking in the browser and choosing the Inspect option. From here, select the console tab from the top of the inspect window to open the console. Take a screenshot of the information found in the console window and include it with the submitted support tickets. The only real difference in process between Edge and Chrome is that in some older versions of Edge, the Ctrl + Shift + j shortcut to go directly to the console is not available and you need to go to the inspect window first and then select the console tab.