If you need to diagnose issues on the first layer of Triofox, there are two helpful tools for the debugging process of presentation-tier related issues (aka UI).
The first tool is the browser console, which is a standard feature in Firefox, Chrome, Edge, and IE. The second tool is the ASP.Net tracing mechanism, which is a standard feature of .Net Framework.
The Browser Console
If the support team has instructed you to submit the console output, please do the following:
1-From any computer, open your browser and press the F12 key on the keyboard (this works on all major browsers). If you are on a self-hosted environment, it is useful to perform these steps from inside the Triofox server itself, via the http://localhost URL. ASP errors are normally suppressed to outside users, but will display in their entirety if viewed from the server.
2-Go to the web page where the problem occurs
3-Switch to the "Console" tab. Ensure that "errors" are being shown. You can hide "warnings" to limit the output
4-Take a full-screen screenshot (not cropped) of the page showing any errors, as well as the URL, and page output. Example screenshot of the Firefox browser (other browsers will be very similar):
5-Switch over to the Network tab. You may need to reload the page if you do not see any entries. Scroll down and locate any errors. Once you locate and select an error entry, take a full-screen screenshot (not cropped), then copy the entire raw headers to a new notepad file.
6-Switch to the Response sub-tab and copy the entire output to a new notepad file.
7-Send all screenshots and text outputs to the Triofox team with your support ticket
If the support team has instructed you to submit the ASP.Net tracing output, please do the following:
1-Enable tracing in the web config of the web application where the problem occurs. Triofox has two main web components on its UI layer. One is located in a folder called "/portal" and the other is in a folder called "/management." A file called web.config is located in each of these directories. Open this file with notepad and add the following "trace" tag as a sub-node of "system.web":
<trace enabled="true" pageOutput="false" localOnly="false"/>
2-Visit the trace.axd page in the directory of the web application where the problem occurs. Example:
3-Locate the problem page. This is usually the page that was flagged with errors from the browser console->network tab (see step 5 above). Click on the View Details link.
4-From your browser's File menu, please print the entire page as a PDF file, or save the entire web page as HTML.
5-Send all outputs to the Triofox team with your support ticket