Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

How to Create Branching Workflow?

Posted on by 135

Hello,

We are new to Microsoft Dynamics GP and are having a very difficult time configuring our Sharepoint Workflows to match our current processes.  I have found a screenshot from a BKD Technologies webinar that is very similar to what we need to create, but does not provide the "how-to":

We have several departments in which we need to create a branching purchase order workflow.  E.g. if someone from Finance creates a PO, it needs to go to the Finance Director for approval, but if someone from Engineering creates a PO, it needs to go to the City Engineer for approval, and if someone from the Fire Department creates a PO, it needs to go to the Fire Chief for approval, etc, etc.  All of this needs to be setup within one workflow, because we cannot activate more than one Puchase Order workflow type at a time.  Additionally, all of these approvals need to be for POs between a specific dollar amount.

We have looked at the Workflow Administrator's Guide and other resources, but cannot find the information to do what we need.

Can someone please provide assistance asap?  Thanks in advance.

Jeff

 

*This post is locked for comments

  • Jeff Pelech Profile Picture
    Jeff Pelech 135 on at
    Re: How to Create Branching Workflow?

    U3817.capital-workflow-redacted.jpg"/resized-image.ashx/__size/550x0/__key/CommunityServer-Discussions-Components-Files/32/5543.WH1-buyer-exclusion-redacted.png" border="0" />

     

    Also, here is an example of a Capital approval workflow I have made up for one Site ID only but multiple Buyer IDs.  Is there an easier way to do this?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: How to Create Branching Workflow?

    Hi Jeff,

    Sounds like your work flow in almost place, which is great news…and yes they can be hard to configure.

    What if you added a step to require approval when PO amount exceeds some exorbitant threshold for no-inventory items?  (Like 5,000,000,000) Then others would fall below that threshold and pass through the workflow without approval?

    Seems like it might work?

    Donnette

  • Jeff Pelech Profile Picture
    Jeff Pelech 135 on at
    Re: How to Create Branching Workflow?

    Thanks everyone for your assistance.  I think I am almost there, but I keep reading about how tricky it is to create such a workflow.  Here is a basic idea of our internal desired workflow.  I would consider the green boxes step 1 and the purple boxes step 2.  One additional thing is that everything in step 2 is also dependent and filters upon the Buyer ID.  One thing that keeps frustrating me is how to pass step 1 through to step 2. 

     

    I have successfully create eight 1st steps similar to this:

    If Buyer ID = xxxxxxxx and Site ID = CAPITAL then xxxxxx is Approver (based upon different departments)

    However, I need a way to say: If Buyer ID = xxxxxxx and Site ID = NON INV then no approval needed, similar to what I show below in the image.  I realize that Sharepoint does not have a "no approval step", but that is what I need, as the Site ID of NON INV and WH1 and PROGRAMS all require filtering based upon Buyer ID.  Otherwise, any Buyer ID can create a NON INV purchase order without a dollar value attached.  There must be something essential that I am just not grasping here.

     

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: How to Create Branching Workflow?

    Jeff,

    We we rolled out a new solution for GP workflow and as a result have developed several templates (60) this year for typical workflow scenarios.  this has caused us to develop a strong background around developing workflows.  I can probably help you around your workflows a bit.

    Terry

    tcarlton@integrity-data.com

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: How to Create Branching Workflow?

    Hi Jeff,

    I had a similar GP workflow .I restricted it using Buyer ID's. Example: If BuyerID = XXX then approver = XXX.  I also placed limits on who could approve and added steps to escalate approval when dollar amounts exceed limits.  It was 1 WF and it worked great...it just took time to configure the different approval scenarios.

    GP's manuals only covers the basics of what the workflow can do.

    If you want to send me a screen shot(s) of your workflow I can help you with the steps.

    Donnette

    dspencer@headwaters.com

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans