Resource Action Scenarios

Skelta Workflow.NET 2004 Help

This topic deals with common business scenarios that can be addressed using Resource Actions

A set of scenarios for each Resource Action is described in the following sections:

Approval Action Scenarios
Checklist Action Scenarios
Information Action Scenarios
ResourceSet Action Scenarios
Task Action Scenarios

1) Approval Action Scenarios

Description: This section describes a set of scenarios where the Approval action can be applied. It describes the Properties setting for each scenario.

(i) Single User Approval

Case: Sending Approval activity to single user.

Property Setting:

Set the 'To' property which should map to one user.
Setting AAA to 100% or 1 will not make any difference, because only one person is involved in the Approval Action.

(ii) Escalation in Single User Approval

Case: Finding an alternate resource for the approval, if the original resource is not available (e.g., when he/she is on leave or he works in another shift and is not available currently or at the time of execution).

Property Setting:

The key property involved in identifying resource availability is 'Consider only Business Hours for Timeout?'.
1. If 'Organization' is selected, then it considers only shift details from Organization Calendar and Holidays that are set in the Organization calendar.
2. If 'Resource' is selected, then it considers the shift details of the Resource and his holiday details.
3. If 'No' is selected, then it will not consider Organization or Resource shift and holiday details. It will not check for resource availability.
Set 'Consider only Business Hours for Timeout?' to 'Resource'.
Set 'Ignore Unavailable Resource' to 'No'.
Set 'AlternateResource Allowed' property to 'Yes'.
Set holiday for the Original Resource or set a shift where the he/she will not be available at the time of the execution of the Action (provided an alternate resource has been set and is available and shift details have been set for him/her).

Settings in ActivityList Page::

Click on the Original Resource’s Calendar and set holiday or change the shift so that he should not be available.
Click on the 'Alternate Resource' link and set the Alternate Resource to handle the workflow. Select the Workflow name from the list and Submit.
Click on the Alternate Resource’s Calendar and set the shift, so that he should be available at the time of execution.

(iii) Group Approval

Case: Sending activity to multiple users to get approval from all the users.

Note: For a more detailed explanation of group approval scenarios click here.

Property Setting:

Set the 'To' property to be mapped to multiple resources.

(iv) Setting approval limits for group approval

Case: Sending activity to multiple users to get approval from one or more users based on the properties that are set.

Property Setting:

Set the 'To' property to be mapped to multiple resources.
Set the 'Min. Acknowledgements [% or Number] ' to identify minimum number of persons to acknowledge.
Set the 'Max. Acknowledgements [% or Number]' to identify the maximum number of persons to acknowledge.
Set 'Affirmative Answer for Approval [% or Number]' (shortly called AAA) to identify the number of positive decisions to make the output as 'Approved'.
Set 'Action Limit[% or Number]' which identifies the number of persons to take decisions. It can be either approved or rejected.
Set 'Wait For All The Participants To Act' to 'No'. This alerts the engine once the AAA is reached i.e. number of 'Approved' decision count reaches AAA.
Otherwise it will wait for all the people to take decision and out of that, it checks for number of approvals and rejection and then the engine is alerted based on that.
Setting 'Hide Responses' to 'No', allows the approver to view other approvers comments and decision.

(v) Setting time limits for approval

Case: Setting maximum time for the user(s) to take the decision. After that activity will be removed from his/her pending activity list.

Property Setting:

Set the 'To' property to map one or more resources.
Set 'Minimum Time for Action' to check whether the resource will be available for the next set of time.
Set 'TimeoutWarningforAcknowledgement' to alert the Users, if MinimumAcknowledgement count has not reached by this time.
Set TimeoutWarningforAction' to alert users, if ActionLimit has not reached by this time.
Set 'TimeoutForAcknowledgement' to alert the users, if Maximum Acknowledgement count has not reached.
Set 'TimeoutForAction' to alert the users, if either Minimum or maximum acknowledgement count has reached or ActionLimit has reached. And it will wait for the users who have acknowledged. If AAA i.e. Affirmative Answer for Approval has not reached, then the output will not be considered as 'Approved'.

