Hi Sean We find that if we add a new proof reviewer via fusion, it seems to add a new stage. In our case we remove members of a team and add the new reviewer - it's a reassign scenario - but it's adding a new stage for them. It's not what we want but it might be worth investigating. Stuart
Hi Kelly It's not something that I've come across. I would typically base my trigger on a field update or a document update. Would that work? All the best Stuart
Remember that if you want to leave the original on the issue, you can use a download doc module and then upload doc module onto the task, although always put docs at the project level.
Hello all. Does anyone know the syntax of the fulltext search in the Fusion execution history? I can search for an object ID by putting double quotes around it but nothing else seems to work. For example, searching for hyphenated words or multiple words doesn't return anything or just unconnected...
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.
Hi Manish, it'll be running twice for each of your two assignees. Try putting an array aggregator on, linking back to the object, presumably a task, the assignees are assigned to, so you have a single output bundle. Stuart
Hi Manish, it could be that and I recommend you tick that box to prevent self-generated events. However, it could also be running multiple times if you have more than one assignee. Check the number of bundles coming out of the upstream modules. All the best, Stuart