When a user marks the InspectionComplete field and clicks Update, the user making the update and the date/time of the update need to be recorded in separate fields. Which approach will accomplish this?
A.
Create a Validation Rule that checks for a change in the InspectionComplete field...
B.
Enable Reflection on the InspectionComplete widget...
C.
Create aPreupdate Rulethat checks for a change in the InspectionComplete field and updates the UpdatedBy and UpdatedDateTime fields
D.
Create an EventFired Rule that would be triggered...
In the GuidewireGosu Rulesframework,Preupdate rulesare the designated location for performing last-minute entity modifications before they are committed to the database. According to theInsuranceSuite Developer Fundamentalsguide, Preupdate rules are ideal for audit-trailing or setting "shadow fields" that depend on the state of other fields.
When the user clicks "Update," the bundle enters the commit phase. The Preupdate ruleset is executed while the transaction is still "in-flight." By checking if the InspectionComplete field is "changed" (using the isFieldChanged() method), the rule can programmatically set the user and timestamp. This ensures the data is captured regardless of which PCF page or API call triggered the update. Options likeValidation Rules(A) are meant for error checking, not data assignment.EventFired Rules(D) occurafterthe database commit, meaning any changes made there would require a whole new bundle and transaction, which is highly inefficient and creates infinite loops.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit