An organization requires an automated process when a custom object record, Project__c, is updated to a status of 'Cancelled'. The requirements specify: sending an email notification to the project manager, updating the status of all related child Project_Task__c records to 'Cancelled', and removing all associated temporary draft logs from the system. Which limitation of Process Builder must the Salesforce Administrator account for when designing this solution?
- Process Builder cannot natively delete records, so deleting the temporary draft logs requires calling a Flow or Apex action.Cevap
- BProcess Builder cannot update child records directly, so an Apex trigger must be written to update the related Project_Task__c records.
- CProcess Builder automatically executes DML operations inside loops when updating related records, leading to governor limit failures.
- DProcess Builder can only execute immediate actions on standard objects, requiring Workflow Rules to process custom objects.
Cevap
Process Builder cannot natively delete records, so deleting the temporary draft logs requires calling a Flow or Apex action.
Process Builder provides native actions for updating related records, creating records, sending email alerts, and submitting records for approval. However, it lacks a native 'Delete Records' action. To delete records, an administrator must either invoke an autolaunched Flow or call Apex code from the process.
Adım Adım Çözüm
Anahtar Kavram
Process Builder Native Capabilities and Limitations