An administrator wrote a field update action for a workflow rule on a field that is hidden via Field-Level Security.
When the workflow rule triggers, what happens to the data in the hidden field?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
Workflow rules run whether or not the end user is able to see the field.
When a field update action is written for a workflow rule on a field that is hidden via Field-Level Security, the behavior depends on the context of the update.
If the update is triggered by a user action such as editing a record or clicking a button, the user will not be able to update the hidden field. This is because the Field-Level Security settings restrict the user's access to the field, and the update action will fail.
However, if the update is triggered by a time-based trigger such as a scheduled workflow rule or a time-dependent action, the update will succeed regardless of the Field-Level Security settings. This is because time-based triggers operate in a system context, which bypasses the Field-Level Security settings and updates the field regardless of whether it is hidden or not.
Finally, if the user has "Modify All Data" enabled in their profile, they will be able to update the hidden field regardless of the context of the update. This is because "Modify All Data" permission grants users unrestricted access to all records and fields, including those with Field-Level Security settings.
Therefore, the correct answer to the question is option B: "The field is updated, even though it is hidden" when the update is triggered by a time-based trigger.