From OpsWise Documentation Wiki
Contents |
Overview
The Email task allows you to create and send emails. In order to execute Email tasks, you first need to define an Email Connection, which defines the server information and other pertinent information.
Creating a New Email Task
- From the Navigation Pane, select Email Tasks.
- From the trigger wizard, select New. OpsWise Automation Center displays the Email task screen.
- Using the field descriptions provided below as a guide, complete the fields as needed.
- Click the Submit button to save the record and return to the menu, or, right-click on the title bar and select Save to save the record and remain on the current display.
- If appropriate, repeat these steps for any additional tasks you want to add.
Shown below is a sample Email task screen. The task run statistics shown at the bottom appear after the first time this task has been launched.
Email Task Field Descriptions
The table below describes the fields, buttons, and tabs on the Email task definition and task instance screens. Most fields appear on both screens; however they do not always appear at the same spot. In the latter case, the table provides a field description at the location found on the task definition screen. Some fields appear only on one of the screens. Field labels shown in bold appear only on the task instance screen and are labelled as such.
| Name | Description | |
|---|---|---|
| Task Name | Required. Name used within OpsWise Automation Center to identify this task. Up to 40 alphanumerics; variables supported. Note • It is the user’s responsibility to develop a workable naming scheme for tasks. | |
| Email Template | Optional. The name of the Email template defined using the Email template screen. The Email template allows you to specify standard recipients and text for outgoing emails. Type in a name, or click the magnifying glass to browse to an existing Email template or create a new one. You must specify either an Email template or Email connection, or both. If you specify both, the Email server specified in the Email Connection record overrides the server in the template. | |
| Invoked by | Task instance only; system-supplied. How the task instance was launched. Options:
Trigger: [Trigger Name] - The instance was launched by the named trigger. Workflow: [Workflow Name] - The instance was launched by the named workflow. Manually Launched - The instance was launched by a user. To identify the user who launched the instance: |
|
| Task | Task instance only; system-supplied. | |
| Instance Reference Id | Task instance only; system-supplied. | |
| Summary | User-supplied description of this task. | |
| Status | Task instance only; system-supplied. See Task Status. | |
| Status Description | Task instance only; system-supplied. Provides additional information, if any, about the status of the task. | |
| Start Time | Task instance only; system-supplied. The time the task started. | |
| Duration | Task instance only; system-supplied. The amount of time the task took to run. | |
| End Time | Task instance only; system-supplied. The time the task completed. | |
| Hold on Start | If enabled, when the task is launched it appears in the Activity display with a status of Held. The task runs when the user releases it. . | |
| Member of Groups | User-defined. Allows you to select one or more Opswise groups that this task definition belongs to. Click on the lock icon to unlock the field and select groups. | |
| Email Connection | Required. The name of the Email connection defined using the Email connection screen. The email connection specifies information about the email server. You can also specify the Email connection in the Email template (see above). You must specify either an Email template or Email connection, or both. If you specify an Email template and an Email connection, the server selected in the Email connection overrides the server selected in the Email template. Type in a name, or click the magnifying glass to browse to an existing Email server definition or create a new one. | |
| Reply-To | Required. Specifies the email address of the sender. Use commas to separate multiple recipients. Variables supported. | |
| To | Required. Specifies the email address of the recipient. Use commas to separate multiple recipients. Variables supported. | |
| CC | Optional. Specifies the email address of the party being sent a copy of the email, if any. Use commas to separate multiple recipients. Variables supported. | |
| BCC | Optional. Specifies the email address of the party being sent a blind (hidden) copy of the email, if any. Use commas to separate multiple recipients. Variables supported. | |
| Subject | Optional. Specifies the subject line of the email. Variables supported. | |
| Body | Optional. Contains the text of the email message. Variables supported. | |
| Late Start | If enabled, and if the task instance starts after the time or period specified, the task instance is flagged as late. You can specify a time or duration to determine a late start (see Late Start Type below). To determine whether a task instance started late, open the task instance and locate the Started Late field; the field is checked if the instance started after the specified time or lasted longer than expected. | |
| Late Start Type | If Late Start is enabled, use this field to specify whether you want to use time (see Late Start Time below) or duration (see Late Start Duration below) to determine whether the task instance started late. | |
| Late Start Time (hh:mm) | If Late Start Type is Time, the time after which the task start time is considered late. Use hh:mm, 24-hour time. | |
| Late Start Duration | If Late Start Type is Duration, use this to specify .... You can specify any combination of days, hours, minutes, and seconds. | |
| Late Finish | If enabled, and if the task instance finishes after the time or period specified, the task instance is flagged as late. You can specify a time or duration to determine a late finish (see Late Finish Type below). To determine whether a task instance finished late, open the task instance and locate the Finished Late field; the field is checked if the instance finished after the specified time or lasted longer than expected. | |
| Late Finish Type | If Late Finish is enabled, use this field to specify whether you want to use time (see Late Finish Time below) or duration (see Late Finish Duration below) to determine whether the task instance finished late. | |
| Late Finish Time (hh:mm) | If Late Finish Type is Time, use this to specify the time after which the task finish time is considered late. Use hh:mm, 24-hour time. | |
| Late Finish Duration | If Late Finish Type is Duration, use this to specify the longest amount of time this task instance should take to run. You can specify any combination of days, hours, minutes, and seconds. | |
| Early Finish | If enabled, and if the task instance finishes before the time or period specified, the task instance is flagged as early. You can specify a time or duration to determine an early finish (see Early Finish Type below). To determine whether a task instance finished early, open the task instance and locate the Finished Early field; the field is checked if the instance finished before the specified time or did not last as long as expected. | |
| Early Finish Type | If Early Finish is enabled, use this field to specify whether you want to use time (see Early Finish Time below) or duration (see Early Finish Duration below) to determine whether the task instance finished early. | |
| Early Finish Time (hh:mm) | If Early Finish Type is Time, use this to specify the time before which the task finish time is considered early. Use hh:mm, 24-hour time. | |
| Early Finish Duration | If Early Finish Type is Duration, use this to specify the shortest amount of time this task instance should take to run. You can specify any combination of days, hours, minutes, and seconds. | |
| First Time Ran | System-supplied. Displays after task has been run. The date and time this task first ran. | |
| Lowest Instance Time | System-supplied. Displays after task has been run. The shortest amount of time this task has taken to run. | |
| Last Time Ran | System-supplied. Displays after task has been run. The last date and time the task ran. | |
| Average Instance Time | System-supplied. Displays after task has been run. The average amount of time this task takes to run. | |
| Number of Instances | System-supplied. Displays after task has been run. The number of times this task has run. | |
| Highest Instance Time | System-supplied. Displays after task has been run. The longest amount of time this task has taken to run. | |
| Last Instance Duration | System-supplied. Displays after task has been run. The amount of time the task took to run the last time it ran. | |
| Submit button | Submits the new record to the database. | |
| Update button | Saves updates to the record. | |
| Launch Task button | Manually launches the task. | |
| Delete button | Deletes the current record. | |
| Task Virtual Resources tab | Allows you to create virtual resource definitions for controlling access to resources by multiple tasks. See Creating Virtual Resources. | |
| Variables tab | Displays all variables associated with this task. | |
| Actions tab | Allows you to specify actions that the system will take automatically based on events that occur during the execution of this task. Events supported are task instance status, exit codes, late start, late finish, and early finish. Actions include:
|
|
| Task Instances tab | System-supplied. Displays a list of all instances generated by this task. | |
| Triggers tab | Displays a list of all triggers that have been defined to launch this task. Also allows you to add new triggers. For instructions, see Triggers. | |
| Notes tab | Displays all notes associated with this task. See Runbook Notes. | |
Specifying When a Task Runs
You can run the task as part of a workflow, specify triggers that run the task automatically based on times or events, or run the task manually.
Monitoring Task Execution
You can monitor all system activity from the Activity screen and can view activity history from the Activity History screen.

