
Hi everyone,
I'm new to Salesforce and I am a Business Architect interested in no code/low code dev. I have a number of Workflows that I'd like to automate with Lightning Flow. They are in swimlane format, where each swimlane is a Role that is played in the Workflow. My use of the word Role here is different than the Salesforce Role associated with Users (more of an organizational position than role). In my world, a Role is a "hat" that a qualified and authorized Individual in the organization can wear. An individual can be authorized to play multiple Roles and a Role can have many authorized Individuals. If you are authorized to play a Role in a Workflow, then you can perform the activities in the swimlane designated for that Role.
When work moves from one swimlane to another, this is a handoff between Roles. There are generally 3 use cases for handoffs: 1) to a specific Individual; 2) to a Role at a specific company location (could be played by an Individual with a backup Individual); and, 3) to a Pool where Individuals in a certain Role can accept responsibility for the work that is "posted" to the Pool. There first 2 use cases are "push work" handoffs, the 3rd use case is a "pull work" handoff.
My question is -- how do I implement a multi-swimlane Workflow in Lightning Flow? Flow, from what I can tell, cannot allocate elements within a flow to Roles (as I've defined them above). My thought is that I need to have a separate Flow for each swimlane and somehow use Case Teams, Case Team Roles, and Queues to handle the handoffs. If that's the solution, I'm not sure how to dump work from a Flow into a Queue and alert the Role associated with the Queue that there's new work to be done.
My proposed approach doesn't seem to be a very elegant solution because I would then have to set up queues for every Individual, every Role at each location, and every Pool (my 3 use cases above). Is there a better way to do this? Thanks so much for your help.
Dale
For handoffs like you mention with internal roles that don't match Salesforce Roles, we use custom user lookup fields. It's a bit clunky, especially if you have more than, say, half a dozen different roles working on the same item, but it does help with reporting and historical tracking as well.