An administrator needs to build an autolaunched flow to update the resolution status of multiple high-priority Support Cases associated with an Account. Which two design configurations should the administrator implement to efficiently handle this logic while adhering to Salesforce governor limits?
- Execute a single Get Records element before the Loop to retrieve all matching Support Cases in a single query.Cevap
- Add updated Case records to a Record Collection variable inside the Loop and execute a single Update Records element after the Loop.Cevap
- CPlace an Update Records element directly inside the Loop element to commit changes immediately for each individual Case record.
- DConfigure a Roll-up Summary element inside the Loop to calculate total open cases across lookup-related objects.
Cevap
The administrator should execute a single Get Records element before entering the Loop, collect modified records into a Record Collection variable during iteration, and execute a single Update Records element after exiting the Loop.
Bulkifying flows requires keeping database operations (Get Records, Create Records, Update Records, Delete Records) outside of Loop elements. Fetching records prior to the loop and updating a collection after the loop completes guarantees the transaction stays well within governor limits.
Adım Adım Çözüm
Anahtar Kavram
Flow Bulkification and Loop Design Patterns