| TEXT |
Field will be executed as you move down. "Neither the twain shall
meet." The HEADER, by the way, will run no matter which way you are
going. Think of that.
The EXIT ACTION is often used to clean up after an option has been
run, sometimes with a call to the Kernel utility KILL^XUSCLEAN. If there
are variables that the application wishes to protect from this call,
[protected variables], there is a field in the Option File where these
variables may be entered, and they will not be killed.
Each option in the Option File has an EXIT ACTION Field
associated with it: ^DIC(19,{Option IEN},15). This field may contain M
programming code which will be executed each time that this option is
popped from the user stack. EXIT ACTIONS are the opposite or ENTRY
ACTIONS, not surprisingly.
If you think of a menu as a tree with a Primary Menu trunk, the ENTRY
ACTION will be executed as you move up the branches, and the EXIT ACTION
|
