Тёмный

One Flow or not to One Flow Per Object 

Salesforce Automation Hour
Подписаться 4 тыс.
Просмотров 1,7 тыс.
50% 1

Опубликовано:

 

14 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 2   
@confusedguyl100
@confusedguyl100 2 года назад
I don't think my current org is crazily complex, but we already have many automations on various objects. Having one flow per object, even just for when records of that object is updated is restrictive because it means if one sub-flow under the master flow fails, all other sub-flows will fail since they are in one transaction. I think restrictive entry criteria, Flow Order of Executive, Flow Explorer and Flow Orchestrator took care of the question One Flow or not to One Flow Per Object
@terrycole
@terrycole 2 года назад
Not!
Далее
Send Emails to Dynamic Recipient with Flow
36:26
Просмотров 8 тыс.
Salesforce Screen Flow
52:08
Просмотров 340
Cool Parenting Gadget Against Mosquitos! 🦟👶
00:21
How Many Flows Should You *Actually* Have Per Object?
14:42
Build Schedule Triggered Flows
1:00:39
Просмотров 608
Fundamentals of Salesforce Flow Formulas
1:03:42
Salesforce DevOps Center - Complete Setup and Demo
24:11
OAuth 2.0 and OpenID Connect (in plain English)
1:02:17
Open Q&A recorded on October 4, 2024
55:30