Contents
What Salesforce actions can be done with process builder but not with workflow?
In addition to everything a workflow can do (except for sending outbound messages), you can:
- Create a record (not just Tasks!)
- Update related records.
- Launch a Quick Action.
- Post to Chatter.
- Launch a Flow.
- Call Apex code.
- Submit for approval.
- Invoke another process.
Which two behaviors may occur if workflow rules are evaluated after a field change by a field update?
Workflow rules trigger validation rules on field updates. D. Cross-object workflow rules result in re-evaluation after field change.
How are workflow rules used in process builder?
Workflow rules would let you update an “invisible” field to the user. This was great for lots of data validation and controls. With Process Builder (and Visual Workflow) the field must be visible and editable by the user in order for the tool to update the field.
Can a workflow rule update invalidate a Validation rule?
Workflow rule field updates (and hence by association, Approval Process field updates) don’t fire Validation Rules. Because updates to records based on workflow rules don’t trigger validation rules, workflow rules can invalidate previously valid fields.
Can a parent record be updated in process builder?
For updating related records, Process Builder can update any field on any related record, where Workflow can only update some fields on a parent record of a Master-Detail relationship. Process Builder can also update multiple related records in a situation when all of a record’s child records need the same update.
When does a field update happen in process builder?
If you are doing a field update inside of a workflow that field update does not happen until after all the workflow criterias and process builder actions take place. What you have to be careful about is having the process builder rely on a field being updated by a workflow inside of that same execution context.