Add an approval process to an existing flow, record not extended from Task

[Money]

I have an ask to modify a process that was built by a previous developer, using flows. I'm more of a workflow person, with decent knowledge of how the flows work in ServiceNow...

My 1st question:

I've added an approval action to the flow, but I am unable to add the related list that shows the approvers since the table isn't extended from Task... Is there a way to see the approvers so the designated folks can approve?

My 2nd question:

I'm editing an existing flow. I'm adding the approval logic but would like for the rest of the flow to either continue or end based on the approval. I have figured out how to "end flow" if rejected. But how would I group the rest of the flow under the if statement for, "this record has been approved"?

[Josh Pirozzi]

Hi @Money ,

For your first question: Are you routing the Approval Request to an individual or group? Either way, you shouldn't need to view the Related List. I'd recommend that you add a couple of 'If' statements below the Approval Request.

1. First will search for the parent record sysID that the Approval Request is associated to, and then verify if the Approval State is Approved. If yes, proceed with the remainder of the Flow.
2. Then, if the Approval is Approved,  there should be a 'Then' with a plus beneath it where you can nest the remainder of the flow.

Thanks,

Josh Pirozzi

[Money]

Thanks Josh!

Ultimately it is a group approval where I am requiring only one person to accept or reject. Since this post, I did add my if statements and figure out point number 2, thank you for answering. There were those 3 little dots to the left of the step number that I didn't see, which allowed me to move the rest of the steps 'under' my approval...

However, there is a requirement for the approvers to be able to navigate to the custom table (record which isn't extended from task), and see the approvers there. In addition, the approvers will be able to navigate to that approval record and approve. I was going to build a solution for it, but wanted to make sure I'm not building something that's already in place. I planned to simply create the relationship on the approvals table with our custom table, and populate the parent sys ID via the flow, once that approval record is generated.