2

There is not much documentation yet surrounding the release of Scheduled Flows (Winter 20).

This article (https://releasenotes.docs.salesforce.com/en-us/winter20/release-notes/rn_forcecom_flow_fbuilder_start.htm) states that "When your flow starts, a flow interview runs for each record that matches your filter—no looping required. The matching record is stored in the $Record global variable, so you can reference the variable or its fields throughout your flow."

So my question is this. Does anyone know how this relates to bulification? If it runs the interview via the $Record global variable, then do I assume that I don't bulkify my update to a set of records, but rather have an Update Record element in the flow for every record, and then assume that the schedule automatically wraps these up into a single Update?

Also, do I assume that the $Record global has access to all fields on that object during the interview? Since I am not performing a "Get" and therefore are not able to specify the fields I need to complete my operations?

  • 1
    this question could easily be answered by an experiment by using a scheduled flow that operates on 2+ recs and updates them (where the recs have a trigger) - the debug log will clearly indicate whether they are bulkified – cropredy Nov 12 at 22:50
1

A user from the Process Automation group came back to me with this:

1Q: Yes. Design the flow as if you are working on a single record. And scheduled flow does the bulkification for you.

2Q: Yes. You have access to all the fields on the record.

3Q: Scheduled Flow is run as the "Automated Process" user. This is different from Default Workflow User

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.