SystemService (under PlatformServices)
PlatformServices also contains a child “SystemService” container, accessible from its property sheet as shown below. Unlike other child services, SystemService does not appear in the Nav tree.
Figure 113. SystemService from property sheet of PlatformServices.
When you expand SystemService, you see most of the same properties available in the default Platform Service Container Plugin view (see “PlatformServiceContainer parameters”). In addition, as shown below, there is a container slot “Station Save Alarm Support”.
Figure 114. Station Save Alarm Support expanded in property sheet of SystemService.
Properties under “Station Save Alarm Support” allow you to configure the alarm class and other parameters to use for “station save” alarms. Such an alarm may occur, for example, if there is insufficient disk space to complete the save.
Properties work the same as those in an alarm extension for a control point.
NOTE: Other platform warnings from defined limits, such as for low memory, low disk space, and so on are not really alarms—they simply generate a yellow overlay in the lower right corner when viewing the station in Workbench. If you need actual alarms, you can link from an appropriate boolean slot of the SystemService component (for example, “LowHeap”) into other persisted station logic in another area of the station.If linking to PlatformServices, be aware that you should change the link type from “handle” to “slot path”. For related details, see “PlatformServices binding and link caveats”.