Juan Cortines (cortj)
Principal Software Engineer
Pegasystems Inc.
cortj Member since 2014 7 posts
Posted: May 11, 2020
Last activity: May 12, 2020
Posted: 11 May 2020 7:10 EDT
Last activity: 12 May 2020 9:36 EDT

Troubleshoot with Client for Windows


In order to enable the "debug" options in Client for Windows, the "prpc.container.debuggable" customisation property must be set to "true".

When Client for Windows is built with this option enabled, an additional "Debug" menu item is displayed on the top left of the application's window.

When clicking on the "Debug" menu item, the list of available processes will unfold. The number of processes may vary, but usually it is made up of a main "Bootstrap" process and one or two additional "WebView" processes.

Select "Bootstrap" > "Toggle Developer Tools", if you are interested on debugging Client for Windows internal routines such as Client Store's Data Synchronisation.

Most of the time, you'll be interested on debugging the UI. For this select "WebView" > "Toggle Developer Tools". Please note there may be more than one WebView instance, so make sure you select the one you are interested in.

To learn how to use Chrome's DevTools, please refer to Chrome's documentation 

Retrieving and reading logs 

At this moment Client for Windows does not have a built in functionality to retrieve logs remotely.

However reading the logs file on Windows is quite straight forward since, unlike Android and iOS, application's data is not sandboxed.

To read the logs simply open a File Explorer and navigate to "AppData\Roaming\Pega\logs" under the User's folder (usually under C:\Users\UserId).

Please note the application name in the "Roaming" folder may be different if Client for Windows has been customised to have a different one.


***Edited by Moderator Marissa to add the Developer Knowledge Share tag***

Pega Platform 8.4 Developer Knowledge Share