The Tasks tab of the Project Explorer organizes the worksheets that are processed as background tasks (i.e., server-based maintenance tasks that are not directly related to screen operations or device I/O) during project runtime.
- You can use Alarm worksheets to define when alarms are trigged, how they must be handled, and what messages they generate.
(You can then use the Alarm/Event Control screen object to display your alarms on screen, but that is a separate procedure.)
- You can use Trend worksheets to select project tags that should be displayed as data trends and/or saved as historical data.
(You can then use the Trend Control screen object to actually display your trends on screen, but that is a separate procedure.)
- You can use Recipe worksheets to select project tags that will load values from and/or save values to an external file. These worksheets are typically used to execute process recipes, but you can store any type of information such as passwords, operation logs, and so on.
(You can then call the Recipe function to actually run a configured Recipe worksheet, but that is a separate procedure.)
- You can use Report worksheets to design runtime reports that are either sent to a printer or saved to disk.
(You can then call the Report function to actually run a configured Report worksheet, but that is a separate procedure.)
- You can use ODBC worksheets to set up connections and exchange data with other ODBC-compliant databases.
- You can use Math worksheets to develop complex runtime logic using the built-in scripting language.
- You can use Script worksheets to develop complex runtime logic using VBScript.
- You can use Scheduler worksheets to run commands at specified times, dates, or trigger events.
- You can use Database worksheets to set up connections and exchange data with external databases using the standard ADO.NET interface (as an alternative to ODBC).