You are setting up and testing a workflow with approval hierarchy in Dynamics 365 Business Central.
In Approval User Setup, you configure the following users:
You create and enable an approval workflow. You configure the workflow to use the approver limit type Approver Chain.
To test the workflow, User1 creates a purchase order for $1,100 and runs the Send Approval Request function.
You need to identify the actions that occur when the workflow runs.
Which set of actions occurs?
User1 has an approval limit of $500, and the purchase order is for $1,100. Since the workflow is configured to use the Approver Chain, the request will be routed through the hierarchy of users until it reaches a user with a sufficient approval limit to approve the amount. User2 has an approval limit of $1,000, which is not sufficient to approve the $1,100 purchase order. Therefore, the request will be escalated to User3, who has an approval limit of $5,000. However, in an Approver Chain, the request still routes through the next user in the chain even if they can't approve the full amount. Thus, User2 will receive the approval request first, followed by User3. Once both User2 and User3 approve the request, the purchase order will be released.
the correct answer is C.
How it can be C? Approval Limit of User 2 is $1000. and Purchase Order created with the amount of $1100. I have tried the same setup mentioned here and there isn't a correct answer for this question.
The approver limit type is Approver Chain. By definition : this option creates approval request entries on all users on the approval hierarchy up to and including the first qualified approver. This will include the approvers which amount of the document requested is beyond their approval limit. This page explains approver limit types perfectly : https://ebs.com.au/blog/how-approver-limit-type-works-for-purchase-order-workflows-in-microsoft-dynamics-365
The approver limit type is Approver Chain. By definition : this option creates approval request entries on all users on the approval hierarchy up to and including the first qualified approver. This will include the approvers which amount of the document requested is beyond their approval limit. This page explains approver limit types perfectly : https://ebs.com.au/blog/how-approver-limit-type-works-for-purchase-order-workflows-in-microsoft-dynamics-365
The question states that the workflow is configured using Approver Chain. This rules out answer A. Answer A would be correct if the workflow was configured using Direct Approver. Answer B is describing 'First Qualified Approver' and I rule out Answer E because it goes straight to User3. It cannot be Answer D because User1 submits the PO for approval so User1 is not going to receive an approval request.
I have tried this exact scenario in CRONUS and result is A
For you to have got the result as A, you must've had your 'Approver Limit Type' in the Workflow set to Direct Approver instead of Approver Chain.
User 1 raises the request, so won't go to them for approval. Should go to 2, then 3.
Hi Guys, I see many confusion here but as per scenario when approval workflow is in place then it will ignore the direct approver and follow the hierarchy described. Therefore if the amount is greater than 1100 then approval request will go to user 3 and will get approved since user 3 has approval limit up to 5000 then it will never require to reach to user 4. so the right answer can be B as the first and final qualified approver. or correct answer should be C following the hierarchy and change status to released without sending the request to user4.
the correct answer is E reason: we need to follow the chain. user 2 has the allowance to confirm 1000 USD the amount that needs to be confirmed is 1100 USD hence he will not be asked as he cannot confirm anyways. user 3 is has rights to confirm and once he did the next person is user 4 that needs to confirm. The reason that it doesnt end with User 3 is the same reason why it doesnt jump to user 4 for confirmation. the confirmation is set to the chain. Hence First 3 needs to confirm and as 4 needs to confirm anything 1 did 4 needs to confirm after that.
Approver Chain – This option creates approval request entries on all users on the approval hierarchy up to and including the first qualified approver. This will include the approvers which amount of the document requested is beyond their approval limit. With the above setup, below will be the approval request entries that will be created: Order Amount Approval Request Entries Notes Approver ID Status < 500 User 1 Approved The Order will be automatically released > 500 and < 1000 User 1 Approved Only User 2 will approve. Order will be released once approved. User 2 Open > 1000 User 1 Approved User 2 will still get an approval request regardless of the Approver limit and will go to User 3 as the last approver. Once User 3 approves, the order will be released. User 2 Open User 3 Created
Bit complicated to understand how they answer option E
I've in my system the result is A
What I understand, User 1 requests. $1,100 User 2 will still get an approval request regardless of the Approver limit and will go to User 3 as the last approver. Once User 3 approves, the order will be released. So it should be C
the correct ans is C
Approver Chain, so C is correct
I have tried this exact scenario in CRONUS and the result is different. Either the question is wrong/unclear or the answer is wrong. The question states that User 1's approver is User 4, which does not have an approval limit (did NOT state it is with unlimited approval) . It didn't state that User 1, 2, and 3 are linked in anyway even though their approval limits appear to be in hierarchical structure. This setup actually errored out - "No qualified approver was found". If User 4 is set up with unlimited approval, then the answer is A because it is the only user that is linked to User 1 where as User 2 and 3 are not, hence they stay outside of the approval chain when related to User 1's request.
Here is the description of the scenario for Approver chain Description Approver Chain - Specifies that approval request entries are created for all the requester’s approvers, up to and including the first qualified approver. This is typically used to support a scenario where the approval must go up the hierarchy to find someone with sufficient spending limit to sign off. In this scenario user 1 creates and order is approved, user 2 is open awaiting approval and user 3 is created until user 2 approves, they then approve and the document is released.
Option C
Neither the question, nor the answer are OK. The question is missing the Approver Type condition :) -> Because Approver Limit Type = Approver Chain is always defined per certain Approver Type condition in the workflow -> that can either Salesperson/Purchaser or Approver... So no time to waist looking for the correct answer ;)
But for Approver Chain, no matter Salesperson/Purchaser or Approver, the approval workflow will follow the Amount chain. IMHO, it is C.
There isn't a correct anwer. User 3 should be the direct approver from user 4.And then user 4 should first approve and user 3 next. If it follows the chain it follows the flow of direct approvers until it finds a "qualified" approver. Each direct approver until then must approve.
This came in exam. Still not sure of an answer.
User 2 only 1000, and purcharse is 1100.
It´s A
The question information is incomplete. The Approver Type and not the Approver Limit Type determines who is notified first about the approval. Approver Type of Approver means that that User4 will be notified. Approver Type of Salesperson/Purchaser means that the user matching the Salesperson/Purchaser of the document to be approved will be notified first. The approver chain requires Approver IDs to be set not just limits. Since we don't have any information about Approver Type or other Approver IDs other than User4 is the approver of User1 we have to assume A is the correct answer.
Esla C
correct
the correct answer is C.
la c es correcta
Answer is E. Firstly,based on the amt of PO it will need User3's approval. Secondly, with the approval hierarchy set once User3 done it will gose to User4 who is considered as the final approver.
The Correct Answer is A, as user 4 is the direct approver for user1 and user1 is creating the PO so it will direct goto user4 for approval and user4 has also no limit.
Right the "C" answer
Answer is C - Because it is setup with Approver Chain This option creates approval request entries on all users on the approval hierarchy up to and including the first qualified approver. This will include the approvers which amount of the document requested is beyond their approval limit. https://ebs.com.au/blog/how-approver-limit-type-works-for-purchase-order-workflows-in-microsoft-dynamics-365
User2 doesn't even meet the requirement due to the amount of $1100. So it goes to User3.
I choose B, according to this: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/424756/workflow-approver-limit-type Approver Limit Type = Approver Chain: Document amount < 100: The request is automatically approved. Document amount between 100 and 500: A request is sent to USER 2. Document amount over 500: A request is sent to both USER 2 and USER 3.
I now think I was wrong. Correct is B
Once user3 approves then the order is released
The correct answer is A, I have tested it in Business Central. The "Approval Chain" works first with the "Approval ID".
Answer should be A, In approver chain it goes to the next approver in hierarchy, here User 4 is in the next approver, it seems like a direct approver setup due to the scenario which is given but answer is A.
THE CORRECT ANSWER is C Setting the Approver Limit Type to Approver Chain routes approval requests to all approvers in the hierarchy even if the request is above their approval limit. That’s also the reason that User 4 doesn’t get an approval request, even if he’s the direct approver. You would have to set the Approver Limit Type to Direct Approver instead of Approver Chain.
La respuesta correcta es A porque menciona el primer aprobador y ese es el usuario 4 https://learn.microsoft.com/es-mx/training/modules/create-workflows/2-manual-creation
correct
Correct answer is E
C is the correct Answer
Read the User4 Direct Approval Comment. Not sure why this is so hard
Why would it be c, with the comment ofuser 4 why would it go through all the other users if the only one wh can oapprove are 3 and 4
If user 4 was not direct approver for user 1. Answer C would be correct.
User 2 only has an approval limit of $1000 and the request is $1,100. User 2 can't approve it so C isn't correct.
🔹 Key Factors to Consider Approval Chain Behavior In Approval Chains, requests flow step by step through the hierarchy until an approver with sufficient approval limit is found. User2 ($1,000 limit) is next in line after User1 ($500 limit). Since User2 cannot approve the $1,100 order, it must be forwarded to User3 ($5,000 limit). User3 can approve it directly, meaning it does NOT need to go to User4. Role of User4 User4 is only a direct approver for User1. However, the system only escalates to a direct approver if needed (i.e., if no one in the chain can approve). Since User3 has a sufficient approval limit, the request stops there, and User4 does not need to approve.
So the correct sequence of actions would be: - User3 receives the approval request because their limit accommodates the $1,100 amount. - Once User3 approves the request, the purchase order is released.