Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Task management follows the same concepts that are applied to Ticket Management in general, with some exceptions. The exception arises because Task Tickets can be created only as children of Service Requests, Incident, Problem, and Change Requests. Task Tickets are related only to the parent ticket and no other tickets. The Task Tickets are created to assign different tasks to users or groups. On the completion of tasks, you can update the parent ticket with the results.

The default process is applied when the ticket did not match the entry criteria of other task process workflows that are active. By default, the status of the Default Task Management Process Flow is set to Published.

The process of a default task management is shown in the following diagram:                             

 

To view how the flow diagram looks in the application, click Default Task Management Process Flow.

The following steps explain how default task management process workflow works:

  1. When a ticket is raised, based on the matching conditions the entry criteria is verified to assign the request. When no conditions are matched, the request is assigned to Service Desk (L1) group.
  2. The ticket is assigned to the respective analyst in the Administrative group for resolution.
  3. When a resolution is identified, the ticket is closed as successful. If the resolution is not identified, the ticket is closed as failed and is reopened for resolution. 

The following section provides details of the Default Task Management Process Flow configuration.

Entry Criteria

The Task Management entry criteria in the predefined workflow configurations get applied to the ticket based on the ticket source. The following table lists the entry criteria that is available for Task Management Management tickets:

DefineAssignSetNotify
Entry CriteriaSort OrderProcess TypeDefault Assignment

Auto Assignment RulesStatusPhaseReason CodeEmail Template
UserGroupSort OrderIf CriteriaThen Assign To
NA999Auto Route----------NewTaskNone--

Process Steps

 The following steps list the Action Options that are available with the predefined workflow configurations for Task Management Process Flow.

Step: Accept Assignment

Define Tab

Basic PropertiesAdvanced Options
TypeNameDescriptionClose Window on SaveWeb Service OperationsMandatory Fields
Accept AssignmentAccept AssignmentAccept AssignmentNo----

Permission Tab

GroupsRolesUsersLimit To
Public and Administration------

Step: Complete as Successful

Define Tab

Basic PropertiesAdvanced Options 
TypeNameDescriptionClose Window on SaveWeb Service OperationsMandatory Fields
Update TicketComplete as Successful

Action to complete the task as successful

Yes----

Permission Tab

GroupsRolesUsersLimit To
Public and Administration------

Set Tab

Set Ticket Parameters
Reason CodeStatusPhase
CompletedClosedClosure

Step: Complete as Failed

Define Tab

Basic PropertiesAdvanced Options 
TypeNameDescriptionClose Window on SaveWeb Service OperationsMandatory Fields
Update TicketComplete as FailedAction to complete the task as failedYes----

Permission Tab

GroupsRolesUsersLimit To
Public and Administration------

Set Tab

Set Ticket Parameters
Reason CodeStatusPhase
As Cancelled / Rejected / DeniedClosedClosure

Step: Reopen and Take Ownership

Define Tab

Basic PropertiesAdvanced Options 
TypeNameDescriptionClose Window on SaveWeb Service OperationsMandatory Fields
Accept AssignmentReopen and take ownershipAction to reopen the closed task and take ownershipNo----

Permission Tab

GroupsRolesUsersLimit To
Public and Administration------

Set Tab

Set Ticket Parameters
Reason CodeStatusPhase
ReopenedActiveTask
  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.