Managing parallel reviews

Brian_Winter

Got a tough one.  I have a parallel activity that contains several RA/MA sequential activities.  If one Review gets rejected, the whole darn SR goes Failed, not just the individual activity segment.  



This link:  https://social.technet.microsoft.com/Forums/en-US/293c3666-0aea-4599-9415-0abbb2b20e20/parallel-activity-failed-when-an-activity-inside-fail?forum=administration says it's default behavior and cannot be changed.  Boo on that.

I find this to be a horrible design since many paths may be successful.  You can't say one fail makes the ticket failed.  Anyway, HOW are you supposed to work this way?  Basically the End User is selecting several Roles that go to different Approvers and Implementers.  God knows I don't want to have one SR spin of X child SRs.  I'm trying to keep it all in one ticket, one workflow.

 Ideas?  Suggestions?

Nicholas_Velich

Hi Brian,

My suggestion here would be a PowerShell script and/or Orchestrator runbook that monitors for these failed Activities or Service Requests, and takes the appropriate actions thereafter to get the Service Request back on-track. For example, whenever one of these cases is found, the script/runbook could skip the failed Review Activity, and set the Service Request to go back to "In Progress" (or rerun the skipped activity).

Thanks,
Nick

Nicholas_Velich

Hi Brian,

My suggestion here would be a PowerShell script and/or Orchestrator runbook that monitors for these failed Activities or Service Requests, and takes the appropriate actions thereafter to get the Service Request back on-track. For example, whenever one of these cases is found, the script/runbook could skip the failed Review Activity, and set the Service Request to go back to "In Progress" (or rerun the skipped activity).

Thanks,
Nick

Brian_Winter

That was our solution.  Not elegant but workable.