Todd Newman - 7 months ago
The workaround suggested by salesforce (10 years ago!) is not a good workaround. Take my recent use case: I want to default the opportunity name for a specific record type. Since it's a required field I can't remove it from the layout. The workflow/trigger value won't be visible to the user prior to save. So the user will be forced to enter a value which is then overwritten. That's a confusing experience.
Lenn Goethals - 9 months ago
A good example is contract status. We don't want users to be obligated to fill in the status themselves since this is determined based on, indeed, a workflow. The status is however always mandatory so our users are obligated to pick a random value on creation. This is very user unfriendly!
Tony Kenny - 11 months ago
Same issue, and the workflow wont work as the record needs to save in order for the Field Update to fire.
In the end we used a validation rule to force the Sales team through the Stages. Not super elegant but its getting the job done for us till we find a better solution.