Server Alert Action IDs
The typical application handles alerts and errors in the following way:
1. Server sends out an alert.
2. Client application receives the notification of the alert in a callback method.
3. Client application displays the alert in a dialog. The dialog shows buttons with corresponding strings
received from the alert description.
4. An operator resolves the alert condition (places more blank discs in the input bin for example).
5. The operator selects one of the buttons which triggers a reply to the server.
6. The server receives the reply, checks that the condition has been fixed and sends out an alert
acknowledgement.
7. Client application receives the alert acknowledgement in a callback method.
One of the ways to reply to a server alert is with an Action ID. A unique Action ID is assigned to every possible reply for a server alert or error. The list of Action IDs and their meanings are listed in the table below.
Action ID / Action meaning
1 “OK”
2 “Retry”
3 “Yes”
4 “No”
5 “Cancel”
6 “Reject Disc”
7 “Retry or Pass”
8 “Pass Disc”
9 “Stop Line”
10 “End Job”
11 “Abort Job”
12 “Disable Autoloader”
13 “Disable Printer”
14 “Disable Recorder”
2010-02-03