Skip to main content
Solved

Multiple Workflow Automations

  • February 15, 2024
  • 8 replies
  • 369 views
G
Community Debut
Forum|alt.badge.img

I know this has been asked in various different ways but I haven’t found a concrete answer.

I’m creating an Employee Onboarding Process and one of the options is that the hiring manager can select various software titles to be installed on the laptop.  The number of apps will vary.

Right now a child ticket is created and attached to that child ticket  are the various apps to install, listed as Service Request Items.  

The plan is to use the Azure AD app to automatically add users to AzureAD groups that auto install the software.

But I cannot get the automation right.  If I do one Workflow with multiple conditions for the software,  once it hits the first ‘yes’, it runs and that's it.  It doesn’t go through the rest of the conditions.

If I create multiple workflows, only one fires.

Is there a way to have multiple workflows fire for one ticket?  Or is there a dynamic way to execute actions against multiple service requests attached to a ticket?

Best answer by zachary.king

Hello @Garuda, complex automations can be frustrating in freshservice. @ekrasner has a great idea to build them out further. Thankfully workflow automators are getting some enhancements mid-term this year. Including the ability to loop, and build workflow “components” that will be reusable throughout the workflow. Fingers crossed, they come sooner rather than later.

View original
    zachary.king
    Kamakshi V
    M
    3 people like this
    • zachary.king
      zachary.king
    • Kamakshi V
      Kamakshi V
    • M
      MDavies
    Did this topic help you find an answer to your question?

    8 replies

    ekrasner
    Community Debut
    Forum|alt.badge.img+2
    • ekrasner
    • Community Debut
    • 24 replies
    • February 16, 2024

    We do this. At the end of your 1st workflow, run a powershell node and using the WebAPI, do something link set the status of the ticket to pending and update a custom field and then have the second workflow initiate on the status change from open to pending and the custom field have your test in it.  I actually daisy chain 5 workflows doing this.

    Kamakshi V
    G
    Alex Pr
    3 people like this
    • Kamakshi V
      Kamakshi V
    • G
      Garuda
    • Alex Pr
      Alex Pr
    zachary.king
    Skilled Expert
    Forum|alt.badge.img+16
    • zachary.king
    • Skilled Expert
    • 951 replies
    • Answer
    • February 19, 2024

    Hello @Garuda, complex automations can be frustrating in freshservice. @ekrasner has a great idea to build them out further. Thankfully workflow automators are getting some enhancements mid-term this year. Including the ability to loop, and build workflow “components” that will be reusable throughout the workflow. Fingers crossed, they come sooner rather than later.

    - Zach / ITOps Supervisor - ITSM
    PatrickMurphy
    Kamakshi V
    2 people like this
    • PatrickMurphy
      PatrickMurphy
    • Kamakshi V
      Kamakshi V
    G
    Community Debut
    Forum|alt.badge.img
    • Garuda
    • Author
    • Community Debut
    • 1 reply
    • February 20, 2024

    @ekrasner Thanks for the idea.  This definitely sounds like the way to go.

    I assume you are running the powershell node on an Orchestration server?

    ekrasner
    Community Debut
    Forum|alt.badge.img+2
    • ekrasner
    • Community Debut
    • 24 replies
    • February 20, 2024
    Garuda wrote:

    @ekrasner Thanks for the idea.  This definitely sounds like the way to go.

    I assume you are running the powershell node on an Orchestration server?

    That is correct.  Just so it is understood. The reason I use the PowerShell node and not just an action in the workflow to set the status is that in doing just the action, it doesn’t see that as an update to the ticket and the subsequent workflow will not be initiated. Using the PS node, the system sees that as an update to the ticket

    zachary.king
    M
    2 people like this
    • zachary.king
      zachary.king
    • M
      MDavies
    JoshuaGessaro
    Community Debut
    Forum|alt.badge.img
    ekrasner wrote:
    Garuda wrote:

    @ekrasner Thanks for the idea.  This definitely sounds like the way to go.

    I assume you are running the powershell node on an Orchestration server?

    That is correct.  Just so it is understood. The reason I use the PowerShell node and not just an action in the workflow to set the status is that in doing just the action, it doesn’t see that as an update to the ticket and the subsequent workflow will not be initiated. Using the PS node, the system sees that as an update to the ticket

     

     

    But how do you daisy chain 5 of them together?
    The second one picks up the status change each time and the subsequent workflows won’t run.

    What am I missing?

    M
    Community Debut
    • mattdurant
    • Community Debut
    • 4 replies
    • January 7, 2025
    zachary.king wrote:

    Hello @Garuda, complex automations can be frustrating in freshservice. @ekrasner has a great idea to build them out further. Thankfully workflow automators are getting some enhancements mid-term this year. Including the ability to loop, and build workflow “components” that will be reusable throughout the workflow. Fingers crossed, they come sooner rather than later.

    Do you have a source for the information on workflow automators getting enhancements?  Obviously this hasn’t happened yet, but I can’t find any references to this being something that’s coming.  The workflow engine in Freshservice has been one of the most frustrating to work...

    C
    M
    M
    4 people like this
    • C
      Chris Meunier
    • M
      MaximeB
    • M
      MDavies
    • E
      ElPolloDiablo
    M
    Top Contributor
    Forum|alt.badge.img+1
    • MaximeB
    • Top Contributor
    • 7 replies
    • March 21, 2025
    zachary.king wrote:

    Hello @Garuda, complex automations can be frustrating in freshservice. @ekrasner has a great idea to build them out further. Thankfully workflow automators are getting some enhancements mid-term this year. Including the ability to loop, and build workflow “components” that will be reusable throughout the workflow. Fingers crossed, they come sooner rather than later.

    Hi, do you have a source, an update on that or something? 1 year later still nothing and workflow need more love from dev team :)

    M
    M
    2 people like this
    • M
      mattdurant
    • M
      MDavies
    Daniel Söderlund
    Skilled Expert
    Forum|alt.badge.img+14
    MaximeB wrote:
    zachary.king wrote:

    Hello @Garuda, complex automations can be frustrating in freshservice. @ekrasner has a great idea to build them out further. Thankfully workflow automators are getting some enhancements mid-term this year. Including the ability to loop, and build workflow “components” that will be reusable throughout the workflow. Fingers crossed, they come sooner rather than later.

    Hi, do you have a source, an update on that or something? 1 year later still nothing and workflow need more love from dev team :)

    The talked about it on the roadmap session.  

    Solution consultant @ synerity.eu, A new error is always a sign of progress!

    Reply


    Most helpful members this week

    Terms of UsePrivacy Notice