I have created a sub flow with inputs and outputs but the subflow icon is not available in the Elements menu. The flow fires after a record is saved, so my understanding is it should be able to fire subflows (unlike the before save fire). It is available if I create an Auto launched flow but that's not what I want. I also don't want to fire this from a process, as the sub flow needs to fire in a loop.
Does anyone know of any other reason subflows would not be available, or is this expected?
Unfortunately, the flow Loop element doesn't work that way. The correct method is to build a three-part loop, which has an initialization Assignment, a Decision branch to know when to stop, and an increment Assignment to increase the counter value.
As you can see, step 1 initializes Counter to 0, then we head into a decision where Counter is less than 3. If so, we enter the Loop branch, which does whatever logic you like, then adds 1 to Counter. This repeats until Counter equals 3, at which point it continues to the Continue branch.
The equivalent version of this in Apex Code would be:
for(Integer counter = 0; counter < 3; counter++) {
// Do logic here
}
Because you are using flow, it will respect user permissions. If you were to invoke a visual flow instead and use invokable APEX you could get around this and run in system mode using the without sharing keyword on the class.
But what I think is the best approach in this use case would be to use a visual flow and use a session based permission set that gets activated only for the step where the auto dispatch is supposed to fire. I prefer this approach because it further clarifies the intention of those implementing this solution --> the without sharing notation on the apex class could be there for many reasons and without any explanation.
Best Answer
There is a clear indication in the documentation what kind of core action are available in record trigged flow. Unfortunately, subflow element is not supported