#DF21 Here are the announcements that I could catch from Dreamforce ’21. Enjoy 🙂
In today’s digital economy, it is more important than ever for businesses to ensure that their customers trust them. And one of the core pillars of establishing this trust is to ensure that businesses are handling their customers data with utmost care.
On one side, businesses want to collect as much data about their customers as they can to ensure that they can wow their customers by providing a personalized, tailor-made experience and on the other side, they also need to ensure that this data is not misused or abused.
Implementing Salesforce or already using Salesforce? Do you have a well-defined development & release management process to ensure that you are doing it the right way, using all the proper tools & technologies, automating processes where it can and should be automated?
Do you have a proper process to ensure that you are building an optimal solution on Salesforce, leveraging on the platform’s features and capabilities, not incurring technical debt and not cutting corners on best practices?
If your Flow includes a DML element such as Create, Update or Delete records, or a Submit for Approval core action, then there is a possibility that it might fail. For example, a create or update may fail if it does not pass the validation rule. And when the flow fails, Salesforce displays a standard message in red text that reads “An unhandled fault has occurred in this flow”. But with an error message like this, users will have no clue of what happened and if they did anything wrong.
A better option is to use something called ‘Fault’ path in Flow. Fault Path is also called Fault Connector or Fault Line. With Fault path, you can display a more meaningful message and guide users on what to do. To create a fault path, create a screen element with useful message and connect it to the DML element.
How do you delete or deactivate the apex classes / triggers on your Salesforce Production Org? Unfortunately, it is not as simple as going to the Apex class and hitting the delete button or unchecking the ‘Active’ checkbox.
For deleting or disabling the code, you can take one of the following two routes: