The system automatically records provisioning jobs within the history space of the
Supervisor.
Figure 6. Provisioning related histories in Supervisor’s history space
The system automatically creates these histories using the following names:
- DeviceNetworkHistoryRecord contains one record for each provisioning job attempted. The record includes various fields that record the job's finished
state, submitting user, stations to process, and whether the job has been disposed of.
- DeviceStepHistoryRecord contains one record for each run for each station step, per station, for any provisioning job. The record includes the step's
type, finished state, description, station, and whether the step was disposed of (that is, it was included in a job that was
disposed of).
- NetworkStepHistoryRecord contains one record for each initial step to run only once (that is the Update Licenses step). The record includes the step's
type, finished state, description, network type, and stations to process.
CAUTION: Do not rename, delete, or clear these histories on the
Supervisor, for example by using the Database Maintenance view on the
Supervisor’s history space. These histories are used by the station’s BatchJob API code, and by various job list views.
Deleting these histories can result in provisioning-related files becoming orphaned, such that it becomes impossible to know
if they can safely be deleted. Therefore, examination of these histories is optional, and in most cases you can simply ignore
them.