AX 2012 Workflow - Escalation using Managerial Hierarchy

(0) Share

Report

Posted on by Didier Jean Pierre

227

Hi,

I have set up escalation using the Managerial Hierarchy. By so doing, my objective was to have the same users in the approval process (also using the Managerial Hierarchy) to intervene whenever the an approver does not approve within the set time limits.

4744.Image-1.png

My issue is that instead of using the Managerial Hierarchy to escalate, the system is escalating to the last user in the Managerial Hierarchy (specified in the exit criteria).

Thanks to advise.

Regards

Didier

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Fredrik Sætre 12,644 on at

Like (0)

Report

Your escalation happens through the hierarchy if the worker has a General Manager.

All positions have general managers except the top record in the hierarchy. That is why this happens I guess.

Was this reply helpful? Yes No
Didier Jean Pierre 227 on at

Like (0)

Report

Though all workers have the same General Manager (as the last approval and escalation level), the task should go through at least one approver before being assigned to the General manager

Was this reply helpful? Yes No
Jonathan Halland 11,310 on at

Like (1)

Report

Hi Didier. You have specified a stop condition of general manager, this means workflow will loop through the hierarchy until it finds somebody who is the general manager and "stop" there and assign it to that person.

Was this reply helpful? Yes No
Didier Jean Pierre 227 on at

Like (0)

Report

Hi. Thanks for your input. However, don't I require a stop condition ?

Actually, I cannot use Line Manager Level as it varies from a worker to another. For some workers there is only 1 level while for others there may be up to 4 levels.

I, in fact, need something like the Assign to all users retrieved (in hierarchy options). How do I do that in Escalation ?

Was this reply helpful? Yes No
Suggested answer

Jonathan Halland 11,310 on at

Like (0)

Report

Hi Didier.

You logically do require a stop condition for hierarchies.

Unfortunately AX doesn't really provide an easy solution to your problem. We've had a similar requirement a couple of times and have ended up using a workaround whereby you need to setup 4 levels of escalation each with a stop condition along the lines of:

if heirachy.level = 1 or role = "General Manager"

if heirachy.level = 2 or role = "General Manager"

if heirachy.level = 3 or role = "General Manager"

if heirachy.level = 4 or role = "General Manager"

it is really not a desirable solution, but so far has been the only workaround I have found. This solution does have a drawback. If the GM is the next level it will be reassigned back to the GM 3 times before achieving "final action"

Was this reply helpful? Yes No

Community site session details

AX 2012 Workflow - Escalation using Managerial Hierarchy

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates

Community site session details

AX 2012 Workflow - Escalation using Managerial Hierarchy

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates