Consider that you’ve created content and published it, but it’s not appearing as expected for one of your end users. To identify the issue, you want to test the content directly on the end user’s Desktop application. However, the end user’s application might not have the Desktop Studio extension installed. In such cases, you can still use Diagnostics to identify and troubleshoot the content by opening it as a standalone entity directly on your end user’s Desktop application.
To open Diagnostics on Desktop applications where the Desktop Studio is not available, follow these steps:
Go to the Desktop application where you want to troubleshoot the content.
Launch Diagnostics on Desktop using the following keyboard shortcut:
Press
Ctrl + alt + ;
Once Diagnostics opens on your Desktop application, it displays all relevant content and widgets for the page. Follow the steps mentioned in the following articles to troubleshoot your content and widgets.