Jump to content

Steve G

Hornbill Developer
  • Posts

    745
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by Steve G

  1. Hi @Giuseppe Iannacone, I have a couple of ideas for this, will need some changes to the import tool though, leave it with me and I'll get back to you. Cheers, Steve
  2. What's New Cloud Automation Integration for ServiceNow. Update fields in any ServiceNow table record.
  3. What's New Cloud Automation Integration for ServiceNow Incident Tasks. Update field values within Incident Task records.
  4. What's New Cloud Automation Integrations for PagerDuty. Administer Users, create and process Incidents. See the Hornbill Wiki for more information.
  5. We've made some changes to a number of the Hornbill Open Integration Tools, to support a number of Hornbill platform changes that will happen once the automatic application update feature is released. If you run any of the following tools then can you please update to the latest version before automatic application udpates are enabled: Azure User Import Tool (goAzure2HUserImport) CSV Asset Import Tool (goCSVAssetImport) Database Contact Import Tool (goDb2HcontactImport) Database Asset Import Tool (goDBAssetImport) Database User Import Tool (goDb2HUserImport) Generic Request Import Tool (goHornbillRequestImport) LDAP User Import Tool (goLDAPUserImport) Organisation Import Tool (goHornbillOrgImport) ServiceNow Request Import Tool (goServiceNowRequestImporter) Snow License Manager Asset Import Tool (goSnowCloudAssetImport) Supportworks Requets Import Tool (goSWRequestImport) Note - the latest version of the above tools will work now, as well as when your instances take the updates they are to support. If you have any questions regarding these tools, please post to the Integration Connectors, API & Webhooks forum. Thanks, Steve
  6. Hi @Steven Cotterell, I can see your issue in those screenshots... You've set the Human Task (Start Change Implementation) to have a datetime field with an ID of h_custom_21, but then you're not writing that task answer into the Incident - then attempting to use the Custom 21 field from the request - which is not auto-populated... Think there may be some confusion here - when you define a field in a Progressive Capture form that matches a Request field, then this will be populated when the Request is logged - but tasks in workflows don't work like that. With tasks, you need to do "something" with the task outputs completion... So if you want the task answer to be used in the request, then it must be written to the request using a Requests > Update Request > Custom Fields node. If you just want to use that datetime value it in that stage of the BPM, then you can inject the Task field into the Get Local Time node directly as so: Cheers, Steve
  7. Hi @Steven Cotterell, This is possibly due to the manual datetime seed in the variable injection field... When setting the input to Manual, you should see the following inputs asking for year/month/date/hours/minutes: And only get the freetext field when using the variable injection button: I've tested with entering the manual datetime in the correct manner, and injecting a datetime variable, and both are working for me as expected. Cheers, Steve
  8. Hi @clampj, We've just released a new package for ITOM that enables integration with Rapid7 InsightVM. Details can be found here: Cheers, Steve
  9. We've just released a new package to the ITOM Package Library: Rapid7 InsightVM The package contains the following operations that can be performed against your InsightVM deployment: Start Scan Get Scan Details Get Asset Details Create Tag Add Asset Tag Remove Asset Tag Add Vulnerability Exception Remove Vulnerability Exception Update Vunerability Exception Status Add Asset Vunerability Validation Remove Asset Vunerability Validation The package is available to install from the Package Library now! If you have any questions, or suggestions of additional operations for this package, then please let us know here. Thanks, Steve
  10. We've just released an update to the Hyper-V package, which is available to install or update on your Hornbill instance now! The following are the new operations in this package: Set Memory Set Processor New VHD Get VHD Add VHD to VM New Network Adapter Move VM The operations are documented on the Hornbill Wiki. Thanks, Steve
  11. What's New ITOM Content Pack - New package for managing Rapid7 InsightVM deployments. See the Hornbill Wiki for more information. ITOM Content Pack - New automation operations within the Hyper-V package: Add Network Adapter, Add VHD to VM, Get VHD Details, Move VM, New VHD, Set Memory, Set Processor. See the Hornbill Wiki for more information.
  12. What's New Cloud Automation Integration for BeyondTrust Remote Support - Generate a new Remote Support Session. See the Hornbill Wiki form more information.
  13. Hi @TomW, The file can be retrieved from the API endpoint, with some extra path items: https://mdh-p01-api.hornbill.com/{yourInstanceId}/dav/reports/{reportId}/{reportFileLink} Replacing: {yourInstanceId} with the ID of your Hornbill instance; {reportId} with the ID of the Report; {reportFileLink} with the link to the file from the output of the call to reporting::reportRunGetStatus API. Note, you need to provide the API key in the request headers when retrieving the file, just as you would when making other API calls into Hornbill. Let me know how you get on. Cheers, Steve
  14. What's Changed Cloud Automation Integrations for ServiceNow. Populate additional field values when creating or updating Incidents, Problems and Change Requests on ServiceNow tickets.
  15. Hi @AndyGilly, Are there any error messages in your browser console when attempting to load that page? Thanks, Steve
  16. Hi @chrisnutt, You could always use the Service Manager Request Import Utility to do this It's a tool that we wrote that allows you to log requests in Service Manager from an external data source - which could be a CSV or Excel Spreadsheet via an ODBC connection. There are example configuration files in the release archives, and on the Github repository. Cheers, Steve
  17. Hi @AndyGilly, This would usually mean there are no managed assets in the list that you have selected against the node in the workflow: And the list: If you're adding users to a group using the node, you should only really select one target machine though, otherwise the job will be executed on each machine in the list. So the node should be configured as so: Cheers, Steve
  18. What's New Cloud Automation Integrations for ServiceNow. Add Comments and Work Notes to ServiceNow tickets.
  19. Thanks @samwoo @James Targett As @samwoo has mentioned, you can create Hornbill requests using MS Flow, there's a basic example here: And once you have your flow in place and working, you can schedule the execution of it using these instructions: https://docs.microsoft.com/en-us/power-automate/run-scheduled-tasks As well as using Flows, or the API Scheduler that Steve mentioned above, if you have Azure Automation the you could schedule a Runbook to log a request in Hornbill Service Manager. Example Runbooks are available in the Azure Automation Runbook Gallery, just search for Hornbill. Let me know if you need any more information. Cheers, Steve
  20. Hi @chriscorcoran, This is probably due to the Microsoft refresh token in your Keysafe Teams key expiring, so we're unable to generate a new access token with it... How this works is, when you first connect a Keysafe key to your Microsoft account, Microsoft give us 2 tokens for authentication of requests made against their API: The access token - we use this to authenticate the Hornbill to Microsoft API requests. This token has a 1 hour shelf-life before it expires - at which point we need to generate a new access token with the refresh token, for any subsequent API calls; The refresh token - this allows us (as in your Hornbill instance integrations) to create new access tokens once the access token expires. The refresh token lasts for 14 days. So if the access token and the refresh token have both expired, then you need to revoke and reconnect your Keysafe key to your Microsoft account. I did make some changes in the last update of this integration to better handle the refreshing of tokens, so you should only have to do this once - as long as the integration is called at least once every 14 days. Let me know how you get on. Cheers, Steve
  21. Hi @chriscorcoran, Managed to get to the bottom of the issue with the extra logging, and it's now fixed. Could you give it 10 mins for the update to hit your instance and try again, please? Let me know how you get on. Cheers, Steve
  22. What's Fixed Cloud Automation Integrations for Microsoft Teams. Fixed issue with error reporting.
  23. What's New Cloud Automation Integrations for RequestTracker. Tickets - Create, Update, Get and Add Comments to tickets. See the Hornbill Wiki for more information.
  24. Thanks @chriscorcoran, I'll review the logs and get back to you. I presume the re-run gave the same output? Steve
  25. Hi @chriscorcoran, I've not been able to replicate your issue, so I've added some enhanced logging to the Post to Channel operation to help with the debugging of thi issue. Could you give it 10 mins for the update to hit your instance, then try again and let me know once done so I can check the logs, please? Cheers, Steve
×
×
  • Create New...