Description of Task Management Functions
The Task Management Console has two functions, to track task trees and to diagnose exceptions. You must be in the Task Manager Remedy permission group (KS_TSK_Manager) to access the Task Management function.
NOTE: You must also be a menber of the KS_TSK_Manager Remedy permission group to see the Kinetic Task Manager link from the Service Catalog Console.
Along the top of the console is the logged in user, a logout link, and version information.
Directly below that are the web and Remedy servers being accessed.
The Task Management console has two tabs: Exceptions and Executions.
The exceptions tab is used to display all the exceptions (errors) thrown by tasks on all task trees.
Example of the Exceptions tab:
Each exception is listed with the newest at the top.
Clicking on the Show Execution icon will take you to the Executions tab for that particular submission with the details of the exception revealed.
If you click directly on the exception, more details are revealed:
The Source ID is the Instance ID of the service item/execution of this tree. The Tree Name and Tree Instance ID are provided in a couple of places. The Node Name and Node Type (the Task handler used) are also listed. These items all assist you in locating the problem node and tree.
The Error and the Cause tell you what exactly the error was and what the task engine has identified as the cause. This will assist you in correcting the error condition.
|Created At||Status||Type||Source Root||Source Group||Source ID||Tree|
|05/08/2013 13:29:57||Active||Handler Error||Kinetic Request||Brents Test Catalog II > Approval Service Item||AG005056960055lIuKUQqKRJRwBfsi||Send Email|
|A problem was encountered processing the 'utilities_echo_v1_1' (utilities_echo_v1_1) node on the 'Send Email' (ID005056960055SYuKUQwH9IRw7fci) tree.|
A problem was encountered processing the 'utilities_echo_v1_1' (utilities_echo_v1_1) node on the 'Send Email' (ID005056960055SYuKUQwH9IRw7fci) tree. ERROR: KineticTask::TaskParameterException: Unable to process the 'input' parameter for node 'utilities_echo_v1_1' (utilities_echo_v1_1): <%=@template['Service Category Name']%> CAUSE: KineticTask::TemplateError: Unable to retrieve hash value for the key "Service Category Name". STACK TRACE: lib/kinetic_task/engine_processing.rb:942:in `build_task_parameters' lib/kinetic_task/engine_processing.rb:934:in `each' lib/kinetic_task/engine_processing.rb:934:in `build_task_parameters' lib/kinetic_task/engine_processing.rb:793:in `execute_handler'
Clicking on the Edit icon on the top right allows you to show/hide the notes and actions for the node (depends on circumstance and error what actions are available). Resolution Notes are required to take action on the error.
The close icon closes the exception details.
The executions tab is useful for seeing all the activity that occurs related to an instance of a task tree.
When first displayed, unless displayed via clicking on the Show Execution icon on the Exceptions tab, this tab is blank. To display executions, enter a Source Root. A Source Group and/or Source Id can be specified to further limit the search.
Click on an execution in the list to display more details:
The top of the execution details lists the source information, including a link to the Tree Builder for the source Tree. If the submission is a Kinetic Request submission, there is also a link to the review request for the submission. By default exceptions are shown. Clicking on an exception shows the same details that are available in the Exceptions tab (see section above for details).
In the execution details, the triggers for the task tree instance are shown first followed by the task or node instances. Information on connectors is not shown, but implied by the presence of node instances.
Clicking on a triggers shows details for that trigger.
And clicking on a node shows details for that node.
The node details will include any results. This can be important information for troubleshooting. It allows visibility of data being passed, possibly, from one node to another. It can also provide source Ids for deferred nodes, since this Id is often a result returned.