Valid PDII Dumps shared by ExamDiscuss.com for Helping Passing PDII Exam! ExamDiscuss.com now offer the newest PDII exam dumps, the ExamDiscuss.com PDII exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com PDII dumps with Test Engine here:
Universal Containers has an existing automation where a custom record called Account Plan is created upon an Account being marked as a Customer. Recently, a Workflow Rule was added so that whenever an Account is marked as a Customer, a 'Customer Since' date field is updated with today's date. Now, since the addition of the Workflow Rule, two Account Plan records are created whenever the Account is marked as a Customer. What might cause this to happen?
Correct Answer: C
Recent Comments (The most recent comments are at the top.)
Dan - May 15, 2023
C is correct. When a trigger fire again because of 'Re-evaluate Workflow Rules After Field Change',the static variable's value will be reset.
Ran - Apr 03, 2023
Answer is A. Workflow rule can't create a record. thus 'Re-evaluate Workflow Rules After Field Change' is pointless. My verdict was the existing automation is an apex trigger that creates custom record of Account Plan object. Since it's a workflow field update, it executes before update triggers and after update triggers, regardless of the record operation (insert or update), one more time (and only one more time),thus two Account Plan records were created. To prevent this, we could use a static variable to ensure that it only fires once in the same transaction.
Recent Comments (The most recent comments are at the top.)
C is correct. When a trigger fire again because of 'Re-evaluate Workflow Rules After Field Change',the static variable's value will be reset.
Answer is A.
Workflow rule can't create a record. thus 'Re-evaluate Workflow Rules After Field Change' is pointless.
My verdict was the existing automation is an apex trigger that creates custom record of Account Plan object.
Since it's a workflow field update, it executes before update triggers and after update triggers, regardless of the record operation (insert or update), one more time (and only one more time),thus two Account Plan records were created.
To prevent this, we could use a static variable to ensure that it only fires once in the same transaction.