When an Execution Condition is evaluated as:
|
True |
The procedure behaves normally |
|
False and no message is defined |
The system behaves as if the procedure does not exist. Example If the procedure is assigned to a key, nothing will happen when the user presses the key. |
|
False and a message is defined |
A user may think the procedure exists. However, when the user selects the procedure, the message displays and the procedure will not run. |
If the expression contains unavailable points, a user may think a procedure exists. However, when the user selects the procedure, the following message displays.
The execution condition for this procedure contains unavailable points. Would you like to execute the procedure anyway?
If the user clicks:
|
Yes |
The procedure can be performed |
|
No |
The procedure is not performed |
Examples of how an Execution Condition is Used
If a custom application provides security information as a CIMPLICITY point, this feature can be used to provide security control for procedure execution.
If an application runs in modes, such as Manual and Automatic, this feature can be used to disable certain procedures while in Automatic mode.
|
|
4. Configure a procedure;s advanced properties. |
