Cloud History Export Manager (nCloudDriver-CloudHistoryExportManager)

The default view for the Cloud History Folder component, the default view to discover histories inside the station’s history database, and add them to the database of history exports to the cloud.

NOTE: In some versions of the driver, you may see the Archive button enabled. This button engages the action to individually archive a single history export. However, that action has been disabled, so clicking this button will do nothing. The button will be removed or fully disabled in a future release.

Like other manager views, the Cloud History Export Manager is table-based. Each row represents a proxy history (or a history folder) under Histories.

When you use the History Learn command, it automatically adds CloudHistoryExports for all the histories in the station's history database. On the subsequent history export attempts it will try to export all records from all of the histories. If you have a station with a very large history database, this could negatively affect communications performance with the cloud. To avoid this situation, an added Learn Histories configuration dialog appears which provides the ability to filter the Cloud History Exports that are automatically created from the station's history database.

NOTE: Large history databases could be either a large number of histories (e.g. tens of thousands of histories), or a smaller number of histories with a large number of records. For large history databases, you may want to consider clearing the histories, or clearing older records before adding CloudHistoryExports.

Figure 59. Cloud History Export Manager view with the Learn Histories configuration dialog

When you click OK in the configuration dialog a confirmation dialog appears which allows you to cancel the operation if desired.

Cloud History Export Learn Config properties

The History Learn command provides the ability to filter the Cloud History Exports that are automatically created from the station's history database. This can be helpful if you need to use the History Learn command on a very large station, but want to avoid adding certain histories, or are trying to keep the size down by adding in steps.

Name	Value	Description
Device Exclusion Patterns	string	This is a semicolon-separated list of matcher patterns, which accepts wildcard characters: “`?`” for one history, and “`*`” for any number of histories. A HistoryDevice that matches with a pattern in the Device Exclusion Pattern field will not be mapped by a CloudHistoryFolder, and none of the histories below it will be exported.
History Exclusion Patterns	string	A semicolon-separated list of matcher patterns, which accepts wildcard characters: “`?`” for one history, and “`*`” for any number of histories. A History with a historyName portion matching one of the patterns in the History Exclusion Patterns field will not be mapped by a Cloud History Export.
Begin Export Time	date/time/time zone	This is an editable timestamp field. The default value is the present time when the “History Learn” button was clicked. This property provides a starting point for the earliest history records to be sent to the cloud. Only history records created after the specified time will be sent to the cloud. You can set your Cloud History Export components to only export history records from the present moment ( recommended practice). Or you can set it to export records from a point in time in the past, such as the start of the week or month. Also, you can set it to begin exporting records at a future time only, such as starting at the end of the current month. If the field is left at default, it will begin exports with the current time, it will not send any older data.

Columns

To open this view, expand Config > Drivers > NiagaraCloudNetwork > CloudSentienceDevice and double-click the Histories node.

Columns

Column	Description
Name	Reports the name of the entity or logical grouping.
History Id	Reports the History Id.
Enabled	Indicates if the network, device, point or component is active or inactive.
Status	Reports the current condition of the entity as of the last refresh: {alarm}, {disabled}, {down}, {fault}, {ok}, {stale}, {unackedAlarm}
State	Reports the current state.
Last Sent to Cloud	Reports the timestamp of the last time a value was sent to cloud.

Buttons

New Folder creates a new folder for devices. Each such folder provides its own set of manager views.
New creates a new device record in the database.
Edit opens the device’s database record for updating.
Discover runs a discover job to locate installed devices, which appear in the Discovered pane. This view has a standard appearance that is similar to all Device Manager views.
Add inserts into the database a record for the discovered and selected object.
Match associates a discovered device with a record that is already in the database.
Archive: Archives the history.
The automatic History Learn command creates a CloudHistoryFolder for each HistoryDevice it finds in the station’s history database, including the local station. This helps organize the potentially large number of history exports into a logical structure. It also provides some performance improvement for extremely large stations by decreasing the number of children in a single container. The History Learn command is strongly recommended over standard history discovery and adding, as it will help avoid creating duplicate history exports for a single history.
NOTE: If you create two cloud history exports for a single history, you will cause overlapping records in the Honeywell Forge cloud database, which results in missing or incomplete data for cloud-based applications. For this reason, it is a recommended best practice to use the History Learn workflow to reduce the likelihood of duplicate exports.

CAUTION: When exporting large histories to the cloud it is possible to generate enough data that Honeywell Forge cloud will block the device. To prevent this, the History Learn job can be configured with a Begin Export Time such that only history records created after that time will be sent to Honeywell Forge.