Jump to: navigation, search

Debug Block

You can use the Debug block to define a specific checkpoint in a module or application. This is useful when you are developing an application and need to debug runtime logic that isn't running as intended.

For example, you might add some ECMAScript expressions to an Assign Variables block to assign values to certain variables, but discover that the logic isn't producing the desired result.

To assist in debugging this, you could add a Debug block immediately after the Assign Variables block to capture the values of the variables as they exist at that time. These values can then be reviewed in Designer Analytics, under the debugcheckpoints property of the Session Detail Record (SDR) .

Important
The Debug block is only processed in the Dev, QA, and UAT application streams. It is ignored in the Live stream.

Debug tab

Capture Checkpoint

Select this option to enable debugging for a specified checkpoint.

Checkpoint Name

Specify the name of the checkpoint to be captured. You can also specify a variable that holds the value of the checkpoint name.

Condition

Specify the condition as a script expression. For example:

var02 === 1

Data tab

This tab displays a list of variables that can be captured by the checkpoint. Select the variables that you want to include.

Advanced tab

Enable the Write these statements to platform logs option if you want to write the results of the specified ECMAScript expressions to platform logs that can be reviewed by Genesys support. Click Add Log to enter the ECMAScripts.

You can also specify an error message statement to add to the logs if the expression evaluations result in an error.

This page was last modified on July 25, 2019, at 13:28.

Feedback

Comment on this article:

blog comments powered by Disqus