Steve G

Hi @Martyn Houghton, Examples of the required format: https://your.jira.url http://your.jira.url:8080 Thanks, Steve

Hi @Martyn Houghton, An error should be thrown when the integration node fails, which should give you a detailed description of what the failure was. Is this not happening, or have you got Continue On Error set to Yes (which would skip the error)? All new iBridge integrations now handle the trapping of failures much more gracefully, and have status and error output params as a minimum with relevant information output to help diagnose issue, but the Jira integrations were built before this process was implemented. We'll add those in when we get chance, I'll let you know once released. The endpoint URL should be in the format: https://your.jira.url I'll add that example to the wiki page. Cheers, Steve

Hi @Nbt, You need to HTTP PUT the file into that location, not POST. Regards, Steve

Hi @Nsherman, This is already possible if you're subscribed to Microsoft Forms Pro & Power Automate with premium connectors. The ability to populate form variables via URL parameters is a Forms Pro feature, and not available in the standard Forms, hence the Forms Pro subscription being required. I've found this video on YouTube which takes you though how to pass variables into Forms Pro forms via the URL parameters - this is how you would pass the request reference through, so that you can use it in the Power Automate API call back into Hornbill. And there's this forum comment that describes how to make API calls back into Hornbil via Power Automate (which used to be called Flow - but the nodes are the same ): The APIs you may need in Hornbill are as follows: Add a new post to the request timeline Update various request columns, including custom fields I hope this helps, Steve

Hi @HHH, I'm afraid we have no method to trigger the opening of an external URL via a BPM node. The closest you will be able to get to this would probably be creating a task in the workflow and assigning it to a user to process - that task could then have a URL within it which would allow the user to open the Jira ticket details page and action appropriately. Other options could be: Writing the URL to a timeline post against the request which would send the user a notification that it needs actioning; Storing the Jira ticket ID in a custom field and have a Custom Button defined to open the Jira ticket page. Cheers, Steve

@Izu, This additional logging has now been implemented, v1.17.1 can be downloaded from here: https://github.com/hornbill/goHornbillCleaner/releases/latest Regards, Steve

@Izu, Just an FYI, there are no service levels associated to forum posts: The issue you have reported is entirely a logging one - if you have provided RequestCatalogItems, then they will have been added to the filter. I'll add it to the list to get the tool logging updated to include this parameter, and will reply here once it hits the top. Regards, Steve

Just to close this off, and in case anyone sees this behaviour in future, the username required the domain specifying. Cheers, Steve

Hi @Berto2002, The error suggests that the account being used to authenticate the requests doesn't have sufficient permissions to retrieve lists of Teams. Note, the above integration has been deprecated and replaced by Microsoft > Teams > Channel > Send Message, which requires significantly less rights that the old integration. There are a number of ways that you can retrieve Teams Group & Channel IDs, the easiest is probably by clicking the ellipses next to a channel in Teams, then Get link to channel, and copying the Channel ID and Group ID straight out of the link that Microsoft provides. You could also use the Get-Team and Get-TeamChannel cmdlets from the Microsoft Teams Powershell Module. Hope this helps, Steve

Hi @AndyHill, This is likely due to the package being updated from the package library on your instance since Wednesday, and your SIS not being updated due to a bug that is now fixed. If you restart the SIS service on the machine running it, it will update to the latest version and your packages will then be able to be downloaded: Thanks, Steve

Hi @AndyHill, We've just released new versions of the Teams Integrations, which use their own keysafe key types and a minimal sets of rights rather than being bundled into the wider Microsoft key permissions: Hope this helps! Steve

@Rob Gething We've just released new versions of the Teams Integrations, which use their own keysafe key types and a minimal sets of rights rather than being bundled into the wider Microsoft key permissions: Hope this helps. Steve

Hi @Paul Alexander, Looks straightforward enough, I'll add it to the list and let you know once we've had chance to look at it. Cheers, Steve

Hi @Berto2002, I had a quick look and it was a 10 minute job, so I added a new operation to do what you need: The existing Post To Channel integration will now return the ID of the newly created message, and this ID can then be fed into the Message ID input of the new Reply To Channel Post integration, basic example: This message, and the reply, were both posted from this workflow: Hope this helps. Cheers, Steve

Hi @Berto2002, Re: via email, I'm not sure, but I expect something could be done with Power Automate and the Teams connector. The cloud automation that we have will only create new messages in a channel, and not reply to existing messages, but we will certainly be adding a new cloud automation to perform that action. Typical timeframes usually lrun to weeks rather than months, but depend on the teams workload & other priorities. Thanks, Steve

Hi @Berto2002, Thank you for your suggestion. I've added it to our list, we intend to extend the Teams integrations now that their APIs are out of beta, and will include an operation to perform action. Will let you know once we've built these. Cheers, Steve

@Izu, When you say KBs, do you mean the FAQ's that are against the Service that the Problem has been raised against? If that's the case, then no, they are not deleted. Thanks, Steve

Hi @Caroline, The utility now been updated to support these changes in the platform, and can be downloaded from Github. Cheers, Steve

Hi @Caroline, We'll take a look at this issue this afternoon and will let you know how we get on. Cheers, Steve

Hi @aykut.boyraz, The API call in that post will indeed return contact details for a given email address And thanks for commenting @Martyn Houghton, much appreciated Cheers, Steve

Hi @Ann-MarieHolloway, There isn't an alert currently, but I can see the value in having some alerting setup when imports fail. I'll add it to the list and will let you know once we've had chance to investigate possibilities. Thanks Steve

Hello eveyone, We've just released v1.1.0 of the Document Import Utility: Features Added support for setting an owner against imported documents Added caching of created and found tags, so fewer API calls are required into your Hornbill instance Fixed Issue where tags containing backslash characters could not be found This can be downloaded from Github, and is documented on the Hornbill Wiki.

Hello everyone, We've just released v1.2.0 of the Database Asset Relationship Import Utility. This release requires Service Manager build 2241 or above. Changes Updated tool to support move of Configuration Manager into Service Manager Added version check against Github repo Improved logging back to Hornbill instance This can be downloaded from Github, and is documented on the Hornbill Wiki.

Hello everyone, We've released v1.16.0 of the Database Asset Import Utility. This release requires Service Manager build 2241 or above. Features Added support for importing Software Asset Management records when creating or updating assets Improved logging, including: grouping log details per-asset; basic log details added to instance log Added version check against Github repo Changes Optimised import process, including the local caching of Hornbill asset records for each class & type Refactored code to remove duplicated & unnecessary code Rounded time taken output to the nearest second Fixes Removed a number of possible race conditions when using multiple workers This can be downloaded from Github, and is documented on the Hornbill Wiki.

Hi @Martyn Houghton, This has now been released, and requires the Service Manager update that was released last night: It's pretty basic in this release - it only supports deleting Contacts and Organisations whose IDs are provided. Additional filtering options will arrive in due course, but that will require some additional changes to the Core app. Cheers, Steve