LinkedIn

Salesforce Screen Flow - Roll Back Behavior

-

 Similar to Apex Roll Back, as part of Winter 22, Salesforce has introduced Flow Roll Back feature also. Let us see the transaction behavior when using roll Back along with Screen Flow.


1. Feature Details

As of now Roll Back feature is available only for Screen Flows. 

All pending operations in the current transaction will be rolled back on adding Roll Back element to a fault connector.

This is useful when we have a series of DML operations happening in a single transaction and ScreenFlow will try to combine all those into a single transaction

2. Use Case - Single Input Screen - Multiple DML 

I would like to develop a screen where you can create both Account and Contact together on a single screen. The flow looks like below:




The input screen looks like below:



And once you enter details in all fields and click on next, Below operations will be happening:


Below is the Transaction Behavior




3. Add failure to Contact Save

Now let us add a validation rule on Contact to make the email field mandatory:



Now try to submit the screen without entering the Email field. 


The behavior is as mentioned below:


4. How to Add Roll Back Behavior

Instead of the above flow, if the Contact creation got failed, we would like to rollback Account creation also. Let us see how this can be achieved by replacing the fault connector action with Roll Back behavior instead of a screen message.


Now try to create new data:



5. Transaction Behavior after adding Roll Back


Also in the debug you can notice that both account and contact save happening in the same transaction, and that is the reason Roll Back is a success here.


6. Use Case Modified -Multiple Input Screen  - Multiple DML

Now let us modify the screen flow to use 2 separate screens for entering Account and Contact Data:


Let us try to create new Account and Contact now without entering an email :


7. Transaction Behavior


8. Why Roll Back didn't happen?

If you check the debug log you can see that Account and Contact creation happened as 2 different transactions and Roll Back will happen to DML operations occurring in the same transaction

Account Debug:


Contact Debug:


This is because based on this documentation, a flow transaction is end when a screen element, local action and pause element is executed.

9. Summary

Based on the above analysis, Roll Back will be happening for DMLs which are part of the same transaction only. Even if we have multiple DMLs as part of the same screen flow, but they end up in different transactions, Roll Back will not be successful.

Comments

  1. Anonymous29 December 2021 at 17:10

    I wonder about how to see debug log about flow process. Could you let me know about it?

    ReplyDelete
  2. bhanu24 June 2022 at 00:01


    Thanks for sharing this information
    Mulesoft Training
    Mulesoft Online Training

    ReplyDelete
  3. bhanu27 September 2022 at 07:27

    Thank you for sharing very useful information.
    Mulesoft Online Course
    Mule ESB Training

    ReplyDelete
  4. Stel8 October 2022 at 19:49

    How do I go about when I reject an approval and want to go back to the previous picklist in my case. What are the steps in details if you don't mind me asking? Very great website and please keep the information coming.

    ReplyDelete
  5. Stel8 October 2022 at 19:53

    So I have 1 approval process and 1 flow that calls that approval process. Once the flow triggers, it emails the approval and the approval can email approve or reject. It works well when approves but when I reject I want it to go to the original picklist since it didn't get approve. My picklist are A, B, C, D. Approval is needed for A, and B. If A is rejected it should stay at A

    ReplyDelete
    Replies
    1. Meera R Nair9 October 2022 at 05:29

      Hi Stel,

      I think you need to have custom logic around this, since rollback behavior is supported only for screenflows. So you might need to store the previous picklist value in some other field, and once rejected, retrieve this and update back the picklist.

      Delete
    2. Stel10 October 2022 at 02:27

      Hi Meera, could you point me to some examples for references? Much appreciated!

      Delete
  6. Stel10 October 2022 at 11:43

    Hi Meera, I found this reference https://www.salesforcebolt.com/2020/10/get-prior-value-of-formula-field-in.html and it's using workflow but can it be done with flow to store the value?

    ReplyDelete
  7. AYAN2 January 2024 at 22:07

    This comment has been removed by the author.

    ReplyDelete
  8. AYAN2 January 2024 at 22:09

    Thanks for sharing this useful post.
    Clone Flows in Salesforce

    ReplyDelete

Post a Comment

Popular posts from this blog

Subscribing to Salesforce Platform Events using External Java Client - CometD

-
Image
Platform Events follow event based Architecture, where multiple subscribers can subscribe to a published event in real time manner.  Below diagram shows the basic Architecture of the event-based communication Model: Event - This is a change in state for a business process Event Message - Data about the event Producer - Publisher of the event Event Bus - A communication and storage service for published events Event Consumer - A subscriber to the channel Platform events can be subscribed internally and also externally Platfrom events  - Internal Subscription Below are some scenarios in which you can consume platform events internally: 1. When we need to execute functionalities asynchronously to save govornor limits 2. To build a proper exception logging framework - You can find more details here  How to subscribe Internally? we can see more details about this in a different blogpost. Platfrom events  - External Consumption Many Organizations are moving to event-based integration appr
Read more

Salesforce Security - Restriction Rules and Scoping Rules

-
Image
1. Overview Salesforce provides a very effective security model where we always start with the most restrictive access and then open up access using additional mechanisms like sharing rules, and manual sharing based on the requirements.   But there might be scenarios where we need to restrict access based on specific criteria. Salesforce recently introduced 2 approaches to support this requirement. Those are restriction rules and scoping rules. Let us see this in detail. 2. Restriction Rules - Overview Using restriction rules we can apply an additional level of filter on top of records to which a specific user is having access. 3. Scoping Rules - Overview Scoping rules help to filter the default records visible for a user based on specific criteria. But it is not preventing access to other records. 4. Compare Restriction Rules and Scoping Rules 5. Restriction Rule - Example Company ABC is having Job Applications getting created through their company portal and synched to Salesforce. T
Read more

How to develop reusable Invocable Apex methods for Flows

-
Image
 Salesforce is adding many new features and capabilities to Flows. But there are still some scenarios where you need to call apex methods from Flows to execute complex operations - when Flow is not capable of doing that or the performance will be low when you implement that using flows. Let us see how we can build reusable apex methods for Flows. For this let us consider 2 sample scenarios: Scenario 1 - Quick Create Account/Contact I want to build a screen, where the user can select the object needs to be created, and then create a record of that object by entering the required details. Also if the record creation is getting failed, I want to create an exception record with details. Solution Let us see how we can utilize Apex action for this. For this first let us create an Apex Invocable method, which can accept a list of wrapper class as shown below: You can see, this invocable method is accepting a List of wrapper class variables and also returning a list of wrapper class variables.
Read more