Process Builder is a way of automating business processes. It is an upgraded version of the Workflow Rule. Whenever a user creates a process, the system automatically creates a Visual Workflow – and a Flow Trigger (which is now deprecated) – to call the Flow. Creation of the Flow happens behind the scenes; and therefore, a user does not need to interact with these ‘shadow’ (behind the scenes) Flows. Process Builder is a powerful tool for system administrators and developers to implement business processes without writing code. However, with great power comes great responsibility – If a user starts creating a new process for each requirement – or creating processes without understanding Salesforce limitations – then, a user may encounter many issues, either in future or, during testing/deployment phase.
In my last post Getting Started with Process Builder – Part 64 (How to fix MIXED_DML_OPERATION error), I discussed how to solve Mixed Data Manipulation Language (DML) Operation Error by using Time-dependent/Scheduled action. The Time-Dependent/Scheduled action separates DML operations, on Setup and non-Setup Objects, in the same Process, and, thereby, avoids incurring a Mixed DML operation error.
This article goes one step further; it discusses another common error – ALL_OR_NONE_OPERATION_ROLLED_BACK Error. The article shows – (1) why errors could occur; (2) how to identify errors (by using a debug log); and, finally, (3) how to solve the problem.
Business Use case
Donna Serdula is working as a System administrator at Universal Containers. They just implemented Quotation Management in Salesforce. Serdula has a requirement from her manager that, as soon as an Opportunity Stage is updated to Closed Lost then auto update related quotes status to Denied.
What is ALL_OR_NONE_OPERATION_ROLLED_BACK Error?