Niagara provisioning jobs are automatically recorded within the history space of the Supervisor, as shown in histories highlighted in Figure 54.
These histories are automatically created using the following names:
DeviceNetworkHistoryRecord
Contains one record for each Niagara provisioning job attempted. Includes various fields showing the job's finished state, submitting user, stations to process, and whether it has been disposed.
DeviceStepHistoryRecord
Contains one record for each “run for each station” step, per station, for any Niagara provisioning job. Includes various available fields, showing the step's type, finished state, description, station, and whether disposed (included in a job that was disposed).
NetworkStepHistoryRecord
Contains one record for each initial “steps to run only once” step (that is “Update Licenses” for any Niagara provisioning job). Includes various available fields, showing the step's type, finished state, description, network type, and stations to process.
Do not rename, delete, or clear these histories on the Supervisor, for example 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.
Copyright © 2000-2014 Tridium Inc. All rights reserved.