Introduction
The management of execution errors aims
at:
-
Enabling expert and end users to better
understand the errors that may occur when operating
an operation. There are five different errors:
|
- Errors made by the end user when
using the operation: The end user runs
a main operation requiring an object
not yet created.
|
- Warnings: Errors made by the end
user when using the operation: The user
cancels the execution of the operation.
|
-
Enabling expert and end users
to fix the problem.
- Expert user: Whatever the operation
(main or building blocks of a operation),
he can determine which operation is
concerned and can edit or deactivate
it.
|
- End user: He can only delete or
deactivate the main operations (or the
visible operations.)
|
-
Enabling expert and end users to identify
the operations in error in the tree.
-
Keeping track of the information for
the expert user to fix the problems.
Detecting Errors
The operations that are in error display
with a
in the tree. When an error occurs when executing
the application, the following error appears: The Query
dialog box was canceled during execution.
-
The Operation column lists the operations
that are in error.
-
The Diagnosis column describes the reason
why the operation cannot be executed (An object variable
cannot be valuated).
-
The Documentation field helps the user
fix the problem. He can edit the operation and modify
its inputs before launching its execution, or he can
deactivate the operation.
The information about each error is saved
at the level of each feature and can therefore be displayed
by editing the operation.