Question
Sun Life Financial
CA
Last activity: 9 Jan 2025 10:30 EST
Get Values of variables at Runtime in V22.1
in v19.1, we were able to do that through Robot Inspector, which no longer exists in v22.1. Is there another way that we can get the values of all loaded variables at Runtime?
Accepted Solution
Updated: 9 Jan 2025 10:30 EST
Pegasystems Inc.
US
@Thierry_SLF Since this level of debugging is only available in Studio, I suggest using the RuntimeLog for debugging at Runtime. One thing you can do to assist in logging that won't appreciably affect performance, is to use the changed event from each variable to write the new value to the log. I always preface my log messages with "***LOG - " so they are easy to search for. If you do this, you can easily locate all of the places the variables values have changed. This allows you to easily see what the last value was. This technique makes it explicit as to when a variable changed and what its value is (and you could even log what the value was before the change here as well as that information is provided by the changed event).
Another option would be to create your own debugging UI and pass whatever values you want to it.
Pegasystems Inc.
US
@Thierry_SLFIn 22.1.22 and later, there is an option on the Debugging tools menu to view the contents of variable used in the current automation. Add a breakpoint and any variables used in that automation will display and you can view and even edit their values.
Sun Life Financial
CA
@ThomasSasnett, yes, that's good in Studio, but not using the Runtime. Is there any way to access the values of these variables the way Robot Inspector used to do it?
Thanks
Pegasystems Inc.
US
@Thierry_SLFMay I ask what would require seeing these values at Runtime versus in Studio while you are testing?
Sun Life Financial
CA
@ThomasSasnett We use that a lot when troubleshooting issues on users' or unattended machines
Accepted Solution
Updated: 9 Jan 2025 10:30 EST
Pegasystems Inc.
US
@Thierry_SLF Since this level of debugging is only available in Studio, I suggest using the RuntimeLog for debugging at Runtime. One thing you can do to assist in logging that won't appreciably affect performance, is to use the changed event from each variable to write the new value to the log. I always preface my log messages with "***LOG - " so they are easy to search for. If you do this, you can easily locate all of the places the variables values have changed. This allows you to easily see what the last value was. This technique makes it explicit as to when a variable changed and what its value is (and you could even log what the value was before the change here as well as that information is provided by the changed event).
Another option would be to create your own debugging UI and pass whatever values you want to it.