Hi all,
I'm building a declarative Flow Framework using Custom Metadata + Autolaunched Flows.
Here’s my setup:
- A Record-Triggered Flow (RTF_Contact_AfterSave) gets flow rules from a Custom Metadata Type (Flow_Rule_Management__mdt)
- It loops through those rules and calls a generic executor subflow (SBF_Contact_Executor)
- Each rule includes the name of the subflow to be executed (Subflow_Name__c)
My goal is to make the SBF_Contact_Executor dynamic and scalable, without hardcoding logic in a big Decision element. I want to avoid locking the Executor with too many branches, especially as we add more logic over time.
However, when I add a Subflow element, the Flow Builder does not show the option
“Let the flow name be selected at runtime”.
Is this dynamic subflow call feature generally available now?
Are there any requirements or limitations that could prevent the option from appearing?
Is there a native (no-package) way to avoid bloating the Executor with Decisions and still call subflows dynamically?
#Flownatics #Flow-Orchestration #Flow #Flows @Yumi Ibrahimzade @Daryl Moon @Guilherme Dornelas