Finance | Project Operations, Human Resources, ...

Workflow - Approval Based on Originator

(0) Share

Report

Posted on by BoGLG

Is it possible for Workflow to accommodate the following scenario for a GL batch approval. There are no dollar limits involved. It is simply based on who submits as follows:

User or Active Directory Group 1 submits batch - Get approved by Manager 1

User or Active Directory Group 2 submits batch - Get approved by Manager 2

User or Active Directory Group 3 submits batch - Get approved by Manager 3

etc. etc,

I hope I described that adequately. The approver is determined by who originates and nothing else.

Thanks!

Categories:

Microsoft Dynamics GP

All responses (7)

Answers (0)

Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: Workflow - Approval Based on Originator

I apologize, I was thinking out loud there.......

What I meant to say, the only way to have workflows approved by the originator's manager or skip-level manager, would be the way I mentioned using the 'Assign To' field in the workflow step(s), you could choose the following:

Selection Type: Hierarchy

Start From: Workflow Originator

Assign To: Direct Manager (or skip-level manager or number of levels of manager)

This should look at who the originator of the GL batch is, i.e. the Windows user account logged in as while submitting the workflow for approval, then assign it to the direct manager, skip level manager or any number of manager level, based on your setup.

For the workflow approval conditions, you could leave that as requiring approval in every case, or you could add further conditions there if you only wanted specific GL batches to be approved.

Hopefully that is clearer, but let me know if you have any questions, if not.

Thanks,
BoGLG 75 on at

Like (0)

Report

RE: Workflow - Approval Based on Originator

Hi Derek!

You answered my original question as follows:

"By default, there isn't a way to do this. While we can setup a workflow so that it would be routed to a manager based on the user or group that submits it, in this case a GL batch, for approval."

What did you mean when you say - While we can setup a workflow so that it would be routed to a manager based on the user or group that submits it, in this case a GL batch, for approval?

Do you mean that it can be done? or did you mean to say can't??

Thank You!
Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: Workflow - Approval Based on Originator

It is actually looking in Active Directory, at the same time it validates the originator. There is a manager field in the user properties for the Active Directory Users and you'd want to put their direct manager there.

If you were looking to use skip level managers, then you'd want to make sure that the originator's direct manager had their manager specified in Active Directory the same way, and so on.
BoGLG 75 on at

Like (0)

Report

RE: Workflow - Approval Based on Originator

Meaning like when you click on a co-worker's email address in Outlook and it shows their Manager and who reports to them. Is that what it looks at?
BoGLG 75 on at

Like (0)

Report

RE: Workflow - Approval Based on Originator

Meaning like when you click on a co-workers email address in Outlook and it shows their manager and people who report to them . Is that what it looks at?
BoGLG 75 on at

Like (0)

Report

RE: Workflow - Approval Based on Originator

Hi Derek. In this scenario, what is GP workflow looking at to determine that originator's direct manager. Is it looking at active directory?
Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: Workflow - Approval Based on Originator

By default, there isn't a way to do this. While we can setup a workflow so that it would be routed to a manager based on the user or group that submits it, in this case a GL batch, for approval.

I'm wondering if you couldn't setup the workflow so, under 'Assign To' for the workflow step, you could choose the following:

Selection Type: Hierarchy

Start From: Workflow Originator

Assign To: Direct Manager (or skip-level manager or number of levels of manager)

Theoretically, this should look at who the originator of the GL batch is, that is submitting it for approval, then assign it to the direct manager, skip level manager or any number of manager level.

Otherwise, there isn't a way to really do it through the workflow step conditions, as we would need the Windows user or group in a specific table in Dynamics GP, which we don't have short of what Workflow puts in after it is submitted. I know customers frequently make use of the SY00500 table, but that is more the user id from Dynamics GP, and not the actual Windows user or group.

Thanks,