(I suspect) It's so that Fusion doesn't have to download every single custom field to render it available to choose from, which prevents the problem that occurs when there are too many fields in the environment and fusion modules start timing out just trying to open them.

It was just a scheduled run, so it would check for any tasks with an operation ID but not an order ID every X minutes (I think it was 20? but I don't recall), no webhook required.

I have integrated with Wordbee in the past. What I did when I created the wordbee order was store the operation ID on the triggering object in an "Operation ID" field. Then I had another scenario that periodically looked for objects that had a "Operation ID" field but not an "Order ID" field, and th...

One problem that I was running into a lot was that you can only have one business rule for an object event type, i.e. you can only have one business rule for project updates, but I needed to be able to apply different rules for different situations.   What I did to handle this was to create a "Busin...

Yeah exactly, and you should be able to do a search for the iteration (ITRN) where $$TODAY is between the start date and the end date of the iteration.

If you're just trying to create a simple text file, create it as a "txt" extension. You can't create a "doc" file by mapping text strings into the body, doc files (and indeed all office files) are actually zip files in disguise.

I suspect you have a map wrong somewhere. It appears that the field you are trying to populate is "custom dropdown field value", not whatever field it actually is you're trying to populate.

Since it sounds like you're wanting to tie this to the end of a sprint, which is on a schedule, I would just setup your fusion scenario on the same type of schedule instead of using any type of automatic trigger.

HWAT

Exactly this Sven, yeah. Thanks for clarifying.