CasewareDocs

Debugging Workflow

You can debug workflow actions and embedded dialogs.

App Workflow

In this dialog box you can run the debugging of a macro added to a custom routine in a workflow. All routines that can be run will be displayed. Select the routine(s) you want to check.

You can use the following commands for the check:

Commands for checking (Workflow)
Command Description

Close Debugger

Closes the dialog box.

Start debugging the app workflow action

Opens the debugger of the program in which you created the selected routine.

Abort debugging immediately

Cancels the debugging and closes the corresponding dialog box. This icon is only available as long as the debugger is open.

Toggle the task cancellation request

Abort debugging immediately cancels the debugging immediately. Using this command might lead to a corrupt file. In contrast to this command the Toggle the task cancellation request command does not cancel the debugging immediately. Use this command to set Is cancellation requested to "True" or "False". If it is set to "True", the macro will check if the debugging can be completed. With this command you can test if the cancel process works correctly when the user runs a corresponding command, i. e. when he cansels the tagging. This icon is only available as long as the debugger is open.

Start Debugger Settings dialog

Opens the Debugger Settings dialog box where you can define which messages should be displayed during the debugging.

Help

Opens the help for the debugging of a routine.

Step-by-Step

  1. Select the routine(s) you want to check.
  2. Click Start debugging the app workflow action to start the debugging. The debugger of the program in which the selected routine was created will be opened.
  3. Start the debugging in the corresponding environment.
  4. If you have set breakpoints, the status will be shown at each breakpoint. Click Continue with debugging the task to resume the debugging after a pause.
  5. In the right area information concerning the context of the audit test (SmartContext object) is displayed. Use the icons to sort this information by category or in alphabetical order. For some entries additional information is available. Click the corresponding name. If further information is available, an icon will be displayed. Click the icon to show the information.

Debugging Embedded Dialogs

In this dialog box you can run the debugging of embedded dialogs. All embedded dialogs that can be run will be displayed. Select the embedded dialog you want to check.

You can use the following commands for the check:

Commands for checking (Embedded Dialogs)
Command Description

Close Debugger

Closes the dialog box.

Start debugging the embedded dialog

Opens the debugger of the program in which you created the selected routine.

Start debugging in the existing execution context

This command can be used for two purposes:

You can resume the debugging after cancellation.

After the debugging you can run another test in the same context (i. e. the dialog box is still open) without having to test the complete application again. This is useful if you want to test a data preparation routine. This way you can test the routine without having to run an import again.

Only available for audit tests.


Enable/Disable IP Protection

This function defines if information and error messages should be displayed encrypted. If you use Enable IP Protection, the message will be displayed encrypted. Moreover, temporary files will be deleted after the debugging. Select Disable IP Protection to show all messages concerning the encrypted running of routines. If you use this setting, temporary files will not be deleted after the completion of the debugging.

Not available for workflows.


Abort debugging immediately

Cancels the debugging and closes the corresponding dialog box. This icon is only available as long as the debugger is open.

Run on:

You can only debug on desktop.

Only available for Standard Import Routines.


Toggle the task cancellation request

Abort debugging immediately cancels the debugging immediately. Using this command might lead to a corrupt file. In contrast to this command the Toggle the task cancellation request command does not cancel the debugging immediately. Use this command to set Is cancellation requested to "True" or "False". If it is set to "True", the macro will check if the debugging can be completed. With this command you can test if the cancel process works correctly when the user runs a corresponding command, i. e. when he cansels the tagging. This icon is only available as long as the debugger is open.

Start Debugger Settings dialog

Opens the Debugger Settings dialog box where you can define which messages should be displayed during the debugging.

Help

Opens the help for the debugging of an embedded dialog.

Step-by-Step

  1. Select the embedded dialog you want to check.
  2. Click Start debugging in the new execution context to start the debugging. The debugger of the program in which the selected routine was created will be opened.
  3. Start the debugging in the corresponding environment.
  4. If you have set breakpoints, the status will be shown at each breakpoint. Click Continue with debugging the task [Name of the task] to resume the debugging after a pause.
  5. In the right area information concerning the context of the audit test (SmartContext object) is displayed. Use the icons to sort this information by category or in alphabetical order. For some entries additional information is available. Click the corresponding name. If further information is available, an icon will be displayed. Click the icon to show the information.

If you only want to see the dialog without debugging, press the Ctrl Button and click Start debugging the embedded dialog.

The InputOutput Parameters area is only relevant if you use SmartDataExchanger(sDE). In this case you can proof the exchange logic.

  1. In the DataExchangerName field enter the name given in the code.
  2. Click the InputParameters or OutputParameters field. A Browse button appears. After clicking this button the InputParameter Collection Editor or OutputParameter Collection Editor dialog box is shown.
  3. Click the Add button to enter the properties of an input parameter/output parameter (i.e. an if condition) of the routine you want to debug.
  4. On the right side click the Name field and enter the name.
  5. Click the Type field and select the corresponding type.
  6. Enter a value. The name entered in the Name field is shown in the Member area.
  7. Repeat the steps 3 - 6 if you want to add further members.
  8. Click the OK button.
  9. Start the debugging.