RX_CALLBACKS_HISTORY

Field Name

Description

ACCOUNT

The customer's account number.

INCIDENT_ID

The ID associated with the incident resulting from the call. This field corresponds with the ID field in the RX_INCIDENTS table.

REGION

The region in which the incident is located. This field uses the REGION domain.

PRIORITY

The priority of the call (how high it will appear on the callback list), sorted descending (i.e., the larger priority number will be called first).

REASON

The reason for the callback (e.g., estimated time of restoration is about to expire).

RETRY_COUNT

The running number of retries.

MIN_RETRY_COUNT

The minimum number of times to attempt calling back (before auto-delete, if enabled, will delete a callback record).

AUTO_DELETE

Indicates whether a callback should be deleted automatically. This field uses the YES_NO domain. This field should not be edited.

BUSY_WAIT

Time (in minutes) to wait until the next callback if there is a busy signal.

NO_ANSWER_WAIT

Time (in minutes) to wait for the next callback if there is no answer.

PREV_RESULT

The result of the previous callback. This field uses the CALL_RESULT domain.

PREV_CALLER

The operator who attempted the previous callback.

PREV_CALL_TIME

The time that the previous call was attempted.

NEXT_CALL_TIME

The earliest time the next callback attempt should take place.

CALLING

Flag to note if the callback is currently be processed. This field uses the YES_NO domain.

CALLING_EXPIRES

The amount of time before the currently loaded callback is returned to the queue if no action is taken. This value corresponds with the MinutesCallingValid value in DataServices.exe.config.

CALLER_TYPE

Who made the last callback. This field uses the CALLER_TYPE domain.

COMMENTS

Notes from the operator or dispatcher.

CHANGE_DATE

The time and date an operation was performed on the callback record.

OPERATION

The operation (e.g., insert, delete, update) performed on the incident record.

QR code for this page

Was this helpful?