Q: 2
You want the Timezone field to be pre-populated when the location record is changed in Job Info.
How do you configure this?
Options
Discussion
My pick: C, has come up in plenty of practice sets, always linked to the trigger field for rule execution. The business rule should fire when Location gets updated in Job Info, not when Timezone changes. Seen a similar setup in a mock test, C was spot on. Pretty sure that's the right config here, but let me know if anyone's had it work differently.
C tbh, since the rule needs to fire when Location gets updated in Job Info. Assigning the rule to Timezone's onChange (like in D) wouldn't work for auto-filling on location change. Pretty sure that's how SAP expects it-anyone seen a working D?
But if the field to watch is Location and not Timezone, wouldn't D be a trap?
C/D? I get why D looks tempting, since it's about Timezone, but the key is "when Location record is changed". Trigger should be on Location field in Job Info (option C), not the Timezone field. Pretty sure that's what SAP expects. Anyone see differently?
Makes sense that it's C since the update should happen when Location changes, not when Timezone is touched. Rule has to trigger on Location's onChange. Pretty sure that's how SAP config expects it-unless I'm missing an edge case here.
C all day for this. The rule should fire when Location changes in Job Info, not when the Timezone field changes. That way you pull the right timezone based on the new location automatically. Pretty sure that's how SAP configs want it, but open if someone actually got D to work.
My vote is C is right. The rule should fire when the Location field changes, not when Timezone changes. D is a common trap here since it's about the Timezone field, but C matches SAP config logic from similar questions I've seen. Agree?
Option D seems right to me because the rule should fire when Timezone field is changed in Job Information, not Location. So I'd pick base object as Job Information and trigger on Timezone onChange. Might be missing something but that's my take.
Probably C, this matches a similar question from a practice exam where the trigger was set on the Location field change.
Yeah, C makes sense here. To pre-populate Timezone when Location changes, you want the rule on Job Information base object and have it trigger onChange of the Location field. That way, any time the location updates, the rule can grab and set the correct timezone value. I'm pretty certain on this one but nudge me if I missed anything!
Be respectful. No spam.
