Troubleshooting
This topic describes possible sources of errors and how you can track down the cause of a problem.
To simplify troubleshooting, you can enable logs for workflows in the configuration settings, see Workflow in the Configuration topic of the Core Administrator Guide.
There are two types of errors:
- Records are displayed incorrectly.
- Commands are executed incorrectly.
Common Errors and Causes
Scenario | Error | Cause / Solution |
---|---|---|
Level | Level not opened from a command | Define the input criteria. |
Enter the level number in the command. | ||
Records | Too many records | The index or key length is missing. |
None / too few records | The level is not opened as a child. | |
The key used to select records is too long causing records to be excluded. | ||
Check that you are using the correct index to select records. | ||
The record parameter is of the wrong type. | ||
The wrong records are displayed | The order in which the actions are carried out is wrong; the process is called first and then the parameter entered. | |
Too many records displayed when accessing the level a second time | The parameter stack was not cleared. | |
Parameters | Parameters are empty | Info Area and Field entered incorrectly or left blank. |
Wrong parameter entered. | ||
Mathematical and string operations do not work | The parameter is of the wrong type. | |
Buttons | Default buttons are unavailable | Many default buttons are level-dependent and cannot be used in the workflow. In many cases you can define the same functionality yourself. |
Actions are not carried out when the button is clicked | Wrong button ID. Check that the ID of the button is the same as the value entered in the command. | |
Trigger | Triggers are not executed | The trigger format is spelled incorrectly. Open the trigger in the Trigger info area, and copy the trigger's name using Ctrl+C. Enter the name in the workflow using Ctrl+V. |
The source info area has not been specified. | ||
Actions | The result is incorrect for commands that trigger several actions | Spread the actions over several commands, and execute these one after another. Test where the error lies and fix the problem. |
Making Values Visible
When troubleshooting, make sure you keep track of which values are stored in the records and parameters after each step.
To display the values:
Records | Select View > All Mask Fields from the menu. |
Record Parameters | Define a process with this parameter as an input parameter. |
Field parameters | Display the parameter using the Set Text action. |