The following are some noteworthy points regarding Process Builder:
- A process's API name must be less than, or equal to, 77 characters, and it's always associated with a single object.
- Using Process Builder, you can't delete records. If you want to do that, you have to use Flow with Process Builder.
- To set the
Textdata field to blank, you can use{!$GlobalConstant.EmptyString}.
- By default, the process owner will receive an email from Salesforce. If the process fails at runtime, or if any fault occurs, the error or warning messages might refer to a Flow instead of a process. If you want to notify other users and your IT department, use the Apex Exception Email, under the Salesforce setup.
- The process follows all of the governor limits that apply to Apex.
- You can have a maximum of 50 active rules and processes on any object. Rules include Workflow Rules, Escalation Rules, Assignment Rules, and Auto-Assignment Rules.
- Process actions are executed in the same order in which they appear in the Process Builder.
- You can't delete an active process; first, you have to deactivate it. Once you have deactivated a process, you can immediately delete it.
- If a custom field is referenced in a process/Flow, you can't delete that field.
- Before you change a custom field’s type or name, make sure that it isn’t referenced in a process that would be invalidated by the change.
- An immediate action on a record update obeys validation rules.
- A scheduled action on a record update skips validation rules.
- If any of the actions fail, the entire transaction fails and an error message is displayed.
- File type custom fields aren’t supported in Process Builder.
- External objects and deprecated custom objects aren’t supported in Process Builder.
- If a single action group includes multiple
Update Recordsactions that apply different values to the same field, then the last action’s value is used. - The total number of process criteria nodes that are evaluated and actions that are executed at runtime is 2,000.