Has anyone been able to get this How to update user type attribute of an Asset objects using Automation after Import | Jira | Atlassian Documentation to work with a "schedule' trigger?
I have it working up to the web request, and it says it is running successfully. I have tested the URL in Postman and can see that it is pulling the Account ID for the users in the log.
I added an audit log step to show what the AAIDUser was pulling for {{webResponse.body.accountID}}, and it is blank.
I am guessing this is because my AQL query returns more than one email address and the web request isn't looping through each variable?
Any ideas on how I can use the schedule option vs the 'when created'??
Hi @Bekkah Crisp ,
I have implemented this solution once. But I used the "When object created" trigger, not the scheduled trigger.
If you use the scheduled trigger, I presume you loop over each found object, an perform a API call per user object.
Best regards,
Kris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bekkah Crisp ,
I have been testing with this a bit, but unfortunately I have also not been lucky getting an automation rule to loop over an "Lookup Objects" result, and perform a webrequest for each result.
It seems to work fine when you use the "Send Email" action instead of webrequest.
So i'm also curious to see if there is a solution for this. For now, I will stick to my "Object Created" trigger.
Best regards,
Kris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Kris,
I actually ended up getting it to work. For me, it ended up being an auth issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.