Default Actions are defined in every Process Type of every Workorder Type. However, some Actions are not applicable or differently implemented for the Workorder Type Start, for obvious reasons.
There are 3 types of default Actions: Internal Actions, General Actions and typical Mailer Actions.
| Internal Actions |
These Actions are never activated by Interface events. They are only activated as a result of the processing of other Actions. Additionally, some are activated through the ModelSetup610 Interface.
-
activate - (Start-up action for the Model to get “running”) all relevant Aspects are activated as GMEs.
- scheduleStart - (Start-up action for the Model to get “running”) a new Start Work Order is created and scheduled first in the Work Order Queue.
- workorder - (Start-up action for the Model to get “running”) the first Work Order is taken from the Work Order Queue as next Work Order.
- open - a Process is started (i.e. it's corresponding Interface is opened).
- xMessage - a Test message is shown in a pop-up window.
- xHold - the running Work Order is closed and placed as next first Work Order in the Queue, a Start Work Order is opened.
- xSwap - the running Work Order is closed and placed as next first Work Order in the Queue while the original first Work Order is opened.
- xKill - the running Work Order is closed and placed in the Archive, the Interface is closed and the Engine is stopped.
| General Actions |
These Actions apply to any “normal” Work Order Task. They have to do with general procedure short-cuts.
- pin - Fix the Interface Window on it's current position on the Screen instead of the default position for the Window.
- hold - Close the running Work Order and place it as next first Work Order in the Queue, open a Start Work Order.
- nextFirst - Close the running Work Order and place it as next first Work Order in the Queue, open the Work Order that was first in the Queue.
- stop - Close the Work Order File and place it in the Archive, open a Start Work Order.
- file - Close the Work Order File and place it in the Archive.
- inspect - Open an Inspect Window to check the Model's contents (only for Test purposes).
| Mailer Actions |
These Actions make it possible for a running Task to get mail and react on these events.
- mail - activate the “Mail” signal of the Interface (not activated by Interface events).
- noMail - activate the "No Mail" signal of the Interface (not activated by Interface events).
- getLetters - Get all "Mail" message information from the Resource's Mail Queue and make it available to the Interface.
- showLetter - Make a "Mail" message's properties (for a message that is activated in an Object Window) available to the Process' Interface.
- openLetter - Close the running Work Order and place it as next first Work Order in the Queue, open the Mailer Work Order.
| to top of document ˆ | to next page > |