(vi) Hiding responses from other users in a group approval

Case: To hide display of comments or decision taken by other approvers.

Property Setting:

Setting 'HideResponse' to 'Yes' will hide the comments or decision taken by others in this particular approval.

(vii) Considering resource holidays, leaves and work shift hours for setting timeouts

Case: Sending activities to resource based on Company calendar or resource calendar details (considering holidays, shift, week holidays). Also it will check resource availability and allocate alternate resources based on availability.

Property Setting:

The key property involved in identifying resource availability is 'Consider only Business Hours for Timeout?'.
1. If 'Organization' is selected, then it considers only shift details from Organization Calendar and Holidays that are set in the Organization calendar.
2. If 'Resource' is selected, then it considers the shift details of the Resource and his holiday details.
3. If 'No' is selected, then it will not consider Organization or Resource shift and holiday details. It will not check for resource availability.
Set 'Consider only Business Hours for Timeout?' to 'Resource'.
Set 'Ignore Unavailable Resource' to 'No'.
Set 'AlternateResource Allowed' property to 'Yes'.
Set a holiday for the Original Resource or set a shift where he/she will not be available at the time of the execution of the Action (provided an alternate resource has been set and is available and shift details have been set for him/her).

(viii) Forwarding to other resources

Case: Delegating the approval to some other resources, if the original resource is busy or wishes to delegate.

Property Setting:

Set 'Forwardingallowed' property to 'Yes' in the approval action..

Settings in ActivityList Page::

Click on the Original Resource’s Calendar and set holiday or change the shift so that he should not be available.

(ix) Handling unavailable resources

Case: There is a property that handles the situation by ignoring the original resource if he is not available and considering the alternate resource i.e. when the original resource is not available, the workflow engine will decide whether it should be sent to alternate resource or it should not be sent to anybody.

Property Setting:

Set 'Consider Business Hours for Timeout?' to 'Resource'.
Set 'IgnoreUnavailable Resources' to 'No'. This will ignore the original resource (if he/she is not available) and check for alternate resource otherwise the output will be 'Not enough resources to acknowledge'.
Set 'AlternateResource Allowed' to 'Yes' to consider the alternate resource if original resource is not available. Otherwise the output will be 'Not enough resources to acknowledge'.

Top

2) Checklist Action Scenarios

Description: This section describes a set of scenarios where the Checklist action can be applied. It describes the Properties setting for each scenario.

(i) Text box/Memo questionnaire

Case: Displaying text box control in ActivityList page to give provision for entering any text which can be used later.

Property Setting:

Click on 'Questions' property of the checklist action.
Type number of questions that you want to put for the Users. Click 'AddNew'.
Type the name of the question.
Select 'Textbox/Memo from the dropdown list.
If 'Mandatory' is checked, then it will prompt the users to enter some data in the text box at runtime. Click on 'Next' button.
Set the default value for the text box. This is optional. This value will be shown for the user while opening the activity.

(ii) Checklist questionnaire

Case: Displaying check box control in ActivityList page to give provision for selecting the option which can be used later in the workflow design.

Property Setting:

Click on 'Questions' property of the checklist action.
Type number of questions that you want to put for the Users. Click 'AddNew'.
Type the name of the question.
Select 'CheckBox' from the dropdown list.
Type the number of answers for this question.
If 'Mandatory' is checked, then it will prompt the users to select one answer at runtime. Click on 'Next' button.
Set 'Options' which is the answer for the above question.
Set the default value for the check box. This is optional. This value or answer will be selected by default for the user while opening the activity.
Set the 'Values' which is the value for that particular answer.

(iii) Radio button questionnaire

Case: Displaying radio box control in ActivityList page to give provision for selecting the option which can be used later in the workflow design.

Property Setting:

Click on 'Questions' property of the checklist action.
Type number of questions that you want to put for the Users. Click 'AddNew'.
Type the name of the question.
Select 'Radio' from the dropdown list.
Type the number of answers for this question.
If 'Mandatory' is checked, then it will prompt the users to select one answer at runtime. Click on 'Next' button.
Set 'Options' which is the answer for the above question.
Set the default value for the check box. This is optional. This value or answer will be selected by default for the user while opening the activity.
Set the 'Values' which is the value for that particular answer.

(iv) Mixed questionnaire

Case: Displaying mixed controls in ActivityList page to give provision for entering any text, as well as selecting some options that can be used later.

Property Setting:

Click on 'Questions' property of the checklist action.
Type number of questions that you want to put for the Users. Click 'AddNew'.
Type the name of the questions and select the type of controls for that question.
Select 'Radio' from the dropdown list.
If 'Mandatory' is checked, then it will prompt the users to to enter some data or select some answers at runtime. Click on 'Next' button.
Set the default value for the controls. Its optional. This value will be shown for the user while opening the activity (if it is textbox) and control will be selected by default if it is Radio or Checkbox or dropdownlist.

(v) Using questions to make decisions on the workflow execution path

Case: Setting the controls as the Decision maker for the checklist action. Out of all the controls that are provided for the checklist, only 'dropdownlist' control will the be taken as the Decision Maker. The dropdown list values only can be used to route the workflow execution path.

Property Setting:

Click on 'Questions' property of the checklist action.
Type number of questions that you want to put for the Users. Click 'AddNew'.
Type the name of the question.
Select 'Dropdown' from the dropdown list.
Type the number of answers for this question.
If 'Mandatory' is checked, then it will prompt the users to select one answer at runtime. Click on 'Next' button.
Set 'Options' which is the answer for the above question.
Set the default value for the check box. This is optional. This value or answer will be selected by default for the user while opening the activity.
Set the 'Values' which is the value for that particular answer.
These dropdownlist answers will be displayed in the 'Link' condition, which can be used to route the workflow based on the selected dropdown list value at run time.

(vi) Setting action limits for group Checklist completion scenario

Case: Assigning Checklists to multiple users to get one or more users to act on it based on the properties that are set.

Property Setting:

Set the 'To' property to be mapped to multiple resources.
Set the 'Min. Acknowledgements [% or Number] ' to identify minimum number of persons to acknowledge.
Set the 'Max. Acknowledgements [% or Number]' to identify the maximum number of persons to acknowledge.
Set 'Affirmative Answer for Checklist Completion [% or Number]' (shortly called AAC) to identify the number of actions to make the output as 'Completed'.
Set 'Action Min Limit Checklist Completion [% or Number]' which identifies the number of persons to take action.
Set 'Wait For All The Participants To Act' to 'No'. This alerts the engine once the AAC is reached i.e. number of 'Completed' action count reaches AAC.
Otherwise it will wait for all the people to take action and out of that, it checks for number of completed Checklists and then engine is alerted based on that.
Setting 'Hide Responses' to 'No', allows the resource to view the comments and responses of other resources in the group.

(vii) Setting time limits for Checklist assignment

Case: Setting maximum time for the user(s) to complete the task. After that activity will be removed from his/her pending activity list.

Property Setting:

Set the 'To' property to map one or more resources.
Set 'Minimum Time for Action' to check whether the resource will be available for the next set of time.
Set 'TimeoutWarningforAcknowledgement' to alert the Users, if MinimumAcknowledgement count has not reached by this time.
Set TimeoutWarningforAction' to alert users, if Action Min Limit has not reached by this time.
Set 'TimeoutForAcknowledgement' to alert the users, if Maximum Acknowledgement count has not reached.
Set 'TimeoutForAction' to alert the users, if either Minimum or maximum acknowledgement count has reached or Action Limit has reached. And it will wait for the users who have acknowledged. If AAC i.e. Affirmative Answer for Checklist Completion has not reached, then the output will not be considered as 'Completed'.

(viii) Hiding responses from other users in group Checklist assignment

Case: To hide display of comments or responses of other resources.

Property Setting:

Setting 'HideResponse' to 'Yes' will hide the comments and responses of other resources involved in this particular Checklist assignment.

(ix) Considering resource holidays, leaves and work shift hours for setting timeouts

Property Setting:

The key property involved in identifying resource availability is 'Consider only Business Hours for Timeout?'.
1. If 'Organization' is selected, then it considers only shift details from Organization Calendar and Holidays that are set in the Organization calendar.
2. If 'Resource' is selected, then it considers the shift details of the Resource and his holiday details.
3. If 'No' is selected, then it will not consider Organization or Resource shift and holiday details. It will not check for resource availability.
Set 'Consider only Business Hours for Timeout?' to 'Resource'.
Set 'Ignore Unavailable Resource' to 'No'.
Set 'AlternateResource Allowed' property to 'Yes'.
Set a holiday for the Original Resource or set a shift where the he/she will not be available at the time of the execution of the Action (provided an alternate resource has been set and is available and shift details have been set for him/her).

(x) Forwarding to other resources

Case: Delegating the Checklist assignment to some other resources, if the original resource is busy or wishes to delegate.

Property Setting:

Set 'Forwardingallowed' property to 'Yes' in the action.

Settings in ActivityList Page::

Click on the Original Resource’s Calendar and set holiday or change the shift so that he should not be available.

(xi) Handling unavailable resources

Case: There is a property that handles the situation by ignoring the original resource if he is not available and considering the alternate resource i.e. when the original resource is not available, the workflow engine will decide whether it should be sent to the alternate resource or it should not be sent to anybody.

Property Setting:

Set 'Consider Business Hours for Timeout?' to 'Resource'.
Set 'IgnoreUnavailable Resources' to 'No'. This will ignore the original resource (if he/she is not available) and check for alternate resource otherwise the output will be 'Not enough resources to acknowledge.
Set 'AlternateResource Allowed' to 'Yes' to consider the alternate resource if the original resource is not available. Otherwise the output will be 'Not enough resources to acknowledge'.

(xii) How to use the data entered in the Checklist during the Process

Case: Make use of Checklist question’s answers values throughout the workflow and also for application purpose using XMLAction.

Property Setting:

Create a variable of string type in the Start action whose name is in the format shown below:
'^'+ action name + 'AnswersXMLCheckList'
E.g., If the Checklist action name is 'ReviewOrder' then the variable should be named ^ReviewOrderAnswersXMLCheckList.
Create a link between Checklist action and XMLAction with output like 'ActionCompleted' or any drop down list values.
In the XML Action, select the variable ^ReviewOrderAnswersXMLCheckList from the 'GetVariable' property.
Click on 'SetVariables' property.
Select any other string variable from the dropdownlist and give the XPath format shown below to access the value of various controls —
XPath With attribute:
//checklist/question[@name="RADIO"]/answer
//checklist/question[@name="DROPDOWN"]/answer
//checklist/question[@name="TEXTBOX"]/answer
//checklist/question[@name="MEMO"]/answer
//checklist/question[@name="CHECKBOX"]/answer

Top

3) Information Action Scenarios

Description: This section describes a set of scenarios where the Information action can be applied. It describes the Properties setting for each scenario.

(i) Sending information

Case: Sending information to users regarding approval or rejection, or alerting the users with some information.

Property Setting:

Set the 'To' property to be mapped to one or more users.

Top

4) ResourceSet Action Scenarios

Description: This section describes a set of scenarios where the ResourceSet action can be applied. It describes the Properties setting for each scenario.

(i) How to let users select resources to perform further actions during a stage in the workflow

Case: Setting ResourceSet action to dynamically select a resource at the runtime for handling the next set of actions.

Property Setting:

Create a variable in the Start Action. The variable can be of one of the following types — String, Numeric, Resource or Array.
1. Setting String or Numeric enables the user to assign the task to only one resource.
2. Setting the Resource type, will take all the properties of the selected resource. In this case too it will take the details of only one resource.
3. Setting the Array type enables the user to assign the task to multiple resources for handling the next set of actions. The selected resources' ID will be stored in the array.
Set the 'To' property to be mapped to one or more users.
Set 'Ignore Unavailable Resource' to 'No'.
Set the 'SetVariable' property (this variable takes the selected resources' details).
Set the 'FilterResource' property, which maps to one or more resources. (These resources' email will get displayed in the Activitylist page.)
Use the above variable (i.e., the one selected in the SetVariable property) in the 'To' property of other actions.

Settings in ActivityList Page::

After execution, click on the activity id.
A list of resources whose details have been set in 'FilterResources' property will be displayed.
Select one or more resources from the list and click on 'Proceed'.
The Userid of selected resources will be captured in the variables that have been set in the 'SetVariable' property.

Sample Scenario for the ResourceSet Action

Assume that Kevin is the Project Manager to whom a team of five Senior Developers report. Assume a scenario where he will assign the task of reviewing a document to the Senior Developers.

In the process designer do the following:

In the 'Start' action, declare a variable named 'Assign Resources' of type Array.
Click and drop a ResourceSet action. This action is for selecting resource(s) for reviewing the document.

Set the 'To' property to 'FirstName= Kevin'
Set the 'SetVariable' property to 'Variable.AssignResources'
Set the 'FilterResource' property to 'Designation=Senior Developer'
Save the action property setting
Create the link from the 'Start' action to the 'ResourceSet1' action
Click and drop an Information action
Create the link from the 'ResourceSet1' action to the 'Information1' action
Set the 'To' property of the 'Information1' as UserId—In—Variable.AssignResources

(ii) Selecting one resource or multiple resources

Case: Selecting one or more resources for handling further actions.

Property Setting:

Set the 'To' property to be mapped to one or more users.

To select only one resource, declare a variable in the start action as string or numeric or resource type.
To assign task for multiple resources, declare the variable as 'array' type. This variable takes only the UserId of the selected resources.
Declaring a variable as 'resource' will take only one resource’s id and properties.

Select the above variable in the 'SetVariable' property (this variables takes the selected resources' details).
Set the 'FilterResource' property to map to one or more resource.

(iii) Taking only the user id or all the resource properties

Case: Variables can be stored with userids or all the user properties of the selected resources.

Property Setting:

Set the 'To' property to be mapped to one or more users.
To store UserId in the variable, declare the variable as Array or numeric or string.
To store resources properties, declare the variable as 'resource' type.
Select the above variable for the 'SetVariable' property (this variables takes the selected resources' details).
Set the 'FilterResource' property which maps to one or more resources.

(iv) Setting action limits for group Resource setting scenario

Case: Assigning ResourceSet activity to multiple users to get one or more users to act on it based on the properties that are set.

Property Setting:

Set the 'To' property to be mapped to multiple resources.
Set the 'Min. Acknowledgements [% or Number] ' to identify minimum number of persons to acknowledge.
Set the 'Max. Acknowledgements [% or Number]' to identify the maximum number of persons to acknowledge.
Set 'Affirmative Answer for ResourceSet Completion [% or Number]' (shortly called AAR) to identify the number of actions to make the output as 'Completed'.
Set 'Action Min Limit ResourceSet Completion [% or Number]' which identifies the number of persons to take action.
Set 'Wait For All The Participants To Act' to 'No'. This alerts the engine once the AAR is reached i.e. number of 'Completed' action count reaches AAR.
Otherwise it will wait for all the people to take action and out of that, it checks for the number of completed tasks and then the engine is alerted based on that.
Setting 'Hide Responses' to 'No', allows the resource to view the comments and responses of other resources in the group.

(v) Setting time limits for ResourceSet assignment

Case: Setting maximum time for the user(s) to complete the task. After that the activity will be removed from his/her pending activity list.

Property Setting:

Set the 'To' property to map one or more resources.
Set 'Minimum Time for Action' to check whether the resource will be available for the next set of time.
Set 'TimeoutWarningforAcknowledgement' to alert the Users, if MinimumAcknowledgement count has not reached by this time.
Set TimeoutWarningforAction' to alert users, if Action Min Limit has not reached by this time.
Set 'TimeoutForAcknowledgement' to alert the users, if Maximum Acknowledgement count has not reached.
Set 'TimeoutForAction' to alert the users, if either Minimum or maximum acknowledgement count has reached or Action Limit has reached. And it will wait for the users who have acknowledged. If AAR i.e. Affirmative Answer for ResourceSet Completion has not reached, then the output will not be considered as 'Completed'.

(vi) Hiding responses from other users in a group ResourceSet assignment

Case: To hide display of comments or responses of other resources.

Property Setting:

Setting 'HideResponse' to 'Yes' will hide the comments and responses of other resources involved in that particular ResourceSet assignment.

(vii) Considering resource holidays, leaves and work shift hours for setting timeouts

Property Setting:

The key property involved in identifying resource availability is 'Consider only Business Hours for Timeout?'.
1. If 'Organization' is selected, then it considers only shift details from Organization Calendar and Holidays that are set in the Organization calendar.
2. If 'Resource' is selected, then it considers the shift details of the Resource and his holiday details.
3. If 'No' is selected, then it will not consider Organization or Resource shift and holiday details. It will not check for resource availability.
Set 'Consider only Business Hours for Timeout?' to 'Resource'.
Set 'Ignore Unavailable Resource' to 'No'.
Set 'AlternateResource Allowed' property to 'Yes'.
Set a holiday for the Original Resource or set a shift where the he/she will not be available at the time of the execution of the Action (provided an alternate resource has been set and is available and shift details have been set for him/her).

(viii) Forwarding to other resources

Case: Delegating the ResourceSet assignment to some other resources, if the original resource is busy or wishes to delegate.

Property Setting:

Set 'Forwardingallowed' property to 'Yes' in the action.

Settings in ActivityList Page::

Click on the Original Resource’s Calendar and set holiday or change the shift so that he should not be available.

(ix) Handling unavailable resources

Case: There is a property that handles the situation by ignoring the original resource if he is not available and considering the alternate resource i.e. when the original resource is not available, the workflow engine will decide whether it should be sent to the alternate resource or it should not be sent to anybody.

Property Setting:

Set 'Consider Business Hours for Timeout?' to 'Resource'.
Set 'IgnoreUnavailable Resources' to 'No'. This will ignore the original resource (if he/she is not available) and check for alternate resource otherwise the output will be 'Not enough resources to acknowledge.
Set 'AlternateResource Allowed' to 'Yes' to consider the alternate resource if the original resource is not available. Otherwise the output will be 'Not enough resources to acknowledge'.

Top

5) Task Action Scenarios

Description: This section describes a set of scenarios where the Task action can be applied. It describes the Properties setting for each scenario.

(i) Assigning tasks to users

Case: Assigning a task to the users and setting task status.

Property Setting:

Set the 'To' property to be mapped to one or more users.
Click on 'TaskTypes' and set the number of possible task status. Click on the 'Next' button.
Type the Task status type and number of status for that task type. Click on 'Next' button.
Type the various statuses and set the 'Task Completion Maker' in order to use the status for routing the workflow.

(ii) Setting status for assigned tasks

Case: More than one task types can be created for a task action.

Property Setting:

Select any one of the task types from the TaskTypes drop down and save the action.
Set the 'To' property to be mapped to one or more users.

(iii) Setting task completion status

Case: The 'TaskCompletionMaker' property is used to route the workflow. Statuses that are marked as 'TaskCompletionMaker' will get displayed in the 'LinkCondition' dropdown list. Also the activity will not be removed from the activity list unless and until the task completion maker status is selected.

Property Setting:

Set the 'To' property to be mapped to one or more users.
Click on the 'TaskTypes' and set the number of possible task statuses. Click on 'Next' button.
Type the Task status type and number of status for that task type. Click on the 'Next' button.
Type the various statuses and set the 'Task Completion Maker' in order to use the status for routing the workflow.

Settings in ActivityList Page::

After execution, click on the activityid.
Both the statuses that are marked as TaskCompletionMakers, and those that are not, will be displayed.
Selecting the TaskCompletionMaker status will route the workflow based on the selected status.
Selecting statuses that are not TaskCompletionMakers will not have any effect.

(iv) Setting action limits for group Task assignment scenario

Case: Sending task activity to multiple users to get one or more users to act on it based on the properties that are set.

Property Setting:

Set the 'To' property to be mapped to multiple resources.
Set the 'Min. Acknowledgements [% or Number] ' to identify minimum number of persons to acknowledge.
Set the 'Max. Acknowledgements [% or Number]' to identify the maximum number of persons to acknowledge.
Set 'Affirmative Answer for TaskAssignment Completion [% or Number]' (shortly called AAT) to identify the number of actions to make the output as 'Completed'.
Set 'Action Min Limit TaskAssignment Completion [% or Number]' which identifies the number of persons to take action.
Set 'Wait For All The Participants To Act' to 'No'. This alerts the engine once the AAT is reached i.e. number of 'Completed' action count reaches AAT.
Otherwise it will wait for all the people to take action and out of that, it checks for number of completed tasks and then engine is alerted based on that.
Setting 'Hide Responses' to 'No', allows the resource to view the comments and responses of other resources in the group.

(v) Setting time limits for Task assignment

Case: Setting maximum time for the user(s) to complete the task. After that activity will be removed from his/her pending activity list.

Property Setting:

Set the 'To' property to map one or more resources.
Set 'Minimum Time for Action' to check whether the resource will be available for the next set of time.
Set 'TimeoutWarningforAcknowledgement' to alert the Users, if MinimumAcknowledgement count has not reached by this time.
Set TimeoutWarningforAction' to alert users, if Action Min Limit has not reached by this time.
Set 'TimeoutForAcknowledgement' to alert the users, if Maximum Acknowledgement count has not reached.
Set 'TimeoutForAction' to alert the users, if either Minimum or maximum acknowledgement count has reached or Action Limit has reached. It will wait for the users who have acknowledged. If AAT i.e. Affirmative Answer for TaskAssignment Completion has not reached, then the output will not be considered as 'Completed'.

(vi) Hiding responses from other users in group Task assignment

Case: To hide the display of comments or responses of other resources.

Property Setting:

Setting 'HideResponse' to 'Yes' will hide the comments and responses of other resources involved in this particular task assignment.

(vii) Considering resource holidays, leaves and work shift hours for setting timeouts

Property Setting:

The key property involved in identifying resource availability is 'Consider only Business Hours for Timeout?'.
1. If 'Organization' is selected, then it considers only shift details from Organization Calendar and Holidays that are set in the Organization calendar.
2. If 'Resource' is selected, then it considers the shift details of the Resource and his holiday details.
3. If 'No' is selected, then it will not consider Organization or Resource shift and holiday details. It will not check for resource availability.
Set 'Consider only Business Hours for Timeout?' to 'Resource'.
Set 'Ignore Unavailable Resource' to 'No'.
Set 'AlternateResource Allowed' property to 'Yes'.
Set holiday for the Original Resource or set a shift where he/she will not be available at the time of the execution of the Action (provided an alternate resource has been set and is available and shift details have been set for him/her).

(viii) Forwarding to other resources

Case: Delegating the task to some other resources, if the original resource is busy or wishes to delegate.

Property Setting:

Set 'Forwardingallowed' property to 'Yes' in the action.

Settings in ActivityList Page::

Click on the Original Resource’s Calendar and set holiday or change the shift so that he should not be available.

(ix) Handling unavailable resources

Case: There is a property that handles the situation by ignoring the original resource if he/she is not available and considering the alternate resource i.e. when the original resource is not available, the workflow engine will decide whether it should be sent to the alternate resource or it should not be sent to anybody.

Property Setting:

Set 'Consider Business Hours for Timeout?' to 'Resource'.
Set 'IgnoreUnavailable Resources' to 'No'. This will ignore the original resource (if he/she is not available) and check for alternate resource otherwise the output will be 'Not enough resources to acknowledge.
Set 'AlternateResource Allowed' to 'Yes' to consider the alternate resource if the original resource is not available. Otherwise the output will be 'Not enough resources to acknowledge'.

Top

Skelta - A BPM Workflow Software Company