jnovajosky

@James Ainsworth

This issues appears to affect any logical expression that checks the Assigned Team.

We recently ran into an issue where tickets were being assigned to a specific team, then immediately assigned to a completely separate team. We followed the workflow and were able to pinpoint a specific decision node that was causing the problem. What was interesting is that the expression for this read as: “Hornbill Automations->Get Request Info->Assigned Team == TeamName AND Hornbill Automations->Get Request Info->Owner is not set”. So Hornbill should have picked up that the team was set to something else and the owner was set and followed the ‘No Match’ logic. However, for some reason… it decided to assign to the specified team anyway. I then updated the expression to read: “Hornbill Automations->Get Request Info->Assigned Team is not set” Since the process I was following manually set a Team earlier in the workflow I again expected this decision node to follow the “No Match” logic. It didn’t. It was not until I got hyper specific and set the expression to say: “Hornbill Automations->Get Request Info->Assigned Team != TeamName OR Hornbill Automations->Get Request Info->Assigned Team != TeamName OR Hornbill Automations->Get Request Info->Assigned Team != TeamName AND Hornbill Automations->Get Request Info->Assigned Team != TeamName” It was only at this point that the decision node correctly followed the ‘No Match’ logic pathway. We are now seeing this across the organization and even in some of our Auto Tasks.

This same error is appearing for Direct Outbound emails.

Hello, We were trying to deploy a custom solution of the Hornbill Teams Power Virtual Agent. We followed the instructions in the deployment powershell script and attempted to upload the completed app to Power Apps. However, we ran into an error stating that there was a missing XAML file. Could we get some assistance with this? Solution "Hornbill Power Virtual Agent" failed to import: Error while importing workflow {5ce3d382-8935-ec11-8c64-000d3a0ae61d} type ModernFlow name Search Users: Workflow import: Xaml file is missing from import zip file: FileName: /Workflows/SearchUsers-5CE3D382-8935-EC11-8C64-000D3A0AE61D.json

@Steve G Would it be possible to use the HornBill – Microsoft 365 integration via Power Automate to create a ticket and attach a file instead? - Example for clarification – User fills out a standard Microsoft Form which goes through a Power Automate Flow to create a formatted Word document. Said document is just added as an attachment to a new Hornbill Ticket rather than pulling specific portions of the Form into the ticket via HornBill API. In essence, what I am asking is whether there is a more simplistic method of integrating HornBill with Microsoft 365 utilizing our existing available tools? If this is not a possibility, can we setup a time to go over what the exact requirements would be and the methodology? That way we can always put in a request with leadership to purchase the required tools with a brief estimated cost-benefit analysis.