2 Replies Latest reply on Oct 26, 2017 11:22 AM by xili

    Workflow Help

    Gazz Apprentice

      Hi All,

       

      Require a little help/inspiration...

       

      In a nut shell I'm try to create a workflow relating to equipment loans and purchasing. The first step of the workflow is to make a decision as to whether the user selected "Permanent" or "loan" on the form. Based on the selection the workflow will then create  tasks for the team to check if there is either kit in stock for a loan (short term) or for permanent assignment based on the initial selection (Loans and perm kit are form separate pools).

      Where I get stuck is how to use the exits in the tasks and continue the workflow.

      If I use the "completed" exit to achieve the "in stock" flow that will work fine however if the kit is not in stock there doesn't seem to be a logical exit to the next task to go get a quote.

       

      Without having to create multiple new exits and statuses in tasks is there a method to that can work achieving a "yes" kit is in stock so move to next stage or "no" then request quote for new equipment.

       

      If I use the "completed" exit to achieve the "in stock" flow that will work fine however however if the kit is not in stock there doesn't seem to be a logical exit to the next task to go get a quote.

       

      Another example shown below..if the user has indicated the correct equipment to be returned the I could use the completed exit. However if the task checks show differently to what the user has indicated in the kit return section the workflow then needs to be passed back to the submitter stating the the submitted information is incorrect. Again using cancelled or rejected is not the right approach in my mind as these are used for actual task cancellation and rejections based on other criteria.

       

      Is there some other logic I should be following here, everything I try ends up at the same question "How to exit the task ...." and then continue building the workflow.

       

      Apologies for the babbling.

       

        • 1. Re: Workflow Help
          xili Apprentice

          Apparently you should use the false exit of the "Check Asset Register" IF block to create the "next" task you planed, if there are only two cases. You may use "switch block", if the false exit of IF block is confusing. 

          • 2. Re: Workflow Help
            xili Apprentice

            I misunderstood you last time; not sure if you have figured out a solution, but I believe what you want to achieve should be done at the parent service request level. So basically when a team completes a task created by the workflow, they also need to "indicate" if there is an issue by setting a value on the task form before they set the task to Complete. At this time, the task and workflow execution are done, but the service request isn't fulfilled and a business rule can decide, based on the team updated service request field value from the task form, if the workflow should be triggered to create another task automatically or send communications to the customer or fulfill the service request.