Chris: that's big news.  Thanks v muchJason: definitely agree

Hi ChrisThanks for that.  How do you solve the asynchronous issue where the scenario that calls the other scenario's webhook won't wait for the called scenario to finish before it continues?  My understanding is that after you've called the other scenario's webhook, the current scenario will just ke...

Hi JasonAgreed.  We've asked Adobe for this also.  As well as the above, when scenario are getting large, having to repeat downstream paths is not great.  Referencing a sub-flow would be perfect but perhaps it would be difficult to make the subflows synchronous.

This should be basic behaviour. What's the point of providing a 'required field' feature when colleagues can either ignore it or not even be aware they need to complete these fields if they don't edit the form to fill them in? I'm rather dumbfounded that this isn't basic functionality.

WF has a significant gap in Document functionality. There is no way to assign a type when a document is being uploaded. You can create a field on a custom form and hope the user navigates to Custom forms, selects the correct form and then updates the correct field, but that is massively clumsy. W...

And the ability to add images too.

Right now, when an error or warning occurs on a Fusin scenario, everyone in the Fusion Team is notified. It would be extremely useful if we would select the role or team member to receive these notifications while suppressing them to all other roles/users. All team members don't need to see them s...

It seems not to be possible to display Document-specific custom forms on the Details screen of the document. Users have to navigate to the Custom Forms option on the left-hand nav bar and then select the form. Even then, it appears only on that section (Custom Forms). All other objects (can't pro...