Ive been running into a problem creating a workflow to provide roles to a vendor. Once an identity is created, a form is sent to the listed manager asking them what roles the vendor needs. That form input is a select field that looks up roles with a specific naming convention for them to select. From this input im starting a loop with that form input as the loop input to query the API to find the role+ID and then get/manage access to add it to one of the vendors accounts
The issue im running into is the form input into loop part. I’ve tried the workflow without the loop requesting a single item, but when adding the loop the output is 400 bad request. The odd thing is that I added a send email step with the loop input just to see if my variables were getting messed up but its coming across fine. I think there may be something about the loop or loop input interaction that i am missing
The goal is to provide the ability to select multiple roles for a vendor to grant very granular access through our remote access system. My initial thoughts were
Onboarding form → select roles → Role API to get ID → loop through selected roles to get and add access to vendor account
Unsure without context that this points me in the right direction unfortunately. Our form is select roles tied to security groups for our PAM solution using select field and a search query configuration
This would pass to the Roles API to get the ID based on the selected items, then get access using that RoleID and manage access to provide it. I thought using a search query to get the role based on name would be the easiest route but it never comes out to a singular role based on name alone, maybe im just bad at search queries
I believe there might be an issue with the http request and using inline variables as i noticed a few posts but unsure if that ever got updated. Ive tried formating the variable, using the define variable to encode it, and a few other tweaks here and there. The call works in postman so i know its something with the HTTP request in workflows
Also possible the inline is working as the variable {{$.form.formData.privilegedAccess}}" gives this, but with brackets
EDIT
Seems there was just some buggyness with the steps as adding the define variable and recreating the steps seems to process the HTTP request, although adding a manage access step inside the loop breaks the HTTP request step? marking solved for now as this seems to be a different issue
