Page Comparison

From the Automation Center navigation pane, select Tasks > Timer Tasks. The Timer Tasks list displays.

Click New to display an empty Timer Task Details and enter / select the following values:

<ul>
<li> <b>Task Name</b> = Two Minute Timer
<li> <b>Timer Type</b> = Secocnds
<li> <b>Time Duration in Seconds</b> = 120
</ul>

Click the Save button.

From the Automation Center navigation pane, select Tasks > SQL Tasks. The SQL Tasks list displays.

Click New to display an empty SQL Task Details and enter / select the following values:

<ul>
<li> <b>Task Name</b> = SQL Create Table
<li> <b>Database Connection</b> = (the database connection you created as a [prerequisite|#Prerequisite])
<li> <b>SQL Command</b> = CREATE TABLE opswise_tut${_date("yyyyMMdd",5)} (name varchar(128), value varchar(128)); 
</ul>

Click the Save button.

Create a SQL task called SQL Insert Value with this value:

• SQL Command = INSERT INTO opswise_tut${_date("yyyyMMdd",5)} (name, value) values ('A', 'F'), ('B', 'S'), ('C', 'F');

Create a SQL task called SQL Select Count with this value:

• SQL Command = SELECT count (*) as count FROM opswise_tut${_date("yyyyMMdd",5)} WHERE value = 'F';

Create a SQL task called SQL Delete with this value:

• SQL Command = DELETE FROM opswise_tut${_date("yyyyMMdd",5)};

From the Automation Center navigation pane, select Tasks > Manual Tasks and click New.

In the Manual Task Details, enter / select the following values:

<ul>
<li> <b>Task Name</b> = Pause for Manual
<li> <b>Task Description</b> = A Manual task run at 

${_date()}

 (a variable that indicates the date and time the Manual task launches)
<li> <b>Late Finish</b> = enabled
<li> <b>Late Finish Type</b> = Duration
<li> <b>Late Finish Duration</b> = Hours 00 02 00 (2 minutes)
</ul>

Click the Save button.

Add a Note:

<ol>
<li> Click the <b>Notes</b> tab and then click <b>New</b> to display Note Details.
<li> Enter the following values:
<ul>
<li> <b>Title</b> = Probable database problem
<li> <b>Text</b> = Make sure database is running.
</ul>
<li> Click <b>Save</b>.
</ol>

Add an Email Notification:

<ol>
<li> Click the <b>Actions</b> tab.
<li> Click <b>Email Notification</b> in the list of Action types.
<li> Click the <b>New</b> button to display Email Notification Details for a new Email Notification. 
<li> Enter / select the following values:
<ul>
<li> <b>Status</b> =  ACTION REQUIRED
<li> <b>Email Connection</b> = (the Email Connection you created earlier)
<li> <b>To</b> = (your Email address)
<li> <b>Subject</b> = Issue with Workflow
<li> <b>Body</b> = ${_date}  workflow failure; notification triggered by $\{ops_task_name} |
</ul>
</ol>

Click the Save button.

Return to the Bigger Workflow task and launch it again.

From the Activity Monitor, click the Workflow name to view it from the canvas. This time, the workflow goes down the conditional path. Note that when you set up a conditional path, what would normally be a Failure status for the SQL Create Table task becomes a status of Finished. If you ran this task as a standalone task or without the conditional path, its status would say Failed.
 

 

When the Pause for Manual task launches, it generates the Email Notification we added earlier.
 

The user receives the email, which provides the name of the task that generated it (Pause for Manual in our case). The user might also be running a special Activity Monitor that displays only Manual tasks in the Action Required status. According to our scenario, the user opens the Pause for Manual task and checks the Notes to find out what action he or she is supposed to take. In our case, the Notes say to check the database and bring it back up.

At this point, the workflow processing could continue in either of two ways:

1. Re-run the task that failed and send the workflow down the success path.
2. Set the Pause for Manual task to Completed status and continue the workflow from there.
   We will try both methods.
3. Re-run the failed task; right-click the task and select Commands > Re-run. In a real processing situation, this is the method you would use because you need to create the table before you can continue.
   1. Right-click the task that failed and select Commands > Re-run.
       
      
       
      Note that we are still on the same day so the task fails again because the table already exists. In a real processing situation, the task would go to Success and the subsequent tasks would run as expected.
4. Set the Manual task to Complete status. For the purposes of our exercise, we will get the workflow going again by setting the Manual task to complete.
   1. Right-click the Manual task.
   2. Select Commands > Set Completed.
       
      
       
      The Manual task goes to Success and the rest of the workflow runs.
       
      
       

      Html bobswift

   3. Because we set a two-minute Late Finish flag on our Manual task and we (presumably) took more than two minutes to complete it, the Manual task has been flagged as a late finish. To view the flag, go to the Activity Monitor and click the Manual task name. In the task instance Details, an enabled Finished Late field now displays, and the Duration field indicates the duration of the task.