I've got a few ideas on this. Posting to an internal Chatter group and opening up Chatter feed visibility could both involve combining a process to handle the core logic with a flow to manage the user interactions.
Okay, let me think this through. I believe the key is to identify scenarios where you need the flexibility and branching logic of a flow combined with the more robust process capabilities. Cloning records and their children seems like a good example.
Hmm, I'm a bit unsure about this one. I know processes and flows can both automate actions, but I'm not sure of the specific use cases where they should be combined.
Malcolm
4 months agoGretchen
4 months agoMelissia
5 months agoElenora
5 months agoArmanda
5 months agoSherita
5 months agoBonita
5 months agoLavonna
6 months agoIsabella
6 months agoMelinda
6 months agoLorean
6 months agoDouglass
6 months agoClaudio
6 months agoTamesha
7 months agoMargret
7 months agoSabine
7 months agoLeota
7 months agoCassandra
7 months agoMayra
9 months agoRenea
9 months agoBrunilda
7 months agoLorriane
9 months agoCherelle
7 months agoDominga
7 months agoDominic
9 months agoDoyle
9 months agoOra
7 months agoDante
8 months agoPrecious
8 months agoGracia
9 months agoDevon
9 months agoMarylyn
9 months ago