|
|
|
Task status codes describe the different possible states of a workflow task. Each task in an issue or change order workflow has its own status, separate from the ticket status. Workflow tasks allow analysts to keep track of how long it takes to complete individual tasks within a ticket.
The following table describes the predefined status codes for workflow tasks.
|
Task Status Code |
Description |
|---|---|
|
Approve |
Task approved. |
|
Cancelled |
Task is cancelled and no further updates are possible. |
|
Complete |
Task is complete. |
|
Pending |
Task is started. |
|
Reject |
Task is rejected. |
|
Reopen |
Task has been re‑opened. |
|
Reopen–Wait |
A prior task was reopened. |
|
Skip |
Skip task. |
|
Wait |
Task has not started. |
If your site uses other terminology for identifying the status of a workflow task, you should define status codes that suit your needs and ignore the predefined status codes, or change the definitions to match your use.
For each task status code, you can assign a type of behavior that occurs when the task reaches this state, which provides much more information about the progress toward completing the task. You can also use the accumulate function to track time and cost involved in completing the ticket.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |