3 Replies Latest reply on Jul 10, 2018 10:29 AM by JenBouillion

    Any way for a workflow to not complete when you add an AD HOC task

    JenBouillion Apprentice

      Wondering if anyone has found a way to add an AD HOC task (outside of the normal WorkFlow) and have the SR Workflow not to complete untill the AD HOC task has been completed.  I know its possible in other systems... so there has got to be a way to make it work in ISM.

       

        • 1. Re: Any way for a workflow to not complete when you add an AD HOC task
          Jonathan.Schmidt SupportEmployee

          Hi Jen,

           

          The Wait for child block only captures the current set of children and monitors them.  I think there's a feature request for expanding this as you'd like but I don't think you can do it this way.  I have seen other customers build a boolean that calculates off of total tasks and of completed tasks on the parent object and have triggered rules update that boolean field when tasks are created / completed / etc.  In that sort of setup, your workflow could have a simple wait block that checks for the boolean value before proceeding.

           

          It might not be the cleanest approach, others may have something better, but it's something I have seen others do in such a situation and it appeared to work.

           

          Hope this helps!

          Jon

          1 of 1 people found this helpful
          • 2. Re: Any way for a workflow to not complete when you add an AD HOC task
            MarkLarvo Specialist

            Hi Jen,

             

            I may not be understanding your question and I'm a little new to this but I have just been putting the workflow you show above as the very last block in my workflows.

             

            Limited testing showed this caused the initial workflow to wait until RequestWorkflwoCompletion has finished so I've added it to every SR.

             

             

            comm - workflow on hold.png

            Just remember to check the box to tell the first workflow to wait for this one to finish.

             

            comm - workflow hold chaeckbox.png

             

            Hope that helps! Mark.

            1 of 1 people found this helpful
            • 3. Re: Any way for a workflow to not complete when you add an AD HOC task
              JenBouillion Apprentice

              I do know that mine was not functioning that way previously a year ago but is currently functioning that way today based on my limited test selection.  I know it wasn't supposed to function this way as Jonathan stated above that it isn't supposed to count or include any tasks other than the ones built/ designed in the SR workflow (no additional task manually created).

               

              it did have a little quirky behavior as it didn't have an audit trail on the manually created task but the Status did not go to fulfilled till the manual task was completed.