@Antony6790 Yes, I am using the Fusion DevOps Trigger-Watch For Work Items. If I understand this function it triggers if changes are made to work items in Azure DevOps. You are asking about the Azure Dashboard, are you suggesting invoking an Azure DevOps api instance of the native Trigger-Watch Fo...
I am in the process of integrating Workfront Fusion to Azure Dev Ops. I've successfully created multiple scenarios to create and retrieve tasks but am having issues with the "Watch For Work Items" function. We need visibility of changes to the tasks in Azure DevOps on the fusion side. When I crea...
Hey Lars, after a bit of trial and error I was able to setup the suggested debug fields and added the custom form to a task. The debug fields picked up the Channel. It looks like the preview doesn't handle the {DE:Channel} for some reason and it only works when the form is attached to a task. Tha...
@lgaertner Thanks for the reply. I've tried changing the url from https://hook.app.workfrontfusion.com/xxxxxxxxxxxxxxxxxxxxxxxxxxxssssss?clientToken=999999&channel={Channel} to https://hook.app.workfrontfusion.com/xxxxxxxxxxxxxxxxxxxxxxxxxxxssssss?clientToken=999999&channel={DE:Channel} but it's st...
I have created a custom form with an external lookup to a fusion api. This works fine with hard coded Channel parameter, but I need to pass a radio button choice as a parameter and am unable to get this to work (via preview). The radio button has a label and name of "Channel" and has three choices ...
Hey Arun, We have actually seen the console version of this error but not recently. When it occurred it was for random users with no identifiable pattern. We were able to work around the issue be changing the call to the client to admin mode. Hope this helps. Cheers,] Ken
Hello Arun, That's the same error but rather than a console error it was a soap ui api call error. It turned out to be a simple pw issue, this wasn't spotted right away as we were focusing on the upgrade. Cheers, Ken