The Task Action is used in a Skelta Workflow.NET workflow process design in order to assign a task to a resource or set of resources. This action is used to define the task type and the associated status.
The Properties defined against Task and the role played by the properties are explained in the table below.
|
Property |
Description |
|
This property specifies the resource(s) who have to take up the Task action, this property is tagged with the Ignore Unavailable Resources which in turn is tagged with Alternate Resource Allowed. This will be explained in detail later. |
|
|
This is the subject of the Task. The subject can be customized for each resource. To assign a subject to the Task, click the 'Subject' button in the Properties pane for the Task action. In the window that pops up, customize the subject by appending the various fields to the subject. |
|
|
This is the actual content of the Task sent to the resource(s). The notes can be customized for each resource. To assign the content of the Task, click the 'Notes' button in the Properties pane for the Task action. In the window that pops up, customize the content by appending the various fields to the notes. |
|
|
You can define Task Type and Status under TaskTypes in a Task Assignment. The Status added under Task Types is used to maintain the status of the Task assigned.
|
|
|
Min. Acknowledgements |
This property (referred to as Min.Ack), which can be specified as a number or percentage, is the minimum number of resources who should acknowledge receipt of the Task assignment. This property is related to the 'Timeout warning for Acknowledgement' and 'Timeout for Acknowledgement' properties. To illustrate, when 'Timeout for Acknowledgement' is reached, the activity first checks if the acknowledgement count is less than Min.Ack (if it is set). If it is, the activity will be removed from all activity lists. If the 'Min.Ack' has already been satisfied, then the activity will be removed from the non-acknowledgers' lists. If the Min.Ack value is 0, then the activity checks if the acknowledgement count is less than Max.Ack (if it is set). If it is, the activity will be removed from all activity lists. Else the activity will be removed from the non-acknowledgers' list. If both Min.Ack and Max.Ack are set to 0, then there should be at least one acknowledgement within the set time, otherwise the activity will be removed from all activity lists. |
|
Max. Acknowledgements |
This property (referred to as Max.Ack), which can be specified as a number or percentage, is the maximum number of resources who should acknowledge receipt of the Task assignment. If 'Timeout for Acknowledgement' is specified and achieved, and the 'Min.Ack' is also satisfied, then the activity waits for action from those who acknowledged. If the Min.Ack value is set to 0, then it checks if the acknowledgement count is less than Max.Ack. If it is, the activity will be removed from all activity lists. Else the activity will be removed from the non-acknowledgers' list. If both Min.Ack and Max.Ack are set to 0, then there should be at least one acknowledgement within the set time, otherwise the activity will be removed from all activity lists. |
|
Timeout for Acknowledgement |
This property (referred to as Time For Ack.) specifies the time until which acknowledgement is allowed i.e. the time until which the Task action will wait for acknowledgement. If Min.Ack is set and is not reached, the activity is removed from all activity lists. If Min.Ack is 0, it will check if acknowledgement count is less than Max.Ack. If it is, the activity is removed from all activity lists. Else the activity will be removed from the non-acknowledgers' list. The activity will remain in the acknowledgers' activity list and wait for action from them. Click here to view the flowchart for Timeout for Acknowledgement. |
|
Timeout Warning for Acknowledgement |
This property (referred to as Time Out Warning For Ack.) specifies the time at which a warning is provided to a resource to acknowledge the activity assigned to him/her. If the resource does not acknowledge within this time the engine is notified with a warning. Thus if 'Min.Ack' is set, and it is not satisfied before the given time then a warning is sent. If Min.Ack is 0, it will check for Max.Ack. If the acknowledgement count does not reach the Max.Ack value within the set time, a warning is sent. If both Min.Ack and Max.Ack are not set, this property is ignored. Click here to view the flowchart for Timeout Warning for Acknowledgement. |
|
How Acknowledgement Properties relates to each other |
|
|
Affirmative Answer for TaskAssignment Completion [% or Number] |
This property is used to check what percentage or number of persons should take action for the Task. Decision for the Task is taken only after the specified number or percentage of resources have taken the action. The activity waits for the resources' action until the 'Timeout for Action' is reached. |
|
Action Min Limit TaskAssignment Completion [% or Number] |
This property specifies the minimum number of resources required to act on the Task before the 'Timeout Warning for Action'. If the action limit is reached before the 'Timeout Warning for Action' then the warning message is not shown. |
|
Minimum Time for Action. |
This property specifies the minimum time that is required to finish the action. If the resource does not have the minimum time left in the day to complete the action then the alternate resource is selected. |
|
Timeout warning for Action |
This property specifies when a reminder has to be provided for the resources to act on the TaskAssignment, if the action count has not been reached. If properties such as Max.Ack, Affirmative Action for TaskAssignment Completion (AAT), and Action Limit (AL) are set, once the property values are reached then a warning is sent to the participant. When the timeout is reached, the following checks are made: Click here to view the flowchart for Timeout Warning for Action. |
|
Timeout for Action |
This property's value is used to decide until what time the activity should wait for resource action. If properties such as Max.Ack, AAT, AL are set, once the property values are reached the activity is removed from the task lists of all the resources. When the timeout is reached, the following checks are made: Click here to view the flowchart for Timeout for Action. |
|
Hide Responses? |
If this property is set to 'No', then the resource’s details will be visible to the resources who have acknowledged. |
|
Consider only Business Hours for Timeout? |
If this property is set, all the time out calculations will be done based on only the business hours, i.e. leaves and Organization holidays will not be considered. Business hours for the Organization and Resource can be set using the calendar controls (Organization, Resource ) provided. |
|
Forwarding Allowed? |
If this property is set then the resource is provided with a Forward button. Using this the resource can forward the activity to another resource |
|
Ignore Unavailable Resources? |
If this property is set, when the Task is assigned to the resources list a check is first done to see whether the resource is available. If the resource is not available then a check is made for an alternate resource assigned to the unavailable resource. Simultaneously the value of the property 'Alternate Resource Allowed' is checked. If that is also set, then the Task is assigned to this resource. |
|
Alternate Resource Allowed? |
This property is set to assign a particular task to an alternate resource in the absence or unavailability of any resource. |
|
Severity |
This property is set to indicate the severity of the Task. It can be set to 'Low', 'Medium', or 'High'. |
|
Show Custom Document View Window |
If this property is set, then the Custom Document View Window will be shown. |
|
Send Notification Email |
If this property is set to 'Yes', then notification emails will be sent to the resources. |
|
This is used to set recurring timeout warnings that will be sent to the resources who have to take action. To set multiple timeout warnings, click the 'Multiple TimeOut Warning' button in the Properties pane for the Task action. A new window pops up. In this window, set the interval for the recurring warning as well as the output message. |
|
|
Property settings for Task. |
|
To add the Task action to the workflow click on the Task button in the toolbox. An icon for the Task action will be added in the design area. The action can be linked with the workflow by clicking on the Link button in the tool box. To set the properties for the Task action click on the Task icon in the design area. The properties corresponding to the Task action will be displayed in the Properties pane of the Process Designer. |
![]() |
|
To select the resources to whom this Task is to be sent, click on the button for the 'To' property. A window pops up (Fig 2.), in which the resources can be selected. An expression can be built to select the resources based on the resource properties. Select a property from the list, then select the operator, type of value (Value, Variable, Content), corresponding value for the property and the logical operator. Add the condition to the expression by clicking the Add button. To end the expression select the 'End' instead of a logical operator. To remove a condition already added to the expression, click the Undo button. After building the expression, click the Update button. |
![]() |
|
The subject of the Task can be customized. To prepare the Task subject, click on the button for the 'Subject' property. A window pops (Fig 3.) up where the subject can be typed and customized by appending the resource property values. Click the Update button to save the subject. |
![]() |
|
Notes is the content of the Task. To prepare the notes, click on the button for the 'Notes' property. A window pops (Fig 4.) up where the notes can be typed and customized by appending the resource property values. Click the Update button to save the notes. |
![]() |
|
The TaskTypes property in Task Action provides the interface to add Task Types and Status. The functionality of the Task Action is achieved through this property. A Task Status marked as ! is said to be the Task Completion Status for the Task Action. (E.g. If the TASK COMPLETION Task Type has COMPLETED & ON-HOLD as status, and COMPLETED is tagged with the Task Completion Maker, then, when the Task is submitted with COMPLETED as the selected status, the engine is alerted about the 'COMPLETED' status and it executes the next process in the workflow. The interface shown in Fig 5 is to Add, Edit and View the Task Types and Status added in the Task action. |
![]() |
|
The interface shown below is the second step for adding Task. This interface is displayed after the user selects Add New or Modify from the interface shown in Fig 5. The following parameters can be set here, |
![]() |
|
The interface shown below is the third step for adding a Task. The following Add New or Modify set here, |
![]() |
|
Multiple TimeOut Warnings are repeated warnings sent to the resources regarding timeout of the Task Action. To set multiple timeout warnings, click on the button for the 'Notes' property. A window pops (Fig 6) up where the Time Interval can be typed and the Recurring? option set to 'Yes'. The output message can also be typed here. More than one timeout warning can be set by clicking the New row button and entering the new timeout warning settings. Click the Update button to save the settings. |
![]() |