Operator prompts are created within the phase logic at the phase class level. When you are ready to insert an operator prompt into the phase logic, you need to decide what type of message (Integer, Floating Point, Boolean, or String) the prompt needs to be. The type of message you send will determine not only the format of the response you expect to receive but also the code you will use to send the message.
Following are the codes used in phase logic requests to send operator messages, including prompts, which require a response.
| Type of Message | Request Code (nn is message ID) |
|---|---|
| Send message (no response required) | 30nn |
| Clear message | 3100 (REQDATA1=ID of message) |
| Send operator prompt, Integer | 32nn |
| Send operator prompt, Floating Point | 33nn |
| Send operator prompt, Boolean | 34nn |
| Send operator prompt, String | 35nn |
The
Unacknowledged Prompts button
(in the button bar at the top of
every operator screen in the Batch Operator Interface) flashes to alert the
operator when a phase is sending a message to the operator. The operator clicks
this button to display the Unacknowledged Prompts screen. Double-clicking the
message line opens a dialog in which the operator can enter a response.
Remember that there are several other places in the Batch Operator Interface where the operator can view active messages or prompts, and that operator graphics can also be configured to display such messages and prompts. Any of these locations will allow the operator to respond to prompts as well.
We will add steps and transitions to ask the operator the question about where to send the batch. The first step will be inserted into the existing running logic after the first transition, before the CLOSE_STATE step.