Hello, I need a workflow that iterates through identities from a source and sends an email for each account that each identity has (I have 6 identities in the source). I start with get list of identities, but that only sends 6 emails, and in each email, I see an array with the accounts, but I cannot iterate through them individually. I thought of a nested loop within the get list of identities loop, but identityNow doesn’t allow it.
Without HTTP methods.
Any ideas?
Thanks!
Hello and welcome Sergio
Can you please provide screen prints or pull the json value of your workflow? This will allow us to take a deeper dive into what you have and allow us to advise you on ways to achieve you end goal. Please be sure to remove any sensitive information.
Hi @smenendezp,
There are a few limitations for loops in ISC Workflows.
Could you share the workflow trigger currently in use?
Additionally, if you could share more details on the use case, we might be able to help come with a workaround.
Screenshots of the workflow would be greatly appreciated, thanks!
Thanks, @ksbagade and @mpotti . What we want is to take all the identities from a source and iterate over all the accounts of each identity to manage them. The “get list of identities” operator returns a list of identities, and the “get accounts” operator returns a list of accounts. The idea was to iterate over the list of identities using a loop and nest another loop to go through the account list of each identity, but we discovered that this option is not enabled. Sending the email was to verify that each iteration was done correctly.
So, we thought of another way to do it (although we don’t know if it’s possible.): get the list of identities and then use the “get accounts” operator with the following options:
We understand that this would pass the list of identities to “get accounts” and it would iterate over them, with a loop underneath the “get accounts” to iterate through the accounts and manage them.
Resolving this part would be enough, although the idea is to add a “compare strings” to pass the account status attribute and, based on this status, deactivate those accounts. That part works correctly, but only if we select a single identity. The idea is for it to do this for the entire list of identities.
Thanks!
Hello again, we finally managed to solve the problem by doing it this way:
We take the list of identities filtered by a specific source and iterate through them one by one using a loop. Inside the loop, we take each identity and check using a ‘compare strings’ if the ‘cloudLifecycleState’ attribute is in an ‘active’ state for each identity. If it is, we handle the deactivation of all accounts.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
