I need to setup eReq Workflow for a couple of clients. I am looking for tips, tricks or best practices. Any help will be appreciated.
*This post is locked for comments
I need to setup eReq Workflow for a couple of clients. I am looking for tips, tricks or best practices. Any help will be appreciated.
*This post is locked for comments
Hi Brenda,
I'm pretty sure I posted a reply yesterday on this forum... but somehow it never made it's way to this thread..
Yes the normal workflow process in GP makes usage of the Active Directory hierarchy.. so depending on your company setup, this may not fit your needs for GP approvals..
You can create your own approval rules in WF 2.0, but for a system like eReq with multiple departments and approval levels, it will add even more complexity.. And no, as far as I know you can't use the Organizational Tree from GP for that purpose... which would be nice BTW, since the logic of the department structure is mostly already built there.
I have not played with the WF 2.0 for procurement / requisitions, as we use an external system, but we tested it briefly for the PTE Time & Expenses.. it's much less complex, since there is not necessarily the various levels that come into play and AD hierarchy would do the job.
when you refer to "Normally the workflow approval process for WF 2.0 is driven by the Active Directory (AD) hierarchy... but you can chose to create your own in GP" did you mean create steps for the hierarchy?? or is there some way with in GP?? Possibly using the Organizational tree??
Hi Brenda,
There are plenty of resources out there... just doing a quick search about 'dynamics GP workflow 2.0' returns a lot of good blog entries and YouTube videos:
www.resgroup.com/.../microsoft-dynamics-gp-workflow-2-0-setup-is-easy-as-1-2-3
www.erpsoftwareblog.com/.../microsoft-dynamics-gp-workflow-2-0-configuration-tutorial
This video was published by Microsoft and goes extensively over the setup of WF2.0:
As a general recommendation, make sure your e-mail settings are setup properly as it plays a vital role in the WF communication..
Hope this helps.
We just set it up not too long ago. We had some icks and pains, but so far the process is feasible.
Depending on your requirements, you may want to look at GP2015 R2, as it has some added features for workflows, like file attachments sent via emails in workflows.
Enable the Encumbrance module as soon as possible, as PO Commitments do not work as well. Microsoft has stated to us that the new Purchase Request module was built to work with Encumbrance, not PO Commitments. We are currently looking at doing the transition.
Email Actions is a thing of beauty. Being able to approve requests via email saves on licences within GP, but also enables accessibility, which is a biggie. It's nice when a manager can approve a request on the road, instead of having to login to GP and approve the request. It's based on Active Directory, so you need to setup the hierarchy (populate the Manager field in AD).
You can customize emails being sent for every action in the workflow (Rejection, Approval, Delegation, Completion, Final Approve, etc...).
Workflow delegation allows for proper redirection of requests, in case someone is gone on vacation for a while.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,235 Most Valuable Professional
nmaenpaa 101,156