Looking for ideas

0

Hi Martin,

since we don't have a loop over item list yet, you could implement a loop in another way. Scroll down to the second post from the bottom. I'm looping over all attachments but this would also work for item lists.
https://community.webcon.com/forum/thread/699?messageid=699

There might be a problem though in regards to timeouts. You could change this so that every 3/4 items the loop is interrupted (leading to a different step) and continued using a timeout.

Best regards,
Daniel

Hi Daniel and thank you!

To be honest, I thought about a similar approach yesterday night before falling asleep. But then forgot about it in the morning. LOL :D

Now I don't need to scratch my head anymore. Very useful also the comment regarding time-outs. I wouldn't think of that, so thank you again.

Best regards,
Martin

Hi Martin,

you are welcome. :)

For any future readers I will rephrase the comment to make it more clear why the two "timeouts" are something completely different and may cause problems:

There might be a problem when the loop is executed multiple times. The more items there are the longer it will take and this may result in an error because the execution took to long. This might be even more likely if external systems like the Graph API are called. You could change the loop logic so that every 3 or 4 items the loop is interrupted it leads to a different step. Upon entry in this step a timeout action is triggered which will continue the loop in a minute.

Best regards,
Daniel

Hi!
What about a sub-workflow for each folder in the list? it's easy to store id's, and execute actions with api on paths. You can store the det_id in the corresponding element, so that you don't create it again when updating the list, using filter. It seems a bit easier to implement, and gives more possibilities i think :)

Hi Sebastian,

Yes, that could work as well. I will consider it. Thank you!

Br,
Martin