Need help in the flow

[Aparna Gurav]

Hello Team,

I have created a flow to remove access requests for leavers. However, the current behavior creates multiple catalog tasks for the same catalog item. Ideally, I want only one task per catalog item to remove access. For example, if a user has 5 ServiceNow access requests and leaves the company, there should be just one task generated to remove all ServiceNow access.

Output:

[Dr Atul G- LNG]

Hi @Aparna Gurav 

Practically and via process, what is being done is correct. Let's understand the backend: if a user is leaving and has access to 40 portals, and then an agent needs to remove the user from these 40 portals, how will they remember which portal has been done and which are pending? From a process perspective, it’s better to keep separate tasks for each access removal. This way, you can track the actual effort an agent is putting in, and in the worst case, if there’s an issue with one access removal, you can hold that entire task or mark it as "closed complete" or "incomplete." So, don’t change this behavior.

[Ankur Bawiskar]

@Aparna Gurav 

did you identify the place from where those are getting created?

In screenshots I couldn't find those, seems it's at Step 7 or Step 8

Seems your logic is iterating based on number of applications the user has access to

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Aparna Gurav]

@Ankur Bawiskar : Catalog task created based on 7 no-step filters and 8 no-step for each loop, but I want one catalog task as per the catalog item

[Ankur Bawiskar]

@Aparna Gurav 

then don't iterate

Use only 1 Catalog task action and add details of the apps to be removed for that user in short description or work notes so that it becomes easier for the agent to work

If my response helped please mark it correct and close the thread so that it benefits future readers.