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
Store

Is there a way to link two sets of Tasks together?

I have two Task workflows that trigger on a ticket creation. One task is for the completion of an access request form and each child task gets closed in sequence. I then have a Task that is generated at a different ticket creation to then grant the access. These two Tasks are tracked separately by the due date of the parent tickets so I cannot merge them, but I need a way to have Task2 generated once the final task in Task 1 is closed. Is this possible or should I be rethinking how these two workflows get accomplished?

Find more posts tagged with

tasks

workflow

Accepted answers

All comments

pabely

Have you tried a second element in your Task which triggers when status becomes Closed?

jdmartel

Yes but I have 3-4 sets of Tasks and there is an action rule for each one that determines which Task gets run because they are all slightly different. I need a "fork in the road" that will let me determine with task elements get run when certain custom fields are set.

For example if Custom Field option 1 is checked then run these task elements. If Custom Field option 2 or 3 is checked then run these task elements.

Currently this is done by our Techs manually creating a Parent ticket with those custom fields, and I have a "trigger" custom field that determines when the Tasks get run, and which Task get runs is determined by what other fields are selected. I would like to remove that manual piece between

jdmartel

I resolved this by inserting the original parent ticket into the Task flow, and kept my action rules in place. this will essentially "nest" the 2nd workflow into the first one.