Managing Errors

Managing Execution Errors

The management of execution errors aims at:

Enabling expert and end users to better understand the errors that may occur when operating a behavior. There are 5 different errors:

Input Errors made by the expert user when creating a behavior: One of the inputs of a behavior was incorrectly defined.

Errors made by the end user when using the behavior: The end-user runs a main behavior requiring an object not yet created.

Warnings: Errors made by the end user when using the behavior: The user cancels the execution of the behavior. For instance by clicking Cancel of an Open file box for the Load behavior.

Execution errors: The LoadDocument behavior enables the user to load a document. If this document does not exist, a message is raised indicating that the document is missing.

Enabling expert and end users to fix the problem.

Expert user: Whatever the behavior (main or building blocks of a behavior), he can determine which behavior is concerned and can edit or deactivate it.

End user: He can only delete or deactivate the main behaviors (or the visible behaviors.)

Enabling expert and end users to identify the behaviors in error in the specification tree.

Keeping track of the information for the expert user to fix the problems.

Detecting Errors

The behaviors that are in error display with a

in the specification tree. When an error occurs when executing the application, the following window is displayed:

The Behavior column lists the behaviors that are in error.

The Diagnosis column describes the reason why the behavior cannot be executed (An object variable cannot be valuated).

The Documentation field helps the user fix the problem. He can edit the behavior and modify its inputs before launching its execution, or he can deactivate the behavior.

The information about each error is saved at the level of each feature and can therefore be displayed by editing the behavior. An information field is added to these behaviors (see graphic below) listing the information.

The information provided depends on the User type (expert user, administrator, or end user). In User mode, if an error occurs on a main behavior or on an invisible behavior, the error is displayed and stored on this main behavior.