Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

URGENT!!!! - What does task Run = mean in action rules...Please help

Aakhib

@typhoon87 @mr_typhoon @kellytice

Find more posts tagged with

Accepted answers

All comments

kellytice

You can create a Task (under setup - tickets -tasks) to generate one or more tickets whenever the Task is executed. If a tech goes in and manually runs a task, it will generate those tickets that you have defined in the task.

You can also create an Action Rule to watch for some condition and then take some action when that condition occurs. One of the action options in an Action Rule is to automatically run a Task

A common example of an Action role launching a Task is for a new hire process. I could have an Action role that watches for NEW tickets that have a Request Type called 'new hire'... And then when one of those new hire tickets is actually made, it could launch my 'new hire' Task. The task could them auti-generate tickets to IT, HR, Facilities, etc... to do the work needed to onboard the new person.

Aakhib

I think my question was confusing.. The response you have given is for "How to run task". Sorry about the misdirection.

My question is actually about action after the criteria. If a issue type with CAB is set to trigger a set of task and its elements. I need to set the criteria is "taskrun = or>= or <=" same thing Appears in the advanced search option a criteria..

Find snapshot.. WHAT does TASK RUN mean in the below snapshot.

kellytice

Ah, OK. i understand your question now.

If you have a Task, as mentioned previously it can kick off multiple tickets when that Task is executed... so one Task might kick off 3 tickets that are all somewhat related (even if they don't have a "real" Parent-Child relationship, they are still kind of tied together based on the fact that they were generated by the same Task.

Let's say you run the same Task once per day for two weeks. That's 14 different times that the task has been executed. The WHD system keeps track of which tickets were generated by each "run" of the Task. That is what is represented by "Task Run" ... so all of the tickets generated by the 3rd run of the task will show a Task Run of 3

As an example: In a demo environment, the same task was executed 10 times. In the screenshot below you can see that the bottom two tickets listed (112 and 113) were generated the 9th time the task was run, and the top 3 tickets (109, 110, 111) were all generated the 10th time the task was run:

Aakhib

Thanks Much... I really appreciate the efforts.. My point of actually asking this was coz I have a requirement where

"The Parent should update when the child tasks are either resolved or updated" And hence I was looking for a way in which I can specify an action rule as when the last task or the child is closed the task run should generate a response to the parent..

Is it even possible, What I see is each action rule is for that particular ticket only and no parameters are actually linked except the Parent ticket and child ticket naming or tabs in the ticket itself.

Kindly advise.