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
2 months agoGretchen
3 months agoMelissia
3 months agoElenora
3 months agoArmanda
3 months agoSherita
3 months agoBonita
4 months agoLavonna
4 months agoIsabella
4 months agoMelinda
4 months agoLorean
4 months agoDouglass
5 months agoClaudio
5 months agoTamesha
5 months agoMargret
5 months agoSabine
5 months agoLeota
5 months agoCassandra
5 months agoMayra
7 months agoRenea
7 months agoBrunilda
5 months agoLorriane
7 months agoCherelle
5 months agoDominga
5 months agoDominic
7 months agoDoyle
7 months agoOra
5 months agoDante
7 months agoPrecious
7 months agoGracia
7 months agoDevon
7 months agoMarylyn
8 months ago