Jump to content

Steve G

Hornbill Developer
  • Posts

    591
  • Joined

  • Last visited

  • Days Won

    22

Steve G last won the day on March 5

Steve G had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Hull, UK

Contact Methods

  • Website URL
    https://www.hornbill.com

Recent Profile Visitors

2,680 profile views

Steve G's Achievements

Experienced

Experienced (11/14)

  • Dedicated Rare
  • Very Popular Rare
  • First Post
  • Collaborator
  • Posting Machine Rare

Recent Badges

166

Reputation

  1. 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
  2. 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
  3. @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
  4. 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
  5. 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
  6. 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
  7. 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
  8. @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
  9. Hi @Caroline, The utility now been updated to support these changes in the platform, and can be downloaded from Github. Cheers, Steve
  10. Hi @Caroline, We'll take a look at this issue this afternoon and will let you know how we get on. Cheers, Steve
  11. 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
  12. 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
  13. 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.
  14. 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.
  15. 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.
×
×
  • Create New...